Business Analysis 101: Strategy Analysis Defining Future State Vision Goals Objectives SMART

What This Is

Defining the future state is the BA’s way of painting a clear picture of where the organization wants to be after a change initiative. It captures the vision, high‑level goals, and measurable objectives that guide all downstream analysis work. In a CRM‑implementation project, the future state might be “a single‑view of the customer that enables sales reps to close deals 15 % faster and reduces duplicate data entry to zero.”

Key Terms & Techniques

• Vision Statement – A concise, inspirational description of the desired end‑state. Business Analysis Knowledge Area (KA): Strategy Analysis. Typical deliverable: Vision Document.
• Goal – A broad, strategic outcome the organization wants to achieve (e.g., “increase market share”). KA: Strategy Analysis. Deliverable: Goal hierarchy (Goal → Objective).
• Objective – A specific, measurable target that supports a goal (e.g., “grow market share by 3 % in FY 2027”). KA: Strategy Analysis. Deliverable: Objectives list with success criteria.
• SMART Criteria – A checklist to make objectives Specific, Measurable, Achievable, Relevant, Time‑bound. KA: Strategy Analysis. Deliverable: SMART‑checked objectives table.
• Business Capability Map – Visual representation of what the organization must be able to do to reach the future state. KA: Business Architecture. Deliverable: Capability map diagram.
• Future‑State Process Model – BPMN or flowchart showing how work will be performed after the change. KA: Business Process Analysis. Deliverable: Future‑state process diagram.
• Benefit‑Realization Plan – Links each objective to expected benefits, owners, and measurement methods. KA: Strategy Analysis. Deliverable: Benefits register.
• Stakeholder‑Value Matrix – Matrix that aligns stakeholder needs with future‑state goals to ensure buy‑in. KA: Stakeholder Analysis (part of Strategy Analysis). Deliverable: Value‑alignment matrix.
• Gap Analysis – Comparison of current‑state artifacts (processes, capabilities) with the defined future state to surface work needed. KA: Business Analysis Planning & Monitoring. Deliverable: Gap analysis report.
• MoSCoW Prioritization – Classifies future‑state requirements into Must, Should, Could, Won’t – useful when objectives out‑number resources. KA: Requirements Analysis. Deliverable: Prioritized requirement list.
• Balanced Scorecard (BSC) – Framework that translates objectives into performance metrics across financial, customer, internal, and learning perspectives. KA: Strategy Analysis. Deliverable: BSC scorecard.

Step‑by‑Step Process (Future‑State Definition)

1. Engage Stakeholders & Capture Vision – Run a vision‑workshop (or interview key sponsors) to surface the high‑level “why” behind the change.
2. Elicit Goals & Draft Objectives – Use techniques such as “5 Whys” and “Goal‑Question‑Metric” to turn the vision into concrete goals and SMART‑checked objectives.
3. Model Future State – Create a capability map and/or future‑state process diagrams (BPMN) that illustrate how the organization will operate to meet the objectives.
4. Validate & Refine – Present the models to the stakeholder group, capture feedback, and iterate until consensus is reached.
5. Develop Benefit‑Realization & Gap Plans – Link each objective to measurable benefits, assign owners, and document the gaps that must be closed (gap analysis).
6. Baseline & Communicate – Obtain formal sign‑off (baseline) on the future‑state artifacts and distribute a concise “Future‑State Summary” to the project team.

Common Mistakes

Certification Exam Tips

1. Know the Knowledge‑Area Mapping: Future‑state definition lives in Strategy Analysis (vision, goals, objectives) and spills into Business Architecture (capability maps) and Business Process Analysis (future‑state processes). Questions that ask “Which KA produces the Vision Document?” answer Strategy Analysis.
2. Watch the “Next Step” Trap: If a question describes a completed vision workshop, the next logical BA activity is usually eliciting goals/objectives (not yet writing requirements).
3. SMART is a criterion, not a technique: The exam may list “SMART” alongside MoSCoW, RACI, etc. Remember it’s a validation checklist for objectives, not a prioritization method.
4. Benefit‑Realization vs. Requirements Traceability: Benefits registers are output of Strategy Analysis, while traceability matrices belong to Requirements Analysis. Distinguish them to avoid mixing up deliverables.

Quick Check Questions

1. Scenario: After a vision workshop, the sponsor asks for a concrete way to show how the new CRM will support “faster deal closure.” Which artifact should the BA produce next?
   Answer: Future‑State Process Model (BPMN diagram).
   Justification: It visualizes the end‑to‑end workflow that directly ties the vision to operational steps (BABOK §7.3).

2. Scenario: The team has drafted three objectives, but the project manager worries they are not measurable. Which technique will the BA apply to fix this?
   Answer: SMART Criteria.
   Justification: SMART checks each objective for Specific, Measurable, Achievable, Relevant, and Time‑bound attributes (BABOK §7.2).

3. Scenario: Stakeholders disagree on which future‑state capability should be prioritized. Which prioritization technique is most appropriate?
   Answer: MoSCoW.
   Justification: MoSCoW classifies capabilities/requirements into Must, Should, Could, Won’t, helping resolve priority conflicts (BABOK §7.4).

Last‑Minute Cram Sheet (10 One‑Liners)

1. Strategy Analysis = Vision, Goals, Objectives, Benefits, and Change Scope.
2. SMART = checklist for objectives (not for requirements). ⚠️
3. Vision Document is the output of the “Define Vision” task (KA 7).
4. Capability Map belongs to Business Architecture, not to Requirements Analysis.
5. Future‑State Process Model = BPMN diagram that shows “how” work will be done after change.
6. Benefit‑Realization Plan links each objective to a measurable benefit and owner.
7. Gap Analysis = input: Current‑state artifacts; output: Gap report (KA 5).
8. MoSCoW = prioritization technique for future‑state requirements/capabilities.
9. Balanced Scorecard = translates objectives into performance metrics across four perspectives.
10. Baseline = formal sign‑off on future‑state artifacts; protects scope from later creep (BABOK §5.5).