Next week will be different.
You said that last Sunday. And the Sunday before that one.
It’s the same chaotic week wearing a different date, and it repeats until you sit down and change something on purpose.
And it’s not that you don’t work. You do. The week just moves under your feet.
Monday’s plan meets Tuesday’s reality. A task turns out bigger than you thought. Wednesday hands you a better idea than the one you started with.
By Thursday you’re carrying three half-versions of the project in your head, and the evening goes to sorting out which one you’re even building.
That’s what progress looks like from the inside. Things change as you work, and without a system that absorbs the change, the change eats the week.
Nine steps, one page of paper, 70 minutes the first time, 30 once it’s running.
Three chapters:
The 7 days behind you. What a review is actually for. Theory.
The 5 days ahead. What a plan has to survive. Theory.
The toolkit and the run sheet. The setup, the steps, the page. Practice.
Not recommended, but if you’re short on time, jump to Chapter 3 and run it.
Chapters 1 and 2 explain what each half is for and hand you the reasoning. Chapter 3 is the run sheet with a timer against every step and specific tools linked.
What the Sunday Review is
One sentence: a fixed weekly session where rested-you reviews the past 7 days and makes decisions for the next 5, so tired-you only has to execute them.
One word: iterate.
If this week sucked, the easiest way to make sure next week doesn’t is finding what was wrong with it and deciding, in advance, what happens instead.
Sunday-you is rested. Sees the calendar. Knows Wednesday has the late meeting and Friday is a write-off. Good decisions, cheaply.
Tuesday-you sits down at 21:00 after eight hours of work and a busy evening. Ask him what matters and he opens YouTube, because deciding is expensive and he’s broke. Worse decisions, expensive.
So, don’t ask him. Decide Sunday, execute Tuesday.
Time spent planning buys back more time than it costs.
Two rules hold the whole thing:
The review and the plan are two different jobs.
Review always comes first.
Chapter 1: The 7 days behind you
30 minutes. Facts, diagnosis, cleanup.
In that order, and the order matters: you cannot fix a week you haven’t looked at.
The week was thinner than it felt
Seven dates and what actually happened under them.
Only things that moved.
“Wrote half the sales page”
counts.
“Thought about the sales page a lot”
does not.
“Researched”
counts only if something exists on disk that didn’t exist before. And no line here starts with
“I felt.”
It will look thinner than the week felt. That’s the point of doing it. You remember the week as busy, the page shows three things moved, and both are true. Only one of them ships a project.
This is also the step that kills the two lies you tell yourself every Sunday night:
“I did nothing this week”
and
“I was busy all week.”
Both feel true. Sunday review distills which actually was.
3 wins, or you quit within a month
Then three things that went well. However small.
If every Sunday only tells you what you failed at, you'll find a reason to skip next Sunday.
18 minutes on a dead Tuesday is a win. One uncomfortable email sent is a win.
Fixing the thing that annoyed you for a month (and took 5 minutes to complete) is a win.
10 problems is not a diagnosis
For everything that didn’t move: one sentence.
“Didn’t touch the landing page because I never decided what goes on it.”
“Skipped Wednesday because the meeting ran to 20:00 and I had nothing prepared for a short session.”
Compare that with:
“I was lazy this week.”
That has no fix attached to it. It just feels bad, and feeling bad has never once produced a landing page.
Then the question that pays for the 30 minutes: of everything that went wrong, what one thing limited output the most?
One bottleneck. Hormozi built his approach on this: find the single constraint, put your leverage there, ignore everything else until it moves.
Ten problems is not a diagnosis. One is.
Finding it is one thing, fixing it is a skill. Sitting with the highest leverage task until it’s done, ignoring everything else, is a skill. An important one, and one that needs a lot of practice.
It’s boring. No decision about what to work on. No block in the calendar. Starting too late. A task too vague to begin. Phone within reach.
Whatever it is, next week’s plan has one job: make that specific thing not happen again.
Open loops rent space in the head you build with
Every unfinished small thing takes a slice of attention and keeps it. A dozen of them and you can’t settle when you sit down.
The half-set-up tool. The unanswered message. The 80% draft, the broken link, the friend you owe a reply.
Each one gets one exit: do it, schedule it, or kill it. “Maybe someday” is not a date.
The killing is the part people skip, and it’s the part that works.
Every dead loop you keep alive out of guilt is renting space in the same head you’re trying to build with.
I think I’ve already mentioned this somewhere.
Three numbers beat a page of reflection
This is what makes reviews compound instead of repeat. Same three numbers, every week, same corner of the page:
Sessions done vs planned. “3/3” or “1/5”.
Total build time. Minutes or hours, whatever your tracker says.
One output number for your project. Subscribers, words, videos, sales. Pick one and never change it.
3 numbers, 10 seconds. After 6 weeks you have a chart of your own behavior, and it tells you things no amount of reflecting will.
Like the fact that your good weeks all started with a Monday session, or that the month you “worked constantly” you logged four hours.
We like numbers. What we like more is watching numbers grow.
Chapter 2: The 5 days ahead
20 minutes. 4 decisions, in this order.
One thing that either exists next Sunday or doesn’t
“Work on the course” is not it. “Record and edit module 1” is.
The bar: if the week produced nothing else, would this still count as a good week? If the answer is no, you picked the wrong thing.
How to pick it when everything feels urgent?
Which one moves the project closest to being real for someone else?
Which one am I avoiding? That’s usually the one.
Which one does this week’s constraint actually allow?
That last question is why the review comes first. If your constraint was “no time on weekday evenings,” picking something that needs 10 hours is planning to fail on purpose.
3 real blocks beat 7 imaginary ones
Not “I’ll find time.” Times in the calendar, placed around obligations that already exist.
3 > 7
You want seven, I know. But…
Buehler, Griffin and Ross asked students in 1994 when they’d finish an academic project.
Average prediction: 34 days.
Average reality: 55.
When asked for a date they were 99% certain about, only 30% made it.
You’re not the exception. Nobody is, that’s what makes it a bias.
Take the number that feels right and cut it.
That’s the whole chapter 13 in Morgan Housel’s “The Psychology of Money”.
His line is the one worth keeping:
“The most important part of every plan is planning on the plan not going according to plan.”
Money, evenings - same physics.
A plan built on your best week has no margin, so the first bad day takes the whole plan down.
A plan built on your worst week survives, and surviving is what lets it compound.
In practice that means underplanning on purpose. 3 blocks when you could fit 7.
3 real blocks beat 7 imaginary ones twice. Once on output, once because you end the week having kept your word to yourself. That second one is the whole game long-term.
Four placement rules:
Energy first, gaps second. Put the hardest block where your energy is, not where the calendar happens to be empty. Mine currently is 5 to 7 AM, before the day gets a vote on it. (Why? That’s in the next deep dive).
Same slots every week. Repetition removes decision. A block that moves is a block you negotiate with.
Around real life. Wednesday has happy hour? Don’t schedule a block there and then call yourself undisciplined when it dies. Choose and experience the option you choose to the fullest without regret.
Name them by output. “Record module 1 intro” over “Deep work session”
If you don’t know where your energy actually is, that’s a one-week experiment: rate your energy 1 to 10 at three fixed times a day for seven days. The pattern shows up fast.
Template in resource library under Framework Docs.
If you were to remember just one thing from this post, let it be this. I can’t even count how many times I’ve made this mistake, and I not learned from it.
New here? AchievR is one post a week for people with a real job and a project they refuse to give up on.
Identity, systems, consistency, output, money: things you can use the same night.
The welcome email comes with the Pathfinder Template: a free starting point for picking a project worth your hours.
The week will change on you, what’s about the plan then?
Wednesday, you find a better way to do the thing.
Thursday, somebody sends you an opportunity.
Friday, you realize step 3 made step 1 pointless.
Your project has changed, so the plan you made on Sunday is now out of date.
This is the biggest problem with planning a week ahead. Things come up that are beyond your control, and they come up every week.
There is a solution. Not perfect, but it’s there.
1. Time blocks don’t disappear but move.
If an unexpected event comes up on Monday and you couldn’t stick to the plan, the Monday block moves to Thursday, and so on.
Alternatively, you can stack the blocks on Saturday and catch up.
2. A new idea, a new opportunity, or something you now want to reorganize goes on the list and waits.
Note: write it down specifically. “Rewrite the pricing section” instead of “pricing”, because in three days you won’t know what you meant.
That’s why review is 7 days and plan is 5 days, as weekdays are more predictable.
Split the pile or the pile wins
One more reason weeks feel chaotic: everything sits in the same undifferentiated heap.
Finish the module. Buy your mother a present. Answer the client.
Thirty mixed items in one list adds a lot of friction.
Split the capture into three buckets:
Daily errands.
Day job.
Your project.
Three lists of ten read like a Tuesday. One list of thirty reads like a wall. Same items, different start friction.
Armor the week before it hits you
Name what will try to kill the week, then write the response as an if-then sentence:
“If the meeting runs past 20:00, then I do just the 18-minute version.”
“If Thursday collapses, then Saturday morning is the makeup block.”
“If I’m still scrolling at 21:37, then the phone goes in the other room, and I’ll just go to sleep.”
This isn’t motivational. Gollwitzer and Sheeran pooled 94 studies with over 8,000 people, and if-then plans came out at a medium-to-large effect, roughly doubling how often people actually do the thing.
It works because a tired brain is bad at making plans and fine at following them.
Rules are good because they are cheap to obey. The whole post comes down to: lower friction.
Monday’s first move decides Monday
Write the first physical action of Monday’s block.
Verb + object, something you could start in 30 seconds without thinking.
Instead of
“start module 1.”
Write:
“open the slide file and record the intro.”
Why 5 days and not 7
A few more words on why plan Monday to Friday and leave the weekend empty.
You can’t see the weekend from Sunday. Somebody visits, someone gets sick, you get invited somewhere, the weather turns. Six days out, a weekend plan is a guess dressed as a commitment.
Every plan you break teaches you that plans are optional. Write 7 blocks, hit 4, and you learn to ignore with ease. Do that three weeks in a row and the review stops working, because you stopped believing it.
Empty weekend becomes your buffer. Wednesday collapses, Saturday morning catches it.
Chapter 3: The toolkit and the run sheet
Theory over. This is what you do.