How to Run the 12 Week Year in Notion (and When to Stop)

What you're building (and why the structure matters)

The 12 Week Year, based on the book by Brian P. Moran and Michael Lennington, is a small system with a strict shape: one to three 12-week goals, each broken into weekly tactics, and a weekly execution score — the percentage of planned tactics you actually completed. Score 85%+ most weeks and the goals largely take care of themselves. If any of that is new, the complete guide covers the methodology in depth; this post is purely about implementing it in Notion.

The shape dictates the database design. You need exactly three databases: Goals (the 1–3 outcomes with their lag measures), Tactics (the recurring weekly actions, each related to a goal), and Weekly Check-ins (one row per tactic per week — this is the table your score is computed from). A fourth optional database, Weeks, gives you a 12-row dashboard with one score per week.

Resist the urge to build more than this. The most common Notion failure isn't a missing feature — it's a beautiful eight-database workspace that takes ninety seconds to update, which means it stops getting updated around week three. Everything below is designed to make Friday scoring take under a minute.

Step 1: The three databases

Goals is a simple table: Name (e.g., 'Grow to $30k MRR'), a Lag Measure text property ('$30k MRR by week 12'), and a Status select. Keep it to three rows maximum — the book is emphatic about this, and choosing goals is where most quarters are won or lost before they start.

Tactics has: Name ('Make 10 outreach touches'), a Relation to Goals, a Cadence select (Daily, Weekdays, Weekly), and a Per Week number (how many completions count as 100% — 5 for a weekday tactic, 1 for a weekly one). Each tactic must pass the Friday test: can you answer 'did I do it?' with yes or no? Writing tactics that pass this test is the highest-leverage hour of your setup.

Weekly Check-ins is the workhorse: a Relation to Tactics, a Week number property (1–12), a Done checkbox, and — for frequency tactics — a Count number ('did it 4 of 5 days'). At the start of each week, you create one check-in row per active tactic. A database template with the current tactics pre-filled makes this a two-click job; the friction of creating rows manually every Monday is real, and we'll come back to it.

Step 2: The execution score formulas (real syntax)

Create the optional Weeks database (12 rows, a Week number, and a Relation to Weekly Check-ins), then add a Score formula property. With Notion's current formula language, the simple checkbox version is:

lets(total, prop("Check-ins").length(), done, prop("Check-ins").filter(current.prop("Done")).length(), if(total == 0, 0, round(100 * done / total)))

That reads: count related check-ins, count the ones marked Done, and return the rounded percentage (guarding against an empty week). If you use frequency tactics with a Count property, the proportional version sums actual completions against targets — pull Per Week onto each check-in via a rollup or formula from the related tactic, then: lets(planned, prop("Check-ins").map(current.prop("Per Week")).sum(), done, prop("Check-ins").map(current.prop("Count")).sum(), if(planned == 0, 0, round(100 * min(done, planned) / planned)))

Add a Status formula for at-a-glance color: ifs(prop("Score") >= 85, "🟢 On track", prop("Score") >= 70, "🟡 Slipping", "🔴 Off track"). The 85% threshold isn't decoration — it's the system's core benchmark, and the 85% rule explains why consistency at 85 beats bursts at 100.

One more useful formula, on the Weeks database, computes the current week from your cycle start date so the dashboard highlights itself: dateBetween(now(), prop("Cycle Start"), "weeks") + 1. Wire a filter ('Week number equals current week') into your main dashboard view and Notion will always open on the week that matters.

Step 3: The weekly review template

The weekly review is a 15-minute Friday ritual: read the score, explain the misses in one line each, commit next week's tactic list. In Notion, make it a database template inside Weeks (or a dedicated Reviews database) with three headed sections: 'Score & misses' (linked view of this week's check-ins, filtered to Done = unchecked), 'One-line explanations' (an empty bulleted list — travel? unrealistic cadence? avoidance?), and 'Next week' (a template button or checklist that spawns next week's check-in rows).

The explanations section is the part people skip and shouldn't. A miss caused by a chaotic week and a miss caused by a tactic that was never realistic look identical on the scorecard; the one-line autopsy is how you tell them apart, and it's the input for the only decision the review exists to make — keep the tactic, change its cadence, or replace it. The weekly scorecard chapter goes deeper on reading scores as trends.

Put a recurring calendar event ('Friday 4:30 — score the week') outside Notion. This sentence is doing a lot of work in this guide, and it foreshadows the honest section below: Notion will hold your review template forever, but it will never once remind you to open it.

What Notion genuinely does well here

Planning is Notion's home turf, and the 12 Week Year's planning layer fits it beautifully. Drafting goals, relating tactics, writing the vision doc alongside the databases, keeping last quarter's plan one click away for the 13th-week review — no purpose-built app matches Notion's flexibility for the thinking part of the system. If you already live in Notion, your plan sits next to your notes, projects, and meeting docs, which is a real advantage.

It's also free for this use case, endlessly customizable, and yours. You can add a habit-tracker view, embed the scorecard in your daily dashboard, or restructure everything mid-quarter when you learn something. And the act of building the system yourself teaches the methodology in a way that installing an app doesn't — by the time your score formula works, you understand exactly what a lead measure is.

A fair reading: if your execution problem is planning quality — vague goals, unfocused tactics — Notion plus discipline is a legitimately complete solution, and plenty of people run excellent quarters this way.

The honest limits: where the template quietly fails

No reminders that matter. Notion's notifications are built for collaboration (mentions, comments), not for behavior. Nothing will nudge you Tuesday when your daily tactic is at zero, and nothing will chase you Friday when the week is unscored. The entire 12 Week Year runs on one habit — scoring every week without exception — and Notion is structurally indifferent to whether that habit survives. Your template can't text you.

Score friction compounds. Creating check-in rows every Monday, ticking boxes across a related database, keeping the formulas intact when you rename a property — each is thirty seconds, and thirty-second frictions are exactly what kill measurement habits. The pattern is so consistent it's almost a law: the Notion scorecard is immaculate for weeks one through three, patchy through week six, and abandoned by week eight — at which point you have a plan, not a system.

No accountability. The book's strongest mechanism is another person seeing your score — a WAM or an accountability partner. A Notion page can be shared, but it won't surface your score to anyone, won't run a meeting agenda from it, and a shared page nobody is prompted to open is privacy with extra steps. The failure modes chapter covers why unscored, unwitnessed plans decay on a predictable schedule.

When to graduate to an app (a fair test)

Run the Notion setup for one full 12-week cycle and then check three things: Did you score all 12 weeks? Did anyone else see your scores? Did the Friday review actually happen after week six? If you got three yeses, genuinely — keep your Notion setup, it's working and this post was free quality assurance. Many disciplined solo operators land here.

If you got a no on scoring or reviews, the problem isn't your template design, and rebuilding a prettier one won't fix it. You need the scoring loop to be automatic and the accountability to be built in — which is the specific gap Pilot exists to fill: tactics with real reminders, a score that computes itself as you check things off, streaks and week-over-week trends, and scores that an accountability partner or team actually sees. We wrote a fuller, even-handed breakdown in Notion template vs. a dedicated app.

The migration costs almost nothing: your goals and tactics are already written, and re-entering them takes minutes. Or start clean — paste your goals into the free 12-week plan generator and it will draft the tactic structure for you. Either way, keep Notion for what it's best at — the vision doc, the 13th-week retrospective, the thinking — and move only the weekly loop to a tool that fights for it.