When the Right Idea Is Presented the Wrong Way

Doing the homework is only half the battle. Effective leaders also need to understand how their audience evaluates ideas and make the case accordingly.

Nov 16, 2026  |  By Joe Sharp, Sharp Focus Consulting

communicate idea

Years ago, I spent months developing a solution to a problem that had long frustrated our organization: Across a large campus, we had nearly 800 lighting fixtures containing dozens of different types of bulbs. Keeping replacements in stock was an administrative headache, and maintenance consumed staff time. Inevitably, some lights were always out, and we were spending more on electricity than we needed to.

LED lighting offered a potential solution, but most of the proposals I had seen required significant upfront investment. An alternative option, I found, would be to bring in an outside vendor that would convert our lighting with no upfront capital investment. In this scenario, we would share a portion of the energy savings. They would also assume responsibility for maintaining the lighting going forward.

That potential solution would bring with it financial savings, reduced maintenance demands, safety and aesthetic improvements, and eliminate an ongoing operational headache.

I did my homework — actually, I did a lot of homework, involving facility audits, meetings, research, site visits and financial analysis. By the time I presented the idea, I had anticipated just about every question I thought could be asked. I had taken a complicated problem and put a ribbon around what I thought was a compelling solution.

And the idea was rejected almost immediately.

My initial reaction was frustration. I had done the research, and the economics worked. Even other members of senior leadership acknowledged its merits. For a while, I focused on why I thought the decision was wrong. Eventually, I realized there was a more useful question: Why had I presented the idea that way in the first place?

Knowing How Someone Decides

One of the lessons I've learned from spending much of my career as a CFO, COO and second-in-command is that knowing what a leader needs to know is only part of the job. You also need to understand how a particular person on your team makes decisions.

Normally, I would have started with the problem, followed by a possible solution. But instead of doing that, I became so excited about finding what I thought was the answer that I jumped straight into solutions.

I already understood that about this particular decision-maker. Normally, I would have started with the problem, followed by a possible solution. But instead of doing that, I became so excited about finding what I thought was the answer that I jumped straight into solutions.

It wasn't the first time I fell into this trap. On another occasion, I was preparing a recommendation for a significant capital project. The funding was available, and I had done extensive research that enabled me to negotiate what I believed was the strongest combination of price, quality, service and long-term reliability.

After my presentation, the response was essentially: Go back and do better.

In this case, I should have brought the proposal forward before completing every last negotiation. I knew there would likely be a request to push harder, so I left myself somewhere to go. This time, because I was convinced I had already found the right answer, I had negotiated as far as I reasonably could before presenting it.

I had confused having finished the analysis with being ready to make the case. They aren't always the same thing.

Making the Case

For much of my career, I have been the person immediately below the ultimate organizational leader. People throughout an organization bring the number two their ideas, frustrations, requests, problems and proposals.

Part of the job is being a filter. You ask the questions the leader is likely to ask and identify what's missing. You strip away unnecessary detail to help determine whether an idea is ready — and sometimes whether it should be brought forward at all. You translate between the organization and the person who ultimately must make the decision.

But when you're the number two, there is an interesting problem: Who filters the filter? Often, nobody. There may be no additional layer between your analysis and the person who can approve it or deny it. So you have to learn to be your own filter.

If my responsibility is to help an organization make good decisions, understanding the decision-maker is part of that responsibility.

I haven't always gotten that right. Sometimes enthusiasm gets in the way. Sometimes doing months of research makes us more attached to the answer we've found. And sometimes being convinced we're right makes us less attentive to how someone else needs to process the question.

Understanding how someone makes decisions isn't about manipulation. It isn't about withholding information or maneuvering someone into believing your idea was theirs — it's about recognizing that communication isn't complete simply because you've communicated.

If my responsibility is to help an organization make good decisions, understanding the decision-maker is part of that responsibility.

Here are some questions you can ask yourself before making the case:

  • Does my audience want the recommendation first and the analysis behind it?
  • Does my audience want to be presented with multiple choices or one clear path?
  • Does my audience want numbers and spreadsheets, or are they more open to narrative?
  • Does my audience need time to challenge an idea before becoming comfortable with it?
  • Is my audience receptive when they participate in developing the solution rather than being handed a finished one?

I still don't know whether presenting that lighting proposal differently would have changed the outcome. It might not have. That's important, because the lesson isn't that every good idea will succeed if we package it cleverly enough, it’s that good ideas deserve to be presented in a way that gives them a fair chance.

Being right and being persuasive are two different skills. A well-researched answer is valuable, but the way we help someone understand and evaluate that answer matters too.

After years of sitting in the number-two seat, I've come to believe that the job isn't to get credit for having the right answer. The job is to help the organization reach the right decision.


Author

Joe Sharp

Joe Sharp

Founder

Sharp Focus Consulting

Joe Sharp is the founder of Sharp Focus Consulting and a finance and operations executive with more than 30 years of leadership experience in schools, nonprofits and businesses. He advises organizations and leaders on financial, operational and organizational challenges and writes about the lessons that come from the decisions leaders make every day. Learn more at sharpfocusconsult.com.

NET ASSETS PODCAST

Get Net Assets NOW

Subscribe to NBOA's free twice-monthly newsletter.

SUBSCRIBE
Ask Bo