本文へ移動
cccskills
無料GitHub で公開

"grad-ambidexterity"

"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.".

インストール方法を見る

含まれるファイル(4)

  • SKILL.md5.7 KB
  • examples/sample_scenario.md5.7 KB
  • references/march-1991-model.md11.4 KB
  • references/structural-ambidexterity-design.md14.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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:

IndicatorExploitation-HeavyBalancedExploration-Heavy
R&D spend (% revenue)< 3%5-15%> 20%
New product revenue (% total)< 10%20-40%> 50%
Time horizon of projects< 1 yearMixed> 3 years
Tolerance for failureVery lowModerateVery high
Process formalizationRigidAdaptiveChaotic

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

# 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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

"Implement and select ad bidding strategies from manual CPC to automated target-CPA and target-ROAS. Use this skill when the user needs to choose a bidding strategy, set up automated bidding, or optimize bid parameters — even if they say 'what bidding strategy should I use', 'target CPA setup', or 'smart bidding configuration'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Optimize advertising budget allocation across campaigns using marginal returns analysis. Use this skill when the user needs to distribute budget across multiple campaigns, optimize spend pacing, or maximize overall ROAS under budget constraints — even if they say 'how to split my ad budget', 'campaign budget optimization', or 'diminishing returns on ad spend'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Build CTR prediction models for estimating ad click-through rates from features. Use this skill when the user needs to predict click probability, build an ad ranking model, or evaluate ad creative performance — even if they say 'predict click rate', 'ad relevance scoring', or 'which ad will get more clicks'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Implement Generalized Second Price auction for ad slot allocation and pricing. Use this skill when the user needs to understand search ad auctions, compute ad positions and costs-per-click, or analyze bidding dynamics — even if they say 'how does Google Ads auction work', 'ad rank calculation', or 'second price auction for ads'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Implement VCG mechanism for incentive-compatible ad slot allocation with truthful bidding. Use this skill when the user needs to design a truthful auction mechanism, compute externality-based payments, or understand why platforms may prefer GSP over VCG — even if they say 'truthful auction design', 'VCG payments', or 'incentive-compatible mechanism'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

"Explain blockchain fundamentals including distributed ledger architecture, consensus mechanisms, and block structure. Use this skill when the user needs to understand blockchain concepts, evaluate whether blockchain fits a use case, or design a blockchain-based solution — even if they say 'how does blockchain work', 'do I need blockchain', or 'distributed ledger'.".

日本語の概要は準備中です。原文の説明を表示しています。

charlieviettq/awesome-agent-skill262026年7月20日 更新

charlieviettq のスキルをすべて見る

このスキルの問題を報告する