consulting
Curiosity-Led Execution (5-minute read)
Most organizations don’t struggle because they lack solutions—they struggle because they misdiagnose problems. A structured, curiosity-led approach accelerates alignment, reduces rework, and leads to solutions that actually stick.
My Starting Point
I was not a fan of consultants when I first started working with them. Most were arrogant, had limited focus, and viewed problems or goals in isolation. I later learned that the same could be said for salespeople, executives, and more. It had less to do with the role but was more evident when people presented themselves as experts.
Switching to consulting was a tough sell. When I finally accepted a position, I expected to learn proven methodologies from seasoned experts. The lessons learned were not always what I had anticipated.
Many of the senior consultants I worked with had been highly successful early in their careers. But over time, that success calcified into rigid frameworks and default approaches. They weren’t completely wrong—but they weren’t adaptable or as effective as they could have been, either.
It reminded me of the old metaphor: “If the only tool you have is a hammer, everything looks like a nail.”
At one point, I seriously questioned whether consulting was the right fit for me.
Then I stepped back and looked at the best consultants I had worked with—the ones clients trusted and consistently delivered outcomes. I asked a simple question:
What do they do differently?
The answer wasn’t just expertise. It was curiosity, combined with the desire to deliver a positive experience that delivers tangible positive outcomes.
From Depth to Insight
Early in my career, I went deep—sometimes excessively so.
I read dozens of manuals for a relational database system, cover to cover, just to understand how it worked. Then I spent years, while traveling, going through its source code, trying to understand why it worked the way it did.
That effort paid off. I became recognized as an expert for that product, which opened the door to many challenging and exciting consulting engagements.
But it also revealed a limitation: Depth alone doesn’t scale.
What scaled was the mindset that I developed with it:
- Looking beyond surface-level symptoms.
- Viewing problems from a systemic perspective. Understanding how systems interact (not just how they function).
- Asking how and why decisions were made, not just what decisions were made.
I learned to read between the lines—technically and organizationally. To understand not just systems, but the people and processes behind them.
That context is powerful, but difficult to extract—especially quickly.
The Breakthrough: Structured Curiosity
What ultimately worked wasn’t just knowledge. It was a repeatable approach built on three elements:
- Establish credibility
Demonstrate enough expertise early to build confidence. - Lead with curiosity
Ask thoughtful, relevant questions that show genuine interest—not interrogation. - Close the loop
Articulate your understanding back to stakeholders to confirm, refine, or challenge it.
This creates a feedback loop:
Curiosity → Insight → Validation → Alignment
That loop is where trust—and progress—happens.
A Practical Tactic: The “Columbo Technique”
One of the most effective tools I’ve used is commonly called the Columbo Technique.
The idea is simple: Lower defenses by creating psychological safety—and a sense of control.
Instead of pushing for answers, you:
- Ask informed questions
- Make partial observations
- Then, intentionally leave a gap
Something like:
“I might be missing something, but I’m not fully connecting how X impacts Y…”
This does two things:
- Signals humility (reducing resistance)
- Invites correction (which reveals deeper truth)
People tend to open up—not because they’re forced to, but because they want to contribute. They feel safe because you are focused on understanding the situation and solving the problem, and not pointing fingers or assigning blame.
And once that happens, you get access to what actually matters: the “why” behind the “what.”
Applying This in the Real World
This approach works across consulting, sales, and leadership—but only if applied deliberately.
Here’s how to operationalize it:
1. Start Broad Before Going Deep
Don’t jump to solutions. Map the landscape first:
- Stakeholders
- Systems
- Constraints
- History
2. Use Their Language
Mirror terminology and examples. It builds alignment faster than forcing your own framework.
3. Validate Early and Often
Don’t wait until the end to present conclusions. Share evolving understanding:
- “Here’s what I think I’m seeing…”
- “Does this match your experience?”
- “Can you help me identify reasons why this might not work?”
4. Balance Confidence with Curiosity
Too much confidence shuts people down.
Too much curiosity erodes credibility.
The balance is where influence lives.
5. Optimize for Adoption, Not Perfection
The best solution is the one that gets implemented and sustained—not the one that looks best on paper.
A great example of this is at a large insurance company, where I led a successful 18-month redesign and implementation of a common Risk Management System used across three distinct businesses.
Before I came, they spent two years and several million dollars with a Big 5 Consulting company. The output was several 3” binders filled with specifications, definitions, and design documents. It was amazing, but wasn’t implementable. I have seen that far too often on consulting engagements.
A section in the middle of this post describes what happened with that project.
Make It Repeatable with the CLEAR Framework
This is a simple, reusable model that can help anyone new to a company or role.
The C.L.E.A.R. Framework
C — Credibility
- Establish baseline trust quickly.
- Demonstrate you “speak their language.”
L — Learn
- Map systems, stakeholders, constraints, and history.
- Ask high-quality, layered questions.
E — Expose
- Surface gaps, contradictions, hidden dependencies.
- Use techniques like the “Columbo Method.”
A — Align
- Play back understanding.
- Build shared clarity before prescribing.
R — Recommend
- Deliver solutions optimized for adoption and results, not elegance alone.
Why This Matters
When you lead with curiosity, you move faster—not slower.
You avoid rework.
You uncover hidden constraints early.
You gain stakeholder alignment before decisions are locked in.
And occasionally, you can help solve problems that have existed for years—in a matter of weeks—because you’re solving the right problem.
If this sounds interesting and you would like to discuss it further or seek out assistance, contact me here.
What’s the prize if I win?
In consulting and in business, there is a tendency to believe that if you show someone how to find that proverbial “pot of gold at the end of the rainbow,” they will be motivated to do so. Seasoned professionals will tend to ask, “What problem are you trying to solve?” to understand whether there is a real opportunity. If you cannot quickly, clearly, and concisely articulate the problem, and why this helps solve it, it is often game over then and there (N.B. It pays to be prepared). But, having the right answer is not a guarantee of moving forward.
Unfortunately, sometimes a mere pot of gold just isn’t enough to motivate. Sometimes it takes something different, and usually something personal. It’s more, “What’s in this for me?” No, I am not talking about bribes, kickbacks, or anything illegal or unethical. This is about determining what is really important to the decision maker and in what priority, and then demonstrating that the proposed solution will bring them closer to achieving their personal goals. What’s in it for them?
Case in point. Several years ago I was trying to sell a packaged Business Intelligence (BI) system developed on our database platform to customers most likely to have a need. Qualification performed – check. Interested – check. Proof of value – check. Quick ROI – check. Close the deal – not so fast…
This application was a set of dashboards with 150-200 predefined KPIs (key performance indicators). The premise was that you could quickly tailor and deploy the new BI system with little risk (finding and validating the data needed was available to support the KPI was the biggest risk, but one that could be identified up-front) and about half the cost of what a similar typical implementation would cost. Who wouldn’t want one?
I spent several days onsite with the prospect, identified areas of concern and opportunity, and used their data to quantify the potential benefit. Before the end of the week, I was able to show the potential to get an 8x ROI in the first year. Remember, this was estimated using their data, not figures I just created. Being somewhat conservative, I suggested that even half that amount would be a big success. Look – we found the pot of gold!
Despite this, the deal never closed. This company had a lot of money, and this CIO had a huge budget. Saving $500K+ would be nice but was not essential. What I learned later was that this person was pushing forward an initiative of his own that was highly visible. This new system had the potential to become a distraction, and he did not need that. Had I made this determination sooner, I could have easily repositioned it to align with his agenda.
For example, the focus of the system could have shifted from financial savings to project and risk management for his higher priority initiative. The KPIs could be on earned value, scheduling, and deliverables. This probably would have sold as it would have been far more appealing to this CIO and supported what was important to him (i.e., his prize if he wins). The additional financial savings initially identified would be the icing on the cake, to be applied later.
There were several lessons learned from this effort. In this instance, I focused on my personal pot of gold (based on logic and common sense) rather than on my customer’s priorities and prize for winning. That mistake cost me this deal, but it is one I have not made since – helping me win many other deals.

