We see it time and time again. At the start of a software development project, risk is high and rooted in uncertainty. No matter the project, the company, or the level of expertise of the folks we're talking with - there are always lots of unanswered questions.
- What business value will this create?
- Are we building the right thing?
- Are we solving the right problems?
- Will it be easy to use?
- Will end-users actually use it?
- How will it behave on different devices?
- What will it cost?
- Can I get "buy-in" from investors?
More often than not, various parties involved aren’t yet aligned around a singular vision — or worse, they assume alignment that isn’t actually there.
Enter - the power of prototyping.
In general, the objective of throw-away prototyping is to validate or derive system requirements, flesh out unknowns and, where desired, establish Minimum Viable Product (MVP) features.
Often referred to as "wireframing", the prototyping process starts with those requirements which are poorly understood. Input is gathered from key stakeholders and screens are designed to reflect user interface, navigation and workflow for the desired system functionality. This allows clients to really visualize the end product - not only what it will look like but how the enduser will interact with it. A cycle of feedback and additional requirements naturally evolve through this process until there is consensus amongst the stakeholders.