Most teams plan a new cycle on the morning it starts. We ask everyone to plan it on the Friday before, and to keep Monday for finalizing it.
It's a small change. It adds no meetings and no steps. It only puts the hard part at the moment you're best placed to do it.
Before we go on
Six words to know.
They come up in everything we write. Here they are on one plan at Northwind, a made-up software team on a weekly loop.
- Loop
- Platform team weekly
- The cadence your team ships on: weekly, biweekly or monthly.
- Cycle
- Week of November 2
- One turn of the loop, like a sprint. Here, one week.
- Plan
- Emily CarterDraft
- What one developer commits to for a cycle.
- Outcome
- Cut checkout API latencyp95 340ms → 200ms
- The one result a plan leads with, and the number that will prove it shipped.
- Direction
- Pay down tech debt3 of 4 hours
- A broad area of work that plans give hours to. Your team sets it, and each developer writes their own tasks under it.
- Check
- Rollback planPassed
- Something an agent reviews every task for, like a linter for plans, against standards your team sets.
Friday is when you know the most
At the end of a cycle, you know exactly where things stand. You know what got finished and what didn't, what stalled and why, which conversations changed the picture and what the numbers did.
By Monday, most of that has gone soft. You spend the first stretch of the morning working out where you left off, then you plan from memory. The new cycle starts from a weaker picture, and the planning uses up the time that was meant to get things moving.
This matters more now that so much work happens alongside AI. An agent will start on whatever you hand it, so a cycle depends on how clearly you've said what it's for. That thinking deserves your best information, and on Friday you have it.
Planning lets a cycle end
An unfinished cycle tends to follow you home. There's research behind that feeling: Masicampo and Baumeister found that an unmet goal keeps pulling at your attention, and that making a specific plan for it can stop the pull, before any of the work is done.
That's what planning on Friday gives you. The next cycle's work has a place to live, so it can stay there until Monday.
Monday is for finalizing
What you write on Friday is a draft, on purpose. Things change over a weekend. A customer writes in, a priority moves, or you reread your draft with a fresh head and see that one of the goals was wishful.
So Monday's job is small: read the draft, change what has changed, and commit to it. You're reviewing, so there's no blank page to face, and the cycle can start as soon as you're done. You end up with the two things good planning needs, the detail of Friday and the distance of Monday.
Where it goes wrong
Each day has one way to fail.
Friday fails when planning is an afterthought. A draft dashed off on the way out the door only looks finished, and Monday inherits the problem. It needs real attention, so make room for it.
Monday fails when finalizing turns into starting over. If the draft gets rewritten every cycle, it isn't doing its job, so find out why.
Try it for a few cycles
You can start with nothing more than a shared document. Ask everyone to draft the next cycle before they finish this one, and to treat Monday as the time to finalize it. Give it a few cycles, because the first drafts are never the best ones.
It's also how Steermode runs. Every new loop starts this way: drafts open on the Friday before each cycle with unfinished work carried over, everyone finalizes on Monday, and an agent checks each draft against your team's standards before anyone has to read it.