Flowchart
Should you build the feature customers asked for?
A decision flowchart for founders, from the request to a mockup test and a commitment ask

A decision flowchart for early-stage founders weighing a feature request. Rewrite the request as a problem, interview 12 to 15 users about it before showing anything, check whether people who did not ask have the problem too, test a mockup with a five-second first look, and build only when people beyond the requesters commit. Each no leads to a cheaper next step. Koji's founder playbook explains each step and how to run the interviews with the mockup attached.
Where this appears
What's in this flowchart
Start: A customer asked for a feature
- Write the request as a problem. Who has it, how often, what it costs. Set your kill rules now.
- Interview 12 to 15 users, problem first. The requesters, active customers who did not ask, recent signups.
- Do users who did not ask have the problem too?
- Yes: go to 4.
- No: Build small or drop it. Solve it by hand for the requesters, or tell them why not.
- Show the mockup for five seconds. Ask what they remember and what they think it does.
- Did most people understand the mockup?
- Yes: go to 6.
- No, redesign: go back to 4.
- Did people outside the requesters commit?
- Yes: go to 7.
- No: Run a fake door or a pilot first. Interest is not demand. Get a behaviour signal before you build.
- Finish: Build the smallest version. Ship it to the people who committed, then watch usage for two weeks.
Use this image
Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:
<a href="https://www.koji.so/visuals/should-you-build-the-feature-flowchart"><img src="https://www.koji.so/visuals/should-you-build-the-feature-flowchart/should-you-build-the-feature-flowchart.png" alt="Flowchart for deciding whether to build a requested feature, from the problem interviews to the mockup test and a commitment ask." width="1200" height="1934" /></a>
<p>Source: <a href="https://www.koji.so/visuals/should-you-build-the-feature-flowchart">Should you build the feature customers asked for?</a>, Koji</p>




