From Idea to Product

How do we work up from an idea all the way to a working product/solution? We split this process up in four phases, which are loosely based on the Front-end loading (FEL) method. The idea is to develop sufficient information and understanding early on in the project. This enables strategic decision making about the direction the project will be going and better risk assessment and resource allocation.

Phase 1: Requirements

When you have an idea, before you can turn it into a project, it is important to derive the requirements as completely as possible. This is where we need your domain specific knowledge to get an in depth picture of the problems to solve. Additionally, we try to understand the *why* of the problems so that we can be sure we are solving the root cause and not the consequences.

Phase 2: Concept

Combining all requirements and other prerequisites we will make one or more concept designs. This may involve creating some early prototypes to test feasibility of certain working principles or to compare them. The idea is to do this phase quite thoroughly so that enough details are known to make good decisions regarding the next steps. For example estimates of bill-of-materials and planning.

Phase 3: Engineering/detail

This phase starts when one of the concepts has been picked and approved. The Detailed Design phase entails the complete hardware design and software design and development.

Phase 4: Production and Tests

In the final phase we will produce the prototypes and perform functional testing. We verify if the product we built is working correctly and if it meets the program of requirements. After that we will do acceptance testing in cooperation with the client. This should validate whether the solution actually solves the clients problem. Did we build the *right* thing? In some cases the prototype is also the final product, in other cases we can start field tests and start preparing to scale up production.