Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
World-Class Adaptability & Learning Playbook. Use for: market trend awareness, horizon scanning, PESTLE analysis, organisational agility, Kaizen, PDCA cycles, 5S, lean operations, experimentation culture, hypothesis-driven development, A/B testing, MVP design, knowledge management, decision logs, ADRs, after-action reviews, competitive intelligence, SWOT, Porter's Five Forces, battlecards, pivoting strategy, lean startup, business model canvas, signal detection, scenario planning, learning velocity, value stream mapping, Gemba walks. Trigger when discussing ANY organisational learning, strategic adaptability, continuous improvement, competitive analysis, experimentation, knowledge systems, or pivot/persevere decisions. Also for startup strategy around product-market fit or validated learning. If it touches learning faster, adapting better, or competing smarter — use this skill.
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
Automated enforcement, retrospectives, continuous training
5. Experimentation Culture
The Scientific Approach
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.
Experimentation Lifecycle
Hypothesise — "We believe [segment] will [action] because [reason]."
Organise — Single source of truth per knowledge type. Consistent tagging (domain, jurisdiction, status). SKILL.md architecture for AI workflows.
Share — Push (digests, Slack alerts, onboarding). Pull (searchable wiki, AI Q&A). Social (pairing, knowledge sessions, rotations).
Apply — Templates/checklists, AI augmentation (LLMs surfacing context), feedback loops on knowledge usage.
Decision Log Template
## 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 Template
## ADR-NNN: [Title]
- Status: Proposed / Accepted / Deprecated / Superseded
- Context: Technical context and problem statement
- Decision: The architectural decision made
- Consequences: Positive, negative, and risks
7. Competitive Intelligence
The CI Cycle
Define — What decision will this inform? Be specific.
Separate identity from strategy — Experience, mentoring, and team size enable pivoting. Seek external perspective.
Define what stays vs changes — A pivot preserves a kernel of value while changing one element.
Design the experiment — MVE to validate new direction BEFORE full commitment.
Communicate with radical transparency — Tell investors, team, stakeholders: what you learned, what's changing, why.
Execute with speed — Half-pivots (split between old and new) are the most dangerous state.
Pivot vs Persevere vs Kill
Noise: Random short-term variation. Do not pivot.
Signal: Persistent validated evidence current direction is wrong. Consider pivot.
Kill: Repeated pivots fail, hypothesis space exhausted. Preserve capital, redeploy.
9. Measurement Framework
Adaptability Scorecard (Quarterly)
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
Meta-Metric: Learning Velocity
The single most important metric: validated hypotheses per unit time, weighted by strategic importance.
How fast the organisation converts uncertainty into knowledge.
10. Quick-Start: 90-Day Implementation
Days 1–30 (Foundation):
Weekly trend digest + signal collection
Decision log for all significant decisions
Top 5 competitor monitoring
First PDCA retrospective
SKILL.md knowledge architecture
Days 31–60 (Activation):
First structured experiment (pre-registered criteria)
Stakeholder knowledge gap interviews
First competitive battlecard
Visual management (Kanban/equivalent)
First Kaizen event on a process bottleneck
Days 61–90 (Optimisation):
Refine all cadences (daily/weekly/monthly/quarterly)
Baseline learning velocity + improvement targets
First quarterly PESTLE + Horizon Scan
Assess pivot signals against framework
First Adaptability Scorecard
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.
