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 good UX book topic requires a strong point of view and empathy for readers, not just expertise.
-
•
Evergreen topics balance 20-30% conceptual frameworks and 70-80% practical how-to content.
-
•
Compilations of chapters by multiple authors often lack cohesion and fail to deliver a strong narrative journey.
-
•
The process of writing a UX book is grueling and demands quick, committed effort to avoid long delays.
-
•
Self-publishing is viable but challenging; traditional publishers offer infrastructure, reach, and collaborative support.
-
•
Testing book ideas through workshops, talks, or courses helps gauge interest and refine content before writing.
-
•
Timing and market readiness are critical; books too far ahead or behind the market struggle to succeed.
-
•
Books often gain value over time, sometimes selling better years after release as the field evolves.
-
•
Involving others in the creation process creates stakeholders who help promote the book upon release.
-
•
Writing a UX book is unlikely to generate large royalties; it primarily contributes to advancing the field and professional credibility.
Notable Quotes
"People telling you, you should write a book is nice, but it’s not the real reason to write one."
"The best books balance why and what content with how-to sections to make a topic evergreen."
"We don’t like compilations—books need a singular voice to guide the reader through a journey."
"Writing a book is awful in terms of time and sweat, and it takes a toll on your family life."
"The good side is it’s a gift to yourself and others to dig into a topic you really care about."
"If you want to write a book, you need to write fast and with conviction, not let it linger for years."
"Our approach to publishing is about inclusion, collaboration, and iteration to build a village around the book."
"Running a successful publishing house takes decades to build the infrastructure and relationships."
"Don’t write for royalties; UX books rarely sell in massive numbers, but they advance the profession."
"Timing is crucial—you want to be slightly ahead of the market, but not too far ahead."
Or choose a question:
More Videos
"You’re born on third base but think you hit a triple — that’s the enterprise software delusion."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"The only people who can effectively map a space are those who work and understand that space intimately."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Designing for the dominant default ignores people whose identities are marginalized or excluded."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"Appealing to stakeholders’ best interests helps build trust and rapport."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"My goal today is to showcase how generative AI can go beyond just speeding up our processes and actually catapult us in our career."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Nobody wants to buy or use a sloppy product, especially when enterprise users engage daily for hours."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Consistency over business unit efficiency was a design principle to ensure unified interface and language."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"People were very adverse to changes because a small 0.5% conversion increase meant millions in revenue."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Most of us in design are very process-oriented, but traditional devops tools are task and issue-centric, making collaboration hard."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
