execution
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.
Diamonds or just Shiny Rocks?
During a very candid review years ago, my boss at the time (the CEO of the company) made a surprising comment to me. He said, “Good ideas can be like diamonds – drop them occasionally, and they have a lot of value. But sprinkle them everywhere you go, and they just become a bunch of shiny rocks.” This was not the type of feedback that I was expecting, but it turned out to be both insightful and very valuable.
For a long time, I have held the belief that there are four types of people at any company: 1) People who want to make things better; 2) People who are interested in improvement but only in a supporting role; 3) People who are mainly interested in themselves (they can do great things, but often at the expense of others); and 4) People that are just there and don’t care much about anything. This opinion is based on working and consulting at many companies over a few decades.
A recent Gallup Poll stated Worldwide only 13% of Employees are “engaged at work” (the rest are “not engaged” or “actively disengaged”). This is a sad reflection of employees and work environments if it is true. Since it is a worldwide survey, it may be highly skewed by region or industry and, therefore, not indicative of what is typical across the board. Those results were not completely aligned with my thinking but were interesting nonetheless.
So, back to the story…
Before working at this company, I had run my own business for nearly a decade and was a consultant for 15 years, working at large corporations and startups. I am used to taking the best practices learned from other companies and engagements and incorporating them into our business practices to improve and foster growth.
I take a systemic view of business and see the importance of optimizing all components of “the business machine” to work harmoniously. Improvements in one area ultimately positively impact other areas of the business. From my naive perspective, I was helping everyone by helping those who have easily solved problems.
I learned that while trying to be helpful, I was insensitive to the fact that my “friendly suggestions based on past success” stepped on other people’s toes, creating frustration for those I intended to help. Providing simple solutions to their problems reflected poorly on my peers.
Suggestions and examples that were intended to be helpful had the opposite effect. Even worse, it was probably just as frustrating to me to be ignored as it was to others to have me infringe on their aspect of the business. The resulting friction was very noticeable to my boss.
Those ideas (“diamonds”) may have been considered had I been an external consultant. But as part of the leadership team, I was coming across as someone just interested in themselves (leaving “shiny rocks” laying around for people to ignore or possibly trip over).
Perception is reality, and my attempts to help were hurting me. Luckily, I received this honest and helpful feedback early in this position and was able to turn those perceptions around.
What are the morals of this story?
First, people who are engaged have the greatest potential to make a difference. Part of being a business leader is making sure that you have the best possible team, and are creating an environment that challenges, motivates, and fosters growth and accountability.
Disengaged employees or people who are unwilling or unable to work with/collaborate with others may not be your best choices, regardless of their talent. They could actually be detrimental to the overall team dynamics.
Second, doing what you believe to be the right thing isn’t necessarily the best or right way to approach something. Being sensitive to the big picture and testing whether or not your input is being viewed as constructive was a big lesson learned for me. If you have good ideas but are ineffective, consider that your execution could be flawed. Self-awareness is very important.
Third, use your own examples as stories to help others understand potential solutions to problems non-threateningly. Let them connect to their own problems, helping them become more effective and allowing them to save face. It is not a competition. And, if someone else has good ideas, help support them through collaboration. In the end, it should be more about effectiveness, growth, and achievement of business goals than who gets the most credit.
While this seems like common sense now, my background and personal biases blinded me to that perspective.
My biggest lesson learned was about adaptation. There are many ways to be effective and make a difference. Focus on understanding the situation and its dynamics to employ the best techniques, which is ultimately critical to the team or organization’s success.
Where Ideas, Experiences, and Lessons Learned Intersect 