Customer Obsessed Engineering

Customer Obsessed Engineering

Home
Notes
The Delivery Playbook
Archive
Leaderboard
About

The Delivery Playbook

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
3.2 Security & governance
You don't have to be a security genius to deliver secure, compliant applications. You just need a roadmap to follow, a clear strategy and a tactical…
 • 
Zac Beckman
 and 
Will Yang
3.1 Value mapping
Properly understanding feature value, risks and rewards informs prioritization. It gives you the means to take control of your work and deliver fast…
 • 
Zac Beckman
2.9 Functional architecture
Your functional architecture assembles a finished design. It answers the question, “exactly how will we build our product?”
 • 
Zac Beckman
3.0 Delivery (phase 3)
Phase 3: Creating detailed technical specifications, engineering work, and building a product increment that is ready for production.
 • 
Zac Beckman
2.8 Delivery processes & tools
Your delivery toolchain impacts the entire team, every single day. Getting it right means massive productivity gain.
 • 
Zac Beckman
2.7 Architecture foundation
Your architecture foundation should be immutable. It’s the bedrock on which everything is built, enabling your team to create new capabilities while…
 • 
Zac Beckman
The 30-minute guide to Domain Driven Design: A secret weapon to solve tough problems (Part 2)
Create better team alignment, clearly define boundaries, and design around resiliency, scalability, and customer-driven value.
 • 
Zac Beckman
2.6 Target state architecture
Methodically approaching your conceptual model of the future and the technologies that fulfill that future is crucial if you want to achieve or surpass…
 • 
Zac Beckman
© 2025 Boss Logic LLC · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture