A Project Guide to UX Design: The Field Manual for Working Designers

Most UX books go deep on one method. A Project Guide to UX Design by Russ Unger and Carolyn Chandler does something rarer: it maps the whole project, in the order projects actually happen, with the messy client-shaped parts included.

What does the book cover?

The full arc. Proposals and contracts, the part design education skips entirely. User research and personas. Sitemaps and task flows. Wireframes, prototypes, and annotations. Then the handoff: working with developers, presenting to stakeholders, and surviving the distance between design and launch. Each chapter answers the question working designers actually ask: what do I do at this stage, and what does good look like?

What is its distinctive lesson?

That UX is a project discipline, not a collection of artifacts. The deliverables matter less than the connections between them: research informs personas, personas shape flows, flows structure wireframes, wireframes get annotated so developers can build them. Designers who learn methods in isolation produce orphan artifacts. Designers who learn the project as a whole produce work that moves.

The book is also honest about constraints. Real projects have budgets, politics, and clients who change their minds. The methods are presented with their real-world adaptations, not their textbook ideals.

What do different readers take away?

• Designers in the making: a realistic preview of the job, contracts and compromises included.

• Designers in the field: a reference for stages they rarely touch, and arguments for why each stage matters.

• Clients: literacy about what they are buying and why the steps exist.

Why does Tremoloo share this book?

Because it describes the shape of the engagements we run, end to end. Clients who read it understand our process before we start, and designers who read it ramp faster.

Want a partner who runs UX projects end to end? Meet our product design team.