Every Monday morning used to feel like starting from scratch.
I knew I'd been busy the week before. I just couldn't tell you what had moved forward, what was stuck, or what I'd actually committed to doing next. I was carrying it all in my head, which meant I was carrying it everywhere — including into the weekend.
Sound familiar?
The problem wasn't discipline
I used to think I needed to be better at following through. More organised. More consistent. If I just tried harder, I'd stop dropping things.
But the real problem wasn't effort. It was that I had no system for looking at the week clearly before leaving it behind, and no system for shaping the next one before it started. I was just moving from one week to the next and hoping the important stuff didn't fall through the gaps.
It does fall through the gaps, by the way. Every time.
The reframe that changed how I think about it
A weekly review isn't a performance review. You're not grading yourself or accounting for every hour.
It's a navigation check. A brief, honest look at where you've been and a deliberate decision about where you're going. The difference is in the feeling: one makes you dread Friday afternoon, the other makes Monday morning feel possible. And when you stop trying to account for everything and start using the review to simply orient yourself, something shifts. It stops being the thing you avoid and starts being the thing you actually want to do.
Once I framed it that way, it stuck.
How I built it
The review lives inside a Claude skill — essentially a detailed set of instructions that tells Claude exactly how to run the review, what questions to ask, what sections to cover, and how to handle the output. Think of it like a very specific briefing document that Claude reads before every session.
Building it took a few iterations. The first version was close but not quite right. The financial section needed more structure. The client check-in was too vague. The Big 3 kept coming out woolly instead of specific. So I updated the skill after each of the first few sessions, adding the missing detail, tightening the language, adjusting what got asked and when. By about week four it was running the way I wanted it to.
That process — build, run, notice what's off, fix it — is exactly what I'd tell a client to do with any new system. It's not a failure if the first version needs adjusting. It's just how good systems get built.
How it actually runs each week
Friday afternoons used to be the part of the week I'd just push through to get to the weekend. Now they're the part I find oddly satisfying — because I leave with a clear head instead of a full one.
I open a new chat inside my weekly review project and the skill kicks in automatically. Claude asks me a few open questions first, conversationally — how the week went, what the highlights were, whether there's any context it should hold. Then we work through ten sections together: wins, the financial snapshot, active client health, pipeline, visibility, systems and tools, capacity, a Keep/Stop/Start reflection, the Big 3 for next week, and my 90-day projects.
The whole thing takes fifteen to twenty minutes. At the end, Claude generates a clean, branded HTML document that I download and save.
Here's the bit that makes the system work week after week: I upload that downloaded document at the start of the next session. Claude reads it as context before we begin. That means it already knows last week's Big 3, which clients were flagged, what was outstanding. I don't have to remind it. I don't have to search back through old chats. The continuity is built in.
The sense-check I didn't expect to need
Once the review is done, I run it through something I call my Claude Board.
The Board is a set of different perspectives — different personas, essentially — that I can put the review in front of to see if anything obvious jumps out. A financial lens. A strategic lens. A product development one. The kind of outside perspective you'd get from a trusted advisor, without having to actually call one on a Friday afternoon.
It catches things I miss when I'm too close to my own week.
A simple example first: I'd noted in the review that I needed to follow up with a warm lead in late May. Reasonable. Sensible timing. But the Board flagged it immediately — that's not a plan, that's a vague intention. Put a specific date in your calendar or it won't happen. I did. It's in there.
The more significant example happened a few weeks ago. I'd reported something I'd built as a win for the week and moved on. But the Product and Service Development persona looked at the same information and stopped on it. It pointed out that I'd just described a complete product development cycle without realising it: I'd identified a problem, defined the requirements, then built something that solved it. That's not just a win, it said. That's potentially something other people in your position need too.
Left to my own reading, I would have moved to the next section. I was reporting a win, not sitting with it long enough to ask what else it might be.
The Board reframed it. What I'd logged as a task completion was actually a product I'd built to solve my own problem — and if I needed it, there's a reasonable chance others in my position do too. That observation is now sitting in my 90-day plan as a research question: is there a market for this, and if so, what would that look like?
I wouldn't have got there myself that Friday afternoon. That's the point.
What the system actually gives me
A clear picture of the week that I don't have to hold in my head. A record I can look back at. A Monday morning that starts with a shape instead of a blank page.
And the knowledge that if something is starting to slide, or if I'm sitting on something bigger than I've realised, I'll probably catch it on Friday rather than three weeks later when it's become either a problem or a missed opportunity.
One step to try this week
Before you close your laptop today, write down your three priorities for next week. Not a task list. Three specific things that, if done, would make next week feel like a win.
That's the beginning. The system can grow from there.
Organise · Automate · Breathe.