How we work

What is your point of view and where do you want to go?

By properly formulating your objectives, you provide us with frameworks for the further development of your innovation. We then look together at the opportunities and possibilities and of course also the possible risks. We investigate all development options by means of Business Thinking and Design Thinking. We choose a follow-up process based on your needs and wishes. We mainly work with the Agile method.

Create support

If you are thinking about bringing an innovative product or service to the market, two things are important:

  1. Is there a market for it? You research this yourself through conversations with your target group.
  2. Is it feasible? We will find out for you by building a prototype. This way you quickly know what the (im) possibilities are.

You do not have to go through the steps above in this order. After all, by presenting a well-functioning prototype to your target group, you create more support than with a vague idea.

Run for it

We are not long-distance runners. We get off to a quick start and head for the finish. That does not affect our quality, however. Innovation is only useful if you respond quickly to developments. And we do that.

You can invent alone, you innovate together

That’s why we always sprint with you. We share our knowledge and we constantly adapt our development to the needs and insights within your company. The lines of communication are short and we are in regular contact. This way we get to know each other well and we know what is going on and what is important in your organization.

A step to the next phase

During our short sprints we test your hypothesis or idea. We will then know whether it works and whether users are using your prototype as you imagined. If an adjustment is needed, you will know immediately. And that saves you months of work.

Is the prototype satisfactory? Then you can expand the concept or take the next step towards industrialization. That is also fast, because the prototype is almost identical to the final version. The prototype is therefore almost ready for production.

We make clear result agreements

And we will not stop until we have achieved the agreed goals. Do you want to make changes in the meantime or do you have additional ideas? Which can. Then we adjust the end result to be achieved.

Verification, testing and validation

The V-model provides insight into our development process. It leads to the desired structure, the best result and a good balance between the verification, testing and validation phase. It forces us to formulate your objectives SMART in the verification phase, which we then check in the validation phase. Do the results delivered to the required specifications.

On the left side of the V-model are phases in which a product is designed (specified) and developed into a prototype. A strategic session was often carried out in advance. It is important here that results from the phase are tested against the next phase, this is in relation to the intended change or changes.

On the right side of the V-model are the phases in which testing and verifications are central. The V-model has been a simple tool for years to gain insight into processes for changes in the information provision, in particular for the software. The horizontal line is the formal division between the supplying and accepting party.

Despite the linear presentation of the V-Model, it is also very applicable in our own agile development approach. A useful feature of the V-model is that it provides insight into the phases about which we make agreements with customers.