This week I’ve spent my time exploring the meaning of ‘proof of concept,’ and how this may differ from producing a prototype. I began by researching library books and online resources, and found two key online articles that explained proof of concepts from both a business and design point of view.
In business terms, I’ve learned that a proof of concept can be defined as “a presentation of the proposed product and its potential viability,” which is presented to clients and stakeholders by project managers. Proof of concepts include a “small-scale visualisation exercise” such as a prototype (Rodela, 2021), and also “outline how the idealized product or service would become market-ready, how it would function, if it’s needed, and who is the target demographic” (MacPherson, 2021).
It seems that if project managers want their clients and investors to understand and accept their ideas, then they must justify their commercial viability through research, combined with visualisations such as prototypes. This combination should then be presented appropriately, for example via a Keynote presentation, and must also present other managers and investors with information on potential obstacles or constraints so that they can plan to overcome them (Rodela, 2021).
By presenting a proof of concept in advance of a project, all stakeholders can decide whether or not to commit resources to the project. It is important that the project is presented in as much detail as possible so that managers can anticipate all of the resources needed, such as finance, human resources, technologies, and time; other factors such as market competition and the intended user base will also be considered. Without presenting these for consideration ahead of time, the project could be subject to ‘scope creep,’ whereby the resource requires of a project steadily become greater, despite the project already having been approved (Rodela, 2021).
From this research I’ve compiled an initial roadmap for creating a proof of concept. My Gantt chart has been updated with this in mind, and I’ll be trying my best to follow the roadmap throughout the project. My reading around proof of concepts has also raised my awareness of how much research is required to be presented in a proof of concept, however following a discussion with my lecturer, we have decided that I must focus upon ideation and iterative designing, as that is a key area for assessment within this module.
Road Map
- Research the need for the product
Who are the target market? What are the painpoints in the current process? Get answers by interviewing a representative sample and stakeholders. Consider how a new product might alleviate issues. Produce a list of feelings and perspectives. Draw upon research from the DM7921: Design Research module as evidence. - Map pain points with feedback from representative sample and stakeholders
Draw upon research from the DM7921: Design Research module as evidence. - Ideate the solution. Brainstorm, research competition, and produce a timeline
“The team should then assess each brainstormed solution according to the likely costs, timeline, technologies needed, required operational capacities, competition, resources, and other factors.” (Rodela, 2021) - Create prototype(s) and conduct usability testing
Conduct at least one usability test for each fidelity stage of the prototypes. Be sure to resolve issues that arise and note them for the proof of concept presentation. - Gather and document feedback
“…document the sample group’s feedback about their experience, their reactions, and any other valuable details, including what they think of the user interface.” (Rodela, 2021) - Present proof of concept for approval
“…must present, among other things, the pain points that the product solves, features that address those problems, and technologies integrated to demonstrate the value of the idea.” “…include clearly defined success criteria or project management metrics, evaluation measures, timelines, next project management plans (should it be approved), resources needed, and other aspects” (Rodela, 2021)
References
MacPherson, L. (2021). 5 Steps to a Proof of Concept for Successful Software Development. [online] Designli Blog. Available at: https://designli.co/blog/5-steps-proof-concept-successful-software-development/ [Accessed 16 Oct. 2021].
Rodela, J. (2021). How to Create a Proof of Concept. [online] The Blueprint. Available at: https://www.fool.com/the-blueprint/proof-of-concept/ [Accessed 16 Oct. 2021].