Pugh Assessment & Concept Selection

A complete knowledge and project workspace for structured engineering concept selection. Define the decision, build criteria, select a datum, compare concepts, apply optional weighting, test sensitivity and document the final rationale.

New Pugh project
0 concepts / 0 criteria
Pugh Assessment is a comparative concept-selection method associated with Stuart Pugh. Each concept is compared against a chosen datum using consistent criteria. The classic method uses + / S / − for better, same and worse; this app can also apply criterion weightings to make relative importance explicit.
1. FrameDefine the decision and constraints
2. ConceptsIdentify credible alternatives
3. CriteriaDefine what matters
4. DatumSelect the reference concept
5. CompareScore each concept consistently
6. Decide & IterateSelect, combine or refine concepts
Pugh Method Knowledge Pack
Why use it?

It turns a subjective concept discussion into a visible, reviewable decision process. The value is the reasoning and trade-off conversation, not just the final score.

Classic scoring
  • + better than datum
  • S / 0 similar to datum
  • worse than datum
Weighted scoring

Weight criteria when importance genuinely differs. Avoid using weighting to force a preferred answer; document the basis for each weight.

Good criteria

Use criteria that are independent, measurable or assessable, linked to requirements and written so every concept can be judged consistently.

Choose the datum carefully

The datum may be the current design, an incumbent process, a benchmark or the most understood concept. It should provide a meaningful baseline.

Synthesis

A Pugh matrix often reveals that no single concept is best. Combine strong features from different concepts, create a new hybrid and assess again.

Avoid false precision

Do not treat a narrow numerical lead as proof. Review uncertainty, assumptions, safety, compliance, feasibility and evidence quality.

Team-based assessment

Use a cross-functional team where possible. Differences in scoring are useful because they reveal assumptions and missing information.

Decision record

Capture rejected options, trade-offs and reasons. That traceability is often as important as the selected concept.

Recommended Rules
1. Requirements first

Eliminate concepts that fail mandatory requirements before relying on comparative scoring.

2. Evidence before opinion

Link judgements to calculations, test data, supplier evidence, prototypes or engineering analysis where available.

3. Sensitivity matters

If small changes to weights reverse the winner, the decision is sensitive and deserves further investigation.

Project Definition
Define exactly what decision the matrix is intended to support.
Project Dashboard
0Concepts
0Criteria
0Total weight
0%Matrix complete
Current leader
Candidate Concepts
Add all realistic options. One concept must be designated as the datum/reference.
IDConcept NameDescription / Key FeaturesMaturity / EvidenceMandatory Requirements Met?Datum?
Tip: Use the current design or the best-understood baseline as the datum. If several concepts fail mandatory requirements, record that before scoring rather than allowing a weighted total to hide a fundamental non-compliance.
Evaluation Criteria
Weight 1–5 is optional but useful when criteria have materially different importance.
IDCriterionDefinition / MeasureCategoryWeight 1–5Evidence / Source
Typical categoriesPerformanceSafetyReliabilityManufacturabilityCostScheduleMaintainabilityRiskSustainability
Pugh Assessment Matrix
Score each non-datum concept against the datum. + = better, S = similar, − = worse. Add a short rationale where useful.
Results Dashboard
Datum
Highest score
0Leader score
01st–2nd spread
Decision strength
Concept Ranking
Review both total score and the pattern of strengths/weaknesses.
RankConceptWeighted / Classic ScoreBetter (+)Same (S)Worse (−)Mandatory RequirementsInterpretation
Sensitivity Check
Simulate ±20% weight variation one criterion at a time. A leader that changes easily indicates a sensitive decision.
Run the sensitivity check after completing the matrix.
Decision Team / Approval Record
NameFunctionRole in AssessmentPosition / CommentsApproval / Initials
Project Report
The report combines project definition, concepts, criteria, matrix results, ranking and decision rationale into a professional landscape PDF.
Quality Check Before Approval
Criteria quality

Are criteria distinct, clearly defined and linked to requirements?

Concept fairness

Were all concepts assessed with comparable evidence and the same interpretation of each criterion?

Decision robustness

Would modest changes in weights or uncertain scores materially change the result?

Mandatory requirements

Has any concept been selected despite failing a non-negotiable requirement?

Team challenge

Were disagreements discussed and assumptions exposed?

Traceability

Could another engineer understand why the decision was made six months from now?