Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Coffee with Lou: Should You Write a (UX) Book?
Summary
Everyone feels like they have a book in them—and UX designers, researchers, and (of course) writers are no exception. But having an idea and making it into a book are entirely different things. If you've ever wondered what's involved in the process, how it differs from other types of writing you've done, whether your idea even merits book treatment, or other authorial considerations, well... here's your opportunity to have an informal conversation with a real live publisher of UX books.
Key Insights
-
•
A compelling UX book topic needs a clear point of view and relevance rather than just external encouragement or surface-level expertise.
-
•
Evergreen UX book topics combine 20-30% conceptual frameworks with 70-80% practical 'how-to' guidance for lasting value.
-
•
Books structured as compilations of unrelated chapters tend to fail as they lack a cohesive narrative and singular authorial voice.
-
•
The publishing process benefits greatly from inclusion, collaboration, and iteration, involving multiple stakeholders beyond the author.
-
•
Writing a UX book is time-consuming, emotionally demanding, and risks significant personal and family sacrifices.
-
•
Self-publishing is viable but brings challenges in reach, distribution, and marketing that traditional publishers like Rosenfeld Media have spent years building solutions to.
-
•
Authors who write conversationally with empathy for readers, remembering what it's like to be new, create better UX books than purely authoritative, lecture-style approaches.
-
•
Testing ideas in workshops or courses before writing a book helps refine and prioritize content for a better book structure and audience fit.
-
•
Timing the release of a book is critical; going too far ahead or too late risks losing market relevance or momentum.
-
•
While financial royalties from UX books are typically modest, benefits include increased credibility, speaking opportunities, and consulting rates.
Notable Quotes
"People saying you should write a book is nice, but it’s not the real reason you should write one."
"A really strong book has to be designed as a journey with a consistent voice guiding the reader."
"Don’t write a book expecting to retire on royalties; this is a specialized field with modest sales."
"Writing a book is awful in terms of time, sweat, and time away from your loved ones, but it’s an amazing gift to dig deep into something you care about."
"Inclusion, collaboration, and iteration are the three pillars of how we work with authors to make a book."
"Evergreen content needs a strong perspective on why the topic matters along with practical examples on how to apply it."
"You want someone who writes with equal parts empathy and authority, not just pure authority."
"If your topic is already tackled exceptionally by a prior book, go deeper or wait until the market shifts."
"Testing your book idea through workshops or talks gives a forcing function that helps prioritize content."
"We look to work with authors we like and enjoy being around because writing a book is a long, collaborative journey."
Or choose a question:
More Videos
"You have to go from being able to deliver a message in three bullets and then turn around in the next moment and deliver a massive service blueprint or customer journey."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"We’re all capable of creating and perpetuating toxic work relationships."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"If you have a feeling you’re having the same conversation over and over, a canvas like this can ratchet the conversation forward."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"Quality is value to some person who matters."
John CutlerThe Alignment Trap
November 29, 2023
"Simplicity is not always the answer to complexity, but understanding often is."
Abby CovertStuck? Diagrams Help
October 27, 2022
"Culture is what you tolerate — if you tolerate rudeness or tardiness, it becomes part of who you are."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"Naming things like the 'vibe shift' is powerful in shaping the narratives around future developments."
Devon PowersImagining Better Futures
March 9, 2022
"The best teams I know are a quarter ahead of the product roadmap, seeking out impactful strategic research projects themselves."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Cloud code wasn’t programmed to do this; it’s a very lightweight system where the model does most of the work."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
