JLJose Luis TorresDIGITAL PRODUCTS
SPRINT MVP · TWO WEEKS

Turn the idea into decisions that can be built and tested.

A concentrated process to define the user, reduce the scope, design the essential journey and decide how to validate the product before a major investment.

WHEN IT FITS

To move forward when there is a good intuition, but too many possibilities.

NEW IDEA

You need to find the core

You have an opportunity or concept, but it is still unclear which version deserves to be built first.

BLOCKED PRODUCT

The reach continues to grow

The functions accumulate and you need to recover a proposal, a recognizable path and priority.

INVESTMENT DECISION

You need to reduce uncertainty

Before budgeting for development you want to know what the first version should demonstrate and how to observe it.

THE PROCESS

Two weeks to go from possibilities to a decision system.

01

Diagnosis

Context, problem, user, available evidence and main risk.

02

Definition

Value proposition, essential path and minimum product limits.

03

Prototype

Architecture and representation sufficient to contrast the experience.

04

Validation

Signs, experiments, technical decisions and subsequent roadmap.

DELIVERABLES

You don't get loose ideas. You receive a basis to act.

  • Problem definition document and priority user
  • Value proposition and critical assumptions
  • Functional map and route to the first value
  • Scope Matrix: now, after and out
  • Prototype or navigable scheme depending on the starting point
  • Validation plan with observable signals
  • Technical recommendation and construction phases

Indicative duration: two weeks. The schedule and budget are closed after reviewing the complexity and existing material.

APPLIED EXPERIENCE

The method comes from building our own products.

See all projects →
FREQUENTLY ASKED QUESTIONS

What you should know before you start.

Does the Sprint include full development?

No. Its objective is to define and reduce risk. If it makes sense to build later, The roadmap allows you to budget a first version with much more precision.

Do I need to arrive with documentation?

No. You can start with an idea, an existing product or set of notes. The first job consists precisely of organizing what already exists and detecting what is missing..

Does it work for a product that is already published?

Yeah, when you have to regain focus, rethink the route, prioritize a new version or decide which hypothesis should be tested before expanding.

What happens when you finish?

You will have an explainable scope, a proposed validation and roadmap. You can run it with your team, with me or use it to request comparable quotes.

FIRST CONVERSATION

Tell me the idea and let's find the decision that can eliminate the most risk.

The initial conversation is to check if the Sprint fits and define the starting point.

Raise my MVP