Playbook Lite
A dual-track agile methodology grounded in design thinking. Authored for a consulting firm's strategy operations practice to transform how engagements ran, from discovery through delivery.
Discovery and delivery should run in parallel, not sequence.
Most consulting engagements treat discovery as phase 1 and delivery as phase 2. By the time build starts, assumptions have calcified and stakeholders are locked into a plan that no longer fits the ground truth.
Playbook Lite inverts this. Two tracks run concurrently: a Discovery Track continuously validates hypotheses with users and data, and a Delivery Track ships in short cycles. The tracks feed each other. Insights from discovery reshape delivery priorities weekly. Production feedback reshapes discovery questions.
The result is a team that moves faster without moving blind.
Five operating rhythms across two tracks.
Each rhythm has a cadence, an owner, and a clear output. Teams adopt the ones that fit their context and skip what does not apply.
Continuous Discovery
Weekly user conversations, data reviews, and hypothesis validation. Owned by design + research. Outputs: opportunity backlog.
Sprint Alignment
Two-week delivery sprints synced to discovery outputs. Owned by engineering. Outputs: shipped increments.
Dual-Track Sync
Weekly ceremony where both tracks share learnings and re-prioritize. Owned by product. Outputs: updated roadmap.
Design Critique
Bi-weekly review of in-flight work against principles, accessibility, and heuristics. Outputs: ship-or-iterate calls.
Retrospective
Every four weeks, reflect on ways of working, friction, and wins. Outputs: ways-of-working updates.
Methods, templates, and ceremonies.
Curated from a decade of consulting practice and adapted to the dual-track model. Every tool here survived real engagements.
Service Blueprints
End-to-end process mapping with swim lanes for frontstage, backstage, and support. Used in discovery to surface friction.
Design Principles
Project-specific principles codified in the first week. Referenced in every critique and decision.
Stakeholder Journey Maps
Internal-facing maps showing how decisions and approvals flow. Used to de-risk rollouts.
Opportunity Backlog
Kanban of validated problems and hypotheses, feeding the sprint backlog weekly.
Assumption Cards
Every decision has an assumption card documenting what we believe, why, and how we will test.
Decision Logs
Timestamped record of choices made, alternatives considered, and trade-offs accepted. For handoff and audit.
What keeps dual-track agile from collapsing into chaos.
The speed of this methodology only works with explicit constraints. Without these, teams fragment and quality drops.
Definition of Ready
No work enters a sprint without a validated problem, a success metric, and an assumption card.
Definition of Done
Ships only when it meets accessibility, analytics, and design critique bars. No 'we'll fix it later.'
Timeboxed Discovery
Every hypothesis has a decision deadline. Research that runs forever is banned.
One Owner per Track
Design owns discovery, engineering owns delivery, product owns sync. No diffused accountability.
Escalation Path
When tracks diverge irreconcilably, a 24-hour escalation forces a decision. No stalled projects.
Transparent Priorities
Roadmap is visible to everyone in the firm. No shadow work, no parallel initiatives.
Applied across engagements. Shaped subsequent practice.
Deployed as the default methodology for strategy operations engagements after a 6-month pilot.
Standardized the delivery rhythm across all project types, from pure strategy to tech delivery.
Continuous discovery cut the time from kickoff to first actionable hypothesis in half.
Dual-track sync prevented the late-stage scope negotiations that had plagued previous engagements.
Not a framework. A way of working.
Playbook Lite was never marketed as a proprietary framework. It was taught, shared, and adapted by every practitioner who used it. The point was not to own a methodology. The point was to give teams language and structure for moving fast without moving blind.
It is the ancestor of every dual-track system I have built since. The Strategic Translation Architecture is its grown-up sibling. The Unspoken Balance build used the same rhythm, compressed into twelve hours.
