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
"I’ve been using screen readers for 30 years and accessibility has always been a passion of mine."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"It's kind of Peace Corps for nerds – people come in for a tour and try to have impact at scale."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"Ownership of VOC is a hot potato, so we built a coalition with a facilitator to keep it collaborative and effective."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Leadership doesn’t only mean managing; it can be mentoring, product leadership, or technical influence."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"If you’re managing over 100 design practitioners, it makes sense to start looking at a chief of staff role."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Design takes on a new role as governance practitioner, overseeing branding, content, and accessibility."
Amy EvansHow to Create Change
September 25, 2024
"Telepathy as mind reading means proactively building a talent pipeline and improving recruitment processes."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"If you do anything with other people, you’re creating culture."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"Standalone insights destroy the researcher’s ability to storytelling and engagement."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020