Skip to main content

Business Architecture Glossary

A comprehensive reference of business architecture terms and concepts. Click on any term in your courses to see its definition.

A

Abstraction
Simplification for a purpose: keeping the detail that matters to the question being asked and filtering out the rest, so something too complex to reason about becomes manageable. It is how a model is made, and the purpose sets the level of detail: a board needs less than a project team.
Accuracy Trap
The architect's tendency to optimise presentations for completeness and precision at the expense of audience understanding, producing work that is technically correct and practically ineffective.
Acknowledge, Reframe, and Advance
A three-step response to resistance: name the concern explicitly without dismissing it, translate the architecture work into the resister's terms, and propose a small next step that reduces the perceived risk of engagement.
Adaptive Capacity
An organisation's ability to absorb disruption and come out stronger, because its purpose, strategy, capabilities and operations stay connected and it gets better at adapting with each cycle.
Annotation for Non-Architects
Labels and explanations added to visuals so that a reader without architecture training can extract the key finding without the architect present to explain it.
Application Reference Model (ARM)
The solution-side counterpart of the Business Reference Model: a map of the application capabilities an organisation in a sector needs, in three levels (application domains, application capabilities and application components). The business architect reads it to see where systems cover the capabilities that matter, where they overlap, and where nothing exists.
Architecture Narrative Arc
A four-part structure for effective architecture communication: Tension (the problem the audience already feels), Reframe (what the architecture reveals about it), Evidence (the data that supports the reframe), and Action (the next step that follows logically).
Architecture Review
The leadership's quarterly governance conversation about architecture evidence, owned by its chair and facilitated by the architect. The Four Ares structure the agenda, one question gets the deep dive each quarter, and each review is tied to a live decision.
Architecture Value Proposition
What architecture is worth, stated in organisational outcome language for each audience. It changes as a practice matures: it helps us see (early), it helps us decide (growth), it is how we govern (mature).
Architecture-Grounded Business Case
A business case that adds three kinds of architecture evidence to the financial case: the capability gap and its consequences, the dependency chain (what else is put at risk if this initiative is deferred) and the cost of waiting.
Architecture-to-Solution Gap
The disconnect that opens between what the architecture intended and what gets built when solution teams operate without the architecture in the room, even when blueprints exist, intentions are good, and every individual decision appears reasonable.
Audience-First Thinking
The discipline of reversing the default communication sequence: start with what the audience needs to decide and work backward to what evidence and framing will reach them, rather than leading with what the architecture produced.
Authentic Purpose
An organisation's real answer to "Why do we exist beyond making money?", specific enough to guide choices and trade-offs. Unlike a mission statement on the wall, it can be used to say no.

B

Benefits Tracking
Measuring whether delivered change is producing its intended outcomes, in six steps: define the benefits map (which outputs should produce which outcomes), identify leading and lagging indicators, establish baselines, assign ownership and a reporting cadence, design the intervention protocol, and name who answers for each benefit after the program closes, written to the seat rather than the person so the claim survives a change of executive.
Bootstrapping Challenge
The chicken-and-egg problem of adoption: a reference model needs users to prove it useful, and users won't take part until it is useful, so someone has to found it deliberately rather than wait for contributions.
Build, Buy, or Partner
Peak capabilities should almost always be built and owned; plateau capabilities can use proven external solutions; valley capabilities should be standardised, outsourced or partnered. The choice follows from the capability's tier.
Building a Coalition
Find the frustrated leaders who already feel the pain of misalignment, start with allies rather than skeptics, and distribute the practice across the organization so it outlives any single champion.
Business Architect as Facilitator
Not a commander: a systems thinker who creates conditions for coherent decisions by making alignment visible, brokering difficult conversations, and holding space for discomfort.
Business Architecture
The management discipline that connects an organisation's purpose to its strategy, capabilities and operations, and keeps those connections working as conditions change. It is not IT architecture, process mapping or strategic planning.
Business Architecture as a Strategic Discipline
Business Architecture is not IT architecture, not process mapping, not strategic planning. It is a management discipline dedicated to connecting purpose through strategy through capabilities to operations.
Business Model Canvas (BMC)
Alexander Osterwalder's one-page model of how an organisation creates, delivers and captures value, in nine connected building blocks.
Business Model Canvas as Testable Hypotheses
A one-page visual of how the organization creates, delivers, and captures value, treated not as a static plan but as a set of assumptions to be tested and evolved.
Business Model Scenario Modelling
Tracing, on the Canvas, the cascade of consequences when one building block changes, to test whether a proposed shift produces a consistent new business model before anyone commits to it.
Business Model Vulnerability
A structural weakness in a business model that the Canvas makes visible and financial reports don't, such as dependence on one customer segment or revenue stream: the shape of the problem, not just its financial symptom.
Business Reference Model (BRM)
The HERM's capability model: everything a higher education institution must be able to do, organised into two core value chains (Learning & Teaching, Research) and eleven groups of enabling capabilities. Its business capability model is the backbone the other HERM artifacts connect to.
Business Use Case
The business architect's handoff artifact: a description, in business terms, of the activity a solution must support and why it matters. Its four elements are the capability context, the business activity, the stakeholder needs and the success criteria. It isn't a system specification.
Business Value and Technical Quality Matrix
A two-by-two that plots current systems by business value (how well each serves the capabilities the architecture prioritised) against technical quality (how healthy it is). Its four quadrants are invest and extend, the urgent risk, the comfortable distraction, and retire. The business architect supplies the business value axis.
Business-Level Evaluation
The business architect's comparison of solution options against the architecture, alongside the technical and financial comparisons. It assesses each option for capability gap coverage, strategic alignment trajectory, value stream impact and risk to strategic intent, and frames the trade-offs for the people who decide.

C

Capability
What an organisation must be able to do, described independently of who does it or how. People, process, technology and information are what make it real; investing in one without the others doesn't create the capability.
Capability Filter
The question the business architect asks of every digital or AI proposal: does this serve a capability gap the architecture identified? If it does, evaluate it. If it doesn't, it is a solution looking for a problem.
Capability Gaps
The three ways a capability falls short of what the strategy requires: a maturity gap (it exists but isn't good enough), a resource gap (an element is missing) and an integration gap (the elements don't connect). Each needs a different response.
Capability Heat Map
A view that plots each capability's required maturity (derived from the strategy) against its current maturity on the same scale, so gaps and over-investment show at a glance.
Capability Map
Develop's key model: the organisation's inventory of what it must be able to do, grouped into a handful of areas and drawn independently of the org chart. Heat maps and value streams are views on it.
Capability Plateaus
The stable, usable levels of capability an organisation reaches on the way from its baseline to the target, one for each phase of delivery (Baseline, Plateau 1, Plateau 2, Target). They give the portfolio something concrete to fund and a measure of progress in capability terms. Not the plateau tier of Peak, Plateau and Valley.
Chasm of Miscommunication
The gap that opens when the same words mean different things in different parts of an organisation: agreement that looks real in the meeting and dissolves once execution begins.
Communication Failure vs. Architecture Failure
The distinction between work that is architecturally sound but fails to influence and work that is architecturally flawed; diagnosing which failure occurred determines whether the fix is better analysis or better communication.
Communication Rhythm
A planned cadence of architecture communication events aligned to governance cycles, ensuring that findings arrive when decisions are being made rather than between them.
Communication Tool vs. Architecture Artifact
An architecture artifact is designed for diagnosis by architects; a communication tool is designed for a specific audience to engage with and act on. The same data needs different visual treatment for each.
Community of Practice
A cross-functional group of people who use the method in their own work and meet to share it, so the practice spreads and outlives any single champion.
Conceptual Integrity
The quality an organisation achieves when its key terms are defined consistently across functions, levels, and initiatives, so every handoff carries shared meaning rather than requiring translation.
Consulting vs. Instantiating
The two ways to use a reference model. Consulting uses it as a diagnostic lens or conversation tool without adopting it: fast, cheap and immediately useful. Instantiating adapts it into the organisation's own version, renaming, adding and excluding elements while keeping the reference structure. Consult first; instantiate when consulting has proved useful.
Continuous Design Mindset
Treating strategy and design as a continuous cycle (Discover, Define, Develop, Deliver) rather than a linear plan, execute and review, so the aim becomes adaptive capacity rather than a perfect plan.
Cost of Inaction
A concrete statement of what the organisation loses by not acting. It makes the status quo visible as a choice with consequences rather than the safe default.
Crisis Enthusiasm vs. Organisational Commitment
The distinction between the energy architecture work generates during a crisis (intense but temporary) and the sustained organisational commitment needed to keep architecture visible and used after the crisis resolves.
Cycle Triggers
The signals that call for a new Design4 cycle rather than a correction within the current one: external shifts (disruption, regulation, competition), internal signals (performance, capability gaps, strategic drift) and the evidence reviewed in the standing governance calendar.

D

Decision Brief
A short document, three pages or fewer, written to get a specific decision. It has five parts in order (the decision, the evidence, the options, the recommendation and the cost of inaction), so the reader reaches the recommendation on page one.
Define-to-Develop Handoff
The Cascade's "Capabilities Required" becomes the direct input for capability mapping, ensuring every capability investment traces back to a strategic choice and every strategic choice is supported by identifiable capabilities.
Deliver-to-Discover Feedback Loop
Evidence flowing from Deliver back into Discover: the results services produce, and whether stakeholders are actually better off because of them. It's where outcomes are confirmed, and where shifts in stakeholder needs show up before they become crises.
Dependency Map
A picture of how a set of change initiatives depend on each other, showing which must come first. It distinguishes hard dependencies (one can't function without another), soft dependencies (one delivers more value once another is in place) and shared resource dependencies (two compete for the same capacity).
Design Problem
Relates to how something is conceived or planned : the choices made before or during creation that lead to poor outcomes. The flaw is in the logic, intent, or architecture of the plan itself.
Design-Driven Requirements
Requirements derived from the architecture's own models rather than gathered from scratch. The capability heat map gives the business requirement, the recipe card the stakeholder requirements, and the value stream shows where the solution must create integration, so every requirement traces back to the model that generated it.
Design4 Flywheel
The way each turn of the Design4 cycle builds on the last: what an organisation learns and builds in one cycle carries into the next, so momentum grows instead of resetting to zero.
Design4 Framework
Four connected phases, Discover, Define, Develop and Deliver, that run as a continuous cycle: when one moves, it drives the others, and Deliver feeds back into Discover.
Differentiating vs. Commodity Capabilities
A classification of capability gaps by strategic role, made before solution options are compared. A differentiating capability sets the organisation apart and justifies a solution that fits it precisely. A commodity capability must be performed to the sector's standard and favours a proven, standard solution. In Peak, Plateau and Valley terms, a differentiating capability is a peak and a commodity a plateau.
Discovery Synthesis
The four artifacts a completed Discover phase hands to strategy: a tested purpose statement, the Stakeholder Value Map, the Outcome Model and the environmental scan. Every choice in Define should trace back to it.
Double Diamond
A design-process model developed by the UK Design Council (2005) with four phases: Discover, Define, Develop, Deliver. It operates at product and service level: it designs the thing. This is a different level of work from Design4, which operates at organisational level and designs the organisation that decides, funds, and delivers those things. The shared phase names are a coincidence, not a lineage. See the FAQ on the Design4 Framework page for a full disambiguation.

E

Editing Discipline
Revising an architecture document until every sentence earns its place: translating jargon, separating real uncertainty from habitual hedging, rewriting passive sentences and checking that the first page carries the recommendation. Brevity is more meaning per word, not fewer words.
Effectiveness Before Efficiency
Doing things right is secondary to doing the right things; an operation that processes fast but leaves stakeholders confused is efficiently failing.
Entry Point
The Design4 phase where an organisation starts, chosen by its most pressing gap: Discover for purpose confusion, Define for strategic drift, Develop for execution failure and Deliver for services that don't produce the results they should. If the purpose itself is contested, start with Discover.
Environmental Scan
A structured assessment of the external forces acting on an organisation, usually across six STEEPL dimensions (social, technological, economic, environmental, political, legal), that separates what it can influence from what it must adapt to.
Erosion Dashboard
A table, updated monthly, that sets each capability gap's planned coverage against its coverage in the current scope, so cumulative scope erosion is visible before it becomes permanent.
Evidence Chain
A sequence of findings where each builds on the last and the sequence leads to a specific conclusion, as opposed to an evidence inventory that accumulates findings without establishing a direction.

F

Failure Modes of Shared Vocabulary
Three ways a shared vocabulary fails while looking healthy: false alignment (the same terms, different meanings), category blindness (the model's categories limit what the organisation can see) and governance capture (the model becomes a political instrument for whoever controls it).
First Cycle
A small, fast first pass through the Design4 cycle, about 90 days, that delivers one visible, measurable change before anyone is asked to adopt the approach.
Fitness for Purpose vs. Fitness for Fashion
The test for any new technology: does it serve the design, or the brochure? An option is judged by whether it closes the capability gap, not by how new or impressive it is.
Five Architectural Strategies
Five ways of managing complexity that reference models use: Abstraction (the right level of detail for the audience), Generalisation (recurring patterns), Views (perspectives for different stakeholders), Layering (separate domains such as business and data) and Partitioning (navigable pieces).
Five Categories of Digital Solutions
Automation, augmentation, decision support, prediction and generation: five kinds of digital and AI solution, grouped by what they do rather than by the technology. Naming the category helps the business architect ask which kind of help the capability gap actually needs.
Five Challenge Questions
Five questions to ask of any current state assessment: Where is the business value dimension? What is load-bearing? What is nobody using? What does not exist? Where is the data? They look for blind spots, not errors.
Five-Element Session Design
The structure for a facilitated architecture conversation: the question the session answers, the artifact that anchors the evidence, the participants, the activity sequence (opening, exploration, convergence, close) and the output, a record the participants validate.
Five-Question AI Assessment
Five business questions for any AI proposal. What capability gap does it address? What happens when the model is wrong? What data does it need, and do we have it? What would the organisation need to manage that it doesn't manage today? Would a well-designed human process close the gap anyway?
Four Communication Registers
The four levels at which people process information and make decisions: strategic (direction and investment), operational (how things work and change), technical (systems and data), and political (power, reputation, and position risk).
Four Data Governance Questions
Four questions to ask of any proposal that depends on data. Who owns this data? What happens when systems disagree? Where does data quality undermine capability? Is the data we need available, governed and integrated?
Four Downstream Roles
The four roles a business architect works with once delivery begins, each with its own productive tension with the architecture: the solution architect (scope), the portfolio manager (timing), the program manager (scope against schedule) and operational leaders (pace).
Four Fitness Criteria
Four tests of whether a reference model suits an organisation: Scope (does it cover the right territory?), Language (can its vocabulary be adopted or translated?), Strategic Alignment (does its emphasis match the strategic priorities?) and Connectivity (does it connect to the models already in use?).
Four Stall Patterns
Four ways a facilitated conversation stalls: silence, the loop, avoidance and the derail. Each has its own response, from letting a silence hold to parking a derail and returning to the session question.
Four Stewardship Roles
The four roles a reference model needs to outlive its founders: the Curator (integrity and version history), the Domain Expert (substance), the Community Facilitator (use and adoption) and the Governance Sponsor (an executive who provides authority, budget and protection).
Four Types of Adaptation
The four decisions made when instantiating a reference model: adopt as-is, rename or redefine, add, and exclude. Each is recorded with its rationale, so the next version of the reference model can be applied systematically.
Four Ways Communication Fails
Four mismatches that stop sound architecture work from landing: audience (the wrong people, or the wrong level for their role), format (a medium that doesn't serve the message), timing (the wrong point in the decision cycle) and vocabulary (architecture terms the audience doesn't use).

G

Generalisation
Identifying what is common across many instances and representing it as one reusable structure: how a reference model is made. It gains breadth and loses specificity, so every reference model is a starting point to adapt.
Golden Circle
Simon Sinek's model of three levels, Why, How and What, and the argument that organisations should work from the inside out: purpose first, then approach, then offer.
Governance at Three Frequencies
Reviewing the Four Ares on a standing calendar at three speeds: continuous (weekly or monthly) for operations; quarterly for capability, strategy and benefits, at a forum where a named executive answers for the benefits; and annually for purpose. Signals add reviews; they don't replace the calendar.

H

Handoff Integrity
Whether strategic intent survives as the architecture is translated into requirements and then into a solution design. It is checked by tracing forward from each capability gap to the requirements meant to close it, which also makes missing requirements visible.
HERM Suite
The Higher Education Reference Models (v3.1.1): five connected artifacts (Business Model Canvas, Business Reference Model, Data, Application and Technology Reference Models) maintained by CAUDIT, UCISA, EUNIS and EDUCAUSE under CC BY-NC-SA 4.0.

I

Influence Map
A map of stakeholders by the relationship needed with each: audiences to inform, participants to engage, and allies to recruit through experience. Allies last longer than sponsors because they advocate from what the work did for them.
Integration Failure
A failure in which every capability involved is present and adequately resourced, but they don't connect, so the stakeholder meets the gaps between them as a fragmented experience.
Integration Patterns
The four connections between adjacent phases (Purpose-Strategy, Strategy-Capability, Capability-Operation, Operation-Purpose) where alignment is created or destroyed.
Internal Consistency Test
Checking whether a business model's nine building blocks reinforce or contradict each other. A model whose blocks contradict each other fails in execution even when each block looks sound alone.

L

Leading vs. Lagging Indicators
Leading indicators show whether architecture work is creating the conditions for change before outcomes are visible; lagging indicators confirm whether those outcomes arrived; governance requires both but must lead with the former.
Load-Bearing Systems
Systems that are structurally essential to the capability map. Whatever their age or technical health, each is the only support for a capability the architecture depends on, so it can't be removed without replacing the capability it serves.

M

Measurement Theatre
A dashboard that is rigorous, on schedule and defined at a layer that can't answer the question being asked. It's also the strategy trap that breaks the connection from operations back to purpose.
Meta-Learning
An organisation learning how to learn: getting better, cycle by cycle, at sensing change, making choices, designing capabilities and delivering.
Migration Strategy
How an organisation moves from an old system to a new one: phased migration (in stages), a parallel run (both at once for a period) or a cutover (a switch on a set date). The business architect weighs the options by capability continuity: how critical the capability is during the transition, how testable the replacement is, and how much change the organisation can absorb.
Minimum Viable Governance
The lightest governance that keeps a reference model alive: a named curator, a regular review, recorded adaptation rationale and a version history. Its test: would the leadership team notice if the model disappeared?
Model
A disciplined abstraction of one specific instance (one organisation's capabilities, one process, one data structure) that keeps what matters for understanding it and leaves out the rest.
Models-to-Meaning Gap
The distance between what architecture analysis reveals and what decision-makers actually hear and act on, caused not by flawed architecture but by the failure to translate findings into the language of each audience.
Multi-Altitude Document
A single document layered to serve three different readers: an executive summary that stands alone, a body that adds evidence for informed decision-makers, and appendices containing the full architecture evidence for practitioners.

N

Narrative Integrity Test
A check for a story told several ways: strip each version to its core claim and confirm the claims match. The tension, the emphasis and the request can change with the audience; the evidence and the core claim can't.
Nine Building Blocks
The nine parts of the Business Model Canvas: Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships and Cost Structure. A change in one cascades through the others.

O

Organisational Readiness
Whether an organisation has the four conditions for adopting reference models: executive sponsorship, a constituency that feels the pain, willingness to invest in shared infrastructure, and a collaborative culture, plus the psychological safety to hear what the models show (the chapter's fifth, cultural condition).
Outcome Metrics
Measures of whether stakeholders are better off because of what the organisation does, as opposed to activity metrics, which count what it did.
Outcome Metrics vs. Activity Metrics
Metrics must be derived from the aspiration, not chosen for ease of measurement; the shift from measuring what the organization does to measuring what difference it makes is Define's most lasting contribution.
Outcome Model
The Discover artifact at the purpose end of the theory of change: for each stakeholder group, what motivates it and the outcomes that would show it's better off. Each outcome is written as a stakeholder group, a need, and the direction its level should move. Later phases connect those outcomes down to the services that produce them.
Outputs vs. Outcomes
Outputs are what the transformation program built: systems deployed, processes redesigned, staff trained. Results are how well the live service then produced its output in the period, counted at its Service Output and read for efficiency, quality and effectiveness; the Service Output is the impact ladder's Outputs rung, and a program's outputs are the service's inputs. Outcomes are what changes for the people the service exists for. Closing a capability gap is the condition between the program's outputs and the service's results, not an outcome in itself. Tracking outputs and assuming the rest will follow is the most common failure in benefits tracking.
Outside-In Service Design
Designing a service from the stakeholder's experience inward, so internal operations are built to support that experience rather than the other way round.
Oversight Calibration
Deciding how deeply to engage with each piece of downstream work. For an artifact: produce it, read and challenge it, or know it exists. For a decision during the build: engage deeply when capability coverage is at stake, monitor lightly when only the approach changes, and step back when the decision is purely technical.

P

Pain-to-Solution Bridge
A three-step way to make the case for reference models: name a specific, observable pain; show how a reference model would have addressed it; and propose one bounded first step rather than an organisation-wide program.
Pantry vs. Recipe Distinction
The difference between having all the capabilities (the pantry) and knowing which ones must combine, and how, to produce a specific outcome (the recipe). A capability model shows the pantry; a recipe card shows the recipe.
Peak, Plateau and Valley
Three investment tiers for capabilities, set by the current strategy: peak capabilities differentiate and get heavy investment, plateau capabilities need to be efficient and reliable, and valley capabilities are held deliberately low, either as commodities or to keep exploratory work loose.
Portfolio View vs. Architecture View
Two ways of looking at a set of change initiatives. The portfolio view treats each as a discrete investment, judged on its own cost, benefit, risk and timing. The architecture view treats them as a system with structural dependencies. Sequencing needs both: the portfolio manager brings capacity, the business architect brings dependency.
PPTI Model
The four elements, people, processes, technology and information, that make a capability real. Investing in one without the others doesn't create the capability, because all four must work together.
Practitioner Flywheel
The learn, apply, reflect, improve cycle applied to your own practice: each cycle makes you more capable, and the first one is meant to be imperfect.
Presentation vs. Facilitation
Two ways to run a session. In a presentation the architect is the expert delivering conclusions; in facilitation the architect is the guide, and the group works with the evidence to reach its own conclusions. The audience's role, not the architect's preference, decides which.
Proof of Value
A first reference model initiative designed to show the model is worth investing in: one domain or question, six to twelve stakeholders and a governance sponsor, one deliverable for a real decision, four to eight weeks, and success measured by an insight that changes a decision.
Psychological Safety
Amy Edmondson's term for a shared belief that it is safe to speak up, disagree or admit a mistake without being punished. In a facilitated session the architect builds it by stating the purpose, setting the rules of engagement and naming the difficult truth before the room has to.

Q

Question-First Principle
The discipline of opening any architecture communication with the question the audience is already asking or should be asking, rather than with the methodology or framework used to find the answer.

R

Recipe Card
A reference model artifact that names one outcome (such as Student Success) and lists the capability ingredients, from the value chains and the enabling capabilities, that must combine to produce it. Published by the HERM for higher education.
Reference Architecture
A collection of reference models spanning several perspectives (business, data, application, technology) that together map a whole domain.
Reference Model
A model generalised across many instances to capture what recurs in a domain, maintained by a community as a reusable starting point. A useful reference model is easy to understand and to adapt to purpose: it generalises recurring patterns, serves a community, and can be instantiated for a specific context.
Reference Model Community
The group that maintains a reference model, validates its content and governs how it changes. Without one, the model is a one-time artifact rather than a living shared resource.
Reference Model Evidence
Reference model artifacts (a sector theory of change, a BMC diagnosis, a capability heat map, a recipe card assessment) used to answer governance questions with structured evidence rather than opinion.
Reference Model Maturity Levels
Four levels of an organisation's shared vocabulary: Level 0 (no shared models), Level 1 (informal and inconsistent), Level 2 (formal models in some domains, in silos) and Level 3 (an integrated reference architecture used in governance).
Reference Model Selection Framework
Choosing the first reference model by the organisation's most pressing pain: a sector theory of change for purpose confusion, the Business Model Canvas for strategic drift, the capability model for execution gaps, the recipe card for fragmented stakeholder experience.
Reference Models as Conversation Tools
Using a reference model to change the conversation (to make alignment visible and debatable) rather than as a compliance instrument imposed on people. Used as a conversation tool, it builds shared understanding; imposed, it builds resistance.
Reference Models by Design4 Phase
Reference models sorted by the Design4 phase whose key model they give a starting point for. Discover: a sector theory of change, such as one for mental health services. Define: a pre-populated Business Model Canvas, such as the HERM's. Develop: a reference capability model, such as the HERM BRM. Deliver: an operational pattern, such as a recipe card. A reference model can serve more than one phase, and none is sufficient alone.
Reinvention Tax
The time and energy an organisation spends rebuilding shared definitions and frameworks from scratch at the start of each initiative, because no common language carried over from the last one.
Requirements Hierarchy
The three layers through which requirements descend. Business requirements say why the initiative exists and what outcome it must achieve. Stakeholder requirements say what specific groups need from the change. Solution requirements say what the system must do. It is a translation chain, not a waterfall: intent can be lost at each link.
Reuse, Repair, Buy, or Build
The four ways to close a capability gap with a solution: reuse an existing system, repair or extend one, buy a product or service, or build something custom. Each has different implications for cost, time, risk and strategic fit, and the choice is strategic before it is technical.

S

Same Finding, Multiple Expressions
Expressing one architecture finding differently for each audience and register without losing the core insight. The heat map that takes ten minutes to present can become one sentence for the right audience.
Scope Erosion
The accumulation of individually reasonable scope decisions that together undermine an initiative's strategic intent, until it is delivered on time and closes few of the gaps it was approved to close. The erosion test catches it: after every scope decision, check which capability gaps the remaining scope still closes.
Service Blueprint
A map of one service that shows the stakeholder's journey alongside the internal processes and capabilities that support each step, front stage and back stage together.
Service Operating Model
Deliver's key model: the organisation's capabilities put to work as services, each producing a valued output to an agreed service level (efficiency and quality) and contributing to outcomes (effectiveness).
Service Output
The final valued output a service delivers to its client, counted in units of service delivered. Deliver's performance is measured here, for efficiency, quality and effectiveness. Results are how well a service produced its output in the period: its Service Outputs, counted and read for efficiency, quality and effectiveness. They sit on the impact ladder's Outputs rung.
Session Record
A structured summary of a facilitated architecture session that participants will trust as the basis for next steps, capturing what was agreed, what remains uncertain, and what was explicitly left unresolved.
Simplification Without Distortion
The core discipline of visual communication: removing information that does not serve the communication purpose while preserving the insight the audience needs to act on.
Six Objectives of Reference Models
What a reference model is built to do for its community: three primary objectives (Comparison, Responsibility and Accelerate Change) and three supporting ones (Communication, Education, and Norms and Standards).
Six Sources of Resistance
Six causes of resistance to architecture work: territorial threat, jargon overload, perceived irrelevance, past initiative fatigue, fear of exposure and loss of autonomy. Each has its own signal and needs its own response, not a louder repetition of the message.
So What Cascade
A chain of findings in which each finding's implication ("this matters because…") raises the question the next finding answers, so the evidence builds toward the action. No finding is presented without its so what.
Solution Oversight
The business architect's work once the decision to proceed is made: reading, assessing and challenging other people's solution work against the architecture, so that the strategic intent survives into what gets built. The architect stops authoring and starts overseeing, and keeps the blueprints.
Speed-Complexity-Purpose Triangle
Three forces that have outpaced the traditional planning cycle: faster change in the environment, more stakeholders with competing needs, and purpose as a driver of performance.
Stakeholder Communication Map
A structured tool that answers five questions for each stakeholder group before any communication is prepared: who they are, what they need, which register they're in, which format suits them, and when in the Design4 cycle they need it.
Stakeholder Value Map
The Discover artifact that maps every primary and secondary stakeholder group whose outcomes matter, what each needs at the outcome level (not what it says it wants), and the evidence that it's getting it.
Strategic Choice Cascade
Lafley and Martin's five integrated strategic choices: Winning Aspiration, Where to Play, How to Win, Capabilities Required and Management Systems. Each choice constrains and enables the next.
Strategic Trade-offs
The explicit decisions about what an organisation will not do, including where it will not compete, so that resources and attention go where the strategy needs them.
Strategic, Core, and Enabling Capabilities
Three tiers of capability by business impact. Strategic capabilities direct the organisation and shape its future (in the HERM, the Strategy Management group). Core capabilities create or deliver value through a value chain. Enabling capabilities let the organisation operate and support every value chain. The HERM names core and enabling; the strategic tier comes from BIZBOK, which calls the tiers strategic, core and supporting. Where a capability sits depends on the organisation.
Strategy Traps
Behaviours that break a specific connection in the Design4 cycle: Do-It-All and Dreams-That-Never-Come-True (purpose to strategy; from Lafley and Martin's Playing to Win), the Writing Cheques Trap (strategy to capability), the Initiative Churn Trap (capability to operations) and Measurement Theatre (operations to purpose).
Strategy-Execution Gap
The structural disconnect between what an organisation intends and what it actually delivers. It comes from broken connections between purpose, strategy, capability and operations, not from lack of effort.
Strategy-to-Capability Handoff
The point where Define hands over to Develop: every strategic choice traced to the capabilities it needs. A choice with no capability behind it is an unsupported commitment; a capability no choice needs is an orphaned investment.
Structural Problem
Relates to the underlying framework or system: the foundational elements that hold something together. The flaw is baked into the bones of how something is built or organized, often making it hard to change without rebuilding.

T

The Deciding Capability
The capability that decides how mature everything else needs to be: the one capability whose target can never be deliberately low. Its four parts are Derivation, Validation, Decision records and Redraw rhythm.
The Four Ares
John Thorp's four governance questions, one for each Design4 phase: Are we doing the right things? (Define), Are we doing them the right way? (Develop), Are we getting them done well? (Deliver), Are we getting the benefits? (Discover).
The Four Connections
The four links the Design4 cycle maintains: purpose to strategy, strategy to capability, capability to operations, and operations back to purpose. A break in one is a gap.
The Four Gaps
The four places where execution breaks down, one for each connection in the Design4 cycle: purpose to strategy, strategy to capability, capability to operations, and operations back to purpose.
The Four Owners
Who runs each phase of the Design4 cycle: Leadership runs Discover, Strategists run Define, Architects run Develop and Operations runs Deliver. Running a phase isn't the same as having the final say in it.
The Governance Fork
Two real, costed options put to the leaders with decision rights: one consistent with stated intent, one that continues current behaviour. Leadership chooses on the record, so drift stops being available as a defence. A room can also do a third thing: order a study, with neither branch chosen. The architect treats the study as a branch, with a date it reports and a rule for what each answer decides.
The Impact Ladder
Five rungs, each needing harder evidence than the one below: inputs, activities, outputs, outcomes and impact. Its named failure is climbing one rung too high: claiming a rung your evidence and control don't reach.
The Missing Middle
Define and Develop skipped between Discover and Deliver: a goal and a result with no strategic choice or capability in between.
The Receipts Test
A test of whether a purpose is real. Name the costliest decision the organisation has made, then ask: would the purpose have told you which way to go at the time, and did you go that way? A decision the purpose accounts for is a receipt.
The Solution Trap
Jumping from a problem straight to solutions before purpose and stakeholder needs are understood, so there are no criteria for choosing between them. It feels productive and produces efficient movement in the wrong direction.
The Strategic Thread
The line that runs from organisational purpose through strategic choice, capability gap, value stream, requirement and solution to delivered value. Each downstream role holds one segment of it; the business architect is the one who holds it end to end.
The Three Numbers
The three maturity numbers a capability can carry: current (from assessment), required (from strategy) and validated (from outcome evidence). The findings lie in the gaps between them.
The Unasked Question
The question an audience is carrying but won't voice, often political or personal: "Are you saying my faculty is underperforming?" Audience-first communication predicts it and answers it in the framing, before it turns into resistance.
Three Loss Patterns
The predictable ways strategic intent disappears as requirements move down the hierarchy: the "why" drops out, the measurable displaces the meaningful, and scope becomes a feature list.
Three States of an Ingredient
The three conditions a recipe card ingredient can be in: present (performing as required), absent (a resource gap) or present but not integrated (an integration gap, and the most common).
Three Symptoms of the Gap
The predictable failure patterns when architecture fails to reach its audience: the polite nod (apparent agreement with no follow-through), the wrong takeaway (action on a misunderstood finding), and the jargon wall (shutdown from unfamiliar vocabulary).
Three Types of Capability Gap
Maturity gaps (the capability exists but underperforms), resource gaps (essential elements are missing) and integration gaps (the elements exist but don't connect). Each needs a different response.

U

Useful Before Important
Building credibility by being useful in small, visible ways before asking for larger commitments. Small wins that are visible, attributable to the architecture and repeatable turn helpfulness into a practice people seek out.

V

Value Chains
The end-to-end sequences through which an institution creates value. The HERM BRM has two core value chains for higher education, Learning & Teaching and Research, each a lifecycle of capability stages.
Value Co-Creation
Value created in the interaction between an organisation and its stakeholders rather than delivered to passive recipients, which changes how services, roles and success measures are designed.
Value Network Analysis
A way of mapping what flows between the roles that make an organisation work in practice: tangible deliverables (reports, approvals, data) and intangible ones (trust, shared framing, credibility). It explains gaps that persist despite correct analysis.
Value Stream
An end-to-end collection of activities that creates a result for a customer, stakeholder, or end user.
Value Streams
The end-to-end stages through which an organisation delivers value to a stakeholder, from need to result, showing how capabilities must work together across functional boundaries.
Visual Hierarchy
The principle that the most important finding should be visible first and the audience's eye should follow a logical path toward the decision, achieved through placement, colour, and annotation rather than exhaustive labelling.