--- title: "The prince of user documentation – lessons from Machiavelli" id: "22112" type: "post" slug: "the-prince-of-user-documentation-lessons-from-machiavelli" published_at: "2026-05-22T06:34:28+00:00" modified_at: "2026-05-22T06:35:09+00:00" url: "https://www.cherryleaf.com/2026/05/the-prince-of-user-documentation-lessons-from-machiavelli/" markdown_url: "https://www.cherryleaf.com/2026/05/the-prince-of-user-documentation-lessons-from-machiavelli.md" excerpt: "In 1513, Niccolò Machiavelli sat in exile and wrote the most ruthlessly practical guide to power ever committed to paper. He wasn’t interested in how things should work. He was interested in how they do. Five centuries later, most SaaS..." taxonomy_category: - "strategy" taxonomy_post_tag: - "documentation" - "strategy" --- In 1513, Niccolò Machiavelli sat in exile and wrote the most ruthlessly practical guide to power ever committed to paper. He wasn’t interested in how things should work. He was interested in how they do. Five centuries later, most SaaS companies treat their user documentation as an afterthought: a support cost to minimise, a page to publish and forget. Machiavelli would have wept. > “It is better to be feared than loved, if you cannot be both.” What Machiavelli understood is that power is engineered, not inherited. Your documentation is the most underused weapon in your arsenal. Great user documentation is a customer acquisition engine, a competitive moat, and a conversion machine, if you are ruthless enough to use them that way. ## Chapter I: Know thy enemy’s weaknesses > “The wise man does at once what the fool does finally.” The Prince, Chapter 3 Before you write a single word of documentation, open your competitor’s help centre and read it like an adversary. Where does it go silent? What questions are left unanswered? What frustrations are users voicing in Reddit threads, community forums, and Stack Overflow posts? These are open wounds, and your opportunity. - Use tools like Ahrefs or SEMrush to find queries that rank for your competitor’s product but return thin or unhelpful answers - Search “[Competitor Name] + problem / error / how to” and catalogue every unanswered question you find - Build documentation that directly addresses those gaps by solving the problem better than they do - Notion captured a generation of Evernote users through migration guides and honest comparison pages rather than advertising. That is the play. ## Chapter II: Infiltrate the kingdom aka AI search and chatbot optimisation > “One who deceives will always find those who allow themselves to be deceived.” Attr. Machiavelli If you think about how people actually solve problems today, they don’t type “best CRM software” into Google and read ten reviews. They type: - *“Why is HubSpot so slow at loading contacts?”* - *“How to export data from Salesforce to CSV without errors?”* - *“ChatGPT, what’s a cheaper alternative to Asana?”* They’re searching for answers. They’re one bad experience away from switching. Then they ask their AI chatbot of choice and they trust the answer. Those AI engines are *desperate* for reliable, structured, authoritative data. AI-powered search has changed who surfaces first. When a user types “how do I export data from [Competitor]” into ChatGPT, Perplexity, or Google’s AI Overview, the response they receive is synthesised from the best-structured, most authoritatively written content on the topic. If your documentation answers that question, your product gets recommended. ### Your new playbook Your job is to be the useful ghost that appears right when they need an escape. - When a user asks an AI “How do I fix [Competitor X’s common error]?” – who gets cited? If you’ve done your job right, you do. Write “How to do X in [Competitor] and a faster way” articles that are genuinely useful. They don’t need to be adversarial - Write universal, category-first content that ranks for high-intent informational queries, even when the user isn’t looking for you. - List every frustration, limitation, or missing feature of your top three competitors. Turn each into a natural-language prompt. - Use clear hierarchical structure (H2s, H3s, short paragraphs) that LLMs favour when constructing summaries - Contribute helpfully to Stack Overflow, Reddit, and GitHub Discussions with answers that reference your product naturally and honestly - Schema markup any FAQs so they surface in AI overview panels The goal is positioning. If someone is frustrated with a competitor’s workflow and your documentation shows them a better path, you have not manipulated anyone, you have served them. ## **Chapter III: The art of the migration guide** > “Men are so simple and so much inclined to obey immediate needs that a deceiver will never lack victims.” The Prince, Chapter 18 The most valuable users you can acquire are the discontented. This is because they are already motivated to act. They have already done the hard work of deciding their current tool isn’t working. Your job is to remove every remaining barrier. A great migration guide does these things: - Acknowledges the switching cost honestly; don’t pretend it’s nothing - Maps familiar workflows in the old product to equivalent (or superior) workflows in yours - Anticipates objections and answers them before the user has to ask These pages rank for the highest-intent searches imaginable: “switching from X to Y,” “X alternative,” “migrate from X.” Someone searching those terms is one good documentation page away from becoming your customer. ## Chapter IV: Fortify your own kingdom > “A prince who relies entirely on fortune is ruined when fortune changes.” The Prince, Chapter 25 Machiavelli’s sharpest warning: a strategy built entirely on exploiting others’ weakness is fragile. The moment your competitor improves, your advantage evaporates. You must build something genuinely unbeatable. - Sandbox environments where users can run code examples without leaving the page - Versioned documents that stay accurate across product updates. Nothing erodes trust faster than stale instructions - An open, public changelog that signals momentum and demonstrates that someone is paying attention - Search that actually works: semantic, fast, and forgiving of spelling errors The documentation moat is self-reinforcing. Better documentation attract more users. More users generate more feedback. Better feedback produces better documentation. Competitors cannot copy this easily. It compounds over years. ## Chapter V: Win the loyalty of the people > “It is necessary for a prince to have the people on his side; otherwise he has no security in adversity.” The Prince, Chapter 9 Machiavelli understood something that modern growth teams often miss: the most durable power comes from genuine loyalty. A community that believes in your product will defend it, advocate for it, and produce content about it that no marketing budget could replicate. - Build a community forum directly adjacent to your documentation. Let users answer each other’s questions and surface those answers back into the official documentation - Run a documentation ambassador programme: power users who contribute tutorials, translations, and edge-case guides in exchange for recognition and early access - Create a public roadmap for documentation itself. Show users what’s coming and invite them to vote on priorities ## Chapter VI – Control the narrative > “Everyone sees what you appear to be; few experience what you really are.” The Prince, Chapter 18 The language you use in your documentation shapes how users think about the problem space. This is framing. Every product does it. The question is whether you do it consciously. Name things in ways that centre your product’s conceptual model as the natural default. If your approach to a workflow is genuinely superior, give it a name that sticks. Reference industry standards your product meets, and that competitors quietly don’t. Let the facts do the persuading; the structure of your documentation amplifies them. ## The ethical line Some might ask, isn’t this manipulative? Do not lie. Influence the environment so that the truth your product’s genuine superiority becomes visible at the precise moment a customer needs it: - Publishing accurate, useful information - Ensuring frustrated users can find a better way ## **Conclusion – The ruthless editor** Machiavelli’s final lesson was about will. Most of his advice was simply the courage to act on what everyone already knew but no one was willing to say aloud. Most companies know their documentation is inadequate. They know competitors’ documentation has gaps. They know AI search is changing everything. They just don’t treat documentation as a strategic function worthy of real resources and real ambition. Treat your documentation team like a product team. Give them a roadmap, a backlog, metrics, and a mandate. Audit quarterly. Cut ruthlessly what doesn’t serve you. Double down on what does. The prince who does this, who turns the help centre into a competitive weapon, will find that customers arrive already convinced, already loyal, already sold. Not because of advertising. Because of the documentation. Inspired by Niccolò Machiavelli, The Prince (1532). ### Share this: - [Share on Facebook (Opens in new window) Facebook](https://www.cherryleaf.com/2026/05/the-prince-of-user-documentation-lessons-from-machiavelli/?share=facebook) - [Share on LinkedIn (Opens in new window) LinkedIn](https://www.cherryleaf.com/2026/05/the-prince-of-user-documentation-lessons-from-machiavelli/?share=linkedin) - [Share on WhatsApp (Opens in new window) WhatsApp](https://www.cherryleaf.com/2026/05/the-prince-of-user-documentation-lessons-from-machiavelli/?share=jetpack-whatsapp) - [Share on Bluesky (Opens in new window) Bluesky](https://www.cherryleaf.com/2026/05/the-prince-of-user-documentation-lessons-from-machiavelli/?share=bluesky) - ### *Related* ### Leave a Reply[Cancel reply](/2026/05/the-prince-of-user-documentation-lessons-from-machiavelli/#respond) This site uses Akismet to reduce spam. [Learn how your comment data is processed.](https://akismet.com/privacy/) #### Previous post [Podcast 166: From founder-led to process-driven; how to build a culture that scales](https://www.cherryleaf.com/2026/05/podcast-166-from-founder-led-to-process-driven-how-to-build-a-culture-that-scales/) #### Next post [We tested Google Gemini’s new Omni model to create a promotional video. Here’s what we found.](https://www.cherryleaf.com/2026/05/we-tested-google-geminis-new-omni-model/) #### Browse posts by month Browse posts by month Select Month October 2026 (1) September 2026 (12) August 2026 (8) July 2026 (7) June 2026 (14) May 2026 (8) April 2026 (6) March 2026 (14) February 2026 (9) January 2026 (9) December 2025 (7) November 2025 (9) October 2025 (10) September 2025 (7) August 2025 (6) July 2025 (1) June 2025 (3) May 2025 (2) April 2025 (5) March 2025 (3) February 2025 (3) January 2025 (2) November 2024 (8) October 2024 (3) September 2024 (2) August 2024 (3) July 2024 (4) June 2024 (1) May 2024 (2) April 2024 (4) March 2024 (1) February 2024 (2) January 2024 (1) December 2023 (2) November 2023 (9) October 2023 (8) September 2023 (5) August 2023 (3) July 2023 (1) June 2023 (1) May 2023 (2) April 2023 (3) March 2023 (2) January 2023 (2) December 2022 (4) November 2022 (1) October 2022 (1) September 2022 (1) August 2022 (1) July 2022 (1) June 2022 (1) May 2022 (2) April 2022 (1) March 2022 (1) February 2022 (1) January 2022 (2) December 2021 (1) November 2021 (2) October 2021 (1) August 2021 (1) July 2021 (2) June 2021 (3) May 2021 (5) April 2021 (3) March 2021 (3) February 2021 (1) January 2021 (2) December 2020 (4) November 2020 (4) August 2020 (3) February 2020 (3) January 2020 (1) November 2019 (3) October 2019 (1) September 2019 (1) August 2019 (3) July 2019 (2) June 2019 (3) May 2019 (4) April 2019 (1) November 2018 (2) October 2018 (1) July 2018 (2) June 2018 (4) May 2018 (2) April 2018 (3) March 2018 (4) February 2018 (2) January 2018 (3) December 2017 (2) October 2017 (3) September 2017 (1) August 2017 (3) July 2017 (2) June 2017 (7) May 2017 (4) April 2017 (5) March 2017 (1) February 2017 (7) January 2017 (1) December 2016 (3) November 2016 (4) October 2016 (1) September 2016 (5) July 2016 (1) June 2016 (3) May 2016 (1) April 2016 (2) February 2016 (2) January 2016 (5) December 2015 (1) November 2015 (4) October 2015 (2) August 2015 (1) July 2015 (1) June 2015 (2) May 2015 (3) February 2015 (2) January 2015 (6) December 2014 (1) October 2014 (1) September 2014 (4) June 2014 (4) May 2014 (1) April 2014 (2) March 2014 (3) February 2014 (4) January 2014 (4) November 2013 (2) October 2013 (5) September 2013 (3) July 2013 (3) June 2013 (11) May 2013 (4) April 2013 (6) March 2013 (7) February 2013 (4) January 2013 (4) December 2012 (9) November 2012 (23) October 2012 (14) September 2012 (8) August 2012 (4) July 2012 (12) June 2012 (12) May 2012 (10) April 2012 (8) March 2012 (12) February 2012 (3) January 2012 (6) December 2011 (2) October 2011 (3) August 2011 (1) June 2011 (5) May 2011 (2) April 2011 (1) January 2011 (1) December 2010 (1) November 2010 (3) October 2010 (4) September 2010 (8) August 2010 (5) May 2010 (2) April 2010 (3) March 2010 (3) February 2010 (2) January 2010 (3) December 2009 (2) November 2009 (6) September 2009 (1) July 2009 (6) June 2009 (7) April 2009 (8) March 2009 (3) February 2009 (3) January 2009 (3) December 2008 (1) November 2008 (3) October 2008 (3) September 2008 (4) August 2008 (1) July 2008 (3) June 2008 (5) May 2008 (2) April 2008 (2) March 2008 (3) February 2008 (2) January 2008 (1) November 2007 (3) October 2007 (2) September 2007 (1) July 2007 (3) November 2006 (1) October 2006 (2) September 2006 (3) August 2006 (1) April 2006 (1) March 2006 (3) #### Browse posts by category