Skip to content
Algolithic
All articles

Product2 min read

How we scope an MVP in two weeks

A short, structured discovery turns a big idea into a plan you can build, budget and test — without a 60-page spec nobody reads.

Mara QuinnCo-founder & CEO

Founders often arrive with either a one-line idea or a document so detailed it already contains next year's roadmap. Both are fine starting points. What neither gives you is a version small enough to build quickly and sharp enough to learn from.

Our discovery sprint closes that gap in ten working days.

Days 1–3: understand the problem

We start with people, not features. That means short interviews with a handful of target users, a session with whoever knows the domain best, and a hard look at constraints: budget, deadlines, regulations, existing systems.

By the end of day three we can describe the problem in one paragraph and name the single user journey that matters most.

Days 4–7: map the smallest valuable journey

Next we build a story map of that journey, step by step, and draw a line through it. Everything above the line is the MVP. Everything below waits.

Questions we ask about every item:

  • Does the core journey break without it?
  • Can it be done manually behind the scenes for the first hundred users?
  • Will it change what we learn from launch?

An MVP is the smallest product that teaches you the most. If it doesn't answer a question, it doesn't belong in version one.

Days 8–10: de-risk the scary parts

Every product has one or two things that could sink it — a third-party API with unclear limits, a data model that might not scale, an AI feature that may not be accurate enough. We spend the last days on quick technical spikes to turn those unknowns into knowns.

What you get at the end

  • A product brief your whole team can read in ten minutes
  • A clickable prototype of the core journey
  • An architecture sketch and the technology choices behind it
  • A roadmap split into milestones, with estimate ranges for each
  • A list of open questions and how we'll answer them

Two weeks is short on purpose. It forces decisions, keeps costs predictable, and means you can start building — or decide not to — while the idea is still fresh.

  • Discovery
  • MVP
  • Roadmaps

About the author

Mara Quinn · Co-founder & CEO

Mara has spent fifteen years turning early ideas into products people pay for. She runs discovery and keeps every project pointed at a measurable outcome.

↳Keep reading

More from the workbench.

Engineering2 min read

Shipping weekly without breaking things

Small pull requests, feature flags and a deliberately boring CI pipeline let us release every week — even on products with thousands of daily users.

By Theo Park