World-Class Adaptability & Learning Playbook. Use for: market trend awareness, horizon scanning, PESTLE analysis, organisational agility, Kaizen, PDCA cycles...
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.
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.
| # | 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? |
| 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 |
| 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 |
Dimension 1 — Lean-Thinking People & Agile Teams
Dimension 2 — Lean Business Operations
Dimension 3 — Strategy Agility
| 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 |
| 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. |
| 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 |
Experimentation discipline matters as much as volume. Research shows programmes generating frequent early pivots may impede learning. Run the right experiments, learn the most from each.
| Type | Speed | Fidelity | Best For |
|---|---|---|---|
| Smoke Test | Hours–Days | Low | Demand validation |
| Concierge MVP | Days–Weeks | Medium | Value proposition testing |
| A/B Test | Weeks | High | Conversion optimisation |
| Wizard of Oz | Days–Weeks | Medium-High | Complex feature feasibility |
| Pilot Launch | Weeks–Months | High | Market readiness |
| Hackathon Sprint | Days | Low-Medium | Technical feasibility, ideation |
| Type | Description | Capture Method |
|---|---|---|
| Explicit | Documented, codified. Code, SOPs, runbooks. | Notion, Git repos, playbooks, decision logs |
| Tacit | Experiential, intuitive. Why decisions were made. | Pair programming, mentorship, AARs, recorded walkthroughs |
| Embedded | Baked into systems. CI/CD pipelines, linting rules. | ADRs, automated tests, process templates |
## Decision: [Title]
- Date: YYYY-MM-DD
- Status: Proposed / Accepted / Superseded
- Context: What situation prompted this decision?
- Options Considered: [List with pros/cons]
- Decision: What was decided?
- Rationale: Why?
- Expected Outcome: What do we expect to happen?
- Review Date: When will we assess the result?
## ADR-NNN: [Title]
- Status: Proposed / Accepted / Deprecated / Superseded
- Context: Technical context and problem statement
- Decision: The architectural decision made
- Consequences: Positive, negative, and risks
| Layer | Track | Sources |
|---|---|---|
| Product | Features, pricing, UX, roadmap, APIs | Product pages, changelogs, app stores, dev docs |
| Go-to-Market | Positioning, messaging, campaigns, partnerships | Websites, social, press releases, ad libraries |
| Organisational | Hiring, team growth, leadership changes | LinkedIn, job boards, Companies House |
| Financial | Funding, revenue signals, M&A | Crunchbase, PitchBook, regulatory filings |
| Strategic | Vision shifts, expansion, IP filings | Earnings calls, blogs, patent DBs, conferences |
Google Alerts (free) + Visualping (~£13/mo) + Similarweb free + LinkedIn + Crunchbase + Claude for synthesis
| Type | Description |
|---|---|
| Customer Segment | Same product, different target customer |
| Value Proposition | Same customer, different value (founders resist this most) |
| Channel | Different distribution/sales mechanism |
| Revenue Model | Different monetisation (subscription → transaction, B2C → B2B) |
| Technology | Same value prop, different stack/platform |
| Platform | Application → platform others build upon |
| Business Architecture | High-margin/low-volume ↔ Low-margin/high-volume |
| Market/Geography | Same product → different jurisdiction |
| Capability | Key Metrics | Cadence |
|---|---|---|
| Market Trends | Signals detected/mo, time-to-insight, actionable signal ratio | Weekly/Monthly |
| Org Agility | Decision cycle time, reorg speed, cross-functional collab index | Monthly/Quarterly |
| Kaizen | Improvements/mo, cycle time reduction, defect rate | Weekly/Monthly |
| Experimentation | Experiments/mo, validation rate, time to first learning | Weekly/Monthly |
| Knowledge Mgmt | Articles created/updated, search satisfaction, onboarding time | Monthly |
| Competitive Intel | CI coverage, competitive response time, win/loss completion | Weekly/Monthly |
| Pivoting | Signal-to-decision time, pivot success rate, resource reallocation speed | Quarterly |
The single most important metric: validated hypotheses per unit time, weighted by strategic importance. How fast the organisation converts uncertainty into knowledge.
Days 1–30 (Foundation):
Days 31–60 (Activation):
Days 61–90 (Optimisation):
For extended content — detailed tool comparisons, case studies (Amazon/AWS, Netflix, Toyota,
Ford, NSF I-Corps), advanced frameworks, and templates — consult:
→ references/extended-playbook.md
Remember: Adaptability is not a department. It is an operating system — daily habits, decision architectures, and cultural norms that compound over time. Learn faster than the market changes. BUILD – DOCUMENT – RESEARCH – LEARN – REPEAT.
ZIP package — ready to use