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
"Design helps build capital and seek comfort, which draws in the most powerful."
George AyeThat Quiet Little Voice: When Design and Ethics Collide
November 16, 2022
"We fundraised to cover Tatiana’s salary for three months so she could launch this project very quickly after the war started."
Xenia Adjoubei Sean BruceEmpowering Communities Through the Researcher in Residence Program
March 29, 2023
"We focus on getting top quality participants and let others specialize in testing or analysis tools."
Benjamin Wiedmaier Annie MayfieldRedefining Toolkits: Unbundling to Create a Perfect Match
March 11, 2025
"Design operations provides the connective tissue running through different kinds of projects, making sure we have the right resources and processes."
John DevanneyThe Design Management Office
November 6, 2017
"The developer who refused to run experiments bragged about success, but it was actually a flop once we ran the test properly."
Steve Sanderson Alissa Briggs Jeff Gothelf Bill ScottDiscussion
May 14, 2015
"Jackie Ho talks about how to keep teams accountable and aligned while maintaining their autonomy."
Jemma AhmedTheme 2 Intro
January 8, 2024
"Our jobs as researchers isn’t really to do research. It’s to influence people and help them make decisions."
Megan KiersteadYou Are a Badass at UX: Overcoming Imposter Syndrome
March 10, 2021
"We try to keep things as consistent as possible in terms of the API but document where platforms need to deviate to be good citizens of their environment."
PJ Buddhari Nate BaldwinMeet Spectrum, Adobe’s Design System
June 9, 2021
"Dunbar's number explains why groups around 150 people work best as communities."
James LangIf you can design an app, you can design a community
May 22, 2025
