Prototype helps in validating
The number of patents granted is usually about half of the total submitted in a given year. But how many of those patents became successful, profitable businesses?
How many inventors, tinkerers, and builders are sustaining themselves with their products?
After publishing this post originally, we got requests to clarify the term ' PRD'. This is a document that product development teams use to specify what they will build.
It will contain features, user stories, business goals, and whatnot.
It's a little arrogant, but product teams assume a lot of things at the initial discovery stage of their process ' that they know that a problem exists and, worse yet, that they know how to solve it.
As we’re talking, I notice a roll of batteries wrapped in black electrical tape sitting upright on a chessboard. I’m gonna make a ‘Tesla’ battery out of them,” he replied, referencing the new Powerwall from Tesla that provides energy for residential homes.
If the user experience is of critical importance, a "facade" is enough and building the MVP is a bit like designing a movie set.
When the user's experience seems authentic enough and can be used to examine the service's or product's functionalities, what's behind the facade is irrelevant.
But we were surprised to find that people liked PRDs.
Some designers liked the constraint, and developers like the idea that this document could somehow magically prevent feature creep. They're good starting points, and often-times they're the result of user research, which can be great for validating early concepts.