Development planning
Choose the learning goal for your MVP
Decide whether you need a prototype, discovery milestone, or product release, then define the smallest useful scope.
Choose discovery, a prototype, or a release
If the workflow and dependencies are unclear, discovery should produce a brief and feasibility findings. If the uncertainty is about interaction, a prototype can support a user review. If users need to complete a real task, scope a release with the appropriate access, failure, and operating behavior. These are different commitments, not interchangeable names for the same build.
Describe who will try the first release and what you need to observe. This makes it possible to challenge a feature request against the learning goal rather than adding every future requirement.
Write down what can wait
For a first release, one role model, one language, or one integration may be enough. Rare administrative work may remain manual if the workaround is acceptable and documented.
Security, permissions, and the behavior needed for the agreed task still need attention. Calling a release an MVP does not define which shortcuts are appropriate.
- Who is the first intended user?
- What complete task must they finish?
- What evidence will determine the next investment?
- Which features are explicitly deferred?
Turn the brief into a bounded commitment
Estimate discovery, design, implementation, review, and release separately. Identify unresolved dependencies rather than burying them in a precise-looking total.
Use a first milestone to validate assumptions and the working arrangement. A fixed price or schedule follows agreed scope; fundraising or commercial success is not an implementation guarantee.
Choose a useful next step
For an initial conversation, share the task, your current application, and the main constraint. Use anonymized examples; specific scope and working terms are agreed before a commitment.
Send a brief