Created one shared version of the product
I made sure the client and delivery team could see how mobile, web, USSD and external integrations fitted into the same product outcome.
Case study 05
Financial inclusion · Regulated implementation
My roleProject Manager
Delivering a regulated multi-platform financial product across borders.
A regulated financial-services product delivered across mobile, web, USSD and external integrations.
ClientKacha Digital Financial Services, Ethiopia
RoleProject Manager
EnvironmentRegulated financial-services delivery
OutcomeFinal UAT sign-off completed
The brief
01A regulated financial-services product delivered across mobile, web, USSD and external integrations.
The delivery challenge
02This was not one interface with one straightforward user journey.
The team had to coordinate Android and iOS delivery, a feature-rich administration portal, offline USSD access, secure external integrations and reliable performance. The greatest risk was fragmentation: individual components could appear complete while dependencies or the route to acceptance remained unresolved.
My delivery scope
03- Analysed client documents, requirements and needs
- Turned requirements into user stories and acceptance criteria
- Planned and ran the project kick-off
- Coordinated designers, developers, QA and technical leads
- Ran stand-ups, sprint reviews and retrospectives
- Tracked milestones, risks, dependencies and decisions
What I led
From intent to delivery.
The decisions and delivery moves that kept the work useful, aligned and accountable.
Turned requirements into testable work
I translated requirements into user stories and acceptance criteria that guided design, development and QA without losing sight of dependencies or the wider customer journey.
Kept the client close
Regular communication, demonstrations and product reviews reduced the risk of late surprises. Questions and trade-offs reached the client while there was still time to act.
Treated quality and acceptance as delivery
I coordinated the movement from internal QA to client acceptance, tracked issues and maintained ownership until the agreed work was signed off.
Product experience
A closer look at the digital experience delivered with the cross-functional team.
Evidence of delivery
What the work produced.
Confirmed programme, participation and product outcomes.
The product reached final UAT sign-off
Client requirements remained connected to execution and acceptance
The team worked from clearer, testable priorities
Leadership retained visibility of status, risk and unresolved issues
What this demonstrates
Financial-inclusion deliveryRequirements analysisCross-functional team coordinationClient and stakeholder managementQA and defect resolution
The lasting point
If the client sees the product for the first time during UAT, that is not UAT. That is a surprise party, and nobody enjoys it.
I helped different groups see the same product. That shared understanding made final acceptance a planned stage rather than an unexpected reckoning.