You can also a little bit summarize and-

Basically we split that up in, in three big phases that have sub-phases.

It is still sort of a, a, a waterfall process because it is a hardware development and you need to build stuff and validate stuff.

And doing that in, in that waterfall setting with, uh, clear go, no-go points within the process is really important, uh, we believe.

And what we start with in that first phase, it's a more strategic phase, is where we look at first the framing.

What is the product about? Because people that do not know me, we're a service provider in product development, so people usually come to us with an idea, with an idea for a product or with a certain technology.

And of course, we need to transfer knowledge from them to us and also from us to them.

So how do you basically trade off different requirements? How do you get to the requirements, first of all, from the, let's say, user needs? And then how do you trade them off against each other?