"Documentation is key to product success.\nRead that again. This is what many founders say when asked about the most vital piece in their scaling processes. What has begun as an initial, quick way to get your first few customers, ends up being significant groundwork for continuous growth and scale - that gets amplified with time.\nThe shift from manual or micro-documented processes towards scalable workflows requires a complete shift in thinking: Documentation is not just dumping information into Word/Google Docs/Slack channel/something else, it's the act of carefully constructing instructions for people to use your product efficiently.\nThis can range from how you onboard new users through steps they need to take to use specific features - all the way down to why certain settings are applied and how to change them (yes, this is crucial for successful scaling).\nThe Secret Weapon of Successful Startups\nHowever, documentation is often seen as an afterthought or a task delegated to the quality control department (often outsourced), and later on, it is primarily used by support (again, outsourced) if at all. Unfortunately, no one thinks about its value for growth/scaling - or even just customer happiness. Let's have a look at some numbers that prove how vital good documentation can be:\nA study by Harvard Business Review states that reducing cycle time by just 5% increases a company's profit margin by 25-95%.\nCustomer surveys from Segment show that 39% of customers abandon a website because of bad support, and only 23.5% care about how good the product is (source: articles.segment.com/how-do-customers-really-feel).\nThe conclusion? Speed matters. And by speeding up tasks, you speed up your whole workflow - but this needs to be planned from the beginning.\nWhy Product Documentation?\nGood documentation leads to happy users. This means fewer support issues which result in more time for scaling additional features and generating more revenue instead of covering basic user questions.\nHaving a well-structured knowledge base can lower a significant portion of costs from customer service as some questions are being answered automatically before they reach anyone at all.\nThe Return Of Investment (ROI) of implementing proper documentation enables you to handle around 30% more users/customers with the same amount of employees - even if data says so.\nCreating good quality product documentation is getting easier all the time with tools like Zendesk and Intercom. Start small, iterate, and treat your docs as living and growing organisms.\nusing zendesk as a tool to scale\nGeneral Documentation vs. Product-Specific\nWhy do you need both, and what makes the difference between good documentation and bad one? Let's get started with general documentation: these are handbooks that every company has to build before even thinking about scaling (and not just startups). They include procedures for employees on how to deal with specific issues - like using Excel or creating invoices.\nThe rule of thumb is: If it can be easily copied, don't write a manual.\nImagine your new employee has never worked with Excel before. What would you rather tell them: \"Go Google something, I'm busy right now.\"; or send them a link to an article that shows them step-by-step how to use it within your company's context? In this case, a good rule of thumb is: If it can be found on Google, don't write a manual.\nThe good news is that tools use standardized processes to generate knowledge base articles which are constantly being improved by employees and customers alike. That way, what employees type into the system is immediately reflected in the user interface as a new article for users - no wasting time, no bad information.\nOverall leads to less frustration from both sides and speeds upscaling they never have even dreamed of before. On top of that, it comes without any automated training costs - so you save money there as well. In most cases they wouldn't even need to spend their time typing stuff into Google - and they would not get the user interface that makes it easy to use our product.\nProduct-Specific Documentation\nStartups are different from bigger companies. It is worth building your product documentation with that in mind. Let's have a look at the differences: Smaller teams often work on more than one project or product at once - especially when they are scaling fast. This means everyone has to know everything about all products, big time saver.\nThey usually don't have dedicated people for quality assurance (QA). Onboarding new employees become critical as it saves them time by having 100% accurate information on how things work within the company. Most of the communication happens over Slack, email, chat apps, etc., which means nobody reads manuals anymore.\nhttps://twitter.com/xjamundx/status/1484291717868056577\n\nAnd documentation becomes really important again. Because of this, you need to make sure that whoever created the documentation is still around, to answer questions once you are done reading.\nThis also means you need to keep your product documentation up-to-date at all times. This can be a lot of work, especially when introducing new features or major changes in any part of your product/service. That is why it makes sense to have an automated system for this process.\nRequirements For Documentation\nEvery company is different, which means your documentation will vary greatly depending on the type of work you do. Here are some of the most common requirements:\nEvery team should be able to update articles whenever they want - no matter who wrote them in the first place. Tools like Notion make this super easy for your team.\nNew content should immediately appear on the page of all users (employees and customers) that use that article.\nArticles should be tagged by employees according to their area/topic so that they can easily find what they need. This can also help QA teams monitor what topics are being discussed more often than others.\nAll content must remain professional at all times while having fun with it when possible.\nWhen it's time to scale, the automated system makes documentation more accessible for everyone. That way you can train new hires faster and spend less time updating information around your company. The benefits are clear:\ntools to scale and track\nNotion is a great place for your docs to live\nInternal Processes\nDepending on the type of business you run, your internal processes will vary greatly. But the main idea is to make documentation scalable by having it in a central location - no matter how many departments are involved in each process.\nFor example, when scaling up you might want to expose more access for employees or clients early on. You can do this with our knowledge base software by simply giving them access to articles related to their status, without having to give away too much information.\nThat way new hires can get an idea about how things work within your company right from the start while saving time that would have been spent on telling them everything individually - scaling fast never looked so good.\nYou can also tailor specific instructions based on teams or departments using our software. This way your QA team knows exactly where to go when they have questions, while the support team only has access to relevant articles.\nEvery company is different, which is why it's hard to give specific examples of internal processes that might be good for documentation - but here are some ideas anyway.\nClient onboarding process: The fastest way to get new clients started with your product. Or let them know how you can help them further if their needs change over time.\nKnowledge base: Every article in a centralized location helps people learn and understand what's going on behind the scenes at your company, no matter who wrote it originally.\nInternal communication: Our software gives every employee (at any level) the ability to update articles from within Slack, or whatever communication platform you use. This way you can make sure communication is up-to-date and accurate at all times.\nFinal Thoughts on Documentation\nTo finish off, here are some final pieces of advice when it comes to scaling your documentation in a startup environment:\nThe goal is to have the most up-to-date knowledge base in your industry, so your team and customers know they can trust you for anything.\nWhen introducing new articles, always think about how that change will impact other articles or processes used in your company. This way everyone stays on the same page at all times - perfect for scaling up.\nHaving any type of documentation will set you apart from other companies in your field - but making sure everything is automated makes you truly unique.\nDon’t be scared of documentation, even a simple document with a few paragraphs of a bunch of bullet points is better than no document at all!\n\\https://twitter.com/overquailified/status/1546628456112201728"

Read that again. This is what many founders say when asked about the most vital piece in their scaling processes. What has begun as an initial, quick way to get your first few customers, ends up being significant groundwork for continuous growth and scale - that gets amplified with time.

The shift from manual or micro-documented processes towards scalable workflows requires a complete shift in thinking: Documentation is not just dumping information into Word/Google Docs/Slack channel/something else, it's the act of carefully constructing instructions for people to use your product efficiently.

This can range from how you onboard new users through steps they need to take to use specific features - all the way down to why certain settings are applied and how to change them (yes, this is crucial for successful scaling).

However, documentation is often seen as an afterthought or a task delegated to the quality control department (often outsourced), and later on, it is primarily used by support (again, outsourced) if at all. Unfortunately, no one thinks about its value for growth/scaling - or even just customer happiness. Let's have a look at some numbers that prove how vital good documentation can be:

A study by Harvard Business Review states that reducing cycle time by just 5% increases a company's profit margin by 25-95%.

Customer surveys from Segment show that 39% of customers abandon a website because of bad support, and only 23.5% care about how good the product is (source: articles.segment.com/how-do-customers-really-feel).

The conclusion? Speed matters. And by speeding up tasks, you speed up your whole workflow - but this needs to be planned from the beginning.

Good documentation leads to happy users. This means fewer support issues which result in more time for scaling additional features and generating more revenue instead of covering basic user questions.

Having a well-structured knowledge base can lower a significant portion of costs from customer service as some questions are being answered automatically before they reach anyone at all.

The Return Of Investment (ROI) of implementing proper documentation enables you to handle around 30% more users/customers with the same amount of employees - even if data says so.

Creating good quality product documentation is getting easier all the time with tools like Zendesk and Intercom. Start small, iterate, and treat your docs as living and growing organisms.

General Documentation vs. Product-Specific

Why do you need both, and what makes the difference between good documentation and bad one? Let's get started with general documentation: these are handbooks that every company has to build before even thinking about scaling (and not just startups). They include procedures for employees on how to deal with specific issues - like using Excel or creating invoices.

The rule of thumb is: If it can be easily copied, don't write a manual.

Imagine your new employee has never worked with Excel before. What would you rather tell them: "Go Google something, I'm busy right now."; or send them a link to an article that shows them step-by-step how to use it within your company's context? In this case, a good rule of thumb is: If it can be found on Google, don't write a manual.

The good news is that tools use standardized processes to generate knowledge base articles which are constantly being improved by employees and customers alike. That way, what employees type into the system is immediately reflected in the user interface as a new article for users - no wasting time, no bad information.

Overall leads to less frustration from both sides and speeds upscaling they never have even dreamed of before. On top of that, it comes without any automated training costs - so you save money there as well. In most cases they wouldn't even need to spend their time typing stuff into Google - and they would not get the user interface that makes it easy to use our product.

Startups are different from bigger companies. It is worth building your product documentation with that in mind. Let's have a look at the differences: Smaller teams often work on more than one project or product at once - especially when they are scaling fast. This means everyone has to know everything about all products, big time saver.

They usually don't have dedicated people for quality assurance (QA). Onboarding new employees become critical as it saves them time by having 100% accurate information on how things work within the company. Most of the communication happens over Slack, email, chat apps, etc., which means nobody reads manuals anymore.

https://twitter.com/xjamundx/status/1484291717868056577

And documentation becomes really important again. Because of this, you need to make sure that whoever created the documentation is still around, to answer questions once you are done reading.

This also means you need to keep your product documentation up-to-date at all times. This can be a lot of work, especially when introducing new features or major changes in any part of your product/service. That is why it makes sense to have an automated system for this process.

Every company is different, which means your documentation will vary greatly depending on the type of work you do. Here are some of the most common requirements:

Every team should be able to update articles whenever they want - no matter who wrote them in the first place. Tools like Notion make this super easy for your team.

New content should immediately appear on the page of all users (employees and customers) that use that article.

Articles should be tagged by employees according to their area/topic so that they can easily find what they need. This can also help QA teams monitor what topics are being discussed more often than others.

All content must remain professional at all times while having fun with it when possible.

When it's time to scale, the automated system makes documentation more accessible for everyone. That way you can train new hires faster and spend less time updating information around your company. The benefits are clear:

Notion is a great place for your docs to live

Depending on the type of business you run, your internal processes will vary greatly. But the main idea is to make documentation scalable by having it in a central location - no matter how many departments are involved in each process.

For example, when scaling up you might want to expose more access for employees or clients early on. You can do this with our knowledge base software by simply giving them access to articles related to their status, without having to give away too much information.

That way new hires can get an idea about how things work within your company right from the start while saving time that would have been spent on telling them everything individually - scaling fast never looked so good.

You can also tailor specific instructions based on teams or departments using our software. This way your QA team knows exactly where to go when they have questions, while the support team only has access to relevant articles.

Every company is different, which is why it's hard to give specific examples of internal processes that might be good for documentation - but here are some ideas anyway.

Client onboarding process: The fastest way to get new clients started with your product. Or let them know how you can help them further if their needs change over time.

Knowledge base: Every article in a centralized location helps people learn and understand what's going on behind the scenes at your company, no matter who wrote it originally.

Internal communication: Our software gives every employee (at any level) the ability to update articles from within Slack, or whatever communication platform you use. This way you can make sure communication is up-to-date and accurate at all times.

To finish off, here are some final pieces of advice when it comes to scaling your documentation in a startup environment:

The goal is to have the most up-to-date knowledge base in your industry, so your team and customers know they can trust you for anything.

When introducing new articles, always think about how that change will impact other articles or processes used in your company. This way everyone stays on the same page at all times - perfect for scaling up.

Having any type of documentation will set you apart from other companies in your field - but making sure everything is automated makes you truly unique.

Don’t be scared of documentation, even a simple document with a few paragraphs of a bunch of bullet points is better than no document at all!

https://twitter.com/overquailified/status/1546628456112201728

\https://twitter.com/overquailified/status/1546628456112201728

Documentation: The Secret Weapon of Successful Startups


<p><em class="italic"><strong class="font-bold">Documentation is</strong></em><a href="https://gigaom.com/2008/04/08/10-reasons-why-documentation-is-a-startup-secret-sauce/" target="_blank" rel="noopener noreferrer"><em class="italic"><strong class="font-bold"> </strong></em><u><em class="italic"><strong class="font-bold">key to product success</strong></em></u></a><em class="italic"><strong class="font-bold">.</strong></em></p>
<p>Read that again. This is what many founders say when asked about the most vital piece in their scaling processes. What has begun as an initial, quick way to get your first few customers, ends up being significant groundwork for continuous growth and scale - that gets amplified with time.</p>
<p>The shift from manual or micro-documented processes towards scalable workflows requires a complete shift in thinking: Documentation is not just dumping information into Word/Google Docs/Slack channel/something else, it's the act of carefully constructing instructions for people to use your product efficiently.</p>
<p>This can range from how you onboard new users through steps they need to take to use specific features - all the way down to why certain settings are applied and how to change them (yes, this is crucial for successful scaling).</p>
<h2><strong class="font-bold">The Secret Weapon of Successful Startups</strong></h2>
<p>However, documentation is often seen as an afterthought or a task delegated to the quality control department (often outsourced), and later on, it is primarily used by support (again, outsourced) if at all. Unfortunately, no one thinks about its value for growth/scaling - or even just customer happiness. Let's have a look at some numbers that prove how vital good documentation can be:</p>
<p>A study by Harvard Business Review states that <a href="https://hbr.org/1988/11/fast-cycle-capability-for-competitive-power" target="_blank" rel="noopener noreferrer"><u>reducing cycle time</u></a> by just 5% increases a company's profit margin by 25-95%.</p>
<p>Customer surveys from Segment show that 39% of customers abandon a website because of bad support, and only 23.5% care about how good the product is (source: articles.segment.com/how-do-customers-really-feel).</p>
<p>The conclusion? Speed matters. And by speeding up tasks, you speed up your whole workflow - but this needs to be planned from the beginning.</p>
<h2><strong class="font-bold">Why Product Documentation?</strong></h2>
<p>Good documentation leads to happy users. This means fewer support issues which result in more time for scaling additional features and generating more revenue instead of covering basic user questions.</p>
<p>Having a well-structured knowledge base can lower a significant portion of costs from customer service as some questions are being answered automatically before they reach anyone at all.</p>
<p>The Return Of Investment (ROI) of implementing proper documentation enables you to handle around 30% more users/customers with the same amount of employees - even if data says so.</p>
<p>Creating good quality product documentation is getting easier all the time with tools like Zendesk and Intercom. Start small, iterate, and treat your docs as living and growing organisms.</p>

          <figure style="position: relative; margin: 2rem auto; width: 100%; max-width: 1000px">
            <div style="height: 0; margin: 0 0 0.5rem; padding-bottom: 72.72727272727273%; width: 100%;"></div>
            <div id="fk3k7" class="article-image" style="bottom: 0; left: 0; position: absolute; right: 0; top: 0;" data-alt="using zendesk as a tool to scale" data-src="https://d19d9m2dcgrxq7.cloudfront.net/tools-to-scale.png" data-key="fk3k7"></div>
            <figcaption style="text-align: center; font-size: 0.9rem;" class="text-gray-500">using zendesk as a tool to scale</figcaption>
          </figure>
        
<h2><strong class="font-bold">General Documentation vs. Product-Specific</strong></h2>
<p>Why do you need both, and what makes the difference between good documentation and bad one? Let's get started with general documentation: these are handbooks that every company has to build before even thinking about scaling (and not just startups). They include procedures for employees on how to deal with specific issues - like using Excel or creating invoices.</p>
<blockquote>The rule of thumb is: If it can be easily copied, don't write a manual.</blockquote>
<p>Imagine your new employee has never worked with Excel before. What would you rather tell them: "Go Google something, I'm busy right now."; or send them a link to an article that shows them step-by-step how to use it within your company's context? In this case, a good rule of thumb is: If it can be found on Google, don't write a manual.</p>
<p>The good news is that tools use standardized processes to generate knowledge base articles which are constantly being improved by employees and customers alike. That way, what employees type into the system is immediately reflected in the user interface as a new article for users - no wasting time, no bad information.</p>
<p>Overall leads to less frustration from both sides and speeds upscaling they never have even dreamed of before. On top of that, it comes without any automated training costs - so you save money there as well. In most cases they wouldn't even need to spend their time typing stuff into Google - and they would not get the user interface that makes it easy to use our product.</p>
<h3><strong class="font-bold">Product-Specific Documentation</strong></h3>
<p>Startups are different from bigger companies. It is worth building your product documentation with that in mind. Let's have a look at the differences: Smaller teams often work on more than one project or product at once - especially when they are scaling fast. This means everyone has to know everything about all products, big time saver.</p>
<p>They usually don't have dedicated people for quality assurance (QA). Onboarding new employees become critical as it saves them time by having 100% accurate information on how things work within the company. Most of the communication happens over Slack, email, chat apps, etc., which means nobody reads manuals anymore.</p>

          <div style="display: flex; justify-content: center;">
            <blockquote class="twitter-tweet"><p lang="en" dir="ltr">One of the most impactful things I&#39;ve seen as a developer advocate has been carefully documenting the end to end experience for a specific developer use case and presenting them to the product/documentation teams with all sorts of screenshots, videos, etc.</p>&mdash; Jamund Ferguson (@xjamundx) <a href="https://twitter.com/xjamundx/status/1484291717868056577?ref_src=twsrc%5Etfw">January 20, 2022</a></blockquote>

          </div>
        
<p><br></p>
<p>And documentation becomes really important again. Because of this, you need to make sure that whoever created the documentation is still around, to answer questions once you are done reading.</p>
<p>This also means you need to keep your product documentation up-to-date at all times. This can be a lot of work, especially when introducing new features or major changes in any part of your product/service. That is why it makes sense to have an automated system for this process.</p>
<h2><strong class="font-bold">Requirements For Documentation</strong></h2>
<p>Every company is different, which means your documentation will vary greatly depending on the type of work you do. Here are some of the most common requirements:</p>
<ul>
  <li>Every team should be able to update articles whenever they want - no matter who wrote them in the first place. Tools like Notion make this super easy for your team.</li>
  <li>New content should immediately appear on the page of all users (employees and customers) that use that article.</li>
  <li>Articles should be tagged by employees according to their area/topic so that they can easily find what they need. This can also help QA teams monitor what topics are being discussed more often than others.</li>
  <li>All content must remain professional at all times while having fun with it when possible.</li>
</ul>
<p>When it's time to scale, the automated system makes documentation more accessible for everyone. That way you can train new hires faster and spend less time updating information around your company. The benefits are clear:</p>

          <figure style="position: relative; margin: 2rem auto; width: 100%; max-width: 1000.0000000000001px">
            <div style="height: 0; margin: 0 0 0.5rem; padding-bottom: 62.499999999999986%; width: 100%;"></div>
            <div id="3nhm1" class="article-image" style="bottom: 0; left: 0; position: absolute; right: 0; top: 0;" data-alt="tools to scale and track" data-src="https://d19d9m2dcgrxq7.cloudfront.net/notion-tools-to-scale.png" data-key="3nhm1"></div>
            <figcaption style="text-align: center; font-size: 0.9rem;" class="text-gray-500">tools to scale and track</figcaption>
          </figure>
        
<blockquote><strong class="font-bold">Notion is a great place for your docs to live</strong></blockquote>
<h2><strong class="font-bold">Internal Processes</strong></h2>
<p>Depending on the type of business you run, your internal processes will vary greatly. But the main idea is to make documentation scalable by having it in a central location - no matter how many departments are involved in each process.</p>
<p>For example, when scaling up you might want to expose more access for employees or clients early on. You can do this with our knowledge base software by simply giving them access to articles related to their status, without having to give away too much information.</p>
<p>That way new hires can get an idea about how things work within your company right from the start while saving time that would have been spent on telling them everything individually - scaling fast never looked so good.</p>
<p>You can also tailor specific instructions based on teams or departments using our software. This way your QA team knows exactly where to go when they have questions, while the support team only has access to relevant articles.</p>
<p>Every company is different, which is why it's hard to give specific examples of internal processes that might be good for documentation - but here are some ideas anyway.</p>
<ol>
  <li>Client onboarding process: The fastest way to get new clients started with your product. Or let them know how you can help them further if their needs change over time.</li>
  <li>Knowledge base: Every article in a centralized location helps people learn and understand what's going on behind the scenes at your company, no matter who wrote it originally.</li>
  <li>Internal communication: Our software gives every employee (at any level) the ability to update articles from within Slack, or whatever communication platform you use. This way you can make sure communication is up-to-date and accurate at all times.</li>
</ol>
<h2><strong class="font-bold">Final Thoughts on Documentation</strong></h2>
<p>To finish off, here are some final pieces of advice when it comes to scaling your documentation in a startup environment:</p>
<p>The goal is to have the most up-to-date knowledge base in your industry, so your team and customers know they can trust you for anything.</p>
<p>When introducing new articles, always think about how that change will impact other articles or processes used in your company. This way everyone stays on the same page at all times - perfect for scaling up.</p>
<p>Having any type of documentation will set you apart from other companies in your field - but making sure everything is automated makes you truly unique.</p>
<p>Don’t be scared of documentation, even a simple document with a few paragraphs of a bunch of bullet points is better than no document at all!</p>

          <div style="display: flex; justify-content: center;">
            <blockquote class="twitter-tweet"><p lang="en" dir="ltr">Once again thinking about the importance of good documentation. Having solid outlines &amp; story bibles really makes a difference - not initially having that on the Arcana caused major problems, while having it on Last Legacy and Destiny has helped me jump right into writing.</p>&mdash; Lynne (@overquailified) <a href="https://twitter.com/overquailified/status/1546628456112201728?ref_src=twsrc%5Etfw">July 11, 2022</a></blockquote>

          </div>

Documentation: The Secret Weapon of Successful Startups

Subscribe to Engineer.at and keep growing as an engineering manager.

Related content

Information Architecture, Your Support Buddy To Keep Everything Organized

How Google Uses Mindfulness For Success

Tips For Motivating Your Development Team