We stopped doing quarterly planning and switched to six-week cycles with two-week cooldowns. The cooldowns are for tech debt, experiments, and developer-chosen projects. Team satisfaction scores jumped 30% and, counterintuitively, feature delivery actually accelerated.
Post-mortems without action items are just storytelling. We implemented a strict follow-up process: every post-mortem produces at most three concrete action items, each assigned to a specific person with a deadline. Items that don’t get done within two sprints get escalated or explicitly deprioritized.
Scaling Challenges
We replaced our homegrown metrics pipeline with an off-the-shelf observability platform. The team resisted initially — ‘we can build something better suited to our needs’ — but the maintenance burden of the custom solution was consuming 20% of one engineer’s time every sprint. Sometimes buying is the right engineering decision.
Our initial benchmark numbers looked promising in staging but fell apart under production traffic patterns. The difference? Staging used uniform request distributions while real users exhibit bursty, correlated behavior that exposes different bottlenecks entirely.
None of these changes were revolutionary on their own. The compounding effect of many small, deliberate improvements is what transformed our workflow. Start with the one that resonates most and build from there.
Leave a Reply