The podcast by project managers for project managers. Will your project’s documentation pass the test of time once the project is done and the people are gone? Documentation is at the intersection of information management, organizational design, and personal productivity. Accurate documentation makes teams more efficient and effective.
Table of Contents
01:23 … Essential Project Documents03:43 … Defining Information Management04:34 … Adrienne’s Story05:59 … Performing an Information Audit09:19 … Signs Your System is Out of Control11:33 … Dynamic Documentation12:44 … Improve Your Documentation15:19 … Budget for Closing Documentation16:57 … Finding the Right Balance19:12 … Kevin and Kyle20:27 … Strategies for Meeting Notes23:49 … Have a System25:54 … Getting Everyone Onboard27:25 … Documentation No-Nos30:06 … Personal Productivity31:06 … “The 24-Hour Rule”31:41 … Contact Adrienne32:43 … Closing
ADRIENNE BELLEHUMEUR: I actually say documentation is at the intersection of information management, organizational design, and personal productivity. So documentation kind of underpins these three major disciplines, but the personal productivity is often forgotten.
WENDY GROUNDS: Welcome to Manage This, the podcast by project managers for project managers. My name is Wendy Grounds, and with me in the studio is Bill Yates and Danny Brewer. We’re talking today to Adrienne Bellehumeur, and she is the founder of Bellehumeur Company and co-partner of Risk Oversight. She’s based in Calgary, Alberta. She’s also an expert on productivity, documentation, governance, risk, and compliance; and has delivered 15 years’ experience as an auditor, accountant, analyst, problem solver, and independent consultant.
Adrienne developed a documentation approach called “dynamic documentation,” and she’s a published author of the book “The 24 Hour Rule,” and she’s going to tell us more about that book, as well.
Adrienne likes to talk about processes, tools, and methods, and some of the best strategies to use to maintain effective, efficient, and timely documentation. So as you may have gathered, we’re talking about documentation and information management. So Bill, my question to you is what are some essential project documents that project managers should be maintaining?
Essential Project Documents
BILL YATES: Oh boy, the list goes on and on. They’re all essential, every one of them. Let me start with the legal stuff first. I think project managers who’ve ever done work with, either with outside contractors or their customers, an external customer, they would agree anything related to contracts, addendums, agreements, even the email threads where those may have been negotiated or key decisions were made, those should be considered mandatory. You’ve got to have those backed up. They can’t just be living on your hard drive. They need to be backed up. Also things like the project charter, anything with signatures that gives authority to the project.
And then kind of going down the list, there’s scope things like requirements, scope statement, the product roadmap, the backlog, change requests, logs that keep up with things, task lists, or issue logs. These are dynamic. These need to live. So you have to document them almost with a date stamp on them. That’s true with a risk log or risk register, as well. Major communications, major rollouts, maybe you hit a milestone or something significant, you want to keep those documents. Think about, okay, could someone who doesn’t know anything about this project take a look at it six months, two years later and go, “Oh, okay. Yeah, I get it. I see why you guys made that decision. I see who was involved in it and then what action took place after.”
And then one of the biggest challenges, and I think we’ll hear this from Adrienne as well, when you’re getting ready to wrap up your project, that is one of the most difficult times to make sure that you’re doing good docum...