The challenge
Developing a mobile banking product requires multiple teams and systems to work together. In this engagement, I worked with an outsourced product development agency (Mooncascade), who was building a complex mobile banking product for a large UK bank. Our team was responsible for mapping business requirements, native mobile development and the backend-for-frontend layer, while the client's in-house teams owned backend systems, design, infrastructure and operational capabilities. The work involved evolving scope, technical dependencies and decisions that had to remain coordinated across organisational boundaries.
My role
I joined Mooncascade's delivery team as Product Lead, taking responsibility for mobile product requirements, engineering readiness, stakeholder coordination and product delivery. My role was to hold a clear view of the product and its dependencies, make sure the team had what it needed to execute, and keep stakeholders aligned as the work progressed.
What I led
A roadmap that admits what isn't decided
I introduced a transparent Now-Next-Later roadmap to communicate priorities, unresolved questions and dependencies without creating false certainty around work that was still being defined.
Engineering readiness
I worked closely with engineering to prepare requirements, clarify technical and product decisions, coordinate with designers and make sure upcoming work was genuinely ready for development.
Stakeholder alignment
I kept up regular communication with client stakeholders, surfaced risks and blockers early, and built strong working relationships with the client's delivery team. I also helped the engineering team prepare effective product demonstrations and communicate progress clearly.
The outcome
Mooncascade's mobile deliverables were ready when the wider product was ready. The engagement contributed to the delivery of the Bank's mobile banking applications and the transition toward its internal mobile development capability.
The project reflects a central part of my approach: keeping enough visibility across product, technology and delivery that a complex build moves coherently instead of drifting apart.
