Sustainable Strength

Recovery is not a reward, it is part of the plan.

In strength training, the most disciplined athletes don’t just train hard, they track what fuels the work: calories, sleep, macros. Performance isn’t only about what you do in the gym, it is about what you support outside of it, which is why tools like MacroFactor have become essential for serious lifters. Not for vanity, for visibility, so that every training block is fed with what it needs to grow.

The same principle applies in product. You can’t build a resilient team without knowing what you’re feeding it, and that is where tools like Jira, Aha!, or Linear come in, not just as ticket trackers but as visibility engines. They let you zoom out, spot overtraining, and identify where the strategic work is undernourished. Recovery in product isn’t just about taking breaks. It is about sustaining the energy to build well over time, because burnout doesn’t usually come from sprinting, it comes from sprinting without a cycle.

This is why elite lifters use periodization, planning not just the next workout but the next month, quarter, and year. They alternate intensities, deload, peak, and rebuild, and not because they’re lazy. They’re playing the long game.

Sustainable product teams follow the same rhythm. They don’t live in permanent crunch. They push when they have to, then deliberately create time to reflect, retool, or recharge. They respect the difference between urgency and importance, and they recognize that more activity doesn’t always mean more progress.

When you track your macros, you don’t just know what you’re eating, you know what you’re aiming for. When you track your product macros, the balance of innovation, maintenance, user research, and downtime, you build not just velocity but viability.

One example of this kind of tracking comes from Atlassian’s Team Health Monitors. These are not daily scrums or sprint reviews. They are recurring, focused check-ins designed to assess the long-term health of a team. Each one reviews key areas: clarity of roles, alignment on goals, confidence in decisions, pace of delivery, and engagement with stakeholders. Teams score themselves on a red-yellow-green scale so patterns show up over time. The point isn’t to be perfect, it is to stay aware: to notice stress points early, invest in what’s working, and surface risks before they derail momentum. It’s macro tracking for the makers, less about this week’s burndown and more about whether the system is still healthy enough to support what’s next.

The strongest teams aren’t the ones who go the hardest. They’re the ones who stay strong the longest.

When Your Teammate Doesn’t Sleep

There’s a new variable in 2026 worth naming. AI doesn’t sleep, it doesn’t deload, and it doesn’t take Q4 off to recover for Q1. The pace of an AI-augmented team is now set, in part, by a teammate that has no biology and no boundaries. The risk isn’t that AI burns out. It’s that the humans pairing with AI start absorbing AI’s pace as their own. The pace of the AI is not the pace of the mission. I’ll come back to this in the chapter on AI.

Recovery Is a Leadership Skill

If you want to go the distance, as an athlete, a builder, or a leader, you can’t just train intensity. You have to train sustainability. Recovery isn’t about stepping back, it’s about stepping up with clearer focus, steadier energy, and decisions made from purpose instead of panic.

In the gym you build this with sleep, nutrition, deloads, and reflection. In product you build it with boundaries, cooldowns, strategy days, and macro awareness. You build it when you protect the pause, when you track more than just tickets, and when you care not just about the sprint but about who is still standing after it. The mission won’t slow down, but you can build systems, and teams, that last.