5.2 Define Future State

5.2 Define Future State

Purpose of Defining Future State in BABOK v3

The primary purpose of Define Future State (BABOK Guide v3 Task 6.2) is to determine the set of conditions necessary to satisfy the business need. Once the current state baseline and underlying root causes are understood (Task 6.1), the business analyst works with executive sponsors and key stakeholders to define what success looks like in clear, measurable terms.

Defining the future state requires creating a comprehensive description of the desired enterprise capabilities, business outcomes, organizational structures, process flows, data architectures, and technical infrastructure. The target future state provides the destination toward which all change initiatives, solution designs, and transition releases are aligned.

---

Establishing SMART Business Goals and Measurable Objectives

A Business Goal is a broad, high-level statement of direction or intent that the enterprise seeks to achieve. A Business Objective is a specific, lower-level statement that quantifies the goal and establishes clear measurement criteria.

To ensure business objectives effectively guide solution evaluation and strategy analysis, BABOK v3 mandates that objectives align with the SMART framework:

• Specific: Clearly defines a targeted area for improvement without ambiguity (e.g., "Reduce online loan application processing time").
• Measurable: Defines a concrete quantitative indicator or metric to track progress (e.g., "Reduce application processing time from 48 hours to under 4 hours").
• Achievable: Set realistically within the enterprise's resource, financial, and technical constraints.
• Relevant: Directly aligns with top-level strategic goals and satisfies the core business need.
• Time-bound: Specifies a clear target completion date or timeframe (e.g., "Achieve target by end of Q3 2027").

---

Defining Solution Scope and Context Boundaries

Solution Scope establishes the conceptual boundaries of the proposed change. It defines the set of capabilities, functions, business processes, data flows, and organizational units that will be modified or impacted by the solution, as well as what remains explicitly out of scope.

Key techniques for defining solution scope include:

• Functional Decomposition: Breaking down high-level business capabilities into sub-functions, processes, and technical features to establish scope inclusion.
• Context Diagram: High-level visual diagram depicting the solution as a single central box interacting with external entities (users, external systems, regulatory bodies) via data inputs and outputs.
• Scope Matrix (In/Out Matrix): Formal table listing specific features, business units, or process steps alongside an explicit designation of "In Scope", "Out of Scope", or "Future Phase".

---

Managing Enterprise Constraints and Assumptions

Every future state operates within environmental boundaries. Business analysts must identify, document, and manage constraints and assumptions throughout strategy analysis:

• Constraints: Real limitations placed on the solution or implementation strategy that cannot be changed by the project team. Constraints can be business-driven (e.g., maximum budget cap of $2.5M), technical (e.g., must run on legacy mainframes), regulatory (e.g., mandatory compliance by January 1), or schedule-driven (e.g., system launch prior to peak holiday trading season).
• Assumptions: Statements believed to be true for planning purposes, but which carry uncertainty and must be validated. For example, assuming an existing third-party payment API will maintain 99.9% uptime. Unvalidated assumptions represent potential project risks.

---

Gap Analysis: Bridging Current State to Target Capabilities

Gap Analysis is the core analytical technique used to compare the current state baseline (Task 6.1) against the defined future state (Task 6.2). The gap analysis highlights missing capabilities, process inefficiencies, data deficiencies, and technology shortfalls that must be bridged.

┌───────────────────────────┐      GAP ANALYSIS      ┌───────────────────────────┐
│       CURRENT STATE       │ ─────────────────────> │       FUTURE STATE        │
│ Baseline Capabilities,    │   Identifies Missing   │ Target Capabilities,      │
│ Legacy Tools, Bottlenecks │   Capabilities & Delta │ SMART Goals, Solution Scope│
└───────────────────────────┘                        └───────────────────────────┘

The output of gap analysis directly informs Task 6.4 (Define Change Strategy) by identifying the exact work packages and capability enhancements required to transition the enterprise.

---

Quantifying Value Propositions and Desired Outcomes

In the BACCM model, the future state is defined by the Value delivered to stakeholders. Value propositions can be:

• Tangible (Quantitative): Increased net revenue, operating cost reductions, reduced transaction cycle times, or lower error rates.
• Intangible (Qualitative): Improved brand reputation, higher employee job satisfaction, enhanced regulatory goodwill, or reduced enterprise risk exposure.

---

CBAP Exam Tips & Strategic Guidance

• Goal vs. Objective Distinction: Exam questions frequently present vague goals and ask the candidate to select the true SMART objective. Look for options containing explicit numerical metrics, target dates, and scope boundaries.
• Scope Creep vs. Scope Definition: When defining future state, ensure the solution scope directly satisfies the business need without introducing unrequested "gold-plating" features.