Refactoring UI book club questions

1. 1.

   Wathan and Schoger built their audience through Twitter before writing the book. Does that origin — solving problems publicly in before-and-after format — affect how you trust or use the content?

2. 2.

   They consistently argue for reducing rather than adding when interfaces feel wrong. Is that instinct natural to you, or do you default to adding more?

3. 3.

   The hierarchy argument — that most problems are really priority problems — applies beyond UI. Where else in communication or presentation do you see the same issue?

4. 4.

   The book is pitched at developers who design their own interfaces. Is it appropriate for trained designers? What would a designer find useful versus obvious?

5. 5.

   They recommend starting in grayscale to force hierarchy from form rather than color. Have you tried this? Does the constraint help?

6. 6.

   The book covers product UI almost exclusively — dashboards, forms, cards. How well do the principles transfer to editorial, brand, or marketing design?

7. 7.

   Most design books are heavy on theory; this one is deliberately light on it. Do you prefer to understand why rules exist, or is demonstrated practice enough?

8. 8.

   The self-published, web-only format means the book will eventually go out of print or behind a paywall. Does how a book is distributed affect how seriously you take its ideas?

9. 9.

   They give very specific numerical guidance in places — whitespace multiples, color opacity percentages. Do you find that level of specificity helpful or constraining?

10. 10.

    The book is essentially a collection of heuristics rather than a design system. What are the limits of heuristics as a design education?

11. 11.

    What is one thing you've tried to build or design recently where one of their principles would have directly helped?

How to run the discussion

• Pick six to eight, not all of them. An hour of real discussion covers fewer questions than anyone expects, and racing the list is what makes a book club feel like homework.
• Open with what people noticed, not what they concluded. Asking for a verdict first hardens opinions before anyone has heard each other.
• Let the disagreement run. The questions below that split a room are the ones worth the time; the ones everyone answers the same way can be skipped.
• Ask the quiet person a specific question. A direct, narrow question is far easier to answer than an open invitation to contribute.