When you’re tasked to create a document, you have take good notes when talking to the developers, subject-matter experts, and users, especially if it’s in an area that you are not too familiar with. When I was working on this planning, programming, budgeting, and execution system, I took notes that I could use to produce the documentation that was needed.  If I didn’t understand something, I made sure to ask the person I was interviewing to break it down for me, so I could understand.  My philosophy was that if I couldn’t understand, then the reader probably wouldn’t.

Good note-taking is important because this will be your guide in developing documentation that is accurate and is what the client is looking for. You will usually talk to more than one person, so you have to be able to have records on everything that you discussed. There is no one way to write notes. It really depends on your preference.

I wrote this article about how to use the way you learn to find a note-taking process that works for you.

Written by: Shevonne on February 15, 2011.
Last revised by: Shevonne on March 21, 2011.

Tags: note writing, Notetaking, proposal writing, taking notes, technical writing