Customer Obsessed Engineering
Subscribe
Sign in
Home
Notes
The Delivery Playbook
Archive
Leaderboard
About
The Delivery Playbook
Latest
Top
Discussions
How to write a good hypothesis log — and stop building useless stuff
Most hypothesis logs are feature lists with extra columns. The difference is running it up-front, in real discovery — and actually changing your plan.
Aug 31
•
Zac Beckman
1
Weighted Shortest Job First (WSJF) can’t see your showstopper
WSJF ranks features one by one — which is why a correctly ranked backlog still blows up at the eleventh hour. A steel thread is the fix: deliberately…
Aug 27
•
Zac Beckman
Why I retired “sprint” from the playbook
High-performing teams deploy daily. What’s the two-week box actually for?
Aug 20
•
Zac Beckman
1
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…
Jul 8
•
Zac Beckman
2
1
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…
May 28
•
Zac Beckman
2
1
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…
May 16
•
Zac Beckman
2
2
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.
Apr 30
•
Zac Beckman
2
1
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…
Apr 28
•
Zac Beckman
2
1
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…
Jan 28
2
3.5 Modeling
Engineering models eliminate mistakes & complexity, ensure better testing & reliability, and improve collaboration & understanding.
Dec 29, 2025
•
Zac Beckman
2
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.
Aug 14, 2025
•
Zac Beckman
2
1
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…
Jul 3, 2025
•
Zac Beckman
1
1
This site requires JavaScript to run correctly. Please
turn on JavaScript
or unblock scripts