biz-bsc

asgard-ai-platform ｜ 商業與營運 ｜ 原文 ｜ MIT

用平衡計分卡把策略拆成四構面的可衡量目標

---
name: "biz-bsc"
description: "套用平衡計分卡（BSC）框架，把策略轉成橫跨財務、顧客、內部流程、學習與成長四個構面的可衡量目標。當使用者需要設定策略 KPI、建立策略地圖、讓組織目標對齊、或把日常營運連結到策略願景時使用，即使他們說的是「我們怎麼衡量策略執行」或「我們的 KPI 感覺是脫節的」也一樣。"
metadata:
  category: "WP-13 商學院—策略"
  tags: ["business-strategy", "balanced-scorecard", "performance-management"]
---

# 平衡計分卡（Balanced Scorecard，BSC）

## 概述

平衡計分卡把策略轉成橫跨四個構面的目標和指標，建立一條因果鏈：學習與成長 → 內部流程 → 顧客 → 財務。它回答的是「我們有在執行策略嗎？」，不只是「我們有賺錢嗎？」

## 何時使用

**觸發條件：**
- 使用者需要定義財務指標以外的策略 KPI
- 使用者想把營運活動連結到策略目標
- 使用者在建立策略地圖或績效儀表板
- 使用者說「我們的 KPI 沒有反映策略」或「我們怎麼衡量執行成效」

**何時不要用：**
- 一次性的策略分析 → 用 SWOT 或 Porter
- 專案層級的 OKR → 用 OKR 框架
- 只有財務績效重要時（很少見）

## 框架

```
鐵律：四個構面，有因果連結

BSC「不是」四份各自獨立的 KPI 清單。四個構面形成一條「因果鏈」：

  學習與成長 → 內部流程 → 顧客 → 財務

投資在員工技能（L&G），會改善流程品質（內部），
進而提高顧客滿意度（顧客），並帶動營收（財務）。

如果你的 BSC 構面之間沒有因果連結，那只是 KPI 的大雜燴，
不是平衡計分卡。
```

```
鐵律：每個目標都要有指標、目標值和行動方案

沒有指標的目標只是願望。
沒有目標值的指標只是統計數字。
沒有行動方案的目標值只是希望。

每個 BSC 目標「必須」三者俱全：指標（怎麼追蹤）、目標值
（成功是什麼樣子）、行動方案（什麼行動去驅動它）。
```

### 步驟 1：釐清策略

建立 BSC 之前，先用一句話說出策略：
- 「透過貼近顧客來成長」（關係導向）
- 「以卓越營運取勝」（效率導向）
- 「以產品創新領先」（差異化導向）

策略決定了每個構面中哪些目標占主導。

### 步驟 2：為每個構面定義目標

**財務**（落後指標：結果）：
- 營收成長、獲利能力、成本效率、ROI、現金流
- 問題：「我們必須交出什麼財務成果，才能滿足利害關係人？」

**顧客**（財務的領先指標）：
- 顧客滿意度、留存、獲取、市占、NPS
- 問題：「我們必須提供顧客什麼，才能達成財務目標？」

**內部流程**（顧客的領先指標）：
- 流程效率、品質、週期時間、創新管線
- 問題：「我們必須在哪些流程上表現卓越，才能讓顧客滿意？」

**學習與成長**（基礎：推動因素）：
- 員工技能、文化、技術基礎建設、知識管理
- 問題：「我們必須建立什麼能力，才能改善我們的流程？」

### 步驟 3：建立策略地圖

畫出因果箭頭，連結各構面的目標：

```
[L&G] 訓練業務團隊做顧問式銷售
  ↓
[內部] 把銷售週期從 60 天縮短到 30 天
  ↓
[顧客] 把顧客滿意度分數提高到 4.5/5
  ↓
[財務] 營收年增 20%
```

每個目標都應該連到另一個構面的至少一個目標。孤立的目標代表策略邏輯有缺口。

### 步驟 4：指派指標、目標值和行動方案

對每個目標，定義：
- **指標**：具體的衡量值（以量化為佳）
- **目標值**：附有時間範圍的具體門檻
- **行動方案**：驅動該指標的行動或專案

## 輸出格式

```markdown
# 平衡計分卡：{組織}

## 策略宣言
{一句話的策略}

## 策略地圖

{L&G 目標} → {內部流程目標} → {顧客目標} → {財務目標}

## 計分卡

### 財務構面
| 目標 | 指標 | 目標值 | 行動方案 |
|-----------|---------|--------|-----------|
| {目標} | {衡量值} | {何時達到的值} | {行動} |

### 顧客構面
| 目標 | 指標 | 目標值 | 行動方案 |
|-----------|---------|--------|-----------|
| {目標} | {衡量值} | {何時達到的值} | {行動} |

### 內部流程構面
| 目標 | 指標 | 目標值 | 行動方案 |
|-----------|---------|--------|-----------|
| {目標} | {衡量值} | {何時達到的值} | {行動} |

### 學習與成長構面
| 目標 | 指標 | 目標值 | 行動方案 |
|-----------|---------|--------|-----------|
| {目標} | {衡量值} | {何時達到的值} | {行動} |

## 因果鏈驗證
{說明 L&G → 內部 → 顧客 → 財務之間的連結如何運作}
```

## 範例

### 正確的應用

**情境：** 一家 B2B SaaS 公司的 BSC，策略是「透過產品驅動成長」

| 構面 | 目標 | 指標 | 目標值 | 行動方案 |
|------------|-----------|---------|--------|-----------|
| 財務 | 提高 ARR | 年度經常性營收 | Q4 達 $10M | 擴充定價層級 |
| 顧客 | 改善留存 | 淨營收留存率 | >110% | 推出客戶成功方案 |
| 內部 | 加速功能交付 | 發布週期時間 | 2 週（原本 6 週） | 採用 CI/CD pipeline |
| L&G | 建立產品分析能力 | 受過 Mixpanel 訓練的團隊 % | Q2 前 100% | 產品分析訓練營 |

**因果鏈**：分析訓練（L&G）→ 更快、以資料驅動的發布（內部）→ 產品更好帶來更高留存（顧客）→ ARR 成長（財務）✓

### 錯誤的應用

**哪裡出錯：**
- 列了 15 個 KPI，卻沒有因果連結 → 這是 KPI 大雜燴，不是 BSC。違反鐵律：構面之間必須有因果連結。
- 財務：「營收 $10M」，沒有指標、目標時間範圍或行動方案 → 違反鐵律：需要指標 + 目標值 + 行動方案。

## 常見陷阱

- **目標太多**：每個構面 3-5 個是理想的。超過 5 個就失焦了。BSC 談的是策略優先順序，不是一份完整的 KPI 清單。
- **全是落後指標**：如果每個指標都是落後指標（營收、滿意度分數），你就沒辦法主動管理。要搭配領先指標（訓練時數、管線品質）取得平衡。
- **把 L&G 當事後補上的**：團隊很容易填好財務和顧客，卻在 L&G 卡關。這個構面是基礎，跳過它，整條因果鏈就斷了。
- **層層展開的混亂**：公司層級的 BSC 和部門層級的 BSC 應該連結，但不該一模一樣。部門的目標應該對公司目標有貢獻，不是照抄。
- **BSC ≠ OKR**：BSC 是策略管理系統（4 個構面、因果連結、策略地圖）。OKR 是目標設定框架（目標 + 關鍵成果）。兩者可以並存，但用途不同。

## 參考資料

- 策略地圖的範本和範例，見 `references/strategy-maps.md`
- 與 OKR 及其他績效框架的比較，見 `references/framework-comparison.md`

---
name: "biz-bsc"
description: "Apply the Balanced Scorecard (BSC) framework to translate strategy into measurable objectives across Financial, Customer, Internal Process, and Learning & Growth perspectives. Use this skill when the user needs to set strategic KPIs, create a strategy map, align organizational goals, or connect daily operations to strategic vision — even if they say 'how do we measure strategy execution' or 'our KPIs feel disconnected'."
metadata:
  category: "WP-13 商學院—策略"
  tags: ["business-strategy", "balanced-scorecard", "performance-management"]
---

# 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

```markdown
# 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"

| Perspective | Objective | Measure | Target | Initiative |
|------------|-----------|---------|--------|-----------|
| Financial | Increase ARR | Annual Recurring Revenue | $10M by Q4 | Expand pricing tiers |
| Customer | Improve retention | Net Revenue Retention | >110% | Launch customer success program |
| Internal | Accelerate feature delivery | Release cycle time | 2 weeks (from 6) | Adopt CI/CD pipeline |
| L&G | Build product analytics capability | % team trained on Mixpanel | 100% by Q2 | Product analytics bootcamp |

**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`