Process interviewing is the fastest way to glean pertinent information about a system. See the nine ways people will try to derail interviews and a solution for each. There are a few things that can go wrong before the interview, during meetings and in gaining sign-off on the completed model.
Here are the top nine interviewing problems.
- Stalling – can’t get an appointment
Everyone is busy, but some people can milk “I’m busy” for days. Test their availability by using the (1—3—All) technique. Start by suggesting a specific time, if that does not work then suggest three alternate times. If they decline the alternate times, tell them that you will open your schedule (which includes before work, at lunch, and after work). If they hesitate, you can be pretty certain that it is not really about how busy they are. They have probably “gotten the wrong message” or no message at all. They are worried about what this project will mean to their department, team or even their job.- If they have gotten the wrong message, ask them if you can have ten minutes to show them what you are doing. Go to their desk with your laptop and show them a process. You may want to bring up a demonstration file, and show them how it works. Help them to understand that you will be doing the same thing for their process. The vast majority of the time they will become enamored with the idea that they can participate in the change process and set an interview time. If this doesn’t work, you are going to have to pull rank, because somebody didn’t get the message that everyone was supposed to cooperate. Go to the senior manager (or the designated appointee) and have the manager get the “message” out to the right people. An interview under duress is not ideal, but it is better than no information.
- Defensiveness
When an interviewee takes offense or exception to questions asked about their process, it’s because they believe it’s not in their best interest. For example, if an interviewee thinks that the process improvement effort is about downsizing and it isn’t, then you will need to make a case for why the project is vital to them, the customer and the company.
In some cases, they may have good reason to be defensive. The process may show “they” are the bottleneck. Follow the procedure of isolating one ‘entity” type at a time and gather what information you can. You may need “back into” some of the information by talking to the groups that feed them entities and to the groups they supply. This technique is not a preferred method of collecting process information but may be your only source.
- Too many cooks in the kitchen
Some groups will want the whole team to participate in the interview. They will say “we can get a better representation of what happens if we have everyone’s input” or “let’s get it over all at once by having everyone (or a subgroup) participate.” There are no conditions where it is advisable to have more than one person at a time in the interview. From experience, we have found that it will take longer and your product will not be any better if you interview multiple people at the same time. What usually happens is that people that typically are confident will start to look to others for what happens. The group will debate, add activities, subtract activities and never come to any conclusion. A top consulting firm in the US discussed a process for an hour. At the end of the hour, they could only agree on one step. I have observed many similar situations. It doesn’t work well to interview many people at the same time.
- When placed in a situation where more than one person is in the room for an interview, do the kickoff portion of the meeting and then explain that you want to interview one at a time and you will provide information for the last discussion as a starting point for the next. Then promptly toss the extra people out of the room. Don’t go on until you have the room cleared.
- Micromanager
Sometime the supervisor or boss will want to sit in on the interview to “see how it’s done.” The problem this creates is that the process expert won’t talk freely about the process in front of the supervisor. The supervisor doesn’t want people outside their department to know that processes are not running as efficiently as possible – it would make them look bad. During the interview, a questioning glance, frown or glare can kill the flow of information. For these reasons, do not allow a supervisor to sit in on the interview. Use the same technique as mentioned in “Too Many Cooks in the Kitchen” to remove extra people from the room. If they want to see how “it’s done,” then have them sit in on an interview for an area that they are not in control of, and only if they agree to be a silent observer.
- Artificial tsunami – overload of information
- Sometimes the interviewee is so excited that someone is listening that they want to tell everything they know about the system. Every exception and circumstance is given in rapid-fire detail. Even slowing the interviewee down won’t completely solve this problem. If they don’t prioritize their knowledge, it is like a tsunami of information, indiscriminately washing over the interviewer. Not only is this difficult to comprehend, but it is also almost impossible to capture.
- At this juncture, it is a good time to compliment them on their knowledge and let them know that they are giving you all the right information, but you are having trouble digesting the detail. Explain that will need to capture the process differently so that it will help the team look for opportunities.
- After you have “constructed an information seawall” to stop the flood, retake control of the interview. Ask them to take a common “entity” and walk through the process for that specific entity. Once you have a framework for the process, then you can add additional products. Create the structure of the model that puts the most common process flow along the top of the model with less common streams being placed lower in the model.
- The history teacher
Everybody has stories and it is tempting to use the past to teach principles. Sometimes a lesson in history from the interviewee can cost you thirty minutes or more. Since you should keep an interview to less than an hour, you can’t afford to lose large chunks of time. You have to cut the history lesson short gently. You might say, “I wonder if we could save that story for a later time? I promised I would only keep you for an hour and I have the project manager pushing me hard to finish this critical interview.” Do whatever works for you, but don’t allow the interviewee to ramble. You can bring it back by talking about a specific entity…where does it go next, how long does it take to do that step.
- Everything is unique