Projects
We undertake product development, design and engineering projects for and with our clients. From sketch to steel and silicon. From sticky tape to stepper motors. Blu-tack to batch production. All the way from patent to production - or assisting you part of the journey.
We only work on tangible, discrete products that are ultimately intended for series production. "Things" of all descriptions - covering mechanical, electronic, optical and fluidic elements. Taking into account usability, performance, style, production and costs. We also do embedded and application software where they are part of a hardware development project.
Although every project has its own character, we can typically distinguish 4 project phases:
- Product definition: From idea to reality-checked concept designs
- Proof of concept: Technical feasibility of concept design proven in physical model
- Product development: Detailed design, resulting in engineering prototype and documentation pack
- Production engineering: Further detailed engineering for series or volume production; pilot batch assembly; CE-marking
In many cases phases overlap and are somewhat iterative. Below I'm giving an idea on how a typical start-to-finish product development project might look - but bear in mind the best approach for your project could be different!
With our mix of skills we can also help you solve the technology puzzle in other ways. For example in ideation, design reviews and risk analysis. See here for our other services.
Some projects start from a clear need for help in developing a specific product. A very specific task that needs doing. But in many cases opportunities only take shape after discussing vague ideas, sharing experiences and exchanging insights. From our experience it is very valuable to involve us in this process, and we'll be happy invest the time to be your sparring partner.
Phase 1: Product definition
In the first phase of a product development project the objective is to get a very clear picture of just what the prefered product is, in comparison with a range of alternative products. What product will give the best "bang for the buck"?
We start by drafting a design input document, stating user/stakeholder needs and translating them into design specifications - in the case of medical or diagnostic devices special attention is given to the regulatory situation.
In my view, although this document is the basis for the design it is subject to change as our understanding of specific aspects of the product grows. User feedback on early models might indicate a change in direction. Availability of a new key component might enable a revised cost/performance trade-off. For this reason I find it very useful if a design input document provides context, reasoning and relative value perceptions as well as specs.
Once we have a specification (or a number of alternative specifications) we will research options and generate product concepts down to module and key component level. This also allows us to make an initial manufacturing cost estimate, and get an idea of the styling options and constraints.
It is only when we have a number of feasible (on paper at this stage) concepts that we can plan the next project phases in detail - including the remaining feasibility questions we need to answer in phase-2
We prefer to conclude phase 1 - our Product Definition Study - with an interactive workshop supplementing documentation on paper and CD. Phase 1 can normally be concluded within a few weeks, and can be very valuable it its own right, especially for companies that are planning a funding round.
