{"id":3218,"date":"2020-06-02T04:00:01","date_gmt":"2020-06-02T04:00:01","guid":{"rendered":"https:\/\/blog.hassler.ec\/wp\/?p=3218"},"modified":"2020-05-15T22:02:17","modified_gmt":"2020-05-15T22:02:17","slug":"how-to-write-a-technical-documentation-plan","status":"publish","type":"post","link":"https:\/\/blog.hassler.ec\/wp\/2020\/06\/02\/how-to-write-a-technical-documentation-plan\/","title":{"rendered":"How to Write a Technical Documentation Plan"},"content":{"rendered":"
\n
\n
\n
<\/div>\n<\/div>\n

\n<\/div>\n<\/div>\n

\n
\n
\n
\n
<\/div>\n

<\/div>\n<\/div>\n<\/figure>\n<\/div>\n

\n
\n

There are strong reasons for having a documentation plan. The main one being \u2014 setting up a clear and open help authoring process. Creating a documentation plan means giving every team member an exhaustive reference point. The whole team will act within the guidelines of the plan and that ensures consistency and efficiency.<\/p>\n

\n
\n
\n
\n
<\/div>\n

<\/div>\n<\/div>\n<\/div>\n<\/figure>\n

Structure of a Documentation Plan<\/h1>\n
\n
\n
\n
\n
<\/div>\n

<\/div>\n<\/div>\n<\/div>\n<\/figure>\n

There\u2019s no strict rule defining how detailed the plan needs to be, but if you really want people to use it, make sure it is well-structured and easy-to-navigate. Do not overwhelm your technical writers \u2014 first of all this document should be easy to apply.<\/p>\n

How you structure it depends on specifics of your tasks, of course. It can be product-based, role-based, area-based. But there is a certain structure that is preserved in most of the successful documentation plans, we will talk about that in a bit. Also, we will provide you with the tips of what data to include in a documentation plan.<\/p>\n

A documentation plan is a bit like a user manual in itself, so you will find a lot of similarities with general technical writing. It should be\u00a0logically structured<\/strong>. No need to go crazy and create a documentation plan for a documentation plan, but the least you can do is make sure the information is easy to find. For this, use your favorite\u00a0navigation elements<\/strong><\/a>. We recommend using a TOC for sure. Cross-referencing, breadcrumbs, next\/previous article links would be great, too, but it initially depends on the format you\u2019ve chosen for the documentation plan. Some tech writers fit all the info inside one long document with a TOC being the primary means of navigation. This might work well for some, but we believe that creating a documentation plan using a\u00a0help authoring tool<\/strong><\/a>\u00a0just like you would do for any user manual works best. All the functionality like navigation elements is already there and you can apply your own best practices to documentation plan creation.<\/p>\n

Content of a Documentation Plan<\/h1>\n
\n
\n
\n
\n
<\/div>\n

<\/div>\n<\/div>\n<\/div>\n<\/figure>\n

Since a documentation plan is also a way to align your goals with actions, it all starts with writing the\u00a0goals and objectives<\/strong>\u00a0of the project down. They are going to define everything that will be happening further on.<\/p>\n

No documentation plan can exist without a thorough\u00a0content plan<\/strong>. It gives a great bird\u2019s view of the user manual you are set to create. And, maybe, you will get ideas on how to improve it before the production starts. Of course, before starting a project, there are always\u00a0time frames<\/strong>\u00a0\u2014 this is the next important thing to include.<\/p>\n

When we have an understanding of what to do, it is time to mention the\u00a0responsible people<\/strong>. Make this list detailed if you wish by explicitly describing roles and responsibilities. How these people communicate with each other and outer teams, what the processes are \u2014 should be added in the form of a\u00a0workflow<\/strong>\u00a0description.<\/p>\n

Now, it is time to define the\u00a0tools and resources<\/strong>\u00a0your team is going to use in the process. Add a list of software, websites, and services needed to fulfill the task. If you have a separate\u00a0style guide<\/strong>, you can simply reference it. Or, add a section about design-related things like fonts and font families, colors, page layouts, picture sizes, etc. And, of course, don\u2019t forget to mention what the result of all this work should be. This includes\u00a0types of outputs<\/strong>,\u00a0their formats<\/strong>.<\/p>\n

Anything you deem important can be included. You can set a desirable readability score for topics, average topic lengths, etc. While the core of a documentation plan should remain static, feel free to work on details if the reality dictates that some things should be added.<\/p>\n

Conclusion<\/h1>\n

Having a documentation plan means standing on solid ground. Your entire team will have amazing reference material which is so helpful for a project of any size.<\/p>\n

Documentation plans are extremely helpful when you start something new or before a major iteration of a documentation project. Do you use\u00a0documentation plans<\/a>\u00a0How detailed do you make them? Let us know in the comments below.<\/p>\n

Good luck with your technical writing!
\nClickHelp Team<\/a>
\nAuthor, host and deliver documentation across platforms and devices<\/p>\n

\n
\n
\n
\n
<\/div>\n

<\/div>\n<\/div>\n<\/div>\n<\/figure>\n<\/div>\n<\/div>\n

<\/div>\n
<\/div>\n
<\/div>\n
\n
<\/div>\n
<\/div>\n
\n

\n

Source: https:\/\/medium.com\/level-up-web\/how-to-write-a-technical-documentation-plan-bf4570807f69 <\/a><\/strong><\/p>\n

\n

Written by<\/strong><\/p>\n

\"ClickHelp\"<\/a>ClickHelp<\/a><\/div>\n
\n
\n

ClickHelp – Professional Online Technical Writing Tool. Check it out: https:\/\/clickhelp.com\/online-documentation-tool\/<\/a><\/h4>\n<\/div>\n<\/div>\n

 <\/p>\n

 <\/p>\n<\/div>\n

 <\/p>\n

 <\/p>\n<\/div>\n

<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"

There are strong reasons for having a documentation plan. The main one being \u2014 setting up a clear and open […]<\/p>\n","protected":false},"author":2,"featured_media":3220,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[12,128,47,21,40],"tags":[161],"class_list":["post-3218","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bloghassler-ec","category-clickhelp","category-medium","category-productividad","category-technical-writer","tag-click-help"],"_links":{"self":[{"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/posts\/3218","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/comments?post=3218"}],"version-history":[{"count":1,"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/posts\/3218\/revisions"}],"predecessor-version":[{"id":3221,"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/posts\/3218\/revisions\/3221"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/media\/3220"}],"wp:attachment":[{"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/media?parent=3218"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/categories?post=3218"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hassler.ec\/wp\/wp-json\/wp\/v2\/tags?post=3218"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}