June 17, 2026

I Stopped Using Months to Plan My Year. Week Numbers Changed Everything.

Every January I set ambitious monthly goals. Every February I fell behind. The problem wasn't my discipline — it was the unit I was using to measure time.

For about five years, my annual planning ritual looked exactly the same. December 28th, I'd open a fresh notebook. Write "January" at the top of a page. Under it: "Lose 5 pounds. Read 4 books. Ship project Alpha." Then "February" on the next page. "March" after that. Twelve neat monthly buckets.

By the second week of January, I was already behind. Not because the goals were too ambitious — they weren't. But because a month is a garbage unit of measurement for actually getting things done.

I didn't figure this out on my own. I tripped over it by accident.

The month of January has 4.43 weeks, and that .43 destroyed me

Let me explain how I finally noticed the problem. I was reviewing my team's project velocity at the end of Q2 2024. We tracked everything in monthly sprints. Every month, same number of story points. Every month, wildly different completion rates. Some months we finished everything with time to spare. Other months we were scrambling by the 15th.

I spent an afternoon trying to figure out why. Burnout? Scope creep? Different project complexity? I graphed our output against every variable I could think of. Nothing correlated.

Then I counted the actual working days in each month.

January 2024 had 23 working days. February had 20 — three full days less. That's 13% less working time. But every month, I assigned the same workload. Of course February was going to feel chaotic.

I felt stupid for not seeing it sooner. Months are arbitrary. They don't line up with weeks. A month can start on a Tuesday and end on a Wednesday, leaving you with partial weeks at both ends. Your "monthly" goal might actually give you 19 days to work in one month and 24 in another.

Weeks don't have this problem. A week is always exactly 7 days. Monday to Sunday, or Monday to Friday if you're counting working days. No ambiguity, no drift.

Switching to week numbers — the first attempt was a mess

After the February revelation, I decided to try week-based planning. I printed out a 52-week calendar, numbered each week 1 through 52, and started assigning goals to weeks instead of months.

The first month was terrible.

I had trained my brain to think in months for 30+ years. "The report is due mid-March" made intuitive sense. "The report is due Week 12" felt cold and mechanical. I kept having to convert week numbers back to dates in my head, which defeated the purpose.

My team pushed back too. "What do you mean the deadline is Week 38? What date is that?" Every meeting started with a week-to-date translation session. Productivity actually went down for the first month.

I almost abandoned the experiment right there. The only thing that kept me going was stubbornness — I'd already told everyone this was the new system, and I didn't want to admit it was failing after three weeks.

Week 6 was when it clicked

Around Week 6 of using the new system, something shifted. I stopped converting. I just knew that Week 8 was late February and Week 12 was mid-March. My brain had recalibrated.

And once that recalibration happened, the benefits started showing up everywhere.

First: goal sizing became accurate. When I said "this sprint is 3 weeks," I meant exactly 15 working days. Not "sometime in March." Three weeks. Fifteen days. The math was trivial.

Second: progress tracking became linear. When I was 25% through the year, I was at Week 13. Not "somewhere in March-ish." Exactly Week 13 out of 52. I could look at my annual goals and ask: have I done 25% of the work? With months, that calculation required looking at a calendar, counting days, and doing mental arithmetic. With weeks, it's a single division problem.

Third: communication with the team got dramatically clearer. Instead of "let's revisit this in about a month" — which could mean 3 weeks or 6 weeks depending on who you ask — we said "let's check in at Week 30." Everyone pulled up the same calendar, everyone saw the same date range. No ambiguity.

The week-number tools that actually helped

I'm not going to pretend this was all my own discipline. I tried a bunch of tools and most of them didn't help. Fancy productivity apps with incomprehensible configuration screens. Physical planners that cost $60 and weighed three pounds. None of them stuck.

What actually worked:

  • A simple Google Sheet with 52 rows — one per week. Column A: week number. Column B: date range (I used weeknumber.cc to fill this in). Column C: goal for the week. Column D: done/not done.
  • A printed A4 calendar showing all 52 weeks in one view. I hung it above my desk. Every Sunday night I'd cross off the week that just ended. Physical, visible, satisfying.
  • Slack status set to "W25" or whatever the current week was. My team started doing the same. It became a shorthand — "Ship by W30" in a message header.

Total cost: $0. Total time to set up: about 20 minutes, mostly spent looking up date ranges for each week number.

I should mention one mistake I made here: for the first three months, I used whatever week numbering my Google Calendar showed by default. Then I realized Google Calendar's "Week of year" setting was using US week numbering (Sunday start, January 1 is always Week 1) while my printed calendar was using ISO 8601 (Monday start, Week 1 contains the first Thursday). So Week 12 in my spreadsheet was not the same as Week 12 on the wall calendar.

I discovered this when I showed up to a client meeting a week early. My calendar said Week 12, their calendar said Week 11. They were German. I was using the wrong standard.

Now I just use ISO for everything. It's the international standard, it's unambiguous, and it's what weeknumber.cc defaults to. One less thing to think about.

We're in Week 25 right now — here's what that means for your year

Today is June 17, 2026. We're in Week 25. That's 25 weeks gone, 27 weeks (plus a couple days) remaining.

If you set goals in January, you're just shy of the halfway point. Not exactly halfway — that was Week 26, last week — but close enough. This is the moment to check in.

With month-based planning, the "midyear review" happens in late June or early July, which is somewhere between 45% and 55% of the year depending on when you do it. With week-based planning, I do my review at Week 26. Exactly 50% through the year. No guesswork.

I've been planning this way since the start of 2025. Here's what's different about my results: I finish more things. Not because I'm more disciplined — I'm definitely not. But because the feedback loop is tighter. When Week 15 arrives and I haven't done what I planned for Week 15, I know it the same week. With monthly planning, I'd only check at the end of the month, by which point I'd wasted three extra weeks before noticing I was behind.

The tightness of the loop matters more than the planning system itself. Weeks create shorter loops than months. That's the whole insight.

If you want to try this: don't overthink the tooling. Grab a piece of paper, number it 1 through 52, and write one thing you want done by the end of the current week. If that feels useful, do it again next week. If it doesn't, you lost a piece of paper and five minutes.

What week is it right now?

Check the current week number, see the full year calendar, or look up any date's week number — all free on WeekNumber.cc.

Open WeekNumber.cc →
[ Google AdSense — Article Bottom ]