A simple journaling system for people who keep quitting

Executive overview

Most journaling systems fail because they're either too loose (free-writing) or too rigid (structured planners). Michael Bungay Stanier spent 40 years failing at journaling before building his own format around three morning questions and one evening question.

The system works across daily, weekly, and six-week cycles, keeping reflection grounded in today while maintaining a wider view of what matters.

A journaling practice only sticks when it matches how you actually think — not how you think you should think.

The three morning questions

• What do I notice? — a call to presence; scan inner state and outer environment before the day takes over
• What do I want? — repeated daily, this question builds clarity about what's missing, what's calling, what's not working
• What's the one thing today? — cuts through an overcrowded to-do list; forces a single most-important choice
• The to-do list works better as a menu than a straightjacket — one anchor item creates freedom, not constraint

The evening question

• What's the best thing that happened today? — a gratitude question in disguise
• Reorients attention away from productivity toward what was actually good
• Builds a written record of life's highlights that would otherwise be forgotten

Weekly and six-week rhythms

• Each week opens with a weekly focus section and a single "go deep" question drawn from 16 rotating prompts
• Go-deep questions surface hidden commitments — e.g., "What are you loyal to?" can expose where you're stuck
• The six-week cycle is borrowed from lean production and 37signals: sprint for six weeks, then reset
• Six-week goals give daily check-ins a larger context — a reason for the grind

Monthly reflection

• Takes about one hour, ideally away from a desk
• Revisit the rules you're playing by and the projects that matter
• Review calendar against your four or five key projects — anything not serving them is worth questioning
• Losing the big picture collapses daily work into emails and reactive to-dos

Saying no as infrastructure

• Saying no is only possible when you're clear on what you're saying yes to
• Slow down the rush to yes — default should be no, not yes
• Build criteria in advance for recurring decisions (e.g., five criteria for speaking gigs; accept if two are met)
• The "plus one" test: if this were tomorrow, would I be glad I said yes?
• Every commitment without a no is pouring water into a full glass

Two words instead of one for the year

• A single word of the year is too vague — two words in tension are more useful
• They create a push-pull that surfaces real trade-offs
• Example: "artisanal" (make beautiful things) + "ballsy" (be brave and ambitious) — both true, not easily reconciled