OGB-001 TOGAF Business Architecture: The Level 1 Legacy and Today’s Path

OGB-001 TOGAF Business Architecture Part 1 belongs to the earlier TOGAF Business Architecture Level 1 credential based on the TOGAF Standard, Version 9.2. The Open Group still documents that credential, while also presenting a newer TOGAF Business Architecture Foundation certification based on the TOGAF Standard, 10th Edition. Candidates therefore need to understand the version and credential they are targeting before choosing study material.

The OGB-001 exam uses 30 simple multiple-choice questions in 45 minutes and has a 60 percent passing mark. Its purpose is narrower than full enterprise-architecture certification: it concentrates on business architecture concepts and techniques such as business modeling, capabilities, value streams, information mapping, organization mapping, business scenarios, and their relationship to the TOGAF Architecture Development Method.

That content remains useful because the underlying work—making strategy, value delivery, organizational structure, and capabilities explicit—continues in the newer business-architecture path. The mistake is not studying the older material; the mistake is assuming the older credential and the newer Foundation program have identical bodies of knowledge.

OGB-001 should be studied as a Version 9.2 credential with a newer successor path available

The Open Group describes TOGAF Business Architecture Level 1 as a credential based on Version 9.2 and explicitly notes the newer OGBA-101 TOGAF Business Architecture Foundation path based on the 10th Edition. A migration route exists for people who already hold the Level 1 credential. That creates a clear planning question: are you maintaining historical knowledge, completing an older requirement, or pursuing the current Foundation certification?

For a new learner with no organizational requirement for OGB-001, the newer Foundation path usually deserves first consideration because it aligns to the current body of knowledge. For someone whose employer, training record, or existing credential history references OGB-001, the older exam remains meaningful context. In either case, label notes by version so concepts from the two paths do not become silently blended.

Business capabilities describe what the enterprise must be able to do

Capability modeling is powerful because it separates a stable business ability from the organization chart or technology currently used to deliver it. A capability such as customer onboarding, claims management, product design, or regulatory reporting can remain strategically important even while processes, systems, teams, and suppliers change. That stability makes capability maps useful for investment and transformation discussions.

Exam preparation should go beyond recognizing the word capability. Practice distinguishing capabilities from processes, functions, organizational units, and services. Then consider decomposition and heat mapping: which capabilities are strategically differentiating, which are weak, which require investment, and how do those conclusions affect transformation priorities? The technique is valuable precisely because it gives leaders a view that is less volatile than a project plan.

Value streams show how value is created from the stakeholder’s perspective

A value stream is not simply a process diagram with different labels. It describes the stages through which value is delivered to a stakeholder. The distinction matters because business architecture is often trying to connect strategic intent to how value is experienced, not to document every operational step performed by every team.

Practice by choosing a familiar outcome—such as obtaining a mortgage, resolving an insurance claim, or launching a product—and describing the major value stages. Then map the capabilities required at each stage. This exposes gaps and dependencies more clearly than studying value-stream definitions in isolation and shows why value streams and capability maps become stronger when used together.

Business models frame how an enterprise creates and captures value

Business architecture needs a way to discuss customers, value propositions, partners, channels, resources, cost structures, and revenue logic without immediately descending into system design. Business-model techniques provide that strategic framing. They help architects understand what the organization is trying to accomplish before deciding how architecture should change.

When preparing, compare a business model with a capability map. The model explains the logic of the business; the capability map identifies abilities required to execute that logic. A change in customer segment or value proposition may leave some capabilities untouched while making others newly critical. This relationship is more important than memorizing a single canvas layout.

Information mapping and organization mapping answer different questions

Information mapping focuses on the business information needed by capabilities and value delivery, while organization mapping shows the organizational entities and relationships involved. Mixing the two can cause candidates to treat data ownership, team responsibility, and process execution as the same thing. They are related, but they are not interchangeable architectural views.

Use a simple case study to separate them. For customer onboarding, identify business information such as identity, consent, risk assessment, and account status. Then identify the organizational actors responsible for sales, compliance, operations, and service. Ask where the information is created, used, governed, or handed off. This produces a richer architecture picture than either map alone.

Business scenarios connect architecture work to a concrete business problem

The TOGAF Business Scenario method helps turn broad concerns into a structured understanding of the problem, environment, objectives, actors, and requirements. Its value is discipline: an architecture team can avoid jumping prematurely to a solution by first clarifying what the business is actually trying to change and who is affected.

For exam practice, take an ambiguous statement such as “improve customer experience” and make it specific. Which customers? Which interaction? What measurable outcome? Which actors participate? What current constraint prevents success? This exercise reinforces the difference between a strategic aspiration and an architecture requirement that can be analyzed and traced.

Business Architecture belongs inside the ADM rather than beside it

OGB-001 is not a free-standing business-analysis test. The techniques sit within the TOGAF approach to enterprise architecture. Candidates should understand how business architecture informs the Architecture Vision, Business Architecture work, requirements, opportunities, migration decisions, and stakeholder communication across the ADM cycle.

That connection becomes clearer when compared with TOGAF Enterprise Architecture Foundation. The enterprise-architecture path covers a broader method and governance context, while the business-architecture credential concentrates on business-oriented techniques. They overlap in language and method but serve different depths and professional needs.

A closed-book knowledge exam still benefits from applied exercises

Forty-five minutes for 30 questions is not severe timing, so most candidates gain more by improving conceptual distinctions than by drilling speed. Create comparison tables for capability versus process, value stream versus process, stakeholder versus actor, business model versus architecture model, and information map versus data model. Then test those distinctions through short scenarios.

After a missed question, do not record only the correct letter. Record the misconception. If you selected a process description when the question asked for a capability, write why the process is more operational and why the capability is more stable. This creates an error log that teaches the architecture rather than a memory of the answer bank.

One integrated exercise can cover most of the older Level 1 body of knowledge. Start with a strategic change, such as moving a retailer toward subscription services. Describe the business model, identify capabilities that become more important, sketch the value stream experienced by the customer, map the information required at each stage, and identify organizational units that own or support those capabilities. Then explain how the ADM would use the resulting architecture views.

This integrated approach also helps candidates see what changed between the older and newer business-architecture paths. The techniques are not discarded simply because a new qualification exists. Instead, the current program updates the body of knowledge and adds or reorganizes learning outcomes. Existing Level 1 holders therefore have a migration path rather than being told that their earlier knowledge has no value.

When using historical practice questions, avoid chasing exact scores as the main readiness signal. A learner can achieve a high percentage by remembering wording from an old pool while still confusing the purpose of capabilities, value streams, and organizational maps. Fresh case exercises are more revealing because they force the candidate to choose the right technique for a new business problem.

The credential is particularly relevant when business and technology teams struggle to translate strategy into a common structure. Business architects do not replace strategists, process owners, product managers, or enterprise architects; they provide models that allow those roles to reason about the same enterprise from compatible perspectives. That collaborative purpose should remain visible during preparation.

Candidates should also understand that business architecture operates at multiple levels of granularity. A capability map for an entire enterprise answers different questions from a decomposition focused on one product line. A value stream for acquiring a customer differs from a process map for validating one application. Choosing the right level keeps the architecture stable enough for strategic use while leaving operational detail to more appropriate models.

For final revision, build a one-page relationship map among the major techniques. Business models frame the operating logic; value streams show value delivery; capabilities show required abilities; information and organization maps expose supporting dependencies; business scenarios clarify problems and requirements; the ADM provides the controlled method in which those views are developed and used. If that chain is clear, individual definitions are much easier to retrieve.

Choose the credential that matches the work you need to perform now

The Open Group certifications now include both the older Business Architecture Level 1 route and the newer Foundation certification. That coexistence is why candidates should not rely on the presence of an exam code alone to infer that it is the preferred starting point for a new learner. Verify the current program guidance and any employer requirement before booking.

Whichever route applies, the professional objective is the same: make the business legible enough that strategy can be translated into controlled change. Capabilities, value streams, organizational maps, information maps, business models, and scenarios are useful because they expose different dimensions of that translation. A candidate who can use those techniques coherently has gained more than an exam result.