Chapter 4: Reference Models for Capability Design

A leader walks down the hallway from one faculty to another. One produces graduates employers fight to hire. The other holds an advisory committee meeting twice a year. Same institution, same strategy, radically different levels of capability maturity. He can see the gap. But he has no way to name it, measure it, or explain it in terms that survive a conversation. This chapter gives you that vocabulary: the Business Capability Model, the capability heat map, and the strategy-to-capability handoff that turns architectural insight into investment decisions.

What You'll Be Able To Do

By the end of this chapter, you'll be able to:

Navigate a capability hierarchy and identify the gap between what the strategy requires and what the organization can actually deliver.
Classify capability gaps by type (maturity, resource, or integration) and know the right response for each.
Verify that every strategic choice has a capability behind it, and every heavily invested capability is connected to a current strategic priority.

Introduction: The Walk Down the Hallway

In COR-BA-100, there is a moment that seems small but turns out to be pivotal. Marcus Chen walks down the hallway from Health Sciences to Business Programs. He notices something that everyone at Lakeshore knew informally but nobody had named formally: Tom Beaulieu's Health Sciences faculty had deep, embedded employer partnerships. Clinical placements were co-designed with hospital and healthcare employers. Curriculum was regularly updated based on employer feedback. Graduates were job-ready on day one because employers had been part of the design from day one.

Down the hall, Business Programs held an advisory committee meeting twice a year.

Same institution. Same strategy. Radically different levels of capability maturity. Marcus could see the gap. But he had no way to name it, measure it, or explain it in terms that would survive a conversation with someone who hadn't made the same walk. Three business professionals discussing capability mapping and process modeling in office hallway with documentation boards

This chapter gives Marcus the vocabulary he was missing. The Business Capability Model is a reference model that structures everything an organization must be able to do into a navigable hierarchy. It makes the gap between Health Sciences and Business Programs not just visible but nameable: "Engagement & Relationship Management" is an enabling capability in the HERM Business Capability Model. Health Sciences had it at high maturity. Business Programs had it at low maturity. The reference model doesn't create the gap. It makes the gap impossible to ignore, impossible to explain away as a personality difference between deans, and impossible to discuss without asking: "What are we going to do about it?"

Sign In to Access This Course

Create a free account to access Building the Common Language and start learning.