There’s a classic line from the old television police drama Dragnet where Detective Sergeant Joe Friday (as played by Producer/Actor Jack Webb) tries to keep an eyewitness focused during the process of questioning. He exhorts her to provide: “Just the facts Ma’am…” instead of rambling on or locking up in response to his questions.
Joe Friday’s simple advice also applies to the drafting of Frequently Asked Questions (FAQ’s) about your big change project.
Today’s post is a primer on how to create the right FAQ’s and use them to get stakeholder communication for your change project off on the right foot. In later posts, I’ll get into the drafting and review process to make sure your FAQ’s have the kind of quality that yields results.
Stick to the Facts (or FAQ’s): As a part of ongoing communication with the people impacted by your change, it’s a good practice to ask and answer the questions that folks care most about. You don’t need to ramble on with all of the content that will be included in detailed communications or training, but it’s a good idea to share some basic stuff. That’s what FAQ’s are for.
Everyone’s busy… Imagine you had 2 or 3 minutes to address the top 5 or 6 things that most people would want to know about your change. What would you say? Start by answering these 6 simple FAQ’s which I’ve used on past change projects:
- What is the change?
- Why are we doing this?
- When is this all going to happen?
- What’s in it for me?
- What do you need me to do?
- Where do I go for help?
Of course you may need to write more FAQ’s based on the context and details of your change, but make sure to at least address these basic information needs. I’ve included tips on how to dig up more detailed items below.
There’s More Where That Came From: To get into the more involved FAQ’s, go explain the change to some of your stakeholders and ask them what they want to know more about. (Site visits are great for this) Then draft up the answers you gave – but consider the additional perspectives of the entire company and of each organizational unit.
Here are a few examples of FAQ-generating questions I’ve heard from field employees during site visits:
- Who’s most impacted?
- Who’s less involved?
- Who’s exempt from the change?
- What training is there going to be?
- What parts of the change are non-negotiable?
- What are we losing in this deal?
- What elements of the change are meant to standardize practices?
- Will some areas of the company be allowed to do things differently?
- What innovations are being implemented with the change?
- What’s going to stay exactly the same?
- What technology is involved?
- What have we done to account for the unique nature of operations within my business unit or location?
Closing Notes for Today: I have found that it’s a very good practice to share the answers to Frequently Asked Questions with your stakeholders as a big change approaches. There is no perfect number of FAQ’s – I have seen teams use as few as 4 or 5 or as many as several dozen. I have yet to see a project team that regretted the effort spent creating and sharing FAQ’s with their stakeholders so any number is probably better than doing nothing.
Once the most common FAQ’s have been answered for stakeholders, you’ll be well on your way to closing the case for your change. Tomorrow I’ll give you more tips on how to write good FAQ’s and how you can get them out there for the world to see.
Question for Chatter:
- What’s the risk we run with stakeholders if we don’t give them straight answers to common questions about our changes like the questions on my list above?