Orion Design logo
Article

How engineers choose between concepts.

Good concept selection is not about defending a favourite idea. It is about comparing options against the same criteria, surfacing the real trade-offs, and deciding what needs to be de-risked next.

Teams rarely struggle because they have no ideas. They struggle because several ideas remain plausible at the same time and each stakeholder is weighting success differently. That is when a structured concept-selection matrix becomes useful.

Better question: not “which concept wins?” but “which concept is strongest under the criteria we actually agree matter, and what evidence would change that answer?”

What a strong decision matrix includes

  • stable criteria used across every concept
  • weights that reflect the real project priorities
  • scores grounded in evidence, not just preference
  • a follow-up view of what the matrix does not yet know

Common concept-selection mistakes

Changing the criteria mid-discussion. That usually means the team is trying to defend a preferred solution after the fact.
Weighting everything highly. If every criterion is critical, none of them are helping make the decision.
Treating the output as final truth. The matrix should guide the next test, not replace engineering judgement.

Worked example

One concept might lead on customer value but lag on manufacturability. Another may be technically safer but commercially weaker. The right response is often to identify the best de-risking experiment, not to declare the discussion over.

Use weighted comparison to improve decision quality

The Pugh Concept Selector gives the team a visible way to compare concepts. Pair it with the Product Design Process Map if the chosen concept still needs structured development gates.

Compare concepts transparently

Run a weighted matrix so value, feasibility, manufacturability, and commercial logic are compared in one place.

Open Pugh Concept Selector

Map the next stage after selection

Use the process map if the winning concept now needs clearer planning rather than more debate.

Open Product Design Process Map

Author

Andrew Hunter

Product design engineer working across manufacturability, sustainability, and hardware commercial decisions in Belfast, Northern Ireland.

Source and Attribution

This article was created by Orion Design as part of a human-first engineering knowledge resource for product teams. Use it to inform early decisions, then validate against project-specific data, supplier input, and production constraints.