Most teams are bolting AI onto a traditional operating model. Very few are redesigning the model itself. Work through five steps to find out which one you're doing — and what's actually slowing you down.
Tap every stage your team spends real time in, between an idea showing up and it shipping. The pattern that emerges is your current operating model — whether anyone designed it that way or not.
Bottlenecks usually sound like one of these four complaints. Pick the one you hear most often — in standups, in retros, in your own head at 11pm.
1 = never true of us. 5 = this is just how we operate. Be honest — the score only means something if the inputs do.
Five components, two snapshots. Fill in how the team actually runs today, then sketch what you want to be true instead.
| Component | Current state |
|---|---|
| Inputs | |
| Decisions | |
| Execution | |
| Validation | |
| Learning |
| Component | Future state |
|---|---|
| Inputs | |
| Decisions | |
| Execution | |
| Validation | |
| Learning |
The four moves that turn a diagnosis into a plan. One concrete commitment per box beats four vague ones.
Complete Step 3 to generate your archetype and summary.
Not yet identified — select one in Step 2.
Not yet mapped — tap stages in Step 1.
Everyone who's completed the diagnostic, newest first. Your own entry is highlighted.