Business Architecture Glossary

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

5

5E Framework: Five strategies for growing the community that sustains a reference model: Evolution (improving the model), Enrichment (developing supporting materials), Evangelism (building awareness), Extension (expanding scope), and Extrapolation (connecting to adjacent models).

8

80/20 Approach: The HERM Working Group's design philosophy for the pre-populated BMC: capture what is common to most institutions rather than every possible variation, leaving room for each institution to adapt what is specific to its context.

A

Abstraction: The practice of representing something at a higher level of generality than its real-world implementation, removing specific details to reveal patterns that hold across many contexts.
Accuracy Trap: The architect's tendency to optimize 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.
Action: The fourth element of the narrative arc: the specific next step that follows logically from the evidence, stated as a decision or commitment rather than a recommendation to study the issue further.
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.
Architecture Influence vs. Architecture Documentation: Architecture succeeds when it changes decisions, not when it produces artifacts; documentation is the means, influence is the goal, and optimizing for the former at the expense of the latter is the root cause of the models-to-meaning gap.
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 Practice Sustainability: The organizational conditions that determine whether an architecture practice survives the departure of its founding champion: embedded governance rhythms, distributed architecture literacy, and a communication cadence that operates independently of any single practitioner.
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.
Artifact-Based Exploration: Facilitation techniques that draw participants into the evidence rather than asking them to receive conclusions: table-based assessment, dot voting, gap annotation, and scenario testing using architecture artifacts as the center of the conversation.
Audience-Appropriate Detail: The right level of detail for any visual is determined by the decision being made and the audience making it, not by the completeness of the underlying analysis.
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: Not a mission statement on the wall: the genuine answer to "What would the world lose if this organization ceased to exist?" Specific enough to guide choices, powerful enough to attract commitment.

B

BMC as Diagnostic Tool: The use of a Business Model Canvas to reveal how a business actually works and where it is structurally vulnerable -- not to plan future actions but to make hidden assumptions visible before a crisis exposes them.
Bootstrapping Challenge: The chicken-and-egg problem of adoption: the model needs users to validate it, but users need a useful model before they will participate, requiring a deliberate founding strategy rather than waiting for organic contribution.
Build, Buy, or Partner: Core capabilities should almost always be built and owned; essential capabilities can leverage external solutions; context capabilities should be standardized or outsourced, and the decision follows directly from the capability categorization.
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 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 Capability Model: A structured hierarchy of everything an organization must be able to do, defined independently of how it is organized, who does the work, or what technology supports it.
Business Model Canvas (BMC): A one-page framework that describes how an organization creates, delivers, and captures value through nine interconnected building blocks: not a plan but a picture of the business model's architecture.
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 Modeling: Using the BMC to trace the cascade of consequences when one building block changes, testing whether a proposed strategic shift produces an internally consistent new model before any commitment is made.
Business Model Vulnerability: What the BMC makes visible that financial reporting cannot: structural concentration risks in customer segments, value propositions, and revenue streams -- the architecture of a problem, not just its financial symptoms.
Business Reference Model (BRM): The HERM's capability model artifact -- the most mature and stable in the suite -- organized into two core value chains and eleven enabling groups, serving as the backbone to which all other HERM artifacts connect.

C

Capability: A particular ability or capacity that a business may possess to achieve a specific purpose or outcome.
Capability as an Integrated System: A capability is not a department or a technology purchase; it is four elements working together (People, Processes, Technology, Information) and investing in one without the others produces nothing.
Capability Heat Map: A visual artifact plotting strategic importance against current performance, transforming capability planning from a political process into a strategic one by making gaps and over-investments visible in a single view.
Capability Ingredients: The specific capabilities a recipe card identifies as required for a target outcome; the HERM Student Success Recipe Card lists sixteen ingredients, and the outcome depends on all of them connecting, not merely existing.
Capability Map: A visual representation of an organization's business capabilities, typically organized hierarchically.
Chasm of Miscommunication: The breakdown that occurs when the same words mean different things to different parts of the organization, producing apparent agreement that dissolves as soon as 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: Architecture artifacts are designed for architectural diagnosis; communication tools are designed for a specific audience to engage with and act on -- the same data requires fundamentally different visual treatment for each purpose.
Completeness Instinct: The architect's trained tendency toward including all elements for diagnostic accuracy, which serves architecture analysis but undermines communication when applied unchanged to artifacts intended for non-architect audiences.
Conceptual Integrity: The quality an organization achieves when its key terms are defined consistently across functions, levels, and initiatives, so every handoff carries shared meaning rather than requiring translation.
Connection to the Strategy-Execution Gaps: The absence of shared vocabulary maps directly onto the Four Gaps: without common language at each handoff, purpose cannot connect to strategy, strategy cannot connect to capability, and capability cannot connect to operations.
Consulting: Using a reference model as a diagnostic lens or conversation tool without formally adopting it -- the fast, low-investment mode that produces immediate insight without requiring organizational commitment.
Continuous Design Mindset: The shift from linear planning (plan, execute, review) to a cyclical discipline (Discover, Define, Develop, Deliver) where the goal is not a perfect plan but adaptive capacity.
Continuous Renewal: Retrospectives, experimentation space, cross-functional learning, and stakeholder co-design built into the operating rhythm so that operations evolve rather than ossify.
Convergence: The facilitation phase that moves from broad exploration to specific commitments, involving prioritization, action assignment, and explicit surfacing of disagreements that will otherwise resurface as resistance after the session ends.
Core Considerations: The eight evidence-based principles embedded in the HERM Student Success Recipe Card that explain why specific ingredients are required, making the recipe card an argument rather than a list.
Core, Enabling, and Strategic Management Capabilities: The three types in the HERM BRM: core capabilities deliver value through a value chain, enabling capabilities support all value chains and fail quietly when neglected, and strategic management capabilities govern direction and make the Design4 cycle possible.
Core, Essential, and Context Capabilities: Not all capabilities deserve equal investment: core capabilities differentiate and demand excellence, essential capabilities require adequacy, and context capabilities should be minimized -- and the categorization depends entirely on your strategy.
Cost of Inaction: An explicit statement of what the organization loses by not acting, which is more persuasive than a statement of gains from action because it frames the choice in risk terms that senior leaders already track.
Credibility Through Small Contributions: The practice of building influence by delivering useful, bounded outputs before asking for larger organizational commitments, so that trust is earned through demonstrated value rather than asserted through expertise.
Crisis Enthusiasm vs. Organizational Commitment: The distinction between the energy architecture work generates during a crisis (intense but temporary) and the sustained organizational commitment needed to keep architecture visible and used after the crisis resolves.
Cycle Triggers: The signals that prompt re-entry into the Design4 cycle rather than waiting for a scheduled review: external shifts (market disruption, regulatory change, competitive moves), internal signals (performance drops, emerging capability gaps, strategic drift), and deliberate checkpoints built into the governance rhythm. Organizations that wait for a crisis to cycle are already behind.

D

Decision Brief: A focused written document -- typically three pages -- structured to drive a specific decision: opens with the decision statement, presents headline evidence, states the recommendation, and names the cost of inaction.
Defensive Engagement Risk: The risk that presenting architecture findings to a skeptical group triggers defensiveness rather than productive conversation, addressed by redesigning the experience of encountering the data rather than by softening the data itself.
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: Operational data flowing back into purpose assessment, enabling the organization to detect shifts in stakeholder needs and environmental conditions before they become crises.
Design4 Framework: Four interconnected phases (Discover, Define, Develop, Deliver) that organize Business Architecture into a continuous cycle of alignment and adaptation, operating like gears rather than sequential steps.
Diagnose Your Entry Point: Enter the Design4 cycle at the phase that addresses your most pressing gap: Discover for purpose confusion, Define for strategic drift, Develop for execution failure, Deliver for outcome shortfalls.
Discovery Synthesis: The combined output (purpose, stakeholder map, outcome model, environmental scan) that becomes the criteria for every strategic choice in the Define phase; if a choice cannot be traced back here, it should not be built.

E

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.
Environmental Scan: A structured assessment of external forces (e.g., Social, Technological, Economic, Environmental, Political, Legal) that separates what the organization can influence from what it cannot, grounding purpose in reality.
Evidence: The third element of the narrative arc: specific data points, model findings, or capability assessments that support the reframe and give the audience reason to trust the conclusion being drawn.
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.
Executive Sponsorship: The first required condition for a successful reference model initiative: a senior leader who has personally felt the reinvention tax and will protect the time and attention the effort requires; without one, the initiative becomes a passion project that evaporates at first budget pressure.

F

Fear of Exposure: Resistance arising when architecture assessment feels like a public evaluation of leadership performance rather than a structural diagnosis, activating defensiveness that no amount of accurate data will overcome.
First Cycle as Proof of Concept: A small, fast, focused experiment (diagnostic in weeks one and two, artifact in weeks three through six, one measurable change in weeks seven through twelve) that demonstrates value before anyone is asked to believe in the theory.
First-Page Test: The design criterion for a decision brief: page one should contain the decision, headline evidence, recommendation, and cost of inaction, because the reader with twelve agenda items may not turn to page two.
Five Architectural Strategies: Abstraction, Generalization, Views, Layering, and Partitioning: five approaches for managing organizational complexity, all of which are embodied in how reference models are structured and used.
Five Design Parameters: The five dimensions defining a properly scoped first initiative: Scope (one domain), Stakeholders (6-12 representatives plus a governance sponsor), Deliverable (one specific artifact tied to a real decision), Timeline (4-8 weeks), and Success Criteria (an outcome, not an output).
Five-Element Session Design: The structure for a facilitated architecture conversation: the question to be answered, the artifact serving as shared evidence anchor, the participant mix, the activity sequence (opening, exploration, convergence, close), and the intended outcomes.
Flywheel Effect: Each turn of the Design4 cycle builds on the last, preserving momentum rather than resetting to zero, because the cycle is cumulative, not disposable.
Four Ares as Agenda Structure: Using the four governance questions to organize architecture reviews so that each session addresses a specific phase of the Design4 cycle rather than rehearsing the same general progress report.
Four Ares as the Senior Leader Argument: Asking "Can we answer these four questions with evidence?" reframes Business Architecture from a methodology to adopt into a governance structure for questions leaders already care about.
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 Fitness Criteria: The four dimensions for assessing whether a reference model is worth adopting: Scope (right territory), Language (adoptable vocabulary), Strategic Alignment (matching priorities), and Connectivity (compatible with what the organization already has).
Four Stewardship Roles: The Curator (technical integrity and version history), Domain Expert (subject-matter validation), Community Facilitator (participation and adoption), and Governance Sponsor (executive authority and protection) -- the four roles every reference model community requires to survive beyond its founding energy.
Four Types of Adaptation: The four decisions required when instantiating: Adopt as-is, Rename or Redefine, Add (elements specific to the organization's context), and Exclude (elements that do not apply) -- each with documented rationale so future version updates can be systematically applied.
From Fragile to Adaptive: The organizational transformation that sustained Design4 cycling produces. A fragile organization breaks under pressure because its strategy, capabilities, and operations are misaligned and static. An adaptive organization absorbs and responds to change because alignment is continuously renewed, the capacity to sense-and-respond is built in, and each cycle strengthens rather than depletes the institution.
From Potential to Kinetic Energy: Capabilities are potential energy; operations are kinetic energy. Having capabilities is necessary but not sufficient; the test is whether the stakeholder is actually better off.

G

Generalization: The process of identifying what is common across many instances and representing it as a single reusable structure -- the core architectural strategy by which reference models are built from accumulated organizational experience.
Golden Circle: The principle that organizations which lead with Why before How and What make more coherent strategic choices, build deeper stakeholder relationships, and attract more committed talent.
Governance at Three Frequencies: Continuous (weekly/monthly) for operational performance, periodic (quarterly) for strategic alignment, and cyclical (annually or signal-triggered) for purpose validation -- driven by signals, not calendars.
Governance Cadence: The structured rhythm of model maintenance reviews -- tactical, operational, and strategic frequencies -- that keeps a reference model current without consuming more organizational energy than it produces.
Governance Cycles: The recurring organizational decision-making moments -- board meetings, budget cycles, strategic planning sessions, performance reviews -- that determine when architecture communication will have the greatest influence.

H

HERM Suite: The Higher Education Reference Models (v3.1.1), a suite of five interconnected artifacts -- Business Model Canvas, Business Reference Model, Data Reference Model, Application Reference Model, and Technology Reference Model -- maintained by CAUDIT, UCISA, EUNIS, and EDUCAUSE under CC BY-NC-SA 4.0.

I

Instantiating: Formally adapting a reference model to become the organization's own version, customizing vocabulary, adding context-specific elements, and removing inapplicable ones while preserving the reference structure.
Instantiation: The process of adapting a reference model to produce an organization's own specific version, applying the general pattern to a particular context by renaming, adding, and removing elements while preserving the underlying structure.
Integration Failure: The thesis that most organizational failures are not capability failures but integration failures: individual capabilities are present and adequately resourced but do not connect to produce a coherent outcome for the stakeholder.
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: The discipline of checking whether a BMC's nine building blocks reinforce rather than contradict each other, because a business model with misaligned blocks will fail in execution even if each block appears sound in isolation.
Investment Case: A written argument that connects a proposed capability investment to a strategic choice, quantifies the gap it closes, and makes the cost of the current state visible in terms the financial decision-maker uses.

K

Key Artifacts by Phase: Twelve tangible representations (from the Golden Circle to Service Blueprints) that make the Big Picture visible, debatable, and actionable -- conversation tools, not conference room decoration.

L

Lead with the Pain, Not the Framework: The most effective case for Business Architecture is not a methodology presentation; it is a question that reveals a gap leaders already feel but have not been able to name.
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.

M

Maturity Level Indicators: Observable behavioral signals for each level: at Level 0, definitions are contested in the first thirty minutes of any cross-functional meeting; at Level 3, new leaders are briefed on the reference architecture as part of onboarding.
Meta-Learning: The deepest advantage: not better strategy or better capabilities, but the organization's increasing ability to sense, choose, design, and deliver -- getting better at getting better.
Meta-Learning as Sustainable Advantage: The compounding organizational capability that emerges from repeated cycling: not just better strategy but the ability to sense, choose, design, deliver, and learn faster than the environment changes.
Minimum Viable Governance: The lightest governance structure that sustains a reference model: a named curator, a defined update cadence, documented adaptation rationale, and a version history; the test is whether the leadership team would notice if the model disappeared.
Model: A structured representation of a domain's elements and their relationships that makes something complex understandable and communicable: not a plan but a picture of how something is or should be organized.
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.
Multiple Views: The complementary perspectives the capability model (organized by what the institution does) and the recipe card (organized by what the stakeholder needs) provide; neither view is sufficient alone, and answering only the capability model question produces ingredients without a recipe.

N

Needs vs. Wants: Mapping stakeholder needs at the outcome level (what they need to achieve) rather than the product level (what they say they want) unlocks strategic possibilities that product-level thinking misses entirely.
Nine Building Blocks: The nine components of the BMC -- Customer Segments, Value Propositions, Channels, Customer Relationships, Revenue Streams, Key Resources, Key Activities, Key Partnerships, and Cost Structure -- each describing one dimension of the business model, with changes in any block cascading through the others.

O

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 artifact that connects abstract purpose to measurable stakeholder results by specifying motivations and desired outcomes for each stakeholder group, replacing activity data with outcome evidence.
Outside-In Service Design: Starting with the stakeholder's experience and designing internal operations to support it, rather than starting from internal workflows and hoping the stakeholder benefits.
Over-Customization Pitfall: The risk that an instantiation changes so much of the reference that it loses community connection; the rule of thumb: if more than 20-30% of the reference has been changed, the organization has built a custom model and forfeited the benchmarking and version migration value.

P

Pain-to-Solution Bridge: A three-step framing structure: name the specific, observable organizational pain; connect it to how a reference model would have addressed it; and propose one bounded first step rather than a programme-wide transformation.
Pantry vs. Recipe Distinction: The difference between having a full set of capabilities and knowing which ones must combine to produce a specific outcome -- an organization with the pantry but without the recipe leaves stakeholders to navigate the gaps between individually adequate capabilities.
Past Initiative Fatigue: Resistance arising from accumulated skepticism built by previous organizational initiatives that demanded effort and produced no lasting change, making any new methodology suspect regardless of its merit.
Phases as Gears: The phases are not sequential steps you complete and leave behind; when one moves, it drives the others, and the last loops back to the first.
Political Register: The processing level focused on power, reputation, alliances, and position risk; it activates whenever architecture work implies evaluation of a leader's domain and is the most common source of unexpected resistance.
PPTI Model: The four elements -- People, Processes, Technology, and Information -- that compose every capability; investing in one without the others does not improve the capability because all four must work together.
Practitioner Flywheel: The same learn-apply-reflect-improve cycle that Design4 uses for organizations applies to your own professional development: each cycle makes you more capable, and the first cycle will be imperfect by design.
Predictive Audience Analysis: The practice of identifying in advance the questions a specific stakeholder will ask, designing the communication to answer them before they are raised rather than responding defensively after the fact.
Presentation vs. Facilitation: Presentation positions the architect as expert delivering conclusions; facilitation positions the architect as guide structuring group exploration -- the same architecture findings require fundamentally different session designs for each mode.
Prototyping Before Building: Testing the riskiest assumptions with minimum viable capability versions first, because a prototype that reveals a flaw in week two saves more than a full build that reveals the same flaw in month twelve.
Psychological Safety: The precondition for honest engagement in a facilitated session, established by stating purpose clearly, setting rules of engagement, and naming the difficult truth in the room before the formal session begins.

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 identifies a specific strategic outcome and lists the capability ingredients -- drawn from both value chains and enabling capabilities -- that must combine to produce it.
Reference Architecture: A reference model that specifies not only what elements exist but how they must be designed and connected, establishing standards and constraints in addition to shared patterns and carrying more prescriptive force than a reference model alone.
Reference Model: A generalized, community-maintained model that captures recurring patterns within a domain, providing a shared starting point that any member can adapt to their specific context without building from scratch.
Reference Model Community: The group of organizations that collectively maintains a reference model, validates its content, and governs its evolution; without that community, the model is a one-time consulting artifact rather than a living shared resource.
Reference Model Evidence: The use of reference model artifacts -- capability heat maps, BMC diagnostics, recipe card assessments -- to answer governance questions with structured evidence rather than opinion.
Reference Model Maturity Levels: Four stages of organizational readiness: Level 0 (no shared models), Level 1 (informal, inconsistent vocabulary), Level 2 (formal models in some domains but siloed), and Level 3 (integrated reference architecture used in governance) -- most organizations are at Level 0 or 1.
Reference Model Selection Framework: The principle that the right first reference model depends on the organization's most acute pain: the BMC for strategic clarity, the capability model for execution gaps, and the recipe card for fragmented stakeholder experience.
Reference Models as Conversation Tools: Reference models succeed by changing conversations and producing alignment, not by generating documentation or enforcing compliance -- a model used as a compliance instrument generates resistance; used as a conversation tool, it generates shared understanding.
Reframe: The moment in the architecture narrative where the analysis reveals something the audience had not seen, shifting their understanding of the problem from one category -- resource shortage, personnel failure -- to another: structural misalignment.
Register Mismatch: The communication failure that occurs when content is prepared for one register but delivered to an audience operating in another -- presenting technical findings to a strategic audience, or strategic findings to an audience focused on operational execution.
Reinvention Tax: The time and energy organizations spend re-creating definitions and frameworks that previous teams already built, because no shared language was preserved from one initiative to the next.
Rhythm Map: A calendar-aligned structure showing what architecture communication happens, for whom, in what format, and at what frequency, making the communication cadence visible and governable as an ongoing practice.
Rotating Focus: Organizing quarterly architecture reviews to rotate primary attention through the Four Ares, preventing repetition while maintaining systematic coverage of the full strategy-to-delivery chain.

S

Same Finding, Multiple Expressions: The discipline of taking one architecture insight and articulating it differently for each audience register, without losing the core finding; the heat map finding that takes ten minutes to present can be expressed in one sentence for the right audience.
Scope-First Initiative: A proof-of-value design for a first reference model effort: narrow scope, short timeline, one specific artifact for a real governance conversation -- designed to create one concrete experience that makes the case for every initiative that follows.
Selective Instantiation: A hybrid approach in which an organization formally instantiates a reference model for one domain while continuing to consult it in others, avoiding the all-or-nothing adoption trap that stalls many reference model initiatives.
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: Three primary objectives (Comparison, Responsibility, and Accelerate Change) and three supporting objectives (Communication, Education, and Norms and Standards) that define what a well-designed reference model is built to deliver for its community.
Six Sources of Resistance: Territorial threat, jargon overload, perceived irrelevance, past initiative fatigue, fear of exposure, and loss of autonomy -- each arising from a different cause and each requiring a different response rather than a louder repetition of the original message.
Speed-Complexity-Purpose Triangle: Three converging forces (faster environmental change, multi-stakeholder complexity, and purpose as a performance driver) that have permanently outpaced the traditional planning cycle.
Stakeholder Communication Map: A structured tool that answers five questions per stakeholder group -- who, what, register, format, and when -- before any communication is prepared, replacing instinct with systematic audience analysis.
Stakeholder Ecosystem Mapping: Expanding the lens beyond "the customer" to map all primary and secondary stakeholders whose outcomes matter, including those whose expectations conflict and constrain what the organization can do.
Story vs. Report: Architecture communication organized around a narrative with direction and tension moves audiences toward decisions; architecture communication organized as an accumulation of findings informs without moving anyone.
Strategic Choice Cascade: Five cascading choices (Winning Aspiration, Where to Play, How to Win, Capabilities Required, Management Systems) each building on and constraining the others, creating an integrated strategic logic.
Strategic Register: The processing level focused on direction, investment, and competitive position; communicating in this register means leading with decisions and strategic options, not process details or capability hierarchies.
Strategic Trade-offs: Every "yes" is an implicit "no"; without trade-offs, resources spread thin, teams lack clarity, and the organization defaults to chasing the urgent at the expense of the important.
Strategy as Integrated Choices: Strategy is not a planning document or a to-do list; it is a set of interconnected choices that constrain and reinforce each other, and its power lies in the integration.
Strategy Traps: Patterns that look like strategic thinking but widen the gaps: the Do-It-All Trap (refusing to choose), the Program-of-the-Month Trap (initiative churn), and the Metrics Trap (measuring what is easy rather than what matters).
Strategy-Execution Gap: The persistent, structural disconnect between what organizations intend and what they actually deliver, caused not by lack of effort but by broken connections inside the system.
Structural Contextualization: The discipline of connecting specific architecture findings to their broader organizational significance, so that a decision-maker without architecture training can understand why a finding matters and what follows from it.

T

Tension: The opening element of the architecture narrative: the organizational problem, gap, or risk that anchors audience attention, framed in the audience's own terms rather than architecture language.
Territorial Threat: Resistance arising when architecture work crosses organizational boundaries and leaders feel their domain is being assessed without their involvement or control.
The Four Ares: Four diagnostic questions (Are we doing the right things? Are we doing them the right way? Are we getting them done well? Are we getting the benefits?) that assess alignment across the entire chain from purpose to value delivery.
The Four Ares as Governance: The same four questions, now revealed as a cascading governance system: each question monitors a specific phase and builds on the answer to the one before it.
The Four Gaps: Four specific handoff failures where execution breaks down: purpose disconnects from strategy, strategy outpaces capability, capability never reaches operations, and operations drift from purpose.
The Metrics Hierarchy: Three levels of measurement: outcome metrics (did the stakeholder achieve their goal?), experience metrics (how did it feel?), and process metrics (was it efficient?) -- where organizations naturally gravitate to the bottom and governance must hold attention on the top.
The Solution Trap: The impulse to jump from a perceived problem straight to solutions, skipping the hard work of understanding purpose and stakeholder needs, which leads to efficient movement in the wrong direction.
Three Pages or Fewer: Not a page limit but an editing discipline: the constraint forces the writer to choose between pieces of evidence, eliminating everything that does not directly support the decision, and produces a document more likely to be read than a comprehensive report.
Three Simplification Strategies: Filter to a relevant subset (stating what was filtered and why), aggregate to a higher level (grouping related elements), and focus on contrast (showing only the comparison that matters for the decision at hand).
Three States of an Ingredient: The three conditions in which any recipe card ingredient can be found: Present (performing as required), Absent (a resource gap to be filled), or Present but not integrated (an integration gap and the most common failure mode).
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 components are missing entirely), and integration gaps (the pieces exist but do not connect), each requiring a fundamentally different response.
Three Types of Capability Gaps: Maturity gaps (doing it but not well enough), resource gaps (missing specific elements), and integration gaps (elements that do not connect), each requiring a fundamentally different response.

V

Value Chains: The end-to-end sequences through which an institution creates value; the HERM BRM identifies Learning & Teaching and Research as higher education's two core value chains, each organized as a lifecycle of capability stages.
Value Co-Creation: Value is not delivered to passive recipients; it is co-created through the interaction between organization and stakeholder, which changes job descriptions, service designs, and success metrics.
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 sequence of stages through which the organization delivers value to a stakeholder, revealing how capabilities must work together across functional boundaries and where handoffs create or destroy value.
Versioning: The discipline of releasing numbered model updates with documented change logs and migration guidance, so organizations can update their instances deliberately and distinguish intentional adaptations from outdated residue.
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, color, and annotation rather than exhaustive labeling.
Vocabulary as Infrastructure: Shared organizational vocabulary is not a communication skill but structural infrastructure: invisible when it works, costly to replace when missing, and something that must be deliberately built rather than assumed to develop on its own.

W

Where Not to Play: The discipline of explicit exclusion: the choices about what to stop doing, which markets to exit, and which opportunities to decline are where strategy actually lives.