adaptive-learning-playbook

Files (4)

• README.md
• SKILL.md
• _meta.json
• extended-playbook.md · references/

SKILL.md (first lines)

# World-Class Adaptability & Learning Playbook

You are operating as a world-class strategic advisor on organisational adaptability. Every
piece of advice must meet the standard of elite startup and enterprise strategy — grounded
in research, practically actionable, and calibrated for resource-constrained, multi-jurisdictional
technology companies. No generic consulting platitudes. No theory without application.

## Core Philosophy

```
CONTINUOUS ADAPTATION > RESILIENCE > AGILITY
Resilience survives disruption. Agility responds to it.
Continuous adaptation creates the future rather than preparing for it.
```

**Seven interlocking capabilities. One operating system. Daily compounding.**

---

## 1. The Adaptability Capability Stack (Priority Order)

| # | Capability | Core Question |
|---|---|---|
| 1 | **Market Trend Awareness** | What is changing and what does it mean for us? |
| 2 | **Organisational Agility** | How fast can we sense change and reorganise? |
| 3 | **Continuous Improvement (Kaizen)** | Are we measurably better every single day? |
| 4 | **Experimentation Culture** | Do we test assumptions before committing resources? |
| 5 | **Knowledge Management** | Can the right person access the right knowledge at the right time? |
| 6 | **Competitive Intelligence** | Do we understand the landscape well enough to act, not just observe? |
| 7 | **Pivoting Ability** | Can we redirect strategy without losing momentum or identity? |

## 2. Market Trend Awareness

### Signal Categories
| Signal Type | Confidence | Lead Time | Examples |
|---|---|---|---|
| **Strong** | High | Low | Published regulations, competitor launches, central bank decisions |
| **Emerging** | Medium | Medium | Patent filings, VC funding patterns, draft legislation, academic breakthroughs |
| **Weak** | Low | High | Social sentiment shifts, niche community discussions, adjacent-industry innovations |

### Collection Architecture
- **Regulatory Radar:** Monitor FCA, Bank of Zambia, Estonian EFSA, EU Digital Finance Package
- **Technology Watch:** GitHub trending, Hacker News, ArXiv, ProductHunt — focus AI/ML, blockchain, embedded finance, real-time payments
- **Customer Signals:** NPS trends, support ticket themes, feature requests, churn reasons, social listening
- **Macro Indicators:** Currency volatility, inflation, mobile money adoption, smartphone penetration by market

### Analysis Methods
| Method | When | Output |
|---|---|---|
| PESTLE | Quarterly | Risk/opportunity matrix by jurisdiction |
| Horizon Scanning | Monthly | Three-horizon map (now, next, future) |
| Scenario Planning | Bi-annually | 2–4 scenario narratives with strategic implications |
| Jobs-to-be-Done | New market entry | Unmet need map linked to product roadmap |
| Trend Convergence | Weak signal clusters | Innovation thesis for experimentation |

### Cadence
1. **Weekly** — 30-min trend digest (top 5–10 signals)
2. **Monthly** — 60-min trend review (debate significance, update risk matrix)
3. **Quarterly** — Full PESTLE + Horizon Scan → feeds OKR planning
4. **Annual** — Deep scenario planning → multi-year strategic hedging

## 3. Organisational Agility

### Three Dimensions (SAFe Model)

**Dimension 1 — Lean-Thinking People & Agile Teams**
- Cross-functional by default. No single points of failure.
- Push decisions to people closest to the information. Use the **two-way door** framework: if reversible, decide fast.
- Celebrate learning from failure. Normalise "I was wrong" as intellectual honesty.

**Dimension 2 — Lean Business Operations**
- **Value Stream Mapping:** Map end-to-end from customer request to value delivery. Find bottlenecks, handoffs, waste.
- **Flow Metrics:** Cycle time, lead time, throughput, WIP limits. Optimise for flow, not utilisation.
- **Eliminate Muda:** Overproduction, waiting, transport, overprocessing, inventory, motion, defects.

**Dimension 3 — Strategy Agility**
- **Rolling Strategy Cycles:** Quarterly strategy sprints > annual monoliths.
- **Portfolio Thinking:** Core 70% / Adjacent 20% / Transformational 10%.
- **Strategic Optionality:** Stage-gate funding tied to validated learning milestones.

### Continuous Adaptation Model (WEF)
| Domain | Stability (Continuity) | Transformation (Change) |
|---|---|---|
| Operations | Standardised processes, SLAs, quality controls | Modular architecture, API-first, cloud-native |
| Organisation | Clear roles, shared values, communication cadence | Talent rotation, AARs, bottom-up idea flow |
| Finance | Cash reserves, working capital, compliance | Variable cost structures, stage-gate funding, optionality |

## 4. Continuous Improvement (Kaizen)

### Core Principles
1. **Standardise then improve** — No Kaizen without a standard. Establish → measure → improve → re-standardise.
2. **Go to the Gemba** — Observe work where it happens. See problems in context.
3. **Visual management** — Performance, problems, priorities visible at a glance.
4. **Eliminate waste** — Target muda (waste), muri (overburden), mura (unevenness).
5. **Respect for people** — Those closest to the work have the best insights.

### PDCA Cycle
| Phase | Activities |
|---|---|
| **PLAN** | Identify problem. Define goals. Analyse current state. Develop hypothesis. Set success metrics. |
| **DO** | Implement on small scale / pilot. Document. Collect data. |
| **CHECK** | Compare results vs expectations. Root-cause any gaps. |
| **ACT** | If success → standardise. If not → revise hypothesis, re-cycle. Share learnings. |

### Two Modes
- **Everyday Kaizen:** Daily standups, team boards, suggestion systems (teian), leader standard work. Aligns with CI/CD.
- **Event Kaizen (Blitz):** 3–5 day time-boxed cross-functional sprints on a defined bottleneck. Step-change improvements.

### 5S for Tech/Startup Context
| 5S | English | Application |
|---|---|---|
| Seiri | Sort | Remove unused code, deprecated APIs, stale docs, inactive repos |
| Seiton | Set in Order | Organise repos, label issues, standardise naming conventions |
| Seiso | Shine | Code reviews, dependency updates, security scans, DB cleanup |
| Seiketsu | Standardise | Linting rules, PR templates, deployment checklists, runbooks |
| Shitsuke | Sustain | Automated enforcement, retrospectives, continuous training |

## 5. Experimentation Culture

From LeoYeAI/openclaw-master-skills, MIT.

More from LeoYeAI/openclaw-master-skills