Insights / Building and growing teams

You don't have an execution problem. You have a rhythm problem.

Teams that only watch the two-week sprint see every ticket as an emergency. They run sprint after sprint without checking what they're running toward. Sprinting 52 weeks a year isn't high performance. It's poor pacing.

In Build, Tony Fadell describes a team's momentum as layers of rhythm, from daily work up to the company's big milestones. The short cycles exist to serve the long ones, not to manufacture urgency.

Moving past year-long release plans was a real step forward. But somewhere along the way, reacting fast became the measure of a good team, and reacting to today's fire isn't the same as building tomorrow's foundation. Agility needs a destination.

Good pacing is knowing when to surge for a launch, and when to let the team breathe.

Ask me about

How I pace a team's work around real market milestones.

Email me about this

Let's talk

Hiring for design leadership, or want to compare notes?I read all my messages.