There is a lot of talk about the Minimum Viable Product — a prototype with just enough features to satisfy early customers, and provide feedback for future development. But feature creep often starts much earlier, in the design & development, if not the ideation stage of a project.
One way to keep the scope and budget under control is what I call the Minimum Viable Tool (MVT).
Minimum Viable Tool (noun)
/ˌmɪnɪməm ˌvaɪəb(ə)l ˈtuːl/
A tool with just enough features to create a Minimum Viable Product.
A good Minimum Viable Tool provides just enough constraints to make you stop and think every time you are about to go off scope.
The utopian Minimum Viable Tool makes it impossible to build anything but a Minimum Viable Product.
A familiar concept…
The core concept behind the MVT will be familiar to many readers, from their specific fields.
To a low-fidelity wireframe in Balsamiq, to an interactive prototype in Sketch, Adobe XD or InVision:
Design thinking facilitators advocate for the use of Post-it notes, combined with toddler crayons or thick black markers.
Developers will have encountered the concept under the motto:
Make it work, make it right, make it fast.
— Kent Beck
Although the quote does not mention tooling specifically, it guides programmers in the general direction.
…valuable across fields
The concept of a Minimum Viable Product emerged among tech startups, but has since become a valuable staple of product management, design, development and growth hacking teams across industries and business sizes.
We need a similar overarching term for minimal tooling, to encourage research, and promote this mental model in fields where it is not prevalent already, such as new restaurants that overspend on expensive kitchen equipment.
What is your favourite example of a Minimum Viable Tool, and where do you think this concept could be most valuable?