00
Understand the requirements
Map stakeholders, competitors and constraints
What ecosystem does the project sit in? What do the stakeholders actually need? Who else is in the market? We settle all of that at the start, in a kick-off workshop.
01
Analyse the status quo
Weigh up technology, architecture and strategy
We look at where the project stands and assess the existing technology, architecture and strategy, so we can agree the KPIs early and use what you already have.
02
Build in the open
A working demo every two weeks
There is a running demo every two weeks. Alongside the development itself, the aim is to test with users, stakeholders and regulators on that same rhythm and collect feedback. The cadence can be set to whatever the project needs.
03
Extend
From MVP to finished product
Where the project allows it, I would rather launch early and extend continuously against feedback and new requirements. On greenfield projects that is what produces early results, and early revenue.
04
Measure and reflect
Including after hypercare
With every major release at minimum, we evaluate the results, draw conclusions and adjust the strategy where it needs adjusting. I like to use GDPR-compliant analytics alongside qualitative feedback rounds with stakeholders and users.
05
Scale
From go-to-market to expansion
Once the product has proved itself, I support vertical and lateral expansion into new markets, and the scaling of both infrastructure and new features, so growth can continue.