Sketching User Experiences: Getting the Design Right and the Right Design
Source: https://www.elsevier.com/books/sketching-user-experiences/buxton/978-0-12-374037-3 ↗
Buxton's argument is deceptively simple: sketching is thinking, not drawing. A sketch is disposable, ambiguous, fast — the opposite of a specification.
The book demonstrates that the earliest phases of design require tools that encourage exploration and tolerate vagueness, and that reaching for high-fidelity prototypes too early kills alternatives before they can be evaluated.
Buxton spent decades at Xerox PARC, SGI, Alias, and Microsoft Research, and he was one of the invisible architects behind multi-touch and the Microsoft Surface.
The practical implication for product teams is that the gap between "we need a wireframe" and "we need to think" is where most design value is created and most organizations fail.
This is the best single book on why the front end of the design process matters more than the back end.
Central argument
Buxton argues that sketching is a cognitive act, not an artistic one: the properties of a sketch — disposability, ambiguity, speed — are precisely what make it the right tool for early design exploration. His central thesis is that high-fidelity prototypes, by appearing finished, foreclose alternatives prematurely and shift teams into refinement mode before the right problem has been identified. The book distinguishes between 'getting the design right' (execution) and 'getting the right design' (discovery), insisting that most design value lives in the messy front end that most organizations systematically underinvest in.
Critique
The book's framework was forged inside research environments — Xerox PARC, Microsoft Research — where time horizons and funding structures are fundamentally different from commercial product organizations under quarterly pressure. Buxton's argument that teams should stay in exploratory, low-fidelity modes longer is compelling in principle but underspecifies how to navigate the organizational reality where stakeholders equate fidelity with progress and sketches with insufficient work. The book offers little tactical guidance on how to protect early-phase ambiguity inside delivery-obsessed structures, which is precisely where the argument needs the most support.
Why it matters for product
For a CPO, the book reframes a recurring organizational failure: the pressure to produce wireframes or prototypes before the problem space is genuinely understood is not a process inefficiency but a structural bias toward outputs over thinking. This has direct implications for how discovery is staffed and sequenced — if designers are pulled into delivery squads too early, the exploratory work that Buxton identifies as highest-leverage never happens. The practical intervention is not a new tool but a defended phase: time and permission to work in a mode that tolerates vagueness before the organization's convergence instincts take over.