Set-based Engineering

When using waterfall Project models one of the problems you face is to take important decisions before you really have the knowledge to do so.

The Set-based thinking is to take decisions when you have the required knowledge, meaning that the quality of decisions increase (to keep the design space as open as possible for as long as possible)

Point-Based Design (Traditional Design)

- Select a single feasible design option early

- Refine that single design (or point) as more information becomes available throughout the design process

- Rework the single design until a solution is found that is feasible for all parties

Flexibility, cost and time are valuables during the whole development process.

The risk in a point based design is:

- To Invest in a risky design quickly

- To have to rework the design (depending on a new reality)

- Have longer cycle time depending on lack of short time targets (efficiency)

Set-Based Design

- Focus on keeping the design space as open as possible, for as long as possible, to build knowledge in a systematic way

- Capture the knowledge to be used in future designs

- The team can adapt to new information when needed

- The team is moving with a higher speed since they focus on a specific target, using available data to choose the best solution

- The cost remains low since the team works with assumptions before investing in a technical solution

- Use a funneling process to reduce the number of feasible designs, as constraints are invoked

- If you look at it we often take decisions selecting one idea before we have to

- In the purchasable document there is an example on the design process and its efficiency

- Design efficiency is a measurement of flexibility, cost and time

- With a set-based approach the design team can maximize flexibility, cost and time

As you see in this presentation the Set-Based Thinking is not restricted to engineering it can be used and benefited from in all areas