Change the Pattern, Not the Practice

Sometimes listening reveals that the ritual itself needs to change, and when things stop working, you don’t abandon the ritual, you adapt it. Progress isn’t a straight line, it’s a cycle of push, plateau, and pivot. When you hit the plateau and the usual ritual no longer delivers results, that is not a sign to quit but a sign to evolve.

In the gym, this happens all the time. You run a successful squat cycle, adding five pounds a week like clockwork, and then you stall. Your knees cave, your speed slows, and the bar starts winning. The answer is not to scrap the movement but to change the pattern. Maybe you shift to pause squats, change your stance, or drop the volume to focus on recovery. The ritual of showing up and squatting stays, and only the shape of it changes.

A product team stalls the same way, and the fix is the same. The standup that once helped your team sync becomes a box-checking chore. The planning meeting that used to set priorities now spirals into status updates. That doesn’t mean you stop planning, it means you shift how you plan. You move from live check-ins to async threads, and you replace calendar fatigue with focused, flexible rituals that match what your team needs in its current phase of growth. Rituals that don’t evolve become rules, and rules, as we have seen, break people.

This is especially true in globally distributed teams. At Elastic, our workforce spans time zones and continents, and we had to learn early that rituals built for co-located teams don’t translate. A sync meeting at 10 a.m. in California is 7 p.m. in Berlin and 2:30 a.m. in Sydney. So we changed the pattern and moved toward asynchronous rhythms:

• Key decisions live in documents, not meetings.
• Slack threads replace sidebars.
• Recorded meetings include transcripts and tagged callouts.
• Big calls are followed by quiet time, space for global teammates to reflect, respond, and contribute.

We didn’t stop collaborating, we restructured how and when it happens. The ritual of cross-team communication stayed, its shape changed, and it made space for more voices, not fewer.

We are not the only team that publicly evolved its rituals as it grew. Linear has documented how they shifted from rigid sprints to six-week cycles, lightweight async-first standups, and tighter scope-cutting rituals. The cadence changed and the mission did not. Their team guide reads like a working document of how rituals should evolve as the company evolves around them.

The newest version of this is happening in 2026 with AI. Standups now run with AI-generated summaries instead of live recaps. Retros surface patterns from team data that nobody had the time to read on their own, and mock reviews include an AI co-reviewer. The ritual is still the ritual (show up, learn, adapt), but the form is shifting fast. That is not a problem, it’s a sign that rails can take new shapes when the train evolves. I’ll come back to what AI changes here, and what it doesn’t, in the chapter on AI.

What matters isn’t how you do it, it’s that you keep showing up with purpose. You hit a wall, you adjust, and you don’t abandon the work, you change the pattern. That is the lesson: rituals serve the mission, and when they stop serving it, you reshape them. Don’t confuse rigidity for discipline, and don’t let the form matter more than the function. (And please, don’t treat your favorite product management book like doctrine. Those frameworks weren’t written for your team. Your mission was.)

Rituals aren’t constraints. They’re commitments, but only if we let them evolve. The strongest systems, the longest-lasting teams, and the most resilient lifters all share this in common: they don’t cling to routine for routine’s sake. They adapt, with intention, with feedback, and with the mission in mind.