An effective, direct person-to-person interviewing technique requires that you have prepared a list of questions designed to gain an understanding of the real problems and potential solutions. To get as unbiased answers as possible, you need to make sure the questions you ask are context-free. The context-free question is a high-level, abstract question that can be posed early in a project to obtain information about global properties of the user's problem and potential solutions.

A context-free question is:

  • Always appropriate.
  • Formulated so that it helps you understand stakeholder perspectives.
  • Not biased with solutions knowledge or your opinion of what the solution should be.

Context-Free Interview Script: Great opportunities exist in our industry to improve application development efforts. Understanding stakeholder or user needs before beginning development is crucial to improving this process. Many techniques are available to elicit stakeholder or user needs. One simple and inexpensive technique that is appropriate for use in virtually every situation is the Generic Interview. The Generic Interview can help the developer or analyst understand stakeholder or user objectives and problems. Armed with this insight, developers can create applications that fit the stakeholder or user's real needs and increase their satisfaction.

The Generic Interview in the supplied template for Artifact: Stakeholder Requests features questions designed to elicit an understanding of the stakeholder's or user's problems and environment. These questions explore the functionality, usability, reliability, performance and supportability requirements for the application. As a result of using the Generic Interview, the developer or analyst will gain knowledge of the problem being solved, as well as an understanding of the stakeholder or user's insights on the characteristics of successful solutions.

Guidelines for Use: If the Generic Interview is not suited to your needs, feel free to modify it. With a little preparation and a well-structured interview, any developer or analyst can interview effectively. Here are some hints:

  • Research the background of the stakeholder or user and the company ahead of time.
  • Review the questions prior to the interview.
  • Refer to the format during the interview to ensure the right questions are being asked.
  • Summarize the top two or three problems at the end of the interview.
  • Repeat what you learned to confirm your comprehension.

Do not let the script become overly constraining. Once rapport is established, the interview often takes on a life of its own, and the stakeholder or user may talk at length about the difficulties they're experiencing. Do not stop the stakeholder or user. Record these responses as quickly as possible. Follow up on the information with questions. Once this exchange reaches its logical end, proceed with other questions on the list.

Examples of context-free questions used to find actors:

  • Who is the customer?
  • Who is the user?
  • Are their needs different?
  • What are their backgrounds, capabilities, environments?

Examples of context-free questions that help you understand business processes:

  • What is the problem?
  • What is the reason for wanting to solve this problem?
  • Are there other reasons for wanting to solve this problem?
  • What is the value of a successful solution?
  • How do you solve the problem now?
  • What is the trade-off between time and value?
  • Where else can the solution to this problem be found?

Examples of context-free questions that help you understand requirements on the system or product to be built:

  • What problem does this product solve?
  • What business problems could this product create?
  • What hazards could exist for the user?
  • What environment will the product encounter?
  • What are your expectations for usability?
  • What are your expectations for reliability?
  • What performance/precision is required?

Examples of context-free meta questions:

  • Am I asking too many questions?
  • Do my questions seem relevant?
  • Are you the right person to answer these questions?
  • Are your answers requirements?
  • Can I ask more questions later?
  • Would you be willing to participate in a requirements review?
  • Is there anything else I should be asking you?

Examples of non-context-free questions are:

  • Leading questions: "You need a larger screen, don't you?"
  • Self answering questions: "Are fifty items about right?"
  • Controlling statements: "Can we get back to my questions?"
  • Too long and too complex: "I have a three part question, ..."

When you formulate a set of questions, you also should consider the following:

  • Don't ask people to describe things they don't usually describe.
  • Don't ask questions that assume that users can describe complex activities. Example: tying your shoelace.
  • In general, people can do many things they cannot describe.
  • Empirical evidence - poor correlation.
  • Ask open-ended questions.
  • Avoid questions that begin with "Why?", since such questions can provoke a defensive posture.

When you conduct an interview session, remember:

  • Don't expect simple answers.
  • Don't rush the interviewee for answers.
  • Listen, listen, listen!


© Copyright IBM Corp. 1987, 2004. All Rights Reserved.

Rational Unified Process   2003.06.13