Biz Bsc

Balanced Scorecard (BSC)

Overview

The Balanced Scorecard translates strategy into objectives and measures across four perspectives, creating a cause-and-effect chain: Learning & Growth → Internal Processes → Customer → Financial. It answers "are we executing our strategy?" not just "are we profitable?"

When to Use

Trigger conditions:

• User needs to define strategic KPIs beyond financial metrics
• User wants to connect operational activities to strategic goals
• User building a strategy map or performance dashboard
• User says "our KPIs don't reflect our strategy" or "how do we measure execution"

When NOT to use:

• For one-time strategic analysis → use SWOT or Porter's
• For project-level OKRs → use OKR framework
• When only financial performance matters (rare)

Framework

IRON LAW: Four Perspectives, Causally Linked

The BSC is NOT four independent lists of KPIs. The four perspectives form
a CAUSAL CHAIN:

  Learning & Growth → Internal Processes → Customer → Financial

Investing in employee skills (L&G) improves process quality (Internal),
which increases customer satisfaction (Customer), which drives revenue (Financial).

If your BSC has no causal links between perspectives, it's just a KPI dump,
not a Balanced Scorecard.

IRON LAW: Each Objective Gets a Measure, Target, and Initiative

An objective without a measure is a wish.
A measure without a target is a statistic.
A target without an initiative is a hope.

Every BSC objective MUST have all three: measure (how to track), target
(what success looks like), and initiative (what action drives it).

Step 1: Clarify the Strategy

Before building the BSC, state the strategy in one sentence:

• "Grow through customer intimacy" (relationship-driven)
• "Win through operational excellence" (efficiency-driven)
• "Lead through product innovation" (differentiation-driven)

The strategy determines which objectives dominate each perspective.

Step 2: Define Objectives per Perspective

Financial (lagging indicators — outcomes):

• Revenue growth, profitability, cost efficiency, ROI, cash flow
• Question: "What financial results must we deliver to satisfy stakeholders?"

Customer (leading indicators for financial):

• Customer satisfaction, retention, acquisition, market share, NPS
• Question: "What must we deliver to customers to achieve financial goals?"

Internal Processes (leading indicators for customer):

• Process efficiency, quality, cycle time, innovation pipeline
• Question: "What processes must we excel at to satisfy customers?"

Learning & Growth (foundation — enablers):

• Employee skills, culture, technology infrastructure, knowledge management
• Question: "What capabilities must we build to improve our processes?"

Step 3: Build the Strategy Map

Draw cause-and-effect arrows linking objectives across perspectives:

[L&G] Train sales team on consultative selling
  ↓
[Internal] Reduce sales cycle from 60 to 30 days
  ↓
[Customer] Increase customer satisfaction score to 4.5/5
  ↓
[Financial] Grow revenue 20% YoY

Every objective should connect to at least one objective in another perspective. Orphan objectives indicate a gap in strategic logic.

Step 4: Assign Measures, Targets, and Initiatives

For each objective, define:

• Measure: Specific metric (quantitative preferred)
• Target: Concrete threshold with timeframe
• Initiative: Action or project that drives the metric

Output Format

# Balanced Scorecard: {Organization}

## Strategy Statement
{One-sentence strategy}

## Strategy Map

{L&G objectives} → {Internal Process objectives} → {Customer objectives} → {Financial objectives}

## Scorecard

### Financial Perspective
| Objective | Measure | Target | Initiative |
|-----------|---------|--------|-----------|
| {objective} | {metric} | {value by when} | {action} |

### Customer Perspective
| Objective | Measure | Target | Initiative |
|-----------|---------|--------|-----------|
| {objective} | {metric} | {value by when} | {action} |

### Internal Process Perspective
| Objective | Measure | Target | Initiative |
|-----------|---------|--------|-----------|
| {objective} | {metric} | {value by when} | {action} |

### Learning & Growth Perspective
| Objective | Measure | Target | Initiative |
|-----------|---------|--------|-----------|
| {objective} | {metric} | {value by when} | {action} |

## Causal Chain Validation
{Explain how L&G → Internal → Customer → Financial links work}

Examples

Correct Application

Scenario: BSC for a B2B SaaS company with strategy: "Grow through product-led growth"

Causal chain: Analytics training (L&G) → faster, data-driven releases (Internal) → higher retention from better product (Customer) → ARR growth (Financial) ✓

Incorrect Application

What went wrong:

• Listed 15 KPIs with no causal links → KPI dump, not a BSC. Violates Iron Law: perspectives must be causally linked.
• Financial: "Revenue $10M" with no measure, target timeframe, or initiative → Violates Iron Law: need measure + target + initiative.

Gotchas

• Too many objectives: 3-5 per perspective is ideal. More than 5 loses focus. The BSC is about strategic priorities, not a comprehensive KPI list.
• All lagging indicators: If every measure is a lagging indicator (revenue, satisfaction score), you can't manage proactively. Balance with leading indicators (training hours, pipeline quality).
• L&G as an afterthought: Teams fill Financial and Customer easily but struggle with L&G. This perspective is the foundation — skip it and the whole chain breaks.
• Cascading confusion: A corporate BSC and a department BSC should be linked but not identical. Department objectives should contribute to corporate objectives, not copy them.
• BSC ≠ OKR: BSC is a strategic management system (4 perspectives, causal links, strategy map). OKR is a goal-setting framework (objectives + key results). They can coexist but serve different purposes.

References

• For Strategy Map templates and examples, see references/strategy-maps.md
• For comparison with OKR and other performance frameworks, see references/framework-comparison.md

以下是 biz-bsc/examples/sample_scenario.md 的內容：

# Example: 台灣 B2B SaaS 公司的平衡計分卡建置

## Scenario

**公司：** Flowmix（台灣新創，B2B 工作流程自動化 SaaS）
**規模：** 45 人，ARR 約 NT$28M，主要客戶為中型製造業與物流業
**提問者：** 共同創辦人兼 COO

> 「我們現在有一堆 KPI，但感覺各部門在各跑各的。業務在衝新客數、產品在衝功能上線速度、客服在衝工單關閉率。到了季末大家數字都達標，但 ARR 沒長、NRR 在掉。我想用 BSC 把這些指標串起來，但不知道從哪裡下手。」

背景補充：
- 策略方向：「以產品黏著度驅動成長」（Product-Led Growth）
- 近 2 季 NRR 從 108% 掉到 97%，主因是中型客戶在試用期後的轉換率偏低
- 產品 bug 回報率高，工程團隊缺乏數據工具，改版靠直覺
- 員工滿意度調查顯示：工程師覺得「不知道用戶在用哪些功能」

---

## Analysis

### Step 1：確認策略句

根據 COO 描述，策略句定為：

> **「以產品體驗黏著度驅動 ARR 成長，核心是降低試用轉換流失。」**

這不是「廣撒網拉新客」策略，而是「讓現有與新進客戶留下來、用深、往上賣」策略。因此 BSC 的重心應放在 **Customer 與 Internal Process** 兩個視角，L&G 的核心投資是產品分析能力。

---

### Step 2：各視角目標定義

#### Financial（落後指標）
COO 說 ARR 沒長、NRR 在掉。財務目標鎖定：
- 提高 NRR（現有客戶擴張 > 流失）
- 提高 ARR（在 NRR 回穩後才有健康成長基礎）

#### Customer（財務的領先指標）
NRR 掉的直接原因是試用轉換率低。客戶視角目標：
- 提高試用轉正率
- 提高核心功能採用深度（Feature Adoption）

#### Internal Process（客戶體驗的領先指標）
產品 bug 多、靠直覺改版 → 流程目標：
- 縮短 bug 修復週期
- 建立數據驅動的功能優先排序機制

#### Learning & Growth（所有視角的根基）
工程師沒有數據工具、不知道用戶在用哪些功能 → 能力目標：
- 建立產品分析能力（Amplitude）
- 導入使用者旅程追蹤

---

### Step 3：策略地圖（因果鏈）

[L&G] 工程 & 產品團隊完成產品分析工具培訓 ↓ [Internal] 以用戶行為數據驅動功能排序；Bug P1 修復週期縮短 ↓ [Customer] 試用期核心功能採用率提升；試用轉正率提高 ↓ [Financial] NRR 回升至 108%+；ARR 成長 30% YoY

**邏輯驗證：**
- 若工程師看不到用戶行為（L&G缺口），就無法修對的 bug、排對的功能（Internal缺口）
- 若功能體驗差、bug 多（Internal缺口），試用客戶就不會轉正（Customer缺口）
- 若轉正率低、現有客戶流失（Customer缺口），NRR 與 ARR 就不會成長（Financial缺口）

---

### Step 4：逐目標填入指標、目標值、行動方案

注意：每個目標必須有**指標（Measure）+ 目標值（Target）+ 行動（Initiative）**三件套，缺一不可。

---

## Result

# Balanced Scorecard：Flowmix

## Strategy Statement
以產品體驗黏著度驅動 ARR 成長，核心是降低試用期客戶流失、提高功能採用深度。

## Strategy Map

[L&G] 產品分析能力培訓 → 用戶旅程追蹤上線 ↓ [Internal] Bug P1 修復週期縮短 → 功能排序數據化 ↓ [Customer] 試用期核心功能採用率提升 → 試用轉正率提高 ↓ [Financial] NRR 回升 → ARR 年成長 30%

## Scorecard

### Financial Perspective

| 目標 | 指標 | 目標值 | 行動方案 |
|------|------|--------|---------|
| 提高客戶擴張收益 | Net Revenue Retention (NRR) | ≥ 108%（Q3 2026 前） | 客戶成功計畫 + 功能體驗改善 |
| 提高年度經常性收益 | Annual Recurring Revenue (ARR) | NT$36M（2026 年底） | 以 NRR 回穩為前提，再啟動新客拓展 |

### Customer Perspective

| 目標 | 指標 | 目標值 | 行動方案 |
|------|------|--------|---------|
| 提高試用轉正率 | Trial-to-Paid Conversion Rate | 從 31% 提升至 48%（Q3 2026） | 試用期第 7/14/21 天自動 check-in + onboarding flow 優化 |
| 提高核心功能採用深度 | Core Feature Adoption Rate（啟用 3+ 核心功能的帳戶比例） | 從 40% 提升至 65%（Q3 2026） | In-app 功能引導 + 使用者旅程重新設計 |

### Internal Process Perspective

| 目標 | 指標 | 目標值 | 行動方案 |
|------|------|--------|---------|
| 縮短關鍵 Bug 修復週期 | P1 Bug Mean Time to Resolution (MTTR) | 從 6 天縮短至 2 天（Q2 2026） | 導入 bug triage SLA + on-call 輪值制度 |
| 數據驅動功能排序 | % 功能 roadmap 項目有用戶行為數據佐證 | 從 15% 提升至 80%（Q2 2026） | 每兩週 product analytics review 會議制度化 |

### Learning & Growth Perspective

| 目標 | 指標 | 目標值 | 行動方案 |
|------|------|--------|---------|
| 建立產品分析能力 | 工程 + 產品人員完成 Amplitude 培訓比例 | 100%（Q1 2026 底） | 4 週內部 bootcamp + 外部顧問 2 次工作坊 |
| 建立完整用戶旅程追蹤 | 關鍵事件（Events）埋點完成率 | 核心 30 個事件 100% 覆蓋（Q1 2026 底） | 由資深工程師主導 tracking plan，納入 sprint definition of done |

## Causal Chain Validation

**L&G → Internal：**
工程與產品團隊完成 Amplitude 培訓、埋點覆蓋核心事件後，才能看到用戶在哪一步流失、哪些功能沒被採用。沒有這個基礎，功能排序就是靠感覺，bug 修復也不知道影響範圍。

**Internal → Customer：**
P1 bug 從 6 天修到 2 天，直接降低試用期客戶因體驗問題放棄的比例。功能排序數據化後，roadmap 優先修用戶真正卡關的地方，核心功能採用率才能提升。

**Customer → Financial：**
試用轉正率從 31% 到 48%，直接增加新增 MRR。核心功能採用率從 40% 到 65%，代表客戶黏著度提升，流失率下降，NRR 從 97% 回升至 108%+ 的基礎才成立。ARR 成長 30% 是這條因果鏈全部打通後的結果，而非起點。

---

> **執行優先順序建議：** 先打通 L&G（Q1），再修 Internal（Q2），Customer 指標在 Q2-Q3 才會反應。不要因為 Financial 指標 Q1 沒動就砍 L&G 投資——那正是因果鏈的設計，落後指標本來就最後才動。

請將上述內容寫入 biz-bsc/examples/sample_scenario.md。

Framework Comparison: BSC vs. OKR vs. MBO vs. KPI Dashboard

This document compares four common performance frameworks so you can advise on which to use, when to combine them, and how to avoid conflating them.

---

The Four Frameworks at a Glance

---

BSC vs. OKR — The Most Common Confusion

Structural Difference

BSC is a strategic management system. It forces you to answer: does our daily work connect to our strategy? It requires: 1. A strategy statement 2. Four causally linked perspectives 3. Objectives + Measures + Targets + Initiatives per cell

OKR is a goal-setting framework. It forces ambitious, time-boxed commitment. It requires: 1. An Objective (qualitative, inspirational) 2. 2–5 Key Results per Objective (measurable, binary success/fail) 3. No mandatory causal structure across areas

A Worked Example: Same Company, Two Frameworks

Scenario: B2B SaaS company, strategy "Grow through product-led growth"

BSC version:

The causal chain is explicit: training → faster data-driven releases → retention → ARR.

OKR version (same quarter):

O: Make our product the stickiest in the mid-market segment
  KR1: Net Revenue Retention ≥ 110% by end of Q2
  KR2: Time-to-value for new accounts ≤ 14 days (from 30)
  KR3: Product-qualified leads from in-app triggers ≥ 200/month

O: Ship faster without breaking things
  KR1: Release cycle ≤ 2 weeks by Q2
  KR2: Production incidents caused by releases < 2/quarter
  KR3: CI/CD pipeline coverage ≥ 90% of services

What's missing from OKR alone: No explicit link between "Ship faster" and "Sticky product." No L&G investment tracked. No strategy map showing why these OKRs were chosen. If leadership changes priorities next quarter, the OKRs reset — the strategic logic is lost.

What's missing from BSC alone: No ambitious stretch targets. No quarterly cadence to review and adjust. The BSC Initiatives are vague compared to OKR Key Results.

---

When to Use Which

Decision Rules

Use BSC when:

• The organization lacks strategic alignment (different teams optimize for different things)
• You need to explain why certain KPIs matter, not just what they are
• Executive team wants a board-level view of strategy execution
• The company has never connected HR/L&G investment to business outcomes
• Time horizon is 2+ years

Use OKR when:

• Teams need clarity on quarterly priorities and are willing to be held accountable
• Culture supports transparent goal-sharing across functions
• Growth environment where speed and ambition matter more than precision
• You already have a strategy (BSC or otherwise) and need execution discipline per cycle

Use MBO when:

• Primary need is manager-employee performance reviews
• Organization is hierarchical and annual review cycles are the norm
• Goals are individual-level, not team or cross-functional

Use KPI Dashboard when:

• Operational monitoring, not strategic direction
• You need real-time or daily alerts (uptime, support tickets, conversion)
• Audience is individual contributors, not leadership

Use BSC + OKR together when:

• BSC is the 3-year strategic anchor; OKRs are the quarterly execution cadence
• Corporate BSC → Department OKRs → Individual Key Results cascade

---

BSC + OKR Integration Pattern

This is the most common hybrid in practice. The mapping is:

BSC Layer (annual/multi-year)         OKR Layer (quarterly)
─────────────────────────────         ──────────────────────
Strategy Statement                 →  Company-level O (North Star)
Financial Objectives               →  Finance team OKRs
Customer Objectives                →  Growth/CX team OKRs
Internal Process Objectives        →  Engineering/Ops team OKRs
L&G Objectives                     →  People/HR team OKRs

BSC Initiatives                    →  OKR Key Results (specific, time-boxed)
BSC Targets (annual)               →  OKR Key Results (quarterly milestones)

Integration rule: Every company-level OKR should map to at least one BSC objective. If an OKR cannot be traced to the BSC, either the BSC is incomplete or the OKR is off-strategy.

Anti-pattern: Writing OKRs that only track Financial perspective metrics. This recreates the pre-BSC mistake of managing only what finance reports. If all your OKRs are revenue or cost, you have no leading indicators.

---

BSC vs. MBO

MBO (Management by Objectives) is frequently confused with BSC because both use "objectives." The difference is structural.

MBO predates BSC. Kaplan and Norton designed BSC partly because MBO was producing locally-optimized, strategically-disconnected results. If a client says "we already do MBO," the BSC is an upgrade to that system, not a replacement for performance reviews.

---

BSC vs. KPI Dashboard

A KPI dashboard is a monitoring tool. A BSC is a strategy execution tool. They are not competitors.

KPI Dashboard alone fails when:

• Metrics are chosen bottom-up ("what can we measure?") rather than top-down ("what does our strategy require?")
• No target exists for each metric — the dashboard shows numbers, not health
• Metrics have no owner and no initiative — you see a problem but no one acts

*The BSC produces the right KPIs for a dashboard.* The typical sequence: 1. Build BSC → identify the 15-25 strategic measures 2. Add operational monitors (uptime, NPS raw score, cash balance) that aren't in BSC 3. Dashboard = BSC measures + operational monitors, separated visually

If someone shows you a 60-metric dashboard and calls it a BSC, it is not a BSC. It is a KPI dump. The BSC produces 3–5 objectives per perspective × 4 perspectives = 12–20 measures maximum.

---

Choosing in Practice: Quick Decision Table

Does the client have a clear, stated strategy?
├── No  → Start with strategy work (SWOT, Porter's) before any framework
└── Yes → Continue

Do they need to align multiple departments to that strategy?
├── Yes → Use BSC (strategy map + four perspectives)
└── No  → Continue

Do they need quarterly goal-setting and accountability cycles?
├── Yes → Use OKR (with BSC as anchor if strategy alignment is also needed)
└── No  → Continue

Do they need individual performance management?
├── Yes → Use MBO (or cascade from BSC/OKR)
└── No  → Continue

Do they just need to monitor operations day-to-day?
└── KPI Dashboard (feed it metrics from BSC if BSC exists)

---

Common Mistakes When Comparing Frameworks

Mistake 1 — Treating OKR as a replacement for BSC OKR has no four-perspective structure and no causal chain requirement. You can write OKRs entirely in the Financial perspective and call it done. BSC won't allow that. They solve different problems.

Mistake 2 — Implementing both BSC and OKR independently Two strategy systems running in parallel without integration means each team gets two sets of goals. The integration rule above (BSC objectives → OKR Key Results) avoids this. One strategy, two cadences.

Mistake 3 — Calling a spreadsheet of KPIs a BSC The label "Balanced Scorecard" requires: four perspectives, causal links, and objectives with all three of measure + target + initiative. Without all three properties, rename it a KPI tracker to be accurate.

Mistake 4 — Using BSC for team-level goal-setting BSC is designed for organization or business-unit level. A five-person team does not need a four-perspective strategy map. OKR or simple goal lists work better at that granularity. Cascading BSC to team level produces bureaucracy, not clarity.

Strategy Maps

A strategy map is the visual representation of the causal chain in a BSC. It shows how the organization creates value by linking objectives across all four perspectives with directional arrows.

The map answers: "If we invest in X, it will improve Y, which will drive Z." Without a strategy map, a BSC is a spreadsheet. With one, it's a testable theory of your business.

---

Anatomy of a Strategy Map

┌─────────────────────────────────────────────────────────────┐
│  FINANCIAL PERSPECTIVE                                      │
│  ┌──────────────────┐     ┌──────────────────┐             │
│  │  Revenue Growth  │     │  Cost Efficiency │             │
│  └────────▲─────────┘     └────────▲─────────┘             │
└───────────┼─────────────────────────┼───────────────────────┘
            │                         │
┌───────────┼─────────────────────────┼───────────────────────┐
│  CUSTOMER PERSPECTIVE               │                       │
│  ┌────────┴────────┐   ┌────────────┴──────┐               │
│  │  Customer Acq.  │   │  Customer Retention│               │
│  └────────▲────────┘   └────────▲──────────┘               │
└───────────┼──────────────────────┼────────────────────────-─┘
            │                      │
┌───────────┼──────────────────────┼───────────────────────────┐
│  INTERNAL PROCESS PERSPECTIVE    │                           │
│  ┌────────┴────────┐   ┌─────────┴─────────┐                │
│  │  Sales Process  │   │  Service Quality   │                │
│  └────────▲────────┘   └─────────▲─────────┘                │
└───────────┼────────────────────────┼──────────────────────────┘
            │                        │
┌───────────┼────────────────────────┼──────────────────────────┐
│  LEARNING & GROWTH PERSPECTIVE     │                          │
│  ┌────────┴────────┐   ┌───────────┴───────┐                 │
│  │  Sales Training │   │  CRM Deployment   │                 │
│  └─────────────────┘   └───────────────────┘                 │
└──────────────────────────────────────────────────────────────┘

Rules for drawing the map: 1. Arrows always point upward (L&G → Internal → Customer → Financial) 2. Every objective must have at least one arrow entering or leaving it 3. An objective with no arrows is an orphan — either cut it or identify the missing link 4. A Financial objective with no incoming arrows means you haven't explained how you'll achieve it

---

Three Strategy Archetypes and Their Maps

Kaplan & Norton identified three dominant strategy themes. Each produces a different map shape.

Archetype 1: Operational Excellence

Strategy: Win on price, reliability, and efficiency. (Example: Costco, Amazon fulfillment)

Financial:    [↑ Operating Margin]  ←──  [↑ Volume via Low Price]
                      ▲                          ▲
Customer:    [Lowest Total Cost]  ←──  [Reliable Delivery]
                      ▲                          ▲
Internal:    [Lean Process]  ←──  [Supply Chain Optimization]
                      ▲                          ▲
L&G:         [Process Improvement Skills]  ←──  [ERP System]

Dominant perspective: Internal Process — this is where most objectives cluster. L&G focus: Technical skills, process expertise, automation tooling. Customer value proposition: "We give you the lowest hassle, best price."

Archetype 2: Customer Intimacy

Strategy: Win by knowing customers better than anyone. (Example: Salesforce, luxury brands)

Financial:    [↑ Revenue per Customer]  ←──  [↑ Customer Lifetime Value]
                      ▲                                ▲
Customer:    [↑ Share of Wallet]  ←──  [Deep Relationship / Trust]
                      ▲                                ▲
Internal:    [Customer Needs Analysis]  ←──  [Personalized Service Delivery]
                      ▲                                ▲
L&G:         [Customer Insight Skills]  ←──  [CRM + Data Platform]

Dominant perspective: Customer — more objectives here than other archetypes. L&G focus: Relationship skills, data literacy, customer analytics. Customer value proposition: "We understand you and tailor everything to your needs."

Archetype 3: Product Leadership

Strategy: Win through innovation and best product. (Example: Apple, TSMC R&D units)

Financial:    [↑ Revenue from New Products]  ←──  [Premium Pricing Power]
                          ▲                               ▲
Customer:    [↑ Early Adopter Acquisition]  ←──  [Brand = Innovation]
                          ▲                               ▲
Internal:    [Fast R&D Cycle]  ←──  [IP Development]
                          ▲              ▲
L&G:         [R&D Talent Density]  ←──  [Innovation Culture]

Dominant perspective: Internal Process (R&D focus) + L&G. L&G focus: Deep domain expertise, experimentation culture, talent retention. Customer value proposition: "We give you tomorrow's capabilities today."

---

Step-by-Step: Building a Strategy Map from Scratch

Step 1: Write the strategy sentence

Format: [Grow / Defend / Transform] through [mechanism] by [time horizon]

Examples:

• "Grow ARR 30% in 18 months through product-led growth"
• "Defend market share in Taiwan through superior service quality"
• "Transform from hardware to SaaS revenue model within 3 years"

This sentence determines which archetype you're closest to and what the Financial objectives must be.

Step 2: Set Financial objectives first (top of map)

Ask: "What does financial success look like for our stakeholders at the end of the period?"

Write 2-4 objectives. Classify each as:

• Growth theme: Revenue, ARR, new market entry, pricing
• Productivity theme: Cost reduction, asset utilization, cash flow

Most BSCs should have at least one from each. A BSC with only growth objectives ignores sustainability; only productivity objectives ignores ambition.

Step 3: Identify the Customer value proposition

Ask: "What must we deliver to customers so they give us the financial results we want?"

The value proposition has three components. Pick the primary:

Write 2-4 Customer objectives that directly explain how customers will generate the Financial results.

Step 4: Define critical Internal Processes

Ask: "Which internal processes must we excel at to deliver the customer value proposition?"

Map each Customer objective to the internal process that enables it:

Kaplan & Norton suggest four process clusters as a starting checklist: 1. Operations management: supply, production, distribution, risk 2. Customer management: acquisition, retention, growth, service 3. Innovation: opportunity ID, R&D portfolio, product launch 4. Regulatory & social: environment, safety, community

Not every cluster is relevant to every strategy. Pick what matters.

Step 5: Identify Learning & Growth enablers

Ask: "What skills, systems, and culture do we need to execute those internal processes?"

Three L&G categories:

Each Internal Process objective should have at least one L&G enabler. If you can't identify an enabler, ask: "Why can't we do this process today?" The answer is usually a skills, systems, or culture gap.

Step 6: Draw arrows and validate

For every pair of connected objectives, write a one-sentence hypothesis:

"If we [L&G objective], then [Internal objective] will improve, because..."

If you can't complete the sentence convincingly, the link is weak. Either find the real mechanism or cut the connection.

Validation checklist:

• [ ] Every Financial objective has at least one Customer arrow pointing to it
• [ ] Every Customer objective has at least one Internal arrow pointing to it
• [ ] Every Internal objective has at least one L&G arrow pointing to it
• [ ] No L&G objective has an arrow pointing to it (it's the foundation)
• [ ] No Financial objective has an arrow pointing away from it (it's the outcome)
• [ ] The map tells a coherent story you can explain in 3 minutes

---

Worked Example: B2B SaaS Company

Company: CloudOps — infrastructure monitoring SaaS Strategy: "Grow NRR to 120% within 12 months through proactive customer success"

Financial Objectives

Customer Objectives (linked to Financial)

Internal Process Objectives (linked to Customer)

Learning & Growth Objectives (linked to Internal)

Completed Strategy Map

[ARR $8M] ←── [NRR ≥ 120%] ←── [CAC payback < 12mo]
              ▲                  ▲              ▲
[95% Retention] ←── [ACV +25% upsell] ←── [TTV < 14 days]
       ▲                    ▲                    ▲
[Health Score] ←── [QBR Program] ←── [Onboarding Redesign]
       ▲                ▲                    ▲
[CSM Training] ←── [QBR Playbook] ←── [Onboarding Hire]
                            ▲
                    [Gainsight Deploy]

Causal narrative: We deploy Gainsight and train CSMs on health scores (L&G), enabling proactive account monitoring and structured QBRs (Internal), so customers see continuous value and receive expansion offers at the right moment (Customer), driving NRR above 120% and ARR to $8M (Financial).

---

Common Map Failures and Fixes

Failure 1: Floating Financial Objective

Symptom: "Increase revenue 30%" at the top with no Customer objective below it.

Problem: You've stated a wish, not a strategy. The map doesn't explain how revenue grows.

Fix: Ask "Which customer behavior will produce that revenue?" and add that as a Customer objective with an arrow pointing up.

Failure 2: Internal Process with No L&G Root

Symptom: "Improve code deployment frequency" with no L&G arrow feeding it.

Problem: The process won't improve on its own. Something has to change at the foundation.

Fix: Ask "Why can't we do this today?" The answer is usually skills (team doesn't know CI/CD), systems (no pipeline tooling), or culture (fear of deploying to prod). Add the root cause as a L&G objective.

Failure 3: Too Many Objectives, No Story

Symptom: 25 objectives across 4 perspectives, arrows everywhere, looks like a subway map.

Problem: The map has lost strategic focus. Everything is a priority = nothing is a priority.

Fix: Apply the "3-5 per perspective" rule strictly. Ask: "If we could only achieve 3 things in each perspective, which 3 would most directly execute the strategy sentence?" Cut the rest.

Failure 4: Circular Arrows

Symptom: Arrow from Financial back down to L&G ("Revenue funds training").

Problem: BSC maps causal logic, not budget flows. Yes, revenue funds training — but that's a budget decision, not a strategic hypothesis.

Fix: Remove feedback arrows. The map is always bottom-up (L&G → Financial). Budget allocation is a separate process.

Failure 5: Strategy Map ≠ Strategy

Symptom: Every company in the same industry has an identical strategy map.

Problem: Generic objectives ("improve quality", "increase customer satisfaction") that don't reflect strategic choices. A map should be distinctive.

Fix: Every objective should be falsifiable — someone should be able to look at it and say "that's a trade-off, not every company would make that choice." If all your competitors would nod in agreement at your map, it's not a strategy, it's a list of good things.

---

Cascading: Corporate Map → Department Map

A corporate BSC strategy map must cascade to business units and departments. The rules:

What cascades unchanged: Strategic themes and the direction of causality.

What changes: The specific objectives, measures, and initiatives become more operational.

The test: Can you draw arrows from every department objective to a corporate objective? If not, either the department objective doesn't support strategy (cut it) or you're missing a link in the corporate map (add it).

---

Quick Reference: Strategy Map Design Decisions