minimum viable product
|
proof of concept
|
software development
When you have a big, bold idea with the potential to grow your business and revolutionize an industry, the temptation is to immediately jump to the end result. Yet having a fully fleshed-out, perfectly made, exceptional product or service takes a significant amount of time and money to accomplish. Going from idea to “in market” is a process that can take years of brainstorming, development, configuration, reconfiguration, and testing. Skip any step in that process and the end result may not be everything you want it, or your customers need it, to be. To make sure your developers, investors, and ultimately your users/customers are happy, it sometimes helps to take an intermediate step between bold idea and the final product: a minimum viable product (MVP).
proof of concept
|
software development
In the lifespan of a tech venture, there is both a beginning and an end. The beginning is an idea. It’s ethereal, conceptual, something that exists only in our minds, doodled on the back of a napkin, or sketched out on a whiteboard. On the other end of the tech spectrum, after all the hard work and development, is the end product. It’s the idea shaped into reality, tried and tested and put through the wringer in order to come up with viable hardware or software that addresses a need in the marketplace going unfulfilled. But there’s one key stop on the journey that every tech idea should go through, long before you go into production, before Q & A testing, even before development and prototyping: Proof of concept.