The engineer's
Delivery Playbook

Beta

A living technology delivery runbook turning your team into seasoned experts, delivering reliably the first time and every time. With activity guides, workshops, templates right at your fingertips.

28
Delivery topics
One per subway-map activity
19
Process guides
Techniques with worked examples
6
Workshops
End-to-end facilitation guides
18
Templates
Battle-tested working artifacts
140+
Articles
New content every month
The Delivery Playbook
The Customer Obsessed Delivery Playbook — bound reference volume.

The checklist every engineer needs

Pilots rely on checklists. For every flight, every aircraft, every weather. It's what keeps the plane in the air when the pilot is tired, distracted or wrong about what's happening. Engineers need one too. That's why I wrote the Delivery Playbook.

Open it when you're stuck. When you're planning. When you're not sure what the next move is. It tells you the inputs, the moves and the outputs — so the team in front of you can run the activity with the rigor of a seasoned practitioner, whether they've done it before or not.

The Delivery Playbook is your runbook while Customer Obsessed Engineering is your community, exploring ideas at length — arguments, case studies, stories — where the playbook is lean, prescriptive and ready at your desk. A checklist, not an autobiography. A living toolkit with guides, workshops, templates and an easy to follow map.

Workshops that turn diagnosis into action

Every workshop produces action-items with named owners, expected recovery and a review date. Actions track back to the same waste walk data the workshop started with, and progress is measured over time.

Waste walk

Track team activities to discover what's draining time and effort away — and recapture it by prioritizing and focusing on the 20% of activities that drive 80% of the outcomes.

activity logging · gateway activity · sprint capture
Open the workshop →

GembaKai readout

The gateway session after a sprint of activity logging. Walk the team through the readout, frame the productivity opportunity, pick the next workshop from the data — go after the 80%.

readout deck · sprint timeline · circle of control
Open the workshop →

Rework workshop

Trace rework hours back to their origin. Almost always the highest-leverage starting point — rework upstream turns into everything else downstream.

5 Whys · fishbone · A3 · event storming
Open the workshop →

Automation workshop

Surface the manual work the team has normalized. Five automation domains, cost × frequency × people, ROI matrix with a Theory of Constraints overlay.

ROI matrix · Theory of Constraints · scenario scoping
Open the workshop →

Planning workshop

Find meeting overhead, late decisions and external dependency friction. The hardest of the four because planning waste is diffuse — a hundred small things rather than one big one.

SWOT · meeting audit · event storming · force-field analysis
Open the workshop →

Event storming

A sticky-note-driven design workshop that puts engineers, customers and subject-matter experts around a shared wall to map business events end-to-end — exposing decision points, handoffs and hotspots in half a day.

events · commands · state · ubiquitous language
Open the workshop →
Continuous Improvement

Integrated and effective

The Delivery Playbook leans heavily on continuous improvement. Incremental rapid delivery, tightly integrated feedback loops, and shift-left policy is grounded in practical, every-day actions like the GembaKai waste walk tool — a guided activity that focuses the team on the highest value activities.

Waste Walk sprint summary readout.
  • Capture
    Teams capture effort by activity in the Waste Walk app — pinpointing what drains time and energy.
  • Measure
    Facilitated workshops direct focus where it's needed — driving forward momentum.
  • Adjust
    Progress is tracked. The number moves, or you learn something new, accelerating team velocity.
The bottom line

Use it every day

Open it when you're stuck. Open it when you're planning. Open it when you want to remind yourself of a step. Treat it the way an airline pilot treats a preflight checklist — not as bureaucracy, but as the thing that keeps the plane in the air.

Built and maintained by Zac Beckman — forty years of building software, leading engineering teams across defense, entertainment, research, enterprise and startup contexts. Every pattern in the playbook has been used, broken, refined and used again.