Asking Great Questions
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
Development
Additional Resources



White Papers & Webcasts
Extend, Replace, or Convert; which is the best way forward for COBOL Applications?
Download this white paper, free, compliments of Micro Focus!
Data in Action: Making the Planet Smarter
Register Now
Oracle Accelerate - Not Just Smart but Timely
Download Now!
Why BI is Ripe - Now! - For Businesses of Any Size
Download Now!
The Workday User Experience Video
Watch Workday's Creative Director, Scott Lietzke, discuss the business-centered design philosophy at Workday.
Business Process Framework Demo
Learn about Configurable Business Processes and Calculated Fields. Watch Now!
Rapid Implementation: The New Age of ERP
Download Now!
Manager Experience Demo
Go beyond self-service solutions to perform more effectively. Watch Now.

