A fragmented digital experience in a high-trust category
The client is a well-known pharmacy and wellness retailer operating in a category where customers expect accuracy, speed and reassurance. Their digital presence had grown piecemeal: the experience was inconsistent across desktop, mobile web and app, product discovery was difficult, checkout carried friction, and the Arabic (right-to-left) experience never matched the English one.
The brief was not a redesign. It was a transformation across several fronts at once — a rebuilt storefront, native mobile apps, and a brand-new custom loyalty platform — all bilingual, all consistent, and all delivered by a cross-functional team of designers, engineers and QA working in parallel.
A programme like that does not fail on any single discipline. It fails in the gaps between them: unclear ownership, drifting scope, decisions that stall, and a client who stops trusting the status. That gap was mine to own.
- One experience that broke across desktop, mobile web and app
- Product discovery that made medicines hard to find
- A friction-heavy checkout in a category built on trust
- An Arabic (RTL) experience that never matched the English one
- No first-party loyalty to reward and retain customers
My role: own the delivery, end to end
My remit was project and delivery management across the whole programme — not one discipline, but the thread that held all of them together. I was accountable for the plan, the people, the cadence and the client relationship, from kickoff to launch and handover.
Delivery ownership
a single integrated plan across UX, web, native apps and the loyalty platform, with clear milestones, dependencies and owners so nothing fell between workstreams.
Client communication
regular client calls, a steady reporting rhythm, and honest status on scope, risk and timeline, so the client always knew where things stood.
Getting work done from the team
coordinating designers, engineers and QA day to day, unblocking decisions, and keeping every workstream moving toward the same release.
Documentation
requirements, decisions, specs, acceptance criteria and handover notes kept current, so the work was traceable and the team never started from zero.
Process & governance
the full project-management toolkit: planning, stand-ups, sprint and release coordination, risk and change control, QA gates and sign-offs.
Launch & handover
sequencing the go-live across platforms and handing over a documented, maintainable platform the client’s team could run.
What the programme delivered
Scoped and sequenced as one roadmap, delivered as several coordinated workstreams.
UX & product design
A conversion-focused, trust-led pharmacy experience: simplified category navigation, clearer product detail pages, and a mobile-first journey, built on a scalable design system.
Web storefront
A rebuilt, headless-ready storefront delivering a consistent experience across desktop and mobile web, with a streamlined, lower-friction checkout.
Native mobile apps
Native iOS and Android apps sharing the same design language and commerce logic as the web — a genuine app experience, not a wrapped website.
Custom loyalty platform
A bespoke loyalty platform built and integrated across web and apps, giving the retailer a first-party way to reward and retain customers.
Bilingual, RTL-ready
A fully bilingual English and Arabic experience with right-to-left layouts and mirrored interaction patterns treated as first-class, not an afterthought.
Discovery & checkout UX
Smarter search and recommendations, clearer alternatives, guest checkout and trust signals throughout — reducing cognitive load at every step.
How I ran the delivery
A steady, documented path from alignment to launch — the same project-management process behind every programme I run.
Align
Set the goals, the scope and the success criteria with the client, and turn them into one roadmap with named owners across every workstream.
Plan
Break the programme into milestones and dependencies, sequence the design, engineering, app and loyalty work, and agree the delivery cadence.
Deliver
Run the day-to-day: coordinate the team, keep workstreams in sync, manage risk and change, and hold QA gates before anything is called done.
Communicate
Regular client calls and honest reporting on scope, risk and timeline — surfacing problems early, while they were still cheap to fix.
Validate
Test the experience with real users, feed the findings back into design and build, and remove friction before launch, not after.
Launch & hand over
Sequence the go-live across platforms, then hand over a documented, maintainable platform the client’s team could own.
The delivery stack
The process ran on a tight toolchain: YouTrack held the work and Microsoft Teams held the conversation, with design, code and QA plugged into the same flow.
Agile boards, sprints, issues, workflows and time tracking — the single source of truth for every workstream.
Daily stand-ups, per-workstream channels and the regular client calls and reviews.
Design, interactive prototypes and the usability testing that validated the experience.
Versioned code across web, apps and the loyalty platform, with controlled, repeatable releases.
Structured test cases, defect tracking and the sign-off gates before anything shipped.
One board, a defined workflow
Every piece of work — a design, a screen, an API, a loyalty rule — lived as a YouTrack issue and moved left to right through a single agreed workflow. Work-in-progress was capped so the team finished before it started more, and nothing reached Done without passing a QA gate against its acceptance criteria.
Progress you could see, not guess
Each sprint was tracked against a burndown straight from YouTrack. Velocity, scope changes and slippage showed up early as a line on a chart — not a surprise in a status meeting — and the same reports went to the client every week, so the conversation was about decisions, not “where are we?”.
The delivery rhythm
- Stand-up in Teams to clear blockers
- A live YouTrack board — no status chasing
- Planning, review and retro
- Scope and priorities agreed with the client
- A client call and a reporting update
- Risks, decisions and timeline in the open
- QA sign-off against acceptance criteria
- Release notes and a controlled go-live
The outcome
A multi-workstream programme delivered as one coherent platform — on a plan the client could see and trust the whole way.
One platform, every surface
A consistent, trust-led experience across desktop web, mobile web and native apps — no longer three disconnected journeys.
A loyalty platform of their own
A custom loyalty platform the retailer owns and controls, integrated across every channel.
A genuinely bilingual experience
English and Arabic treated as equals, with RTL layouts that finally matched the quality of the English UX.
Less friction, more confidence
Clearer discovery and a streamlined checkout that made buying in a high-trust category simpler and more reassuring.
A foundation that scales
A design system and headless-ready architecture built to carry future personalisation and AI-led discovery.
A delivery the client trusted
Clear ownership, steady communication and documentation that kept a complex, multi-team programme predictable from kickoff to handover.
Client identity withheld by agreement. This write-up describes my role, process and the work delivered; no confidential figures are shared.