Define Your Question Before You Solve the Problem

The word why written on paper with pencil

To effectively solve problems, you must first understand the question being asked and why it’s important to your stakeholder. Without clarity on why your stakeholder cares, the recommendation you generate might be useless.

The following is an excerpt from my latest book The Elegant Pitch: Create a Compelling Recommendation, Build Broad Support, and Get it Approved (CLICK HERE to get your copy). The book spells out a straightforward process you can immediately use to get your ideas approved.

The first step for generating a clear and compelling recommendation by using the Structured Thought Process is defining the question. All too often when stakeholders ask for a recommendation, we rush off to conduct analysis and bring back an idea as quickly as possible. That approach can cause massive problems because we never stop to get clarity on what the real issue is.

Teams often assume everyone knows what the question is and therefore don’t take the time to document the issue. Even if they do document the issue, they don’t go the extra step of explaining why it’s important to the stakeholder to solve the issue. Without clarity and agreement on the “what” and the “why” of the issue, the likelihood of generating a recommendation that will meet the stakeholder’s needs is low.

To demonstrate the importance of defining and documenting the question, let’s walk through an example. Imagine I’m your stakeholder and I ask you for a recommendation. I ask “Can you get me your best idea for how we can generate an incremental $1MM in profits? Thanks!” I then leave the room. For this exercise, write down the first three ideas that come to mind for how you can solve my problem. Go ahead – write them down so we can refer back to them.

Finished? Okay, let’s look at your ideas. You may have come up with ones like launching a new product, entering a new market, reducing manufacturing costs, conducting a layoff, or raising prices. You might want to launch a new marketing campaign, set up a joint venture, offer discounts to drive sales, or cut travel expenses. These are great ideas but you might have a big problem. Your ideas might satisfy my “what” but you have no idea what my “why” is for why I want this solved.

Understand the “Why?”

Imagine if my request to you was “Can you get me your best idea for how we can generate an incremental $1MM in profits because our earnings quarter ends in three weeks and we have to make up a financial shortfall? Thanks!”

Now look at the list of ideas you generated. Will any of them meet my needs as a stakeholder? Do any get me $1MM in three weeks?

If you’re lucky maybe one does, but most likely not. Think about how much effort you could have wasted if you didn’t understand my “why” of needing that money in three weeks. You might have conducted a large market and new product analysis, generated ideas for prototypes, and put together a launch plan to get the product to market in a blazing fast six months. All that analysis took you two weeks to conduct. When you come pitch your idea, instead of being overjoyed with your brilliant new product launch, I’m furious you wasted two of our precious three weeks messing around with irrelevant analysis. Both of us are at fault. I’m culpable because I didn’t tell you the “why” of my request. You’re at fault because you didn’t ask for the “why” and you didn’t come back to me to confirm the question that needed to be answered.

Let’s change the scenario to one where I ask “Can you get me your best idea for how we can generate an incremental $1MM in profits, because our earnings quarter ends in three weeks and we have to make up a financial shortfall? Thanks!” You know the “why” up front. You’ll focus on ideas resulting in short-term profits. You might generate ideas like locking down all corporate travel for three weeks, raising prices across the board, or deferring a large marketing campaign expenditure to the next quarter. Ideas like those will meet my needs and will receive a warmer reception when you pitch them to me. You won’t waste time on analysis that doesn’t matter. All your energy will focus on helping me achieve my objective. When you build a recommendation that’s mindful of the “why,” your odds of getting your idea approved increase tremendously.

Implications of Defining the Question

There are several implications stemming from defining the question. If you’re the one asking for ideas, be sure to let your team know the “why” behind your request. You’ll set them up to be successful that way.

If you’re the one being asked to generate a recommendation and your stakeholder doesn’t tell you the “why” of the request, ask them what it is. Let them know you want to meet their needs and to do so you have to understand their objectives.

Finally, write the question down. This is part of the discipline. By writing it down, you can go back to your stakeholder with something concrete and confirm it’s the question they want you to answer. If it’s not what they want answered, you’ll be able to iterate with them and refine the question until you’re both in agreement on what they want you to answer. If you’ve ever spent a great deal of effort generating a recommendation only to find out on the back end that you answered the wrong question, you’ll understand how critical this agreement is.

The Elegant PitchIf you want to improve your chances for getting your recommendations approved, grab your copy of The Elegant Pitch now (CLICK HERE to get yours). It will provide you clear instructions for how to create a compelling case that your stakeholder can’t refuse. If you’re interested in taking our course on the method, come check out Structured Thought & Communications. We’re happy to come to your organization and teach your team how to make clearer, more compelling recommendations.

Mike Figliuolo at thoughtLEADERS, LLC

Did you enjoy this post? If so, I highly encourage you to take about 30 seconds to become a regular subscriber to this blog. It’s free, fun, practical, and only a few emails a week (I promise!). SIGN UP HERE to get the thoughtLEADERS blog conveniently delivered right to your inbox!

Photo: good question by Eric

One Response to “Define Your Question Before You Solve the Problem”

  1. RJ Bradner says:

    This is one of my favorite blogs you have written. I was so excited about the concept, I read it twice. How true this is. I learned this lesson early on in my career and it really helped. Another impact of asking the WHY is morale for the team that’s going to do the work. It’s a good reminder for them to understand what the end goal is and how it all plays part in the big picture. Well done Michael. Kudos.

Leave a Reply

  • ©Copyright thoughtLEADERS, LLC. All rights reserved. All materials contained on this site are protected by United States copyright law and may not be reproduced, distributed, transmitted, displayed, published or broadcast in whole or in part without the EXPRESS WRITTEN CONSENT OF thoughtLEADERS, LLC. Content may not be republished, reproduced or distributed in whole or in part without the proper attribution of the work and disclosure of its source including a direct link back to the original content. You may not alter or remove any trademark, copyright or other notice from copies of the content nor can you modify the content in any way. However, you may download material from this website for your personal, noncommercial use only. Links to websites other than those owned by thoughtLEADERS, LLC are offered as a service to readers. thoughtLEADERS, LLC was not involved in their production and is not responsible for their content.

    thoughtLEADERS, LLC has worked to ensure the accuracy of the information included herein. thoughtLEADERS, LLC is not engaged in rendering legal, accounting, or other professional services beyond training, coaching, and consulting. Its reports or articles should not be construed as professional advice on any particular set of facts or circumstances. thoughtLEADERS, LLC is not responsible for any claims or losses that may arise from any errors or omissions in our reports or reliance upon any recommendation or advice provided by thoughtLEADERS, LLC.

    thoughtLEADERS, LLC is committed to protecting your privacy. You can read our privacy policy by clicking here.