Roadmap
The work cut into phases, with effort and the risks we can already see.
- One page
- Phases
- Risks
How it works
For us a roadmap is not a timeline of bars nobody keeps to. It answers three questions.
What is the first version someone can use
Not the smallest imaginable one, but the smallest that helps somebody get through their day. The difference is large: a version with no use produces no feedback, only politeness.
What comes in which order
We cut along what builds on what, not along your departments. Whatever is technically the foundation for something else comes early, even when it looks unspectacular.
What can go wrong
We write down the risks we can already see — the interface with no documentation, the sign-off that depends on one person, the data model in the legacy system. Named risks can be planned for. Unnamed ones turn into delays nobody can be held to.
The result fits on one page. If it does not, we have not understood the project yet.
- A fixed date, if there is one — a trade show, a contract ending, the start of a season.
- The order in which the features matter to you. Not everything is equally important.
A one-page roadmap: phases, what is finished in each, rough effort, named risks.
If you skip this
Without a cut, everything gets built at once and everything is finished at once — which means late. And if you do not know what the first usable version is, you cannot show it to anyone while the budget is still there.
Questions about this step?
A conversation costs nothing and takes half an hour. Afterwards you will know whether we are a fit.