← Back to Frameworks
OMI vs RADAR
Two frameworks. Two different questions. Use OMI when the conversation is about organizational agility. Use RADAR when the conversation is about why AI is stuck. Use both when you need the full picture.
| Axis | OMI | RADAR |
|---|---|---|
| Question it answers | Can our org metabolize change at all? | Where will our AI transformation fail? |
| Scope | Era-agnostic — cloud, mobile, AI, whatever's next | AI-transformation-specific |
| Time horizon | 10+ years — survives the AI hype cycle | 24-36 months — peak heat now |
| Primary audience | CEO, CHRO, COO, board | CIO, CTO, Chief AI Officer, CDO, transformation leads |
| Best use case | Strategic agility assessment, M&A cultural due-diligence, exec-team baseline | AI program autopsy, board AI-committee briefing, vendor / platform selection, agent governance review |
| Output | "You're a Transitional org, score 67/100" | "You're stuck in Pilot Purgatory because Rails is 23/100" |
| Position | The fortress — broad, durable thesis | The spear — sharp, topical, riding the AI wave |
Decision rule
If the conversation is 'are we agile enough to change?'
Use OMI
If the conversation is 'why is our AI stuck?'
Use RADAR
If the question is 'we're transforming for AI — are we set up for it?'
Both, in sequence: OMI sets the metabolic baseline; RADAR diagnoses the AI-specific failure mode.
Don't fold them into one. Distinct framings give you twice the surface area for influence.