Sprint rhythm

Weekly cadence beats sporadic experimentation. Consistent rhythm: plan, ship, measure, learn, repeat.

Typical week

• Monday: review last week, plan this week
• Tuesday-Thursday: ship tests
• Friday: measure running tests, write up learnings

Growth retrospective

Monthly or quarterly: what worked, what didn't, what's next.

What to do with this

• Set a recurring weekly calendar block for sprint planning + retro, without ritual the process drifts
• Ship 2-3 tests per week, fewer means low velocity, more means poorly-instrumented tests
• End each week by documenting outcomes, undocumented tests become undiscoverable learnings inside 3 months
• Run monthly retros to spot patterns, individual test results are noisy but monthly themes show what's really working
• Protect the ritual from other meetings, growth teams that sacrifice sprint rhythm to meeting creep lose the compound effect