Customer Obsessed Engineering

Customer Obsessed Engineering

Home
Notes
The Delivery Playbook
Archive
Leaderboard
About

The Delivery Playbook

Why I retired “sprint” from the playbook
High-performing teams deploy daily. What’s the two-week box actually for?
 • Zac Beckman
3.8 Engineering
Everything until now bought you speed — engineering is where you spend it, turning live specifications into production-ready code one small merge at a…
 • Zac Beckman
Can you rely on SAFe to deliver elite-performer gains?
The cadence got shorter; the shape didn’t change: SAFe is what happens when you keep the waterfall org chart, rename the meetings and run a PI Planning…
 • Zac Beckman
Pull requests are a symptom of low trust: here’s the fix
T*D is the new name for the Playbook trifecta: Test-Driven Development, Trunk-Based Development and Team-Focused Development, fused into one operating…
 • Zac Beckman
Product teams really do outperform: bringing the receipts
Researchers at DORA, McKinsey and Google have spent a decade proving what good engineers already know. It’s time to put that knowledge into practice.
 • Zac Beckman
3.7 Elaboration
Elaboration takes your specifications from skeleton to increment-ready, fleshed out across every layer at which the system is tested — and live-linked…
 • Zac Beckman
3.6 Specification
Before coding we need to make sure our design has enough fidelity. Specification is about adding those details, the happy paths as well as the failure…
3.5 Modeling
Engineering models eliminate mistakes & complexity, ensure better testing & reliability, and improve collaboration & understanding.
 • Zac Beckman
How to use a playbook
Even engineering teams need a playbook, just like a sports league or an elite operations unit. Here’s how having a playbook transforms your team.
 • Zac Beckman
3.4 Tactical event storming
Tactical event storming adds fidelity to your business processes and event maps. It extends your "line of sight" down into the technical design while…
 • Zac Beckman
3.3 Identify product increment
Choosing what to build next is often hard. How do you balance a small, fast-moving feature with making a big impact? How can it be “feature complete…
 • Zac Beckman
Why you need a Zero Trust Architecture (and how to get one)
Shifting from “trust but verify” to simply “never trust, always verify” is the only safe path. Here’s why, plus, a step-by-step plan to get it done.
 • Zac Beckman and Will Yang
© 2026 Boss Logic, Inc. · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture