Weekly Rhythm

Weekly Rhythm

In a two-person project the biggest risk isn't too many meetings, it's loss of sync: two people drifting in different directions and noticing months later. This rhythm keeps sync with minimal meetings.

Weekly

What	When	Duration	Purpose
Week kickoff	Monday	30 min	Pick and own this week's issues. Talk through where last week got stuck.
Pairing session	Wednesday	90 min	One hard task on the same screen. Take turns at the keyboard. This is the hour when learning is most intense.
Week close	Friday	30 min	What got done, what didn't, why. Check the boxes on the month's wiki page.

Everything that stays async: GitHub issues and PR comments. Decisions made in a chat app get lost — anything that needs to be durable is written to an issue or an ADR.

Monthly

What	When	Duration	Purpose
Teaching session	Around the 15th	60–90 min	Explaining concepts to each other at a whiteboard. A concept that can't be explained hasn't been learned.
Rotation	Around the 15th	—	Areas swap (see Team and Roles)
Month close	Last day	90 min	Exit-criteria check, retro, next month's plan, content production

Month-close retro — three questions

1. Which of our decisions this month was good, and why?
2. What took longer than expected this month, and why?
3. What's the one thing we'll do differently next month?

The answers are written at the end of the relevant month's wiki page. The Month 6 blog post and interview narrative will grow out of these notes — so writing the retro is the raw material for the text you'll write later.

If a week slips

It happens. Rule: don't shorten the plan, shift it. Finishing Month 1 in 5 weeks is far better than half-finishing Month 1 and moving on to Month 2; every month is a layer that sits on top of the previous one.