Repetition with Intention

You don’t get strong by lifting heavy once. You get strong by showing up again. And again. And again.

But if you do the same thing forever, you don’t get stronger. You get stuck.

That’s the tension of progress: it demands ritual, but it punishes repetition without variation.

Whether in the gym or in product, growth comes through iteration. Small, deliberate cycles of effort. You log your training. You tweak your form. You try a new tempo. In software, you ship. You measure. You talk to the user. You try again. The process isn’t glamorous. But it’s generative.

Rituals compound. Rules confine.

A rule says “do this.” A ritual says “do this because it matters.” One is brittle. The other bends with you.

Agile isn’t magic. It’s a set of rituals: standups, retros, demos, sprints. They only work when they’re anchored in meaning and adapted to context. Treat retros like checkbox theater and you’re looping, not iterating. If your standup sounds like “I did stuff, I’ll do stuff, no blockers,” you’ve got a ritual without reason.

The same failure shows up in the gym. People find a powerlifting program online and follow it to the letter, even when it doesn’t fit their recovery, their age, their job, their life. They wonder why they plateau, or get hurt. It’s because they forgot the principle beneath the plan.

That’s where most systems fail. Not because the framework is flawed, but because the user is forgotten. They’re treated like an input to a method, instead of the reason for its existence.

Let’s be honest: there’s no shortage of books telling you how to do things. And yes, here we are, writing another one.

But this isn’t a blueprint. It’s a philosophy. The implementation is on you.

What works for one team, one lifter, one body, won’t work for another. That’s not failure. That’s reality.

Stefi Cohen didn’t become a record-breaking lifter by blindly following a single powerlifting template. Her training evolved through experimentation: strength phases, hypertrophy cycles, hybrid athletic blocks. She didn’t just lift heavy. She studied her feedback, varied her stimuli, and rewrote her rituals to fit her mission. Progress didn’t come from rigidity. It came from rhythm and reinvention.

In product, that same spirit of experimentation lives in hack weeks. Short, sacred breaks from routine where teams can stretch in new directions.

Atlassian, Spotify, and Elastic have all embraced this. At Elastic, hack weeks became a celebrated ritual — not just for innovation, but for joy. Some of Elastic Security’s most creative features were born not in sprint planning, but in that carved-out chaos.

Sometimes, the best way to realign with the mission is to deliberately step outside it.

Rituals work when they’re shaped by the user, not imposed on them. They’re tools, not commandments.

And when they’re working, you feel it. Not just in output, but in outlook. A team that trusts its rituals doesn’t need micromanagement. A lifter that trusts their program doesn’t need motivation hacks. The rhythm carries you. The meaning sustains you.

But rituals aren’t static.

They must flex to your fatigue. They must bend to your bandwidth. They must evolve, not just to avoid boredom, but to stay honest with the mission. Same input, same outcome. If the goal has changed, so must the reps.

That’s what separates the lifter who grows from the one who stalls. That’s what separates the product team that adapts from the one that burns out.

Because if the mission is the magnet, rituals are the rails.

They don’t tell you where to go. They keep you from sliding off the path while you find it.

Rituals give you direction.

But progress? That comes from the work itself. The grind, the reps, the effort no one applauds.