grad-ambidexterity
診斷組織探索與開發失衡，設計雙元性結構
中文翻譯
---
name: "grad-ambidexterity"
description: "運用組織雙元性（ambidexterity）理論，在探索與開發活動之間取得平衡。當使用者需要診斷一個組織是過度開發還是過度探索、設計能同時支撐創新與效率的結構，或評估短期績效與長期更新之間的張力時使用。"
metadata:
category: "WP-24 創新與國際化"
tags: ["ambidexterity", "exploration-exploitation", "march-1991", "structural-ambidexterity", "contextual-ambidexterity", "organizational-design"]
---
# 組織雙元性：探索 vs 開發
## 概述
組織雙元性指的是企業同時追求探索（創新、實驗、新機會）與開發（效率、精進、執行既有能力）的能力。March（1991）證明，偏重其中一邊的企業都會面臨次佳的結果：過度開發會陷入能力陷阱，過度探索則會陷入失敗陷阱。
## 何時使用
**觸發條件：**
- 使用者問如何在不犧牲現有業務績效的情況下創新
- 使用者正在重組組織，要同時支撐研發與營運
- 使用者描述出能力陷阱（擅長的是錯誤的事）或失敗陷阱（實驗太多、沒有成果）的症狀
- 使用者提到「explore vs exploit」、「創新 vs 效率」或「雙元組織」
**何時不要用：**
- 分析外部新進者帶來的破壞 -> 用 grad-disruptive-innovation
- 透過策略聯盟取得創新 -> 用 grad-coopetition
- 國際化決策 -> 用 grad-oli 或 grad-uppsala
## 假設
```
IRON LAW: Over-Exploiting Kills Long-Term Innovation;
Over-Exploring Kills Short-Term Revenue
Exploitation WITHOUT exploration leads to a COMPETENCY TRAP: the firm
becomes excellent at yesterday's business and is blindsided by change.
Exploration WITHOUT exploitation leads to a FAILURE TRAP: the firm
burns resources on experiments that never reach market scale.
There is no stable equilibrium — the balance must be actively managed.
```
- 探索和開發會競爭稀缺的資源（注意力、人才、預算）
- 最佳的平衡點會隨產業的動態程度與企業的生命週期階段而移動
- 高階領導層必須主動管理這個張力，它不會自己平衡
## 方法論
### 步驟 1：診斷目前的平衡
評估組織的探索與開發比例：
| 指標 | 偏重開發 | 平衡 | 偏重探索 |
|-----------|-------------------|----------|-------------------|
| 研發支出（占營收 %） | < 3% | 5-15% | > 20% |
| 新產品營收（占總營收 %） | < 10% | 20-40% | > 50% |
| 專案的時間範圍 | < 1 年 | 混合 | > 3 年 |
| 對失敗的容忍度 | 非常低 | 中等 | 非常高 |
| 流程的制式化程度 | 僵化 | 有適應性 | 混亂 |
### 步驟 2：找出雙元性的模式
選擇結構上的做法：
- **結構式雙元性（Structural ambidexterity）**（Tushman & O'Reilly）：把探索單位與開發單位分開，各有不同的文化、流程和指標。由高階領導層在頂端整合。
- **情境式雙元性（Contextual ambidexterity）**（Gibson & Birkinshaw）：個別員工依情境在探索與開發之間切換。需要支持性的文化（紀律 + 挑戰 + 信任 + 支持）。
- **循序式雙元性（Sequential ambidexterity）**：在探索期與開發期之間交替（較少見，適合較小的公司）。
### 步驟 3：設計整合機制
對結構式雙元性，要定義：
- 單位分隔的邊界（實體、文化、匯報線）
- 整合點（共同的高階團隊、知識傳遞的儀式）
- 資源分配規則（固定的探索預算 vs 動態分配）
對情境式雙元性，要定義：
- 行為上的期待（花在探索 vs 開發的時間比例）
- 文化上的促成條件（讓人敢實驗的心理安全感）
- 兩者都獎勵的指標（平衡計分卡的做法）
### 步驟 4：監控並重新平衡
建立檢視週期（每季檢視專案管線的健康度、每年檢視市場趨勢），以偵測是否往任何一個陷阱漂移。定義重新平衡的觸發條件。
## 輸出格式
```markdown
# Ambidexterity Assessment: {Organization}
## Current State Diagnosis
- Balance: Exploitation-heavy / Balanced / Exploration-heavy
- Evidence: {key indicators}
- Risk: Competency trap / Failure trap / None
## Recommended Ambidexterity Mode
- Mode: Structural / Contextual / Sequential
- Rationale: {why this mode fits}
## Design Recommendations
- Exploration unit: {scope, budget, metrics, reporting}
- Exploitation unit: {scope, budget, metrics, reporting}
- Integration mechanism: {how they connect}
## Rebalancing Triggers
- {Condition 1}: shift toward more exploration
- {Condition 2}: shift toward more exploitation
```
## 常見陷阱
- **只有結構分離、沒有整合，就只是分拆（spin-off）**：如果探索單位跟核心業務沒有連結，就會失去綜效。高階團隊「必須」做整合。
- **「創新劇場」不是探索**：從來不出產品的黑客松和實驗室只是浪費資源。探索必須有通往市場的路徑。
- **模式的選擇要看脈絡**：結構式雙元性適合有資源維持獨立單位的大公司。情境式適合每個人身兼多職的小公司。
- **平衡點會移動**：新創應該偏重探索。處於穩定產業的成熟企業可以偏重開發。沒有放諸四海皆準的比例。
- **指標不一致是第一殺手**：如果探索單位用開發的指標（季營收）來評斷，它們還沒能交出成果就會被關掉。
## 參考資料
- March（1991）的適應系統正式模型，見 `references/march-1991-model.md`
- Tushman & O'Reilly 的結構設計範本，見 `references/structural-ambidexterity-design.md`英文原文
---
name: "grad-ambidexterity"
description: "Apply organizational ambidexterity theory to balance exploration and exploitation activities. Use this skill when the user needs to diagnose whether an organization is over-exploiting or over-exploring, design structures that support both innovation and efficiency, or evaluate the tension between short-term performance and long-term renewal."
metadata:
category: "WP-24 創新與國際化"
tags: ["ambidexterity", "exploration-exploitation", "march-1991", "structural-ambidexterity", "contextual-ambidexterity", "organizational-design"]
---
# Organizational Ambidexterity: Exploration vs Exploitation
## Overview
Organizational ambidexterity refers to a firm's ability to simultaneously pursue exploration (innovation, experimentation, new opportunities) and exploitation (efficiency, refinement, execution of existing capabilities). March (1991) demonstrated that firms favoring one over the other face suboptimal outcomes: over-exploitation leads to competency traps, while over-exploration leads to failure traps.
## When to Use
**Trigger conditions:**
- User asks how to innovate without sacrificing current business performance
- User is restructuring an organization to support both R&D and operations
- User describes symptoms of a competency trap (good at the wrong things) or failure trap (too many experiments, no results)
- User mentions "explore vs exploit", "innovation vs efficiency", or "ambidextrous organization"
**When NOT to use:**
- For analyzing disruption from external entrants -> use grad-disruptive-innovation
- For strategic alliances to access innovation -> use grad-coopetition
- For internationalization decisions -> use grad-oli or grad-uppsala
## Assumptions
```
IRON LAW: Over-Exploiting Kills Long-Term Innovation;
Over-Exploring Kills Short-Term Revenue
Exploitation WITHOUT exploration leads to a COMPETENCY TRAP: the firm
becomes excellent at yesterday's business and is blindsided by change.
Exploration WITHOUT exploitation leads to a FAILURE TRAP: the firm
burns resources on experiments that never reach market scale.
There is no stable equilibrium — the balance must be actively managed.
```
- Exploration and exploitation compete for scarce resources (attention, talent, budget)
- The optimal balance shifts with industry dynamism and firm lifecycle stage
- Senior leadership must actively manage the tension — it does not self-organize
## Methodology
### Step 1: Diagnose the Current Balance
Assess the organization's exploration-exploitation ratio:
| Indicator | Exploitation-Heavy | Balanced | Exploration-Heavy |
|-----------|-------------------|----------|-------------------|
| R&D spend (% revenue) | < 3% | 5-15% | > 20% |
| New product revenue (% total) | < 10% | 20-40% | > 50% |
| Time horizon of projects | < 1 year | Mixed | > 3 years |
| Tolerance for failure | Very low | Moderate | Very high |
| Process formalization | Rigid | Adaptive | Chaotic |
### Step 2: Identify the Ambidexterity Mode
Choose the structural approach:
- **Structural ambidexterity** (Tushman & O'Reilly): Separate exploration units from exploitation units with different cultures, processes, and metrics. Senior leadership integrates at the top.
- **Contextual ambidexterity** (Gibson & Birkinshaw): Individual employees switch between exploration and exploitation based on context. Requires supportive culture (discipline + stretch + trust + support).
- **Sequential ambidexterity**: Alternate between periods of exploration and exploitation (less common, suits smaller firms).
### Step 3: Design the Integration Mechanism
For structural ambidexterity, define:
- Separate unit boundaries (physical, cultural, reporting)
- Integration points (shared senior team, knowledge transfer rituals)
- Resource allocation rules (fixed exploration budget vs dynamic)
For contextual ambidexterity, define:
- Behavioral expectations (% time on exploration vs exploitation)
- Cultural enablers (psychological safety for experimentation)
- Metrics that reward both (balanced scorecard approach)
### Step 4: Monitor and Rebalance
Establish review cycles (quarterly pipeline health, annual market trends) to detect drift toward either trap. Define trigger conditions for rebalancing.
## Output Format
```markdown
# Ambidexterity Assessment: {Organization}
## Current State Diagnosis
- Balance: Exploitation-heavy / Balanced / Exploration-heavy
- Evidence: {key indicators}
- Risk: Competency trap / Failure trap / None
## Recommended Ambidexterity Mode
- Mode: Structural / Contextual / Sequential
- Rationale: {why this mode fits}
## Design Recommendations
- Exploration unit: {scope, budget, metrics, reporting}
- Exploitation unit: {scope, budget, metrics, reporting}
- Integration mechanism: {how they connect}
## Rebalancing Triggers
- {Condition 1}: shift toward more exploration
- {Condition 2}: shift toward more exploitation
```
## Gotchas
- **Structural separation without integration is just a spin-off**: If the exploration unit has no connection to the core business, you lose synergies. The senior team MUST integrate.
- **"Innovation theater" is not exploration**: Hackathons and labs that never ship products waste resources. Exploration must have a path to market.
- **Context matters for mode selection**: Structural ambidexterity suits large firms with resources to maintain separate units. Contextual suits smaller firms where everyone wears multiple hats.
- **The balance point shifts**: A startup should be exploration-heavy. A mature firm in a stable industry can be exploitation-heavy. There is no universal ratio.
- **Metrics misalignment is the #1 killer**: If exploration units are judged by exploitation metrics (quarterly revenue), they will be shut down before they can deliver.
## References
- For March (1991) formal model of adaptive systems, see `references/march-1991-model.md`
- For Tushman & O'Reilly structural design templates, see `references/structural-ambidexterity-design.md`