When you’re starting over, it’s tempting to build a big plan that promises to fix everything. But big plans are fragile. What actually creates momentum is a tiny, durable plan you can finish this week. The One-Page Plan is exactly that: a single page that forces clear choices, fits into a 7-day window, and ends with something you can show or sell. It borrows from Basecamp’s idea of fixed time, variable scope, the logic behind Parkinson’s Law, and research on how small wins drive motivation.
Why a one-pager beats a “real” plan
Long plans create an illusion of progress — lots of motion, little movement. A one-pager does the opposite. With a hard time window, you resize the work to fit the week (a technique Basecamp popularized in Shape Up). Instead of asking “How long will this take?”, you ask “What valuable slice could we ship by Day 7 if the deadline is fixed?” That constraint kills scope creep before it starts.
And because “work expands to fill the time available,” a shorter window reduces bloat by default. That’s Parkinson’s Law in practice: if you give yourself a week, you’ll solve it in a week; give yourself a quarter, and you’ll invent a quarter’s worth of problems. See the original description of the effect here.
Finally, you’re deliberately engineering visible progress. As Teresa Amabile and Steven Kramer showed in The Power of Small Wins, noticing forward motion — even tiny steps — is one of the strongest drivers of motivation and well-being at work.
The One-Page Plan (fill this in, no second page)
Goal (1 sentence): What exactly will be live and linkable in 7 days?
Audience & painful moment (2 bullets): Who is it for, and what hurts right before they buy?
Offer (max one): The concrete thing they get; if it’s a “lite” version, say so. Include the price or the next step.
Constraints: Time window = 7 days. Budget = $0–$100. Channels = 1–2. No extra options. Defaults win.
Must-haves (3 items): The minimum set that makes your promise credible. If you can’t list them on one line each, they’re too big.
Nice-to-haves (parking lot): Anything else you think you “need.” You can earn it after feedback.
Risks & test: The one assumption that could break this; the fastest test you can run this week.
Your 7-day schedule
Day 1 — Choose & reduce. Pick one idea you can explain in a sentence. Write the one-pager. Cut scope until you can imagine pressing “Publish” in seven days. If that feels scary, good — you’re finally dealing with the real constraints.
Day 2 — Message & outline. Draft a simple landing message: headline, three bullets, one CTA. Outline the deliverable end-to-end. Keep the path short: “from discovery → decision → action” in under a minute of reading.
Day 3 — First pass build. Make the ugly, working version. Don’t polish. If you’re building a digital product, think MVP in the Eric Ries sense: the smallest version that teaches you something true about demand.
Day 4 — Tight feedback. Ask three people: one ideal user, one peer, one neutral outsider. Give them a single question: “What’s unclear?” Capture only the facts they gave you and the change you’ll make — not a 10-page debate.
Day 5 — Cut & simplify. Remove 20–30% of scope. Replace clever with clear. Choices become defaults. If you’re debating a feature, it’s a candidate for the parking lot.
Day 6 — Ship prep. Final copy. Screenshots/mockups. Basic analytics. One decision path, one CTA. Price or “next step” visible without scrolling. If you’re selling, make checkout boring on purpose.
Day 7 — Ship. Publish. Post once to your main channel. Pin it. Ask for 10 responses (reply, click, or purchase). Schedule a 30-minute retro o
