Part 2 of 9 · 1 min read
Why a framework helps
The problem of the blank whiteboard, and what a fixed order of steps fixes.
Think of a pilot before take-off. The pilot goes through a checklist every time, even after thousands of flights. The checklist does not make the pilot clever. It keeps the pilot from skipping something when nervous or hurried.
A design problem is open-ended. "Design a chat app" has no single answer and no fixed length. Without a method, designers freeze, or they jump to a detail they like and run out of time.
Framework
A framework is a fixed order of steps to follow on every problem of a kind. It does not give the answer. It makes sure nothing important is skipped and that time is spent in the right proportion.
Example: the four steps in this module.
The interview or design review is also a conversation, not an exam. Two engineers are working on a problem that has no perfect solution. The listener is judging how the designer thinks: how they ask, how they reason about trade-offs and how they respond when someone points at a weak spot.
Check yourself:
- Why might a pilot use a checklist even after thousands of flights?
- What is the risk of starting with a detail you like?