up: index
“Does it solve the problem it’s meant to solve?” - The fundamental question that determines whether a design succeeds or fails.
What is Functional Testing?
Functional testing asks whether your creation actually does what it needs to do. Not whether it looks good, not whether it’s clever, but whether it solves the problem you identified in the Define stage.
Core Question
“Does this solution address the real need we identified?”
Functional vs. Other Testing
Functional Testing
Does it work? Does it solve the actual problem?
Aesthetic Testing
Does it look good? Is it visually appealing?
Technical Testing
Is it well-made? Does it meet quality standards?
All three matter, but functional testing comes first. A beautiful solution that doesn’t solve the problem is still a failure.
Functional Testing in Practice
Both Robot Storage and Dollhouse projects demonstrated how functional testing reveals whether solutions actually solve the intended problems.
Functional Testing Methods
Use Case Testing
Walk through the actual use scenario
- What is the user trying to accomplish?
- Can they accomplish it with your solution?
- Is it easier than what they were doing before?
- What unexpected problems arise?
Failure Mode Testing
Try to break your solution
- What happens under stress?
- How does it fail?
- Can users recover from failures?
- What safety concerns emerge?
Comparison Testing
How does it compare to alternatives?
- Is it better than what exists?
- What trade-offs were made?
- Would users actually choose to use it?
Integration with Design Thinking
Define
Functional testing validates your problem definition
- Did you solve the right problem?
- Were your constraints correctly identified?
Prototype
Early functional testing with simple prototypes
- Test core functionality quickly
- Cardboard prototypes for concept validation
- Avoid perfecting non-functional aspects
Test
Iterative functional testing drives improvement
- Test → Learn → Modify → Test again
- Each iteration should improve functional performance
- User feedback reveals functional issues
The 4 Ms and Function
Maker
Does it solve the problem for the actual user?
Machine
Do the tools enable the required functionality?
Method
Are the processes appropriate for functional requirements?
Materials
Do material choices support or hinder function?
Margin
Is there room for iteration when functionality doesn’t meet needs?
When Functional Testing Reveals Problems
Redesign
Sometimes the approach needs fundamental changes
Refinement
Often functionality can be improved through iteration
Redefine
Sometimes testing reveals you were solving the wrong problem
Reflection Questions
- How did functional testing change your understanding of the problem?
- What functional requirements did you discover only through testing?
- When did aesthetic or technical concerns conflict with functional needs?
- How do you prioritize when multiple functional requirements compete?
Navigate: ← Concepts Home | User Feedback ← | Design Thinking →