Business Agility Models

---

The Gap These Models Fill

The agile community has rich vocabulary for team-level practice: Scrum, Kanban, XP, Definition of Done. It has thinner vocabulary for what an agile organization requires — the funding cycles, governance structures, strategy processes, talent practices, and leadership behaviors that determine whether team-level agility can sustain itself.

Business agility models fill that gap. They are maps of the structural dimensions an organization must develop if its teams are to do anything more than perform agile at the standup level. The dominant models all share a similar premise: agility is an organizational capability, not a methodology.

The Business Agility Institute Domain Model

The Business Agility Institute's (BAI) model identifies eight domains across three categories:¹

Customer (the why)

• Customer-centric: the organization understands and serves customers deeply.
• Outcome-oriented: success is measured by impact, not activity.

Relationships (the who)

• Network of teams: small, autonomous teams connected by clear purpose.
• Leadership and culture: leaders who enable rather than direct.
• Individuals: people who can adapt, learn, and contribute outside narrow roles.

Operations (the how)

• Value creation: work flows from idea to value with minimal handoffs.
• Workforce: talent, learning, and HR practices that enable agility.
• Structure and governance: structures that distribute decisions, governance that supports speed.

The model is intentionally not a prescription. It maps the dimensions; the organization assesses where it stands and decides where to invest.

The AgilityHealth Enterprise Radar

AgilityHealth (see Radars) extends its team-level radar concept to the enterprise. The enterprise radar typically measures:

• Leadership agility.
• Strategic alignment.
• Customer focus.
• Lean portfolio management.
• Team agility (aggregated).
• Technical agility.
• Cultural agility.
• Talent and HR agility.

Like the team radar, the enterprise radar is a self-assessment that produces a spider-chart view of where the organization stands and where the imbalances live.²

Other Notable Models

• SAFe's Business Agility Value Stream describes seven competencies including organizational agility, lean portfolio management, and continuous learning culture.³
• McKinsey's Five Trademarks of Agile Organizations reframes the question in business-leadership language: shared purpose, networks of teams, rapid decision cycles, dynamic people model, next-generation technology.⁴
• Stephen Denning's Three Laws of Agile articulates the underlying principles: the Law of the Small Team, the Law of the Customer, and the Law of the Network.⁵

What the Models Have in Common

Despite different vocabularies, the models converge on a few recurring themes:

• Customer obsession. Agility starts with deep customer focus, not internal efficiency.
• Small teams in networks. Decisions distributed; teams autonomous but aligned.
• Funding by team, not by project. Persistent funding to teams; work pulled to capacity.
• Outcome over output. Success measured by impact, not by activity.
• Leadership as enablement. Leaders who serve and clear, not who direct and approve.
• Continuous learning culture. The organization treats its own practices as experiments.

If a model lacks any of these, it's probably not actually about business agility — it's about something narrower (Agile Release Trains, SAFe-style scaling, etc.).

How to Use These Models

• As a diagnostic. Score the organization across the model's dimensions. Lopsided scores reveal where investment is needed most.
• As a conversation framework. The model's vocabulary helps leadership discuss areas that don't yet have shared language.
• As an investment priority guide. Which dimension would produce the most leverage if developed? Often it's the one currently weakest.

How They Fail

• Model as checklist. Treating the dimensions as items to tick off rather than as capabilities to develop.
• Score inflation. Same failure mode as team radars. If leadership pressure produces optimism, the assessment is meaningless.
• Adopting the model without the practices. Naming a transformation "Business Agility" while continuing to fund annually, decide hierarchically, and measure output.
• Confusing model with destination. The model is a map. Filling in every dimension to "level 5" is not the goal; serving customers better is.

Coaching Tips

Pick one model and stick with it.

Switching between models produces vocabulary churn and abandons the shared map you were building.

Focus the weakest dimension.

Don't try to improve all eight. The weakest one limits everything downstream.

Start above the team.

Funding cycles and governance produce more leverage than coaching one more team in Scrum.

Honest assessments only.

Score-inflation kills the model. If leadership can't tolerate honest scores, fix the culture before running the assessment.

Translate to leadership vocabulary.

"Agile" terminology often alienates senior leaders. Use the model's business-shaped language — outcomes, customers, decisions.

Measure progress in customer terms.

The model's dimensions are means. The outcome to measure is customer impact, not the maturity score.

Summary

Business agility models exist because team-level agility hits a ceiling without organizational support. They provide structured language for the dimensions an enterprise must develop — funding, governance, leadership, talent, customer focus — to sustain agility above the team. The models differ in vocabulary; they converge in substance. Used as a diagnostic and conversation framework, they help leadership see what most needs investment. Used as a checklist or a destination, they become bureaucracy.

Back to Business Agility