Release Notes: how to validate technical accuracy

You can validate the accuracy of your release note by creating a checklist and reviewing each item on the list until you know these by heart: Files affected Have you entered the files for its related product? For example, some DLLs may affect one version but not another. Make sure these are not entered by […]

Release Notes: how to test technical accuracy

Grasshopper, what do you after you’ve written your release notes? Test it. Here are four ways to check if the bugs, issues and enhancements are written correctly: 1. Can you reproduce the issue? Have you reproduced the issue on a local machine? Note that you’ll need the same version of the application that the bug […]

[Checklist] Release Notes: 7 Don’ts and 13 Do’s

If your technical writing job involves writing release notes, create checklists for writing, reviewing, and production. Use the following checklist to review release notes. Avoid the following mistakes when writing release notes. When – use if instead use when. The difference between when and if is that when implies something has occurred, for example, when […]

Release Notes: 7 Steps to Better Enhancements

Want to improve the quality of the enhancements in your Release Notes? Here are seven ways. Enhancement Identifier Provide the reference number for the enhancement, such as Salesforce 12345. Business value Describe the benefit to the user if they use this enhancement. Usually, there is a specific business driver or customer request behind each enhancement’s […]

How to write documents for SaaS web applications

SaaS and web-based applications are becoming more popular as they replace desktop or network installations. How you document them is mostly the same as documenting traditional but there are some difference. Let’s take a look. Registration – explain how to set up the account, register an account, common setup issues, and troubleshooting, for example, if […]

How to write Enhancements for Release Notes

What do you need to include in your enhancement release notes? At a minimum, you need to cover the following: Description – identify the new enhancement. Avoid the words new, enhancement, or feature in the title. You can drop these words as it’s implied that it’s an enhancement as it’s in the Enhancement section of […]

Release Notes: Sample Text for Writing Enhancements

An enhancement is a new feature, or an improvement to a current feature, included in the current release. To help the reader understand the enhancement, describe: Where the enhancement is located in the user interface. What parameters need to be configured. What is the default setting. Why you should use this enhancement, for example, a […]

Release Notes: 13 Mistakes to Avoid

It’s easy to overlook the importance of release notes. But when customers want to know exactly what a specific parameter does, it’s the release notes that often turn too. Why? Remember, for very large document sets, it can hard to know which document contains the reference material you need to understand. For this reason, configuration […]

Using Google Plus to Write Technical Documents

Maeve asks on LinkedIn how we can use Google Wave to write technical documents. Well, the first consideration is that Google Wave is not designed as a tech authoring tool but for collaboration and ‘almost’ real-time information exchange. Saying that, it does offer many benefits if you need to plan/coordinate/review documents in a networked environment. Here are some ideas.