The rule of three is a priority framework that sounds too simple to matter: every day, name three outcomes you want to have achieved by end of day. Every week, name three things you want to be true by Friday. Every year, name three things you want to have built, done, or become. The power is in the constraint — three forces triage that ten never does.
What changed in 2026
- AI task-generators made to-do lists longer. It is now trivial to generate 40 subtasks from a project prompt. The rule of three is the human filter on top: which three of those 40 matter today?
- Async communication created "always-on" calendars. Without forced prioritization, every notification competes equally. Three daily outcomes give incoming requests something to compete against.
- Output-based remote work metrics — many teams now measure deliverables, not hours. Naming outcomes before starting the day aligns your effort with what actually gets measured.
How the framework is structured
The rule of three operates at three time horizons, and each level constrains the ones below it:
| Horizon |
Cadence |
Question |
| Yearly |
New year / quarterly review |
What three things would make this year a win? |
| Weekly |
Every Monday morning |
What three things would make this week a win? |
| Daily |
Every morning |
What three things would make today a win? |
Daily outcomes should ladder up to at least one weekly outcome. Weekly outcomes should connect to at least one yearly goal. If a daily outcome does not connect to either, ask whether it belongs today.
How to write a good outcome
An outcome is not a task. It is a state of the world that is either true or not true by the end of the period.
Bad (task): Work on the quarterly report
Good (outcome): Have the executive summary of the Q3 report written and reviewed
Bad (too vague): Do email
Good (outcome): Inbox is at zero and two client threads have been replied to
Bad (too large for one day): Launch the new feature
Good (outcome for today): Feature branch is deployed to staging with smoke tests passing
The test: could you look at the outcome at 5pm and give it a clear yes/no? If not, rewrite it.
How to use it daily
- Before opening email or Slack, write your three outcomes for the day in a notebook or a notes app.
- Scan your task list and calendar — pull only the three things that matter most into your outcomes.
- Start with the hardest outcome first — when energy is highest.
- At end of day, mark each outcome done/not done. No judgment, but be honest.
- Let the two or three undone outcomes inform tomorrow's three — or drop them if they were not actually important.
Common mistakes
Treating tasks as outcomes. This is the most common error. Tasks ("write email to client") have no completion signal. Outcomes ("client has confirmed the meeting time") do.
Writing four or five "outcomes." If you cannot choose three, you have a prioritization problem, not a task management problem. Force the choice.
Skipping the weekly horizon. Daily outcomes without a weekly target drift. Five minutes every Monday morning is all the weekly planning takes.
Changing your three mid-day without a real reason. Interruptions will try to replace your outcomes. Finishing one outcome and then picking up something new is fine. Abandoning an outcome because email arrived is not.
Using it without a task manager. The rule of three says what matters; it does not replace a place to store all the tasks that do not make the cut today.
What to skip
- Elaborate scoring systems — the daily yes/no is enough feedback.
- Sharing your three publicly — the accountability benefit is small; the performative distraction is real.
- Retrospecting too long — a 30-second end-of-day check is enough. Weekly review can be 10 minutes max.
FAQ
What if my job is mostly reactive — support, ops, on-call?
The rule of three is still useful. Name one or two outcomes in the reactive category ("all P0 tickets resolved or escalated") alongside one proactive outcome. It works even in interrupt-driven work.
Is this the same as the Ivy Lee method?
Related but different. The Ivy Lee method uses six tasks prioritized in order. The rule of three uses three outcomes (not tasks) and three time horizons. The emphasis on outcomes over tasks is the key distinction.
How do I handle a day where everything blows up?
On a chaotic day, let go of the three and respond. At the end of the day, note what you actually achieved and set fresh outcomes for tomorrow. One bad day does not break the system.
Where did this come from?
J.D. Meier popularized it as the core of his "Agile Results" system around 2010. The framework is simple enough to survive without a book — three outcomes at three horizons is the whole thing.
Where to go next
See The Pareto principle explained in 2026, Decision journaling explained in 2026, and The Cornell note system explained in 2026.