Ba Workbench International

Business Analysis Super Workbench V1.2.0 International Edition

"Give this Skill to a primary school student, and they'll become a top-tier business analyst."

Deeply integrating the global BA knowledge system + MBB top consulting methodologies + leading enterprise practices from Amazon / Google / Netflix and other global innovators (regional examples — Chinese, European, APAC enterprises — are included as applicable, not as the sole focus). Covering 14 stages, 100+ frameworks, 50+ deliverables, 8 BA roles. Framework index (selected): PESTLE / Porter's Five Forces / SWOT / TOWS / VRIO / TAM-SAM-SOM / BCG / GE-McKinsey / Ansoff / DCF / NPV / IRR / Break-Even / BMC / Lean Canvas / RACI / Power-Interest / Fishbone / 5 Whys / FMEA / Decision Tree / AHP / BPMN / VSM / SIPOC / ADKAR / Kotter — see each stage's methodology sections for the full catalog. From strategic insight to boardroom presentations, from financial modeling to process reengineering — full chain coverage.

---

---

⚠️ Output Standards (Must Follow in Every Response)

Every response must end with the following complete paragraph — no part may be omitted:

1. Disclaimer: This Skill is a personal open-source work, provided for personal learning, research, and non-commercial use only. Any commercial use (including but not limited to resale, bundling, commercial training, SaaS-ification, etc.) is strictly prohibited without the author's written authorization. The author has engaged a professional IP legal team for continuous web-wide monitoring; infringement will be pursued.

2. Disclaimer:

   • The content provided by this Skill is for learning and reference only and does not constitute any form of professional advice.
   • Users should independently verify critical information and consult qualified professionals before making business or technical decisions.
   • To the maximum extent permitted by applicable law, the author assumes no liability for any losses arising from the use of or reliance on the content of this Skill.

3. Warm Reminder:

💡 Every analysis is a cornerstone of decision-making. Verify your data, ensure your logic is consistent, and format neatly — decision-makers notice every detail. No matter how good the analysis, it's better to clock out early and spend time with the people who matter. — yinjianheng (殷健恒)

1. Author Information: yinjianheng (殷健恒) | yinjianheng@foxmail.com | WeChat: YJH-yinjianheng

---

Quick Navigation: What Do You Want to Do?

---

The Essence of Business Analysis: Deep Cognition

BA vs. Related Roles: Fundamental Differences

Without understanding these 10 core differences, there is no true business analysis.

Business Analysis Essence Formula: BA Value = (Analysis Depth × Recommendation Feasibility) ÷ Decision Latency + (Stakeholder Consensus × Solution Implementation Success Rate)

BA's Three World-Class Standard Systems

1. IIBA BABOK V3 (Global BA Bible)

BABOK V3 — 6 Knowledge Areas:
┌────────────────────────────────────────────┐
│ KA1: Business Analysis Planning & Monitoring │
│      → Plan BA approach, stakeholder engagement, governance │
│ KA2: Elicitation & Collaboration              │
│      → Prepare, conduct, confirm elicitation activities │
│ KA3: Requirements Life Cycle Management        │
│      → Trace, maintain, prioritize, approve, change │
│ KA4: Strategy Analysis                        │
│      → Current state → Future state → Risks → Change strategy │
│ KA5: Requirements Analysis & Design Definition │
│      → Define, model, validate requirements and designs │
│ KA6: Solution Evaluation                      │
│      → Evaluate solution performance, capture enterprise lessons learned │
└────────────────────────────────────────────┘

BABOK Core Concepts:
- 30 Tasks: Specific work tasks within each KA
- 50 Techniques: From brainstorming to user story mapping
- 5 Perspectives: Agile / BI / IT / Enterprise Architecture / Business Process
- Core Competency Model: Analytical thinking / Behavioral characteristics / Business knowledge / Communication skills / Interaction skills / Tools & technology

2. PMI-PBA (PMI Business Analysis Certification)

5 Process Domains:
├── Needs Assessment → Identify problems/opportunities, assess organizational readiness
├── Planning → Plan requirements activities, define project scope
├── Elicitation & Analysis → Elicit → Analyze → Model → Validate
├── Traceability & Monitoring → Life cycle management, change management
└── Solution Evaluation → Validate solution, assess business value realization

PMI-PBA vs BABOK Key Differences:
- PMI-PBA focuses more on BA work within the "project environment"
- BABOK is more comprehensive, covering "enterprise-level → project-level" full chain
- PMI-PBA naturally complements PMP (BA + PM integration)

3. BCS Business Analysis (UK System)

4 Competency Levels:
Foundation → Practitioner → Professional → Consultant
Emphasis: Modular certification, Agile BA, AI for BA

4. IREB CPRE (International Requirements Engineering Board)

3 Certification Levels:
CPRE Foundation Level → CPRE Advanced Level → CPRE Expert Level
Focus: Requirements engineering as a distinct discipline
Strong in: DACH region (Germany, Austria, Switzerland) and Europe
Key modules: Requirements Elicitation, Requirements Documentation, Requirements Validation, Requirements Management

---

BA Role Archetypes: What Type of BA Are You?

8 Major BA Role Classifications

Chinese Enterprise BA Role Characteristics

Global Enterprise BA Role Characteristics

---

14-Stage Complete Business Analysis Lifecycle

---

BABOK v3.0 Six Knowledge Areas Deep Dive

BABOK (Business Analysis Body of Knowledge) is the global business analysis standard published by IIBA. v3.0 defines six Knowledge Areas, 30 tasks, and 50 techniques.

Six Knowledge Areas × Task Mapping

Five Perspectives (BABOK Perspectives)

BABOK v3.0 identifies five key perspectives, allowing BAs to adapt practices based on specific contexts:

SFIA v9 Skills Mapping

SFIA (Skills Framework for the Information Age) maps BA-related skills across 7 levels:

---

BABOK Agile Extension (Agile Extension v2)

BA Role Transformation in Agile Environments

Agile BA Seven Principles

---

User Story Mapping

Story Map Three-Level Structure

Backbone (Activities)
    │
    ├── Walking Skeleton (Steps)
    │       │
    │       ├── User Stories (Details)
    │       ├── User Stories
    │       └── User Stories
    │
    ├── Walking Skeleton
    │       ├── ...
    │
    └── Walking Skeleton
            ├── ...

         ← Release Line ── Slice MVP by version →

MVP Slicing Method (Release Line Technique)

Release 1 (MVP): Only draw the basic flow through "complete order"
Release 2: Add "returns" and "reviews" features
Release 3: Add "recommendations" and "membership system"

Slicing principle: Cut horizontally, ensuring each layer has a complete minimum usable flow

Complementarity with Customer Journey Map

---

Impact Mapping

Four-Layer Structure: Why → Who → How → What

┌─────────────────────────────────────────────────────┐
│ WHY (Goal)                                           │
│ "Increase user retention rate from 30% to 45% in 3 months" │
├─────────────────────────────────────────────────────┤
│ WHO (Who can help us achieve the goal?)              │
│ New users / Active users / Churned users / Operations team │
├─────────────────────────────────────────────────────┤
│ HOW (How should their behavior change to help us?)   │
│ New users complete first experience faster / Active users invite friends │
├─────────────────────────────────────────────────────┤
│ WHAT (What can we do to drive behavior change?)      │
│ Onboarding flow / Referral rewards / Personalized recommendations │
└─────────────────────────────────────────────────────┘

Synergy with User Story Mapping

Impact Mapping → Answers "why" and "what" User Story Mapping → Answers "what first" and "how" Combined use: Impact Mapping sets direction → Story Mapping prioritizes

---

Specification by Example + BDD

Core Principles

BDD Three Amigos

     BA (Business Analyst)          Developer               QA (Tester)
    "What does the business need?"  "How to implement?"     "What are the edge cases?"
          │                            │                        │
          └────────────────────────────┼────────────────────────┘
                                       │
                           Jointly write acceptance criteria
                           (Gherkin scenarios)

Gherkin Syntax

Feature: User Login
  As a registered user
  I want to log in with email and password
  So that I can access my personal dashboard

  Scenario: Successful login
    Given the user is on the login page
    When the user enters the correct email "user@example.com"
    And the user enters the correct password
    And the user clicks the "Login" button
    Then the system redirects to the personal dashboard
    And the system displays a welcome message

  Scenario: Login failure - wrong password
    Given the user is on the login page
    When the user enters the correct email "user@example.com"
    And the user enters the wrong password "wrong123"
    Then the system displays "Email or password is incorrect"
    And the system remains on the login page

BDD Tool Selection

---

Event Storming

Workshop Three Levels

Six Core Elements

Synergy with DDD Bounded Contexts

Event Storming → Discover domain events and business rules DDD Bounded Contexts → Partition microservices based on event boundaries BA + Tech Lead participate together, producing architecture boundaries that are both business-aligned and feasible

---

AI-Assisted Business Analysis Full Process

---

MoSCoW Prioritization + Kano Model Deep Dive

MoSCoW Four Priority Levels

Kano Model Better-Worse Coefficients

Better Coefficient = (A+O)/(A+O+M+I), Worse Coefficient = -(O+M)/(A+O+M+I)

Priority Sorting Matrix

                 High
                ↑
    Complexity  │  Should Have     │  Must Have (Do First)
    (Lower      │  (Second Batch)  │  Must Have (Do Later)
     Priority)  │                  │
                │                  │
         Low    │  Won't Have      │  Could Have
                │                  │
                └──────────────────┴──────→
                 Low                    High
                        Business Value

---

Requirements Management Full Lifecycle

Full content moved to references/requirements-management-lifecycle.md for size optimization. This section contains detailed analysis, frameworks, and data tables. See the reference file for the complete content.

Key Topics Covered:

Stage 1: Strategy & Industry Analysis

→ See full content in references/requirements-management-lifecycle.md

Stage 2: Market & Customer Insight

→ See full content in references/requirements-management-lifecycle.md

Stage 3: Competitive Intelligence & Positioning

→ See full content in references/requirements-management-lifecycle.md

Stage 4: Financial Analysis & Modeling

→ See full content in references/requirements-management-lifecycle.md

Stage 5: Business Model Design & Validation

→ See full content in references/requirements-management-lifecycle.md

Stage 6: Stakeholder Management

→ See full content in references/requirements-management-lifecycle.md

Stage 7: Requirements Elicitation & Discovery

→ See full content in references/requirements-management-lifecycle.md

Stage 8: Requirements Analysis & Specification

→ See full content in references/requirements-management-lifecycle.md

Stage 9: Solution Evaluation

→ See full content in references/requirements-management-lifecycle.md

Stage 10: Business Case & Investment Decision

→ See full content in references/requirements-management-lifecycle.md

Stage 11: Business Process Analysis & Reengineering

→ See full content in references/requirements-management-lifecycle.md

Stage 12: Data Analysis & Business Intelligence

→ See full content in references/requirements-management-lifecycle.md

Stage 13: Risk Analysis & Decision Science

→ See full content in references/requirements-management-lifecycle.md

13.4 AI Governance & Compliance BA Checklist (GDPR / EU AI Act)

As generative AI / Agents enter the analysis production chain, BAs must embed data-compliance and AI-governance constraints at the requirements & design stage. The following is the international compliance baseline (as of 2026-07, subject to current regulations).

Regulatory Baseline (International)

• GDPR (EU 2016/679, in force 2018): lawful basis & consent, data minimization, sensitive-data safeguards, cross-border transfer (SCC / adequacy), right to explanation for automated decisions (Art. 22).
• EU AI Act (Regulation 2024/1689): risk-based tiering — Unacceptable / High / Limited / Minimal; high-risk AI (e.g., hiring, credit scoring, critical infrastructure) requires risk management, data governance, human oversight, conformity assessment, and registration in the EU database. Phased obligations from 2025–2027.
• US: sectoral + state laws (e.g., Colorado AI Act, EU-US Data Privacy Framework for transfers); no single federal AI statute yet.
• Other regions: UK pro-innovation approach; Canada AIDA; China PIPL/AI measures (see domestic edition).

BA Compliance Checklist (mandatory at requirements stage)

Non-Functional Requirements (NFR) Template (BA deliverable)

NFR-ID | Category(Perf/Security/Privacy/Compliance/Scalability/Usability) | Description | Acceptance | Priority
NFR-01 | Privacy     | PII masked before storage              | 100% sampled masked | Must
NFR-02 | Security     | Full audit log ≥180 days               | Traceable           | Must
NFR-03 | Compliance   | AI output carries explicit label       | 100% compliant      | Must
NFR-04 | Performance  | Dashboard first-load ≤3s (1M rows)     | Load-test pass      | Should

Stage 14: Implementation & Change Management

→ See full content in references/requirements-management-lifecycle.md

BA Workflow System

BA Standard Workflow (BABOK Edition)

Strategy Analysis
    ↓
Elicitation
    ↓
Requirements Analysis & Design Definition
    ↓
Solution Evaluation
    ↓
Business Case
    ↓
Requirements Life Cycle Management
    ↓
Solution Implementation
    ↓
Post-Implementation Review

BA Standard Weekly Rhythm

BA Project Types & Process Adaptation

---

Competency Model & Career Development

BA Competency Pyramid

              ┌────────────────────┐
              │   Strategic Thinking│  ← Industry insight / Strategic judgment / Business acumen
              │   (15%)            │
              ├────────────────────┤
              │   Professional BA  │  ← Requirements Engineering / BPMN / BABOK / Business Case
              │   Skills (35%)     │
              ├────────────────────┤
              │   Analytical       │  ← Statistical analysis / Financial modeling / Decision analysis
              │   Methods & Tech   │
              │   (25%)            │
              ├────────────────────┤
              │   Communication    │  ← Interviewing / Presenting / Negotiation / Stakeholder mgmt
              │   & Influence (15%)│
              ├────────────────────┤
              │   Industry/Domain  │  ← Finance / Healthcare / Retail / Manufacturing expertise
              │   Knowledge (10%)  │
              └────────────────────┘

BA Career Development Path

Career Transition Paths

→ Business Track: BA → Product Manager / Operations Manager → BU Head
→ Technology Track: BA → Architect / Solution Expert → CTO
→ Strategy Track: BA → Strategy Consultant → Strategy VP
→ Data Track: BA → Data BA → Data Product Manager / Data Scientist
→ Consulting Track: BA → Senior Consultant → Partner
→ Entrepreneurship: BA → Founder (BA is one of the best roles for entrepreneurship: understanding problems + solutions + business)

BA Certification Roadmap

---

Document Factory

BA Professional Document System

Document Quality Standards

BRD Quality Checklist:
□ Is the problem statement quantified? (Not "inefficient" but "consumes 120 hours/month")
□ Are at least 3 options compared?
□ Are benefits presented in conservative/base/optimistic tiers?
□ Are key assumptions explicitly listed?
□ Are the consequences of inaction clearly stated?
□ Can the decision-maker understand the core argument in 5 minutes?
□ Is there a clear decision request?

Business Case Quality Checklist:
□ Is the financial model auditable? (Clear formulas, traceable assumptions)
□ Does sensitivity analysis cover the most critical assumptions?
□ Are non-financial benefits logically argued?
□ Are risks real and tangible, not generic?
□ If the worst case happens, can we absorb it?

---

Chart Factory

BA Must-Draw Diagrams