The Innovation Process
From product design through to establishing manufacturing partners and processes, Response continues to work with companies and individuals to help turn their innovations into a deliverable products.
Companies large and small may have their own internal processes; normally sequential, often following the so called waterfall process. Innovation follows a series of checks and balances
not conforming to established sequential processes. This may be OK where established marketing data provides a tight framework for traditional project planning.
However, for a true innovation the granular detail underpinning this framework is either incomplete or simply doesn't exist; each step is a learning experience
not elegantly catered for by a traditional project plan as it navigates left as well as right along the path.
As more and more fresh companies take on product innovation Response's perspective ideally suits this fast-paced environment.
Ideation
An essential pre-cursor to the concept phase setting the initial assumptions and constraints for the deliverable product.
Ideation helps quantify the innovation without incurring too many overheads. The process should be quick and detail free comprising rough sketches, web extracts, sticky notes, emails etc. Output needs to be clear and unambiguous to facilitate agreement on a clear product direction - often referred to as the Minimum Viable Product.
Output should not be reams of documents and ideas; however, output needs to communicate metrics to be verified and any assumptions required to be validated.
Some may perceive this stage 'an unnecessary comfort' however over the hundreds of projects we have been involved in has shown that spending just one day on Ideation reaps significant benefits down the line.
Response relishes taking part in Ideation dialogue; depending on the extent of our involvement, we often provide input free of charge.
Set the Boundaries
Be optimistic but not unrealistic or unwilling to comprimise in the face of evidence. Establish ideal dates, budgets, expected customer pricing, manufacturing route etc. Consider any headline hazards - these may have a dramatic effect on the product boundaries.
Core values
Clearly define, document and agree the Minimum Viable Product. What should the product do and how? what are its customer benefits? and how it will be sold? Do not ignore manufacturing, or for software its deployment. The MVP should be ruthlessly managed; MVP changes should be evidnetial. Emotional, supposition or hearsay changes should be validated before application; all changes at this point will impact agreed delivery boundaries.
Control and Timescales
Each variable has an impact on delivery; establish a project outline but remember innovation usually means something new so contingenies have to be made for the learning process. Outlining controls (formal requirements, quality, regulatory etc.) will have a positive impact on contingencies.
Conception
Conception explores and evaluates assumptions made at Ideation. This may be via more elaborate sketches, it might be a crude assembly of components, an electronics breadboard, a software wireframe or even a slide presentation.
Concepts test vision and expectations helping all stakeholders and team members visualise the proposed project outcome from a common perspective.
Its not always possible to differentiate a concept from the prototype; this has to be considered in the ultimate project constraints.
Ideally the concept should be capable of testing a range of assumptions resulting from Ideation without massive rework. Output should be sufficiently robust and repeatable to support
the build of a prototype. Output should support the preparation of formal product and project documentation as determined by the final product classification.
Response can help resolve the concept into an effective resource for the project quickly and cost effectively through our network of trusted and skilled partners.
Test Assumptions
Concepts should test assumptions and confirm expectations using the most appropriate and effective method. Ideally concepts should be capable of fast iteration to validate as many assumptions and requirements laid down at Ideation rapidly and cost effectively.
Crystallise
With the concept delivering repeatable results the review should be clearly articulated to all stakeholders culminating in agreement for the way forward. The agreement should unambiguously communicate the scope, the costs and timescales presenting a clear picture of the end result.
Document
With the evidence gained the scope of supporting documentation can be established. The very minimum should be a simple list of clear requirements that can be clearly identified and measured in the final output. For a product in a regulated environment such as medical or aerospace the documentation requirements will be much more extensive and likely include hazard analysis, quality plans, verification and validation plans, and formal product (project) requirement specifications. This is also the time to consider protection via design rights, copyright and patents.
Prototype
The type of product and its complexity determines the prototype route -
from a single iteration for design validation to a sequence of closely related steps intended to evolve a complex product effectively.
For a physical product the early prototypes could be artistic sketches or photo realistic images taken from early digital designs.
Visual prototyping quickly conveys product semantics - shape, form and function identifying materials, finishes, textures etc.
The equivalent stage for software would be interactivity swatches communicating use models and interfaces.
Whatever the product the prototype will culminate in a representative product capable of testing the user experience, manufacturing,
product resilience etc. The prototype may pose more questions and enter into an iterative phase - this is more likely with an innovative product.
Response has dedicated more than 20 years to supporting its clients with effective routes for prototyping their products.
Test Assumptions
Using the most appropriate and effective method the concept should be tuneable to validate as many assumptions and requirements laid down at Ideation.
Crystallise
Once tested and iterated the results coming from a review of the concept(s) should be clearly articulated, documented and the requirements agreed with all stakeholders. A successful requirement should leave no-one in doubt about the scope and finer points of the deliverable product; from this point forward a clear picture of the deliverable product costs should become evident.
Visualise
Clearly define, document and agree the Minimum Viable Product. What should the product do and how should it do it, and what will the customer gain from the product. Do not ignore manufacturing, or in the case of software its deployment.
Production
Response exists to make things! its why we get out of bed every day.
We take pride in each aspect of every innovation we help to bring to market.
We live and breath the innovation process and contribute fully to any part of the process our clients invite us into. The buzz from seeing, touching and
marvelling at the end product is like no other.
For us production isnt just about the end product - its the cullmination of thought,
interaction, choice of supply routes with everything coming together to repeatably build and deliver the best user expereince.
Production is all about detail - manufacture, deployment and delivery and how the customer interacts from the point of purchase onwards.
Response is all about the detail - from understanding materials and methods to the application of tolerances and how they impact the product.
Test Assumptions
Using the most appropriate and effective method the concept should be tuneable to validate as many assumptions and requirements laid down at Ideation.
Crystallise
Once tested and iterated the results coming from a review of the concept(s) should be clearly articulated, documented and the requirements agreed with all stakeholders. A successful requirement should leave no-one in doubt about the scope and finer points of the deliverable product; from this point forward a clear picture of the deliverable product costs should become evident.
Visualise
Clearly define, document and agree the Minimum Viable Product. What should the product do and how should it do it, and what will the customer gain from the product. Do not ignore manufacturing, or in the case of software its deployment.
Contact us
Hey, that's a nice form and you should use it.
Hello!
We would be more than happy to chat with you.
Visit us:
Dix's Field,
Exeter,
Devon EX1 1QA
Mail us:
support@response-design.co.uk
Call us:
UK: 07918 802 379
Int: +44 7918 802 379