Process is a tool
Every framework worth anything was extracted from a specific team solving a specific problem under specific constraints. It worked. Then it got written down, and the constraints didn’t travel with it.
That’s the whole story of why process adoption disappoints. You imported the answer without the question.
Diverge, then converge
Under the naming, most methods are doing the same two things in alternation: open the space, then close it. Generate options without judging them, then commit without generating more.
The failures are usually a failure to switch. Teams stuck in divergence explore forever and call it discovery. Teams stuck in convergence execute the first idea anyone had and call it bias for action. The framework matters far less than whether someone is watching which mode you’re in and saying so.
Blend deliberately
Take the standup and drop the sprint. Keep the design critique and skip the personas. This looks like indiscipline and is usually just fit — the useful question about any ceremony is what it would cost you to remove it, and if nobody can answer, that’s the answer.
Story points are the usual first casualty, and rarely missed. The ritual produces a number that then gets used as though it measured time, by people who have agreed out loud that it doesn’t. Drop it and what’s left is the conversation the estimate was smuggling in — what’s unclear, what’s risky, what nobody has looked at yet — which was the part doing the work, and can be had directly.
Where it breaks
Pragmatism has a predictable failure mode, and it is more common than dogmatism.
“Use what suits the context” is indistinguishable, from inside, from having no process at all. Every skipped step is justified in the moment — that retro wouldn’t have helped, this week is unusual — and the accumulation is a team where nothing is reliable and everything is a judgement call, which is exhausting for everyone who isn’t the founder.
Process exists mostly for the cases where judgement is unavailable: someone new, someone tired, a Friday deploy, a decision made when the person with context is asleep. Those are precisely the cases the pragmatic argument doesn’t consider, because it’s made by someone with full context on a good day.
Adherence also has an underrated benefit: it’s legible. A team that follows a known method can be joined. A bespoke blend that lives in the founder’s head takes six months to learn and cannot be handed over — you’ve optimised for current fit at the cost of every future member.
So: process is a tool, and tools have maintenance. Pick the smallest set you’d defend, write down why each exists, and re-examine it when the team changes size rather than whenever it’s inconvenient.
Takeaway: process is a tool, not a value.