Why Your Retro Isn't Working (And Won't, As Currently Run)
Most retros fail for the same boring reason: nobody owns the follow-through. Here's the format we use instead, and why it puts one name next to every action item.
Read more →Straight-talk essays on agile delivery, leadership, and the kind of organizational structure that survives contact with reality. No frameworks for framework's sake.
We coined the phrase on this site because we kept seeing it in the field: dashboards that look green while the team quietly runs on heroics. Here's what changed at three clients who stopped optimizing for the dashboard and started optimizing for the work.
Read the PieceMost retros fail for the same boring reason: nobody owns the follow-through. Here's the format we use instead, and why it puts one name next to every action item.
Read more →The teammate who saves every launch is also the reason nobody notices the process is broken. On building systems that don't depend on any one person staying late.
Read more →It's rarely the skills gap people expect. It's the identity one — the habit of being the person with the answer. Notes from inside the Manager to Leader Arc.
Read more →Every engagement starts the same way: watching how work actually moves, not how the org chart says it should. What that discovery phase looks like, and why we won't skip it.
Read more →You don't need enterprise process to grow past your founder's memory. A lighter framework for locally-owned businesses getting ready to open location two.
Read more →One shows who reports to whom. The other shows who actually talks to whom to get anything done. Most transformation work fails because it only ever touches the first one.
Read more →