4. Capacity Outcomes¶
Purpose
Description of the competencies and capacities built at each organisational level upon completion of the 90-day roadmap.
1. Objective¶
Upon completion of the 90-day roadmap, the organisation has a demonstrably increased AI capability. This chapter describes which competencies and capacities are built at each level and how you determine whether the desired outcomes have been achieved.
2. Outcomes per Phase¶
Phase 1 — Focus, Direct & Rationalise (Day 1-30)¶
| Capacity Domain | Outcome |
|---|---|
| Strategic insight | The leadership team has one shared view of the AI portfolio: what is running, what is being stopped, what the 'Big Bets' are. |
| Cost awareness | A cost overview of current AI expenditure (licences, cloud, hours) is available. |
| Team composition | A core team (AI PM, Tech Lead, Guardian) has been designated and has agreed a working arrangement. |
| Use case selection | Maximum 2 use cases have been selected based on feasibility and impact. |
Phase 2 — Redesign & Pilot (Day 31-60)¶
| Capacity Domain | Outcome |
|---|---|
| Technical building | The team has brought a working prototype into the hands of real users. |
| Process insight | The team understands how AI changes the work process and has adapted the standard way of working. |
| Measurement skills | A baseline and a first effect measurement have been performed. |
| Risk awareness | The first Hard Boundaries have been defined and tested in the pilot. |
Phase 3 — Codify & Scale (Day 61-90)¶
| Capacity Domain | Outcome |
|---|---|
| Governance | An AI policy and a Guardian role have been formally established. |
| Knowledge retention | The approach is documented so that new team members can get up to speed. |
| Scale preparation | The technical architecture is ready for more users and more use cases. |
| Organisational learning | Lessons learned are recorded and available for future projects. |
3. Maturity Indicators¶
Use the indicators below to determine the level achieved after day 90:
| Indicator | Insufficient | Sufficient | Good |
|---|---|---|---|
| Number of use cases in production | 0 | 1 | 2+ |
| Cost overview available | No | Partial | Complete |
| Hard Boundaries defined | None | Draft | Formally established |
| Process change documented | No | Verbally | In writing in SOPs |
| Guardian appointed | No | Informal | Formal with mandate |
| First benefits measurable | No | Direction | Number with baseline |
Target level after 90 days: at least 'Sufficient' on all indicators.
4. Growth After Day 90¶
The 90-day roadmap builds the foundation. Afterwards, two growth paths are possible:
- Broadening: start more use cases in parallel, using the built-up templates and governance.
- Deepening: scale the pilot use case to a higher Collaboration Mode (e.g. from Mode 2 to Mode 4), or expand to more users.
Use the Three Tracks as a strategic compass for the choice after day 90.
5. Related Modules¶
- Quick Start: AI Project in 90 Days
- Organisation Profiles
- Three Tracks
- Lessons Learned
- Benefits Realisation — Operational
Next step: Determine your Organisation Profile for continued growth → See also: Accelerators