01 · Challenge

High record volume, multiple statuses, one controlled destination.

The branch needed to locate, review and prepare inheritance-related records for centralization while normal customer operations continued. The risk was not simply volume: incomplete files and unclear exceptions could slow the transfer or create rework.

02 · The work

Turn the initiative into an executable branch workflow.

I worked within a three-person branch team to inventory files, validate document status, organize follow-up, and route exceptions. The operating focus was traceability: know what had been checked, what was missing, who needed to act, and what was ready to move.

• Structured the review around clear file status and next action.
• Coordinated follow-up on incomplete or exception records.
• Maintained pace without relaxing documentation controls.
• Supported branch-level completion within the wider Head Office initiative.

03 · Result

More than 1,000 records moved through the branch workflow in about two months.

The work demonstrates practical project coordination inside a regulated environment: organizing a finite body of work, maintaining status visibility, resolving dependencies, and completing a controlled handoff.

01 · Challenge

New digital services only create value when customers can actually use them.

Customers arrived with different devices, confidence levels and transaction needs. Repeated setup questions could consume branch time, while unclear guidance made adoption harder than it needed to be.

02 · The work

Translate product steps into customer-ready support.

I guided customers through registration, activation and common transactions; identified recurring points of friction; and shared usable input with the relevant teams. The emphasis was implementation at the point of use.

• Supported onboarding for Al Ahly Net and later NBE Mobile.
• Tested features, identified bugs and reported recurring friction.
• Trained employees and adjusted explanations to the user’s actual need and level of comfort.
• Escalated issues and feedback that required action beyond the branch.

03 · Result

More than 1,000 customers supported across the two services.

The work shows adoption support as an operating discipline: listen at the front line, make the next step clear, document patterns, and keep feedback moving to the right owner.

04 · Public evidence

A concise set of published service references, clearly separated from contribution claims.

Public product references are included only to establish service context. No customer data is shown, and no authorship or ownership of the interfaces is claimed.

01 · Challenge

Process change is not complete when the org chart changes.

Each stage altered where work happened, who owned the next action, what the customer needed to provide, and how exceptions returned to the branch. Staff needed to understand the new path while continuing to serve customers accurately.

02 · Evolution

Four stages, each changing the operating constraint.

• Manual: branch staff carried more of the end-to-end handling and follow-up.
• Centralized: work moved into a shared operating path, making status visibility and handoffs more important.
• Department-owned: dedicated ownership clarified responsibility while raising the need for complete intake.
• Digital self-service: eligible customers could complete more of the workflow digitally, while the branch continued to support adoption and exceptions.

03 · Contribution

Keep the changed workflow understandable at the point of service.

I supported customers and colleagues through the evolving process, clarified requirements, maintained documentation quality, and routed issues to the correct owner. That contribution sits between process analysis, change support and customer operations.

01 · Challenge

Build a usable commerce operation without adding avoidable inventory handling.

The team needed a credible catalog and purchase path while coordinating product data, four suppliers, payment, customer communication and fulfillment. A traditional receive-and-reship model would add time and handling.

02 · The work

Connect the storefront to the operating reality behind it.

I contributed to the WordPress and WooCommerce build, product and supplier coordination, order tracking, customer follow-up, and day-to-day operating decisions. The system had to support the work after the order button was pressed.

• Structured product information and catalog categories.
• Coordinated supplier availability and order status.
• Tracked more than 200 orders across the shared team workflow.
• Used Excel and the commerce platform to keep operating information organized.

03 · Project evidence

Current public storefront artifacts from the project.

These are public project artifacts. Results are presented as shared team outcomes; the case does not claim sole design, engineering or business ownership.

04 · Fulfillment redesign

Route eligible orders from supplier to customer.

The team established a direct supplier-to-customer path when practical. That removed an unnecessary intermediate handling step while preserving the need for clear order ownership, supplier coordination and customer communication.

01 · Challenge

Help customers start without pretending the website can finalize the order.

The client needed a clear path for people arriving with finished artwork, rough ideas, different garments and uncertain print methods. Public pricing, uploads, payment and fulfillment details were not verified for self-service, so the interface needed to support exploration while keeping the final quote and production decisions with the business.

02 · The work

Turn a collection of pages into one understandable customer journey.

I designed and implemented improvements across the public website, including the visual system, responsive navigation, clearer service routes, the interactive Design Studio and the quote journey. I also handled browser QA, accessibility refinements and launch coordination for the web experience.

• Created separate entry paths for customers with artwork and customers who need design help.
• Built a browser-based garment, color and text preview that stores nothing and collects no payment.
• Connected Studio selections to the quote request instead of making customers repeat known details.
• Kept unverified pricing, turnaround, upload and fulfillment claims out of the public flow.

03 · Project evidence

Current public client-site artifacts.

These screenshots show the live public website and contain no customer data. They document the client-facing web work, not ownership of Custom Station ATL or its printing operations.

04 · Quote handoff

Carry useful context forward, then stop at the right boundary.

The Design Studio transfers garment, color, print side, quantity and method selections into a structured request. The website makes clear that the preview is approximate and that final pricing, garment availability, artwork, timing and fulfillment are confirmed directly before production.