Skip to content

charlieviettq/awesome-agent-skill / .claude/skills/biz-bsc

"biz-bsc"

Verified

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

FileKindSize
SKILL.mdskill md7.1 KB
examples/sample_scenario.mdmarkdown6.4 KB
references/framework-comparison.mdmarkdown9.4 KB
references/strategy-maps.mdmarkdown16.8 KB

references/strategy-maps.md

View on GitHub
# 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:

| Component | Question | Example Measure |
|-----------|----------|-----------------|
| Product/Service attributes | Price, quality, availability, features | NPS, defect rate, on-time delivery |
| Relationship | Trust, responsiveness, partnership | CSAT, account retention, renewal rate |
| Image/Brand | Reputation, aspiration, identity | Brand survey, share of voice |

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:

| Customer Objective | Enabling Internal Process |
|-------------------|--------------------------|
| Reduce time-to-value for new customers | Onboarding automation |
| Increase NPS from 35 to 55 | Frontline issue resolution redesign |
| Grow enterprise segment | Sales methodology upgrade |

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:

| Category | What it Covers | Example Objectives |
|----------|---------------|-------------------|
| Human Capital | Skills, knowledge, competencies | Salesforce certified on consultative selling |
| Information Capital | Systems, databases, networks | CRM data quality ≥ 95% |
| Organization Capital | Culture, leadership, alignment | OKR adoption rate, manager effectiveness score |

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
| Objective | Why |
|-----------|-----|
| Grow ARR to $8M | Core growth target |
| Achieve NRR ≥ 120% | Expansion revenue > churn |
| Reduce CAC payback to < 12 months | Efficiency of growth |

### Customer Objectives (linked to Financial)
| Customer Objective | → Financial Objective |
|-------------------|----------------------|
| Increase enterprise retention to 95% | → NRR ≥ 120% |
| Grow average contract value 25% via upsell | → ARR $8M + NRR |
| Shorten time-to-first-value to < 14 days | → CAC payback |

### Internal Process Objectives (linked to Customer)
| Internal Objective | → Customer Objective |
|-------------------|----------------------|
| Deploy health score monitoring for all accounts | → Enterprise retention |
| Launch QBR (Quarterly Business Review) program | → Upsell / ACV growth |
| Redesign onboarding to 14-day activation milestone | → Time-to-first-value |

### Learning & Growth Objectives (linked to Internal)
| L&G Objective | → Internal Objective |
|--------------|----------------------|
| Train CSMs on health score interpretation | → Health score monitoring |
| Build QBR playbook + train AEs | → QBR program |
| Hire onboarding specialist (IC) | → Onboarding redesign |
| Deploy Gainsight CS platform | → Health score + QBR |

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

| Level | Financial Objective | Customer Objective |
|-------|--------------------|--------------------|
| Corporate | Grow revenue 20% YoY | NPS ≥ 60 |
| Sales Dept | Increase new logo ARR $2M | New customer onboarding CSAT ≥ 4.5 |
| Engineering Dept | Reduce infrastructure cost 15% | API uptime ≥ 99.9% |
| HR Dept | Reduce voluntary attrition to 8% | Internal mobility rate ≥ 20% |

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

| Decision | Guideline |
|----------|-----------|
| How many objectives total? | 12–25 across all four perspectives |
| How many per perspective? | 3–5; L&G often has more because it's foundational |
| Which perspective to start from? | Start with Financial (outcome), work downward |
| How detailed should arrows be? | One arrow per causal hypothesis; label if ambiguous |
| How often to update the map? | Annually for strategy review; quarterly for target tracking |
| Should L&G have an arrow from Financial? | No. Never. Funding is not causality. |
| Can two perspectives share an objective? | No. Each objective belongs to exactly one perspective. |
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall