Back tostdlib
Article

The origin of my Retrospectives Antipatterns book

The author recounts turning a hastily-made talk on retrospective antipatterns into a self-published book, then a traditional deal, exposing pitfalls of publishing, distribution, and audiobook narration for tech leaders.

A quick, on-the-fly talk can become a lasting resource, but the path from slide deck to published book is littered with hidden costs. The author started with a 20-minute GOTO booth talk in 2013, expanded it into a 45-minute presentation, then a Google doc used in facilitation courses, before self-publishing on Leanpub in 2017. Leanpub gave him full control and immediate revenue, but also limited feedback and modest pricing. A contract with Pearson/Addison-Wesley in 2020 promised wider distribution, a professional cover, and Amazon pre-orders. Shipping delays, US-only print runs, and a misleading Amazon bestseller badge exposed the logistical nightmares of traditional publishing. The author also narrated his own audiobook-a decision he now advises against-and later saw the work translated into Chinese and German. Technical leaders can take three practical takeaways: don't assume self-publishing is cheap or simple; validate print logistics and regional availability before signing with a large publisher; and avoid DIY audiobook narration unless you have professional voice experience. The underlying story also reinforces why sharing retrospective antipatterns matters: concrete patterns help teams run more effective meetings and avoid recurring process pitfalls.

Source: linkedin.com
#retrospectives#agile#engineering management#technical leadership#continuous improvement#software development

Problems this helps solve:

Meeting effectivenessProcess inefficienciesKnowledge sharing

Explore more resources

Check out the full stdlib collection for more frameworks, templates, and guides to accelerate your technical leadership journey.