project case studies

Their engineers were flat out on today's products. We took the next one.

read on
Project overview

Next-generation product programme

An established manufacturer knew its next product could be built. It needed to know whether it would pay, and whether it could trust an outside team to lead it while its own engineers kept today's products moving.

Key results.

0 engineerstaken off the products its customers are buying today

The challenge.

The client's engineers could see the next generation of the product was possible. They could not spare the time to build it: every one of them was committed to the products already in the market.

So the client's questions were harder than engineering ones. Would it be commercially viable? And could it hand the decisions, and the whole development programme, to a team outside the building and trust it to finish?

Our approach.

The client chose to judge us on work before committing to a programme, so it started with paid discovery. We found out what the problem actually was, wrote down what working means in numbers, and cut complexity and part count wherever the design allowed.

The client had a commercial decision to make, and needed the risks in front of it. Our proposal set out every stage of the programme, what each would prove, and where the risks of iteration sat.

What we delivered.

Discovery and feasibility, and a staged technical proposal for the full development programme, from design through to a tested prototype.

The outcome.

The client handed us the decisions and the full programme. Its engineers stay on the products its customers are buying today.

We can't say whose. That's usually true of our best work.

Capabilities involved

Your project

Your engineers committed to today's products?

Tell us what the next product needs, and what your team is already committed to.