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.
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
"Teams stuck in the back room doing API work are only two steps away from the customer."
Tim ParmeeChanging Our Design Pressure Points
October 2, 2023
"Make a case to hire people who are product agnostic to connect where products intersect in the rider journey."
Kristin TaylorBuilding Bridges Across Organizational Silos
November 18, 2022
"If you have any questions for the speakers, you really need to put your question in the thread specific to the talk."
Bria AlexanderOpening Remarks
October 3, 2023
"Imagine if everyone you worked with had deep empathy for your customers and made decisions based on those customer needs."
Amy Jiménez Márquez Michael J. Metts Joie ChungThe Atypical UX Manager Path
July 23, 2020
"You are the reason why we are able to have such high quality programming that we do have at this conference this week."
Bria AlexanderOpening Remarks
June 11, 2021
"We can start small, test and validate quickly with a three-week tag team—one PM, one designer, one researcher."
Ted NewardTheme 4: Enterprise Organizational Journey
June 4, 2019
"Share price is actually a model of the expected value of all future income of a company."
Ellen ChisaThe Values of Design
November 29, 2023
"This research skills framework could become a living language of practice that evolves with community contributions."
Dave HoraA Research Skills Evolution
March 10, 2021
"We ended up doing an average of five labs per quarter covering 12 to 15 research questions, which helped avoid design delays."
Feleesha SterlingBuilding a Rapid Research Program
May 18, 2023
