By studying the organization chart, the analyst can confidently schedule interviews with key personnel involved with the system. Of course, there should be preliminary interviews. Later he will conduct a detailed interview with all the people who actually operate the system. Not only will these people use the newly developed system, but they also may be the ones most afraid of change, especially if they feel the computer might replace them. Like an investigative reporter trying to discover the who, what, -when, why and how of a story, the analyst should conduct the interview in such a way that people provide honest descriptions of their jobs. The following questions can help accomplish this goal.
- Who is involved with what you do?
- What do you do?
- Where do you do it?
- When do you do it?
- Why do you do it the way you do?
- How do you do it?
- Do you have suggestions for change?
Interviews help gather vital facts about existing problems, such as lack of quality control or sufficient security, but they also allow the analyst to involve people in change, easing them into it. After all, it is the users’ system, not the analyst’s,
The interview is the prithary technique for information gathering during the systems analysis phases of a development project. It is a skill which must be mastered by every analyst. The interviewing skills of the analyst determine what information is gathered, and the quality and depth of that information. Interviewing, observation, and research are the primary tools of the analyst.