Solve the right problem

A simple answer to the wrong question is still bad design.

Good design solves the right problem.
Paul Graham, Taste for Makers · Feb 2002

From Taste for Makers · 4 notesNoteExampleDemo

Good design solves the right problem. The typical stove has four burners arranged in a square, and a dial to control each. How do you arrange the dials? The simplest answer is to put them in a row. But this is a . The dials are for humans to use, and if you put them in a row, the unlucky human will have to stop and think each time about . Better to arrange the dials in a square like the burners.

A lot of bad design is industrious, but misguided. In the mid twentieth century there was a vogue for setting text in sans-serif fonts. These fonts are closer to the pure, underlying letterforms. But in text that's not the problem you're trying to solve. For legibility it's more important that . It may look Victorian, but a Times Roman lowercase g is easy to tell from a lowercase y.

In software, an intractable problem can usually be replaced by an equivalent one that's easy to solve. Physics progressed faster as the problem became predicting observable behavior, instead of reconciling it with scripture.

1Note

Settings grouped by database table. Filters in the order the API takes them. Simple for us, wrong for the user.

2Demo

Put the control next to the thing it controls.

Mapping and specific labels →

3Demo

Same for numbers. Use tabular figures so columns line up.

Numerals, quotes and spaces →

4Note

Before you design a better import wizard, ask if people need to import at all.

Read article ↗

Try it