Ads by TechWords

See your link here
Receive the latest technology news and information.
Application/Web Development
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
Cloud Computing
View all newsletters




Privacy Policy
 

Asking Great Questions

November 5, 2004 12:00 PM ET

Computerworld - Ever been in a situation where you wanted more information, but couldn't quite figure out how to ask the question? Whether you're eliciting requirements, interviewing vendors, interviewing candidates for a job, deciding who you want on a project team, or just asking your family about their day, you're asking questions and wanting to hear answers.

Imagine if you were interviewing a vendor and asked, "Can you walk me through an example of how that reference account implemented this software?" Or, imagine if you were a candidate for a job but your interviewer wasn't very skilled -- by answering the question the interviewer should have asked, you look like a powerful and suitable candidate.

Selecting the right questions for the situation is a challenge. Questioners can choose from: closed, open-ended (context-free and behavior-description), hypothetical, meta and rhetorical questions, and auditions, to elicit the answers. Here are some techniques to choosing questions.

Closed questions establish the boundaries for the rest of your questions. Use closed questions such as "How many years of Java experience do you have?" or "How many systems have you installed vs. sold?" to establish the boundaries of what the person (or vendor) has done.

Open-ended questions explore how a person wants work performed or performs work. If you use context-free questions such as, "What does success look like?" you can understand what a senior manager wants out of this project. If you use a behavior-description question such as, "Tell me about the most challenging problem on your most recent project," you'll learn what challenge means to a candidate.

Here's how I use context-free questions when starting a project. First, I ask, "What does success look like?" Sometimes, I hear an answer such as, "We released the software on June 15, so we could count revenue for the second quarter." Sometimes, I hear this: "The project team is still intact." Other times, I hear an answer such as, "Finance has the tools to do its job before the end of the year."

I then ask


  • Why are these results desirable?

  • What is the solution worth?

  • What problems does this system solve?

  • What problems could this system create?



Armed with the resulting answers, I can define success for the project. With a definition of success, I can select a life cycle and suitable project activities, and define release criteria to create a project that has more than just a prayer of being successful.

Behavior-description questions help you differentiate the talkers from the doers. Behavior-description questions are of the form "Tell me about a time


Jump to comments

Development

Additional Resources

WHITE PAPER
Approximately 60 percent of data migration projects overrun time or budget, while some fail completely. Download this white paper, "Enhancing Your Chance for Successful Data Migration," to learn the critical steps you need to take to execute a data migration project with minimum cost and risk to your business.
WHITE PAPER
Read the Gartner research note to learn why the TCO of a server-based computing deployment used to deliver all applications to users is around 50% lower than that of an unmanaged desktop deployment.
WHITE PAPER
Economic downturns have a tendency to accelerate emerging technologies, boost the adoption of effective solutions, and punish solutions that are not cost competitive or that are out of synch with industry trends. This IDC White Paper presents the results of an IDC survey of 330 companies in Western Europe, Asia/Pacific and the Americas that measures the receptiveness to Linux and takes into consideration changing views driven by the disruptive economic environment that businesses face today.