Cookbook Recipes
45 problem-centered methods for applied business architecture work, each with a practical stop condition.
Search the workbench
Find a recipe, work product, case study, article, external source, study guide, or SCALE entry without knowing where it lives first.
Showing the main starting points. Enter a term to search all indexed content.
45 problem-centered methods for applied business architecture work, each with a practical stop condition.
Annotated standards, guides, webinars, reference models, and tools with practical context and clear access terms.
Governed, reusable artifacts with instructions, explicit boundaries, and direct links to the recipes that explain the method.
A connected fictional case following a $780M, 48-branch equipment-services company through authorization, preparation, and value realization for a bounded three-branch service-reliability change.
A disciplined, public-information-based approach to studying the BIZBOK system and preparing for the CBA examination.
Download the SCALE Agent Kit and load it into your approved AI for architect-led, evidence-grounded business architecture analysis and portable workspace exports.
Applied essays organized around practice building, strategy and delivery, architecture methods, and stakeholder leadership.
Direct email support for one real business architecture question and limited practitioner mentoring.
The request arrives as a proposed solution, a vague transformation, or a demand for “a capability map,” but the accountable decision, evidence threshold, authority, and boundary have not been established.
The enterprise needs a stable view of what it must be able to do, but the first draft mirrors departments, applications, products, process steps, or a borrowed reference model instead of enduring business abilities.
The “value stream” becomes a swimlane full of activities, systems, functions, and handoffs, obscuring the progression through which a stakeholder actually receives value.
Initiative scope is expressed as features, applications, workstreams, or a project charter with no defensible explanation of which business outcomes, value stages, capabilities, information, organization, policies, or products must actually change.
The strategy has been translated into explicit outcomes, but leaders still cannot show whether funded initiatives collectively cover those outcomes, which investments lack strategic justification, or where measures and ownership break the execution logic.
Architecture review becomes a document checkpoint or presentation ritual rather than a forum for resolving a consequential choice with explicit evidence, authority, alternatives, and follow-through.
A charter or executive intention exists, but the practice still lacks a workable service model, intake, capacity rules, knowledge governance, forum integration, and evidence that it improves decisions.
A workshop, engagement, or initiative produces useful architecture, but the whiteboard dies in a deck, proposals become indistinguishable from approved enterprise truth, and later teams must rediscover the same knowledge.
The practice begins with enthusiasm but no shared purpose, boundaries, decision rights, engagement model, or definition of success.
The information model has become a long, inconsistent list that mixes genuine business objects with synonyms, attributes, documents, events, roles, applications, and local terminology.
Business information is documented, but the organization cannot show where it enters the business, which capabilities change it, how it moves through value delivery, or who governs its lifecycle.
The capability map is either too shallow to support a decision or decomposed into uneven detail that nobody can consistently assess, own, or use.
An existing capability map is dominated by departments, roles, processes, applications, products, and duplicated local abilities, but stakeholders already depend on it and replacing it wholesale would destroy useful knowledge and credibility.
A broad statement such as “improve customer experience” or “modernize operations” creates activity, but it does not identify the outcomes, business changes, evidence, or choices needed for execution.
A portfolio scan, capability heat map, or governance discussion has flagged two or more initiatives as potentially duplicative, conflicting, complementary, or dependent, but shared mappings alone do not establish the correct disposition.
A discovery meeting is scheduled before the decision, participants, evidence, working structure, and expected outputs are clear, so the session produces broad conversation instead of usable architecture knowledge.
A capability model needs business validation, but the workshop risks becoming an unstructured debate about department names, process steps, systems, terminology, and personal ownership claims.
Two groups use different terms, definitions, or boundaries and each insists that its version represents a separate capability, leaving the enterprise with duplication, false standardization, or unresolved ownership conflict.
A capability map has been colored red, yellow, and green without a clear decision, consistent dimensions, defensible evidence, or any indication of confidence, creating visual certainty without analytical discipline.
The first release is either overloaded with desirable scope or reduced to a technical component that cannot produce usable business value on its own.
An initiative remains nominally active but repeatedly misses decisions, funding, dependencies, or mobilization, while status reporting describes delay without identifying the constraint that must actually change.
A broad transformation is divided by department, application, funding source, or delivery team, producing work packages that cannot independently explain their value, dependencies, or contribution to the intended business change.
A capability roadmap either remains a timeless aspiration or becomes a delivery schedule full of projects, tasks, and dates that obscures the business abilities and outcomes being changed.
A requirement is documented and prioritized without a durable explanation of which stakeholder outcome, value-stream stage, capability change, information need, policy, or initiative decision justifies it.
A platform, application, or emerging technology is presented as the solution before the desired outcome, capability gap, value-stream impact, information need, operating-model change, and policy implications have been established.
Business architecture is expected to create enterprise value without the mandate, access, funding, or decision rights normally supplied by an executive sponsor.
Business architecture sits inside an organization whose governance, funding, language, and demand are centered on technology, creating pressure to become an upstream solution-design service instead of a business decision discipline.
Multiple business units claim to own one capability because ownership is being used to mean content stewardship, investment authority, performance accountability, policy control, or operational execution at the same time.
Business architecture is added as a separate review, template, or approval gate, increasing cycle time while portfolio decisions continue to rely on the same incomplete strategic and business evidence.
The EA repository is becoming either an indiscriminate document store or an incomplete diagram catalog, while practitioners duplicate authoritative data and struggle to decide which knowledge deserves governed relationships and lifecycle control.
A proposed strategy, policy, business model, or emerging concept needs architectural analysis before implementation exists, creating pressure either to invent a target solution or to postpone useful modeling until decisions have already hardened.
When an initiative is cancelled, merged, defunded, or abandoned, validated enterprise knowledge disappears with its project files while obsolete scope, target states, and assumptions remain discoverable without clear status.
Architecture from a prior initiative is copied into a new context as an assumed standard, carrying forward local choices, stale assessments, ownership, and constraints that may not represent durable enterprise knowledge.
Teams either model process by habit when capability and value views would answer the decision, or avoid process detail when sequence, handoffs, controls, timing, and exception behavior are essential.
Architecture continues because the enterprise can always be modeled more completely, or it ends when a deadline arrives without confirming that the decision, governance, and downstream consumers have what they need.
The portfolio shows projects, spend, and dates, but leaders cannot see where change is concentrated across business capabilities, which important abilities are neglected, or where multiple initiatives depend on the same enterprise capacity.
A visible symptom such as customer abandonment, rising cost-to-serve, delay, rework, or control failure is being assigned to a familiar function or proposed solution before the enterprise relationships and plausible causes are understood.
Two capability maps use different names, boundaries, levels, identifiers, and organizing assumptions, and each carries useful relationships or institutional authority that would be lost by simply declaring the other map correct.
A consequential architecture decision is buried in meeting notes, presentation slides, email, or memory, leaving later teams unable to tell what was decided, by whom, from which evidence, under what conditions, or when the decision should be reconsidered.
The organization chart shows reporting relationships, but architecture decisions still cannot identify which internal and external organizations participate in value delivery, perform or govern capabilities, control resources, or hold material decision rights.
A capability has been rated important or underperforming, but a maturity score or heat-map color does not explain what prevents it from producing the required outcome, which constraints matter most, or what change is justified.
An initiative describes features, processes, systems, or work packages but does not define how the affected capabilities must operate after delivery, who will own the outcome, or which organizational, information, policy, capacity, and support changes must endure.
Deployment, feature completion, or project closure is being treated as benefit realization even though the organization cannot show the adoption, capability performance, value-stream change, and stakeholder outcome through which value would actually appear.
A release is technically complete but the enterprise has not established whether people, capacity, information, controls, policies, support, ownership, partners, and operating measures are ready to sustain the intended business outcome.
A new regulation, policy, contract, standard, or control obligation is assigned to a familiar function or technology team before the enterprise can trace what behavior, information, accountability, value delivery, and evidence must actually change.
Stakeholder engagement is not an accessory to business architecture. Observation, meeting preparation, facilitation, humor, and the ability to read a room directly affect the quality of the architecture we produce.
Business architects often lead without formal authority. Servant leadership offers a useful model, provided service is understood as stewardship of enterprise outcomes rather than accommodation of every stakeholder request.
How business architects can govern an unruly business object model, preserve canonical business meaning, model lifecycles and states, and connect business objects to automation without collapsing business architecture into data or solution design.
Selecting an enterprise architecture platform for business architecture requires testing how well the tool supports strategy, concepts, scenarios, governance, and the daily operating model of the BA practice.
An operations background is not a detour from architecture; it can supply the consequences, constraints, and institutional realism that abstract models lack.
A small, linked architecture package can outperform a comprehensive repository when it is designed around a real decision.
A practical business architecture approach to the choices, boundaries, decision rights, capacity, and transition required to make strategy operational.
How to limit scope, avoid gold plating, and deliver a narrow but complete first release tied to measurable business value.
Practical guidance for establishing a small business architecture practice, building an initial capability, value stream, organization, and information baseline, and using it to support real business decisions.
What business architects should do when timelines stall, sponsorship weakens, execution never arrives, or business architecture is positioned only as the front door to a larger architecture pipeline.
Alfred D. Chandler Jr.'s history of the managerial enterprise is nearly half a century old. Read critically, it still clarifies the central work of business architecture: coordinating capabilities, value streams, information, decisions, and resources across enterprise boundaries.
The discipline becomes difficult at the boundaries: choosing the right abstraction, linking domains, and making architecture matter to a decision.
Business architecture and business analysis overlap, but they are not interchangeable. One enables a particular change; the other creates and governs reusable enterprise knowledge that shapes many changes.
Turn a request for a map, solution, or transformation into a bounded business-architecture engagement with a named decision, evidence threshold, scope, options, and stop condition.
Create stable capability definitions, test decomposition depth, expose orphaned or weak records, and structure a validation workshop without reproducing the organization chart.
Define outcome-oriented value-stream stages, entry and exit criteria, measures, and enabling capabilities while keeping process activity out of the strategic view.
Trace initiative scope to value-stream stages, capabilities, information, policy, organization, measures, and dependencies, then compare bounded release options.
Translate strategy into explicit outcomes, affected value propositions, required capability changes, initiatives, measures, assumptions, and unsupported objectives.
Normalize business-object identities, definitions, aliases, ownership, authoritative sources, lifecycle states, transitions, and capability use without turning the model into a physical data schema.
First select capabilities that warrant attention using strategic importance, observed performance, evidence strength, and confidence; then diagnose the specific people, process, information, technology, policy, governance, capacity, performance, and dependency conditions that limit a selected capability.
Break a broad change into outcome-oriented packages, expose true dependencies, distinguish prerequisites from preferred sequencing, and build a capability transition roadmap rather than a disguised project plan.
Keep decisions, rationale, conditions, decision rights, accountable owners, evidence gaps, assumptions, conflicts, review triggers, and closure dispositions in one governed record.
Six lightweight structures for beginning a decision-centered engagement without first building a large repository or practice apparatus.
A lightweight working charter for establishing a practice mandate, boundaries, decision rights, engagement model, first 90 days, and measures.
Five portable analysis structures for recurring business-architecture questions that do not require spreadsheet logic.
Six connected, portable structures for carrying a change from organizational context and capability diagnosis through operating-model change, readiness, value realization, and policy impact.
A practical study sequence built around one integrated case, distinction drills, scenario practice, and an error log.
The complete ZIP with agent instructions, launch prompt, setup guide, schemas, workbook, reference architecture, and completed Northstar example.
The controlling behavior, authority, workflow, review rules, commands, security boundary, and output contract for the portable agent.
The portable distribution, product, technical, governance, and trust model for SCALE version 0.5.
The manual and agent-supported workbook for moving from a business question through evidence, architecture, analysis, a work product, and continuing stewardship.
A completed fictional path from question through evidence, proposed architecture, human disposition, analysis, work product, decision, and continuing reuse.
A private working record for mentoring goals, sessions, work reviewed, decisions, and progress evidence.
The Guild’s public landing page for introductory material, white papers, and other openly available resources.
A direct public PDF introducing the discipline, framework, core domains, and intended use of business architecture.
The public glossary for checking formal definitions and avoiding the near-synonym problem that makes BA difficult to learn.
A concise public paper distinguishing business architecture from process work, solution design, and organization charts.
An index of public papers covering alignment, governance, metrics, organization design, risk, and related practice topics.
The official OMG landing page for BACM, useful for understanding the formal relationships among business architecture concepts.
The full public specification for the Business Architecture Core Metamodel.
The OMG standard for ends, means, influencers, assessments, and directives that can anchor strategy mapping.
A public introduction to the Business Model Canvas; useful when BA work must begin above the capability layer.
A public guide for clarifying customer jobs, pains, gains, and the value proposition before translating them into architecture.
A public white paper on linking business architecture to measurable performance rather than stopping at maps.
A practical introductory video from the Business Architecture Guild on capability mapping.
A public explanation of capability maps, common structures, and practical examples.
A second public treatment of capability mapping that is useful for comparing terminology and modeling choices.
A public paper on using architecture to inform organization design without collapsing capability into the org chart.
Public federal service, function, data, and standards models that provide useful reference-model examples in Excel and JSON.
A public white paper on linking risks to business architecture so risk conversations become traceable and decision-relevant.
The GAO maturity framework offers a rigorous public example of staged governance, institutionalization, and management controls.
Public presentation material showing how practitioners frame scenarios, artifacts, and outcomes.
A public paper on maintaining business direction while working with application, data, solution, and technology architecture.
The official BPMN standard page. Use it to keep process notation distinct from value streams and capability models.
Public ASQ guidance on quality tools that complement BA when the work moves from structural diagnosis into root-cause analysis.
A public overview of cross-industry and industry process frameworks. Useful as a comparison point, not as a capability map substitute.
A free desktop tool for ArchiMate modeling and repository-based architecture work.
Public examples, guidance, scripts, and community resources for the Archi tool.
A free browser-based BPMN modeler for lightweight process work without installing a tool.
A free general-purpose diagramming tool for workshops, early models, and stakeholder communication.
The official public blueprint for the ten Certified Business Architect exam domains and their objectives.
Official public program policies covering membership, certification duration, retakes, and administration.
The Open Group’s current overview of the experience-based Open CA program and its three levels.
The official requirements document for experience, competencies, professional development, and contribution.
Official guidance for writing coherent, evidence-based experience profiles around real work and professional judgment.
The searchable Guild catalog for webinars, self-study modules, reference models, volunteer learning, and downloadable practice material. Use it when the topic is known but the relevant Guild product is not.
The Guild’s guide page, including current access information and public portions of the BIZBOK Guide. It is the best place to distinguish public excerpts from the member edition.
A compact Guild orientation to the discipline and its principal concepts. Use it before the longer BIZBOK introduction or formal metamodel material.
The Guild’s topic index for recordings across core domains, extended mappings, governance, and interdisciplinary alignment. Availability varies by item.
The Guild guide to connected architecture relationships, including alignment with customer journeys, requirements, processes, and value creation. Use it to move beyond isolated maps toward a coherent knowledgebase.
A Guild webinar on capability, value stream, information, and organization mapping, plus how the four domains reinforce one another. Useful when a practice has maps but no common foundation.
A collection of canvases, test and learning cards, portfolio aids, assessments, and supporting guides. Use it to frame strategy and hypotheses before translating them into architecture.
A Guild webinar positioning business architecture as the coordinating discipline between business direction and coherent execution. Useful when strategy and delivery operate as separate conversations.
A Guild webinar on using operating models to improve analysis, planning, organizational choices, and executive decisions. Use it when the term operating model lacks a shared meaning.
A Guild webinar on business-object-based capability definition, naming discipline, scope, overlap, and the downstream effects of weak models. Use it to repair an unstable or overly functional map.
The Open Group guide to defining, modeling, decomposing, and applying business capabilities. It provides a TOGAF-aligned comparison point for BIZBOK-based practice.
The Open Group guide to identifying, defining, decomposing, modeling, and mapping value streams to other business architecture elements.
A Guild webinar on common myths, state-based navigation, rapid drafting, validation, and practical use. It is especially useful when capabilities have crowded out the stakeholder-value view.
A Guild webinar linking customer and stakeholder value consumption to the capabilities and investments that create value. Use it to connect journey work with investment shaping.
A Guild webinar on stakeholder definitions, value-delivery roles, mapping principles, and alignment to the core architecture domains. Useful when the label customer hides a broader ecosystem.
The Open Group guide to identifying and representing the business information concepts needed by capabilities and value streams. Use it before jumping directly to data entities or applications.
The Open Group guide to mapping actors, organizational units, relationships, and the broader enterprise ecosystem beyond the reporting hierarchy.
A Guild webinar on business vocabulary, information concepts, capability assessment, value-stream navigation, and technology investment. Use it when data decisions lack business context.
A Guild learning module covering strategy, stakeholder, initiative, product, and policy mapping objectives with linked readings and recordings.
A Guild webinar on product, service, product line, product family, entitlement, and their role in transformation planning. The concepts generalize beyond financial services.
A Guild learning module on performance concepts, heat maps, measurement, and the application of performance management to architecture and portfolio analysis.
A Guild webinar comparing the Guild metamodel and BACM across organization, product, strategy, and initiative domains. Useful when adopting BACM-compliant tooling.
A Guild learning module covering roles, governance structures, team purpose, scaling, organizational application, and maturity assessment.
The Guild maturity model for assessing how a practice is established, governed, adopted, and institutionalized. Use it to frame a credible current state and next stage.
A Guild webinar clarifying the related but distinct roles of value streams, high-level business processes, and capabilities. Use it when teams treat value stream and process as synonyms.
A Guild webinar on aligning Lean Six Sigma practices with business architecture, with emphasis on complementary value-stream perspectives and distinct responsibilities.
The Open Group download page for the modular TOGAF Standard. Use it when business architecture must operate within a broader enterprise architecture method or governance structure.
The Open Group index for topic-specific guidance, including capabilities, business models, information mapping, organization mapping, and value streams.
The Open Group page for licensed access to the ArchiMate standard and related material. Use it when formal notation must span business, application, and technology architecture.
The Guild index for common and industry-specific capability and value-stream reference models. Treat every model as a starting hypothesis that still requires enterprise validation.
A Guild work-in-progress model containing strategic, core, and supporting capabilities plus value streams for cross-industry use.
The Guild transportation model with strategic, core, and supporting capabilities and a set of value streams. It is a useful baseline, not a substitute for enterprise-specific validation.
The Guild companion guide for interpreting and applying the Transportation Industry Reference Model when the model alone does not explain intended scope or usage.
Detailed definitions for PCF 8.0 process elements plus recommended indicators for each process group. Use it when a process taxonomy needs operational definitions and measures.
An archived starter pack with a Visio template, capability notation guidance, and heat-map options. Use it as a visual accelerator, not as a complete method.
IIBA’s freely available foundation for business analysis, covering needs, value, stakeholders, change, context, planning, elicitation, strategy analysis, requirements, and solution evaluation.
A free official glossary for business analysis terminology. Use it to align language around needs, requirements, designs, value, stakeholders, and change before detailed work begins.
IIBA’s central index for standards, articles, podcasts, webinars, competency guidance, and career material. Some resources are public and others require membership.
Free syllabi, glossaries, study guides, fact sheets, and other requirements-engineering references from the organization behind the CPRE standard.
A searchable official glossary spanning requirements elicitation, documentation, validation, management, modeling, and related concepts.
A practical university guide that connects business objectives and scope to stakeholder identification, elicitation, current and future states, requirements, and solution selection.
Downloadable templates for requirements specifications, use cases, process work, estimation, and related analysis tasks, supported by concise how-to guidance.
A clear guide to framing a discovery, researching users and constraints, challenging assumptions, and deciding whether a problem should move into solution exploration.
Federal discovery and design guides with operating checklists for framing work, planning research, identifying roles, synthesizing findings, and communicating what was learned.
Thirteen practical plays that start with understanding what people need and the whole service experience, then connect discovery to iterative delivery, accountability, and outcomes.
The Design Council’s open framework for alternating divergent and convergent work across Discover, Define, Develop, and Deliver. Useful for giving analysis and design work a shared shape.
A broad collection of step-by-step human-centered methods for interviews, observation, synthesis, co-creation, prototyping, testing, and preparing a solution to scale.
A free field guide with 57 methods, practical worksheets, mindsets, and case examples for moving from stakeholder research through ideation and implementation.
A curated collection of free templates for interviews, empathy maps, journey maps, service blueprints, research planning, workshops, and product discovery.
A free template and concise guide for connecting customer touchpoints to the people, processes, systems, and evidence that make a service work behind the scenes.
SEBoK guidance for defining the problem or opportunity, mission, objectives, measures, operational context, and solution-space boundaries before requirements are committed.
SEBoK guidance for identifying stakeholders and turning their expectations, constraints, risks, and operational concepts into an integrated set of needs.
A rigorous public handbook covering stakeholder expectations, technical requirements, logical decomposition, decision analysis, validation, verification, and requirements management.
Open guidance, presentation material, and tools for identifying stakeholders, assessing power and interest, and turning the map into a proportionate engagement plan.
The official UML specification page. Use it as the notation authority when analysis requires use cases, state models, sequence diagrams, or other formal system views.
The official DMN standard for making business decisions, their dependencies, decision tables, and expression logic understandable across business and technical roles.
The official SBVR standard for defining shared business vocabulary and expressing rules precisely without tying them to a specific technology implementation.
A free MIT Sloan course covering the Delta Model, Porter frameworks, resource-based strategy, customer value propositions, competencies, industry structure, and competitive positioning.
A free MIT Sloan course on the organizational conditions behind execution, including shared context, goals, resource reallocation, distributed leadership, and execution culture.
An openly licensed textbook covering external and internal analysis, business- and corporate-level strategy, competition, cooperation, international strategy, and execution.
The official Blue Ocean Strategy guide to visualizing the factors an industry competes on, comparing value curves, and making a differentiated strategic profile explicit.
The official ERRC tool for challenging an industry’s assumptions and deciding which value factors to eliminate, reduce, raise, or create.
A five-step OECD toolkit for challenging assumptions, building scenarios, stress-testing strategies, developing actions, and facilitating foresight work with real cases.
Twelve practical futures-thinking tools, plus suggested pathways for applying them to policy and strategy when uncertainty makes a single forecast inadequate.
A concise federal orientation to analyzing drivers and trends before strategy or planning, with references that connect foresight to organizational and workforce decisions.
A free method library and playbook organized around perspective, opportunity, solution, team, and vision, with instructions, examples, tips, and reusable templates.
UK government guidance for developing and appraising options by examining objectives, costs, benefits, risks, trade-offs, evidence, and value before a proposal is approved.
UK government guidance for building evaluation into the design, implementation, delivery, and review of policies, programs, projects, and services.
A practical introduction to connecting context, activities, assumptions, outputs, outcomes, and evidence so a proposed intervention can be challenged before delivery and evaluated afterward.
A GAO guide with 13 practices for planning results, identifying evidence needs, generating and using evidence, involving stakeholders, and sustaining organizational learning.
A practical six-step evaluation framework with cross-cutting actions and quality standards for designing evidence, engaging stakeholders, judging outcomes, and acting on findings.
A curated open-access library for developing and using logic models in program planning, implementation, communication, and evaluation.
A step-by-step guide for comparing options across qualitative and quantitative criteria, exposing trade-offs, applying swing weighting, and testing the sensitivity of a decision.
Try a broader business term, clear the content-type filter, or begin with the problem-based recipe finder.