| www.bacollective.com No one likes to read documentation. And who can blame them. When is the last time you picked up a user manual? Its probably been awhile. No one even prints documentation anymore. You can maybe find an odd PDF file here or there, and then you have two choices you can print it out and kill a few trees at your own expense, or you can read it online. Most people dont do either. When people dont read documentation, its as much a reflection on the writer as it is on the reader. Thats where the Business Analyst comes in. The Business Analyst is a bi-lingual communicator. The BA speaks the language of Business and of Technology. And each language has many dialects, colloquialisms, and subtle slang in its vernacular. When the BA writes documentation, it needs to command not only the attention, but the respect of its audience. Here are three things to consider when developing documentation as a Business Analyst. First, balance Documentation Style and Substance * Well-written documentation, formatted and laid-out poorly, is not well-written documentation. * Know your audience. Who are you writing for? * Also, usability isnt just for software; its for documentation, too. Create great documentation that is easy to read. * And remember Re-usability is as important as usability. * Last, if your company/project/SDLC doesnt have a Style Guide, create one. A second suggestion is to use Microsoft Word to its Full Potential * Know the basic controls for properly ... |
