How do you scope an MVP that ships in weeks, not months?

Six-week appetite-based planning. Don't plan beyond six weeks because plans change too fast. Decide what outcome you're solving in six weeks, then shape the solution to fit the time — not the other way around.

Most founders scope by features: "I want auth, payments, dashboard, notifications, and analytics." The right approach is scope by outcome: "I want users to be able to do X in six weeks." The same problem can be solved with a full SaaS application, a simpler tool, or even an ebook with email automation. The constraint forces you to find the smallest shape that delivers real value.

Think of it like progressive JPEG encoding. You build the general shape first — blurry but correct — then add details with each iteration. Users see the direction from week one, even if it's rough.

If scope starts overflowing, you flex the features. Simplify options, remove configurability, deliver one thing well instead of three things poorly. Keep the goal, shrink the solution.

Appetite, Not Estimates replaces guesswork with honest constraints — "this is how much we're willing to spend on this problem." Scope Shaping is the practical work of fitting features inside that appetite. Priorities, Not Scope replaces a fixed list with a ranked queue the client controls.

Before scoping an MVP, ask: "What's the one outcome users need to achieve?" Work backwards from six weeks to find the smallest solution that delivers that outcome. If the scope doesn't fit six weeks, it's not an MVP scope — it's a wish list.