Use cases
When to bring ZOYA in
Fourteen situations where an independent measurement of architecture-related cost and schedule exposure changes the decision. You do not need to know which service you need before speaking with us.
Timing
Most of these arrive on a calendar. The earlier in that calendar we start, the tighter the answer.
A board or planning review is coming and the architecture spend has to be defended
A milestone has moved twice and another replan is being drafted
Before roadmap or deal commitments are made on a system nobody has measured
And nobody can price the risk it would actually retire
Earlier is better. The range narrows with the evidence available.
The fourteen situations
Understand the exposure
- A programme, integration plan or major release keeps moving
- You are inheriting, acquiring, consolidating or handing over a system
- A proposed change touches more teams and components than expected
- Leadership wants an independent view of architecture-related cost and schedule risk
- Subsystem teams report green while the end-to-end milestone slips
Make the decision
- Choose what to refactor, replace, isolate, defer or accept
- Defend an engineering or modernisation budget at a review
- Test an internal estimate, a vendor proposal or an investment case
- Compare competing architecture, platform or integration options
- Decide where limited engineering capacity retires the most exposure
Create a defensible path
- Establish which evidence can support the decision
- Identify the assumptions driving the uncertainty
- Map the dependencies carrying the greatest exposure
- Set a baseline that can be measured again later
Three common starting points
| The situation | What is missing | What the assessment changes |
|---|---|---|
| Programme recovery | A milestone has moved twice and every team reports healthy | The work that moved it is located and priced before the next replan adds more contingency |
| Acquisition or inherited system | Nobody has measured what the structure costs to change | A baseline exists before roadmap commitments are made |
| Modernisation business case | The risk a refactor would retire has never been priced | The proposal carries a number a planning review can test |
Who normally commissions it
Leaders accountable for technical risk, delivery commitments or investment decisions, across engineering, architecture, programme leadership, finance, corporate development and assurance.
What the assessment contains See a complete sample deliverable
Request a 30-minute scoping call
No preparation required · The call is free · Zak normally replies within one business day