The situation in front of you.
- Watch one full Playbook, end to end
- Read its Position, Plays and Precedents
- Work the Plan tool by tool, each step ending in Your Next Move
= 1024) leftSidebarOpen = false; if(window.innerWidth >= 1280) rightSidebarOpen = false" :class="{ 'dark': $store.theme.dark, 'left-sidebar-closed': !leftSidebarDesktop, 'right-sidebar-closed': !rightSidebarDesktop, 'overflow-hidden': leftSidebarOpen || rightSidebarOpen, 'sidebars-closed': !leftSidebarDesktop && !rightSidebarDesktop }" dir="ltr">
The situation“I have to ship something this week and it's not ready.”
Leaders who made the same call — what each did, and how it went.
WorkedShouldn’t have been tried
The second half of Charity Majors's engineering argument, codified across her charity.wtf blog and repeated in conference talks, is about separating two operations most teams conflate: deploying code and releasing a feature.
Calxeda built low-power ARM-based servers at a time when the idea was genuinely ahead of its era — microservers that would use a fraction of the power of conventional data centre hardware.
One Playbook for the situation in front of you, the full Library for the year ahead, or five seats for the team you lead. Every one at the Founders' rate.