IA Day 10 —
Evaluate Concepts
Use design specifications, testing and user feedback to evaluate your feasible ideas, identify a current front-runner and expose unresolved questions.
By the end of class, you should be able to…
Evaluate—not describe
Make a judgement using evidence.
Use specifications
Test ideas against requirements that matter.
Use user feedback
Include intended-user/client evidence in the comparison.
Identify a front-runner
Use current evidence to identify the strongest direction without treating the judgement as irreversible.
Evaluation asks: “How well does each idea meet the evidence?”
Specifications
Use relevant essential/desirable requirements as criteria.
Testing
Use models/drawings/CAD evidence where appropriate.
User feedback
Bring the intended user/client back into the decision.
| Criterion | Idea A | Idea B | Idea C | Evidence |
|---|---|---|---|---|
| Essential: one-hand use | Strong | Weak | Medium | Task test + observation |
| Essential: fits storage envelope | Pass | Pass | Fail | Dimension check |
| Desirable: visual clarity | Medium | Strong | Strong | User preference + annotated render |
“Idea B has the biggest handle.”
“Idea B’s larger handle improved grip confidence in user testing, but it exceeds the storage-width specification; Idea A therefore provides the better balance for the intended context.”
Build your provisional concept judgement.
Choose criteria that actually reveal meaningful differences.
Use an appropriate representation and intended-user/client input.
Explain strengths, weaknesses, trade-offs and evidence.
Make the current comparison understandable to a reader.
Be ready to answer these without guessing.
Before you leave…
How Designers Classify Materials
Keep the evidence chain moving: user → research → decision → test.
Organize today’s evidence while it is fresh. Make sure each design decision can be traced to research, testing or intended-user evidence.