leadership

Most Popular Posts, Sorted by Category

Posted on Updated on

If you want to review specific content, this should be helpful. I’ve selected the 4-6 most popular posts for the most popular categories to make it easier to explore. Please ask questions or share your comments as you go. Thank you.

Sales / Selling

Sales Management

Customer Success

Leadership

Business Ownership / Entrepreneurship

Innovation / Innovating

The Strangest Feedback I Ever Received

Posted on Updated on

My first job after my consulting company shut down was building a consulting organization for a spinoff database company. The CEO called me the week before, then invited me to meet him in Manhattan the following week. We met for a few hours, then he handed me a piece of paper with a title and salary. I thought about it for a minute, shook his hand, and said, “Thanks, boss.” We devoted the next few days developing a vision for the team that would boost sales and drive greater customer success.

We worked closely for the next six months, but there were times I could tell that I frustrated him. For example, we once met with a top 3 credit card company. They presented their needs, and he told them we could easily handle it.

On the way back to the hotel, I explained the architectural limitations that would make the project very challenging. Then I presented multiple ideas to accomplish what they needed – just not in the way they envisioned it. My focus was on creating a deal that worked, and not just closing a deal that could ultimately hurt our reputation.

A year or so later, I was on a multi-city road trip to visit customers and prospects with each member of the sales team. It was a Thursday afternoon; I had just arrived at a hotel in San Diego where I’d stayed dozens of times over eight years, and I was relaxed and feeling great.

The CEO called, telling me that one of the architects he hired had just given his notice, and asked me if I thought we should try to get him to stay. I explained that this person was extremely talented and worked well with everyone, but he wasn’t working on the things he was hired to do and had been noticeably unhappy for the past several months. I asked if we planned to revive the project this person helped develop, and the answer was ‘no’.

I went on to explain that while this guy was a great person and technical asset, he wasn’t a good fit for the company now or where it was heading, which is why I recommended letting him go. I said we could use his salary to hire one or two people interested in our current direction and get a better return on that investment.

To me, this was a logical decision, and not an emotional one. Most companies have limited resources, and to win, you need to find the greatest leverage for every dollar spent.

His response was, “The thing I love about you is also the thing that I sometimes hate about you.”

A man in suit standing in front of a mirror that has two reflections. One is overly positive, while the other reflects reality.
“Reflections” created by Nano Banana 2

There was a brief pause of silence, then I replied, “OK, I’ll bite. What is that?” He said that, unlike everyone else who reported to him, I consistently told him what he needed to hear instead of what he wanted to hear. He told me he valued my perspective, which is why he called, but I often frustrated him by telling him something contrary to his beliefs.

This candid conversation didn’t damage our relationship, and it reinforced a core truth about leadership: loyalty demands clarity first, then compliance.

Safe leaders surround themselves with “yes-men” to protect their egos. Exceptional leaders seek out individuals who care enough about the mission and its success to risk temporary friction. This is about doing the right thing, versus who is right.

Leaders should create an environment where all opinions and data are welcomed during the planning phase. Disagreement isn’t disrespect; it is a risk-mitigation strategy. This is where clearly articulating your concerns persuasively helps. True alignment sometimes requires strong but professional debate behind closed doors: looking for flaws and weaknesses in a plan, refining it as needed, and then executing the final decision as a unified team.

So, do you have the courage to provide the truth – even if it is unpopular? Can you do so in a convincing and professional manner? They might hate it in the moment, but they will value your integrity in the end, especially if you are seen as someone focused on improvement and success, and not just a contrarian.

This is what should be expected of executives within an organization, for the overall good of that organization.

Curiosity-Led Execution

Posted on Updated on

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 and more to do with how 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 I learned weren’t always what I had expected.

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 and tangible 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 traveling, reviewing its source code at night, trying to understand why it worked the way it did. That understanding led to new ways of optimizing performance.

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:

  1. Establish credibility
    Demonstrate enough expertise early to build confidence.
  2. Lead with curiosity
    Ask thoughtful, relevant questions that show genuine interest—not interrogation.
  3. 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 you apply it 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

Knowledge explains. Curiosity transforms. 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 is Customer Success?

Posted on Updated on

In most companies, it is a department or a team. I would argue that it should be foundational in a company’s culture. Companies need to focus on providing products and services that solve critical business problems for their clientele. By doing so, they create a predictable revenue stream and install base that supports future growth.

A tripod with legs titled, sales, products, and support, with the words Customer Growth, an upward trending arrow and a crown at the top. This sits on a base having the title, Customer Success Culture.

In a quarterly executive meeting a decade or so ago, the head of the Support organization stated this team was the most important. The head of Engineering then stated that her team was the most important. I chimed in and stated, “Without Sales, nothing happens, but ultimately, if all teams are not focused on the same objective, like a tripod, then all teams will ultimately fail.” Our CEO agreed, and that was the end of the discussion.

You could also argue that Marketing and Services should be included, and I would agree, since it goes back to all teams being focused on a singular, overarching goal.

In a previous post about creating Customers for Life, I wrote about an implementation to address customer churn, a byproduct of the company’s failure in one or more areas. This was a wake-up call for me, as we were very focused on the success of our largest accounts and most productive channel partners – totaling 70% of our revenue, but we took the other “less valuable” accounts for granted. The lesson learned was that 30% of $62M is a large number (a “long tail”), and by applying the same techniques to those accounts, we increased organic growth while minimizing churn, improving our overall Net Revenue Retention (NRR) rate.

Why Customer Success Teams Struggle

  • Lack of Ownership: They don’t own the accounts and often lack the motivation and accountability for each customer’s health and success.
  • Stay Reactive: They are reactive rather than proactive advocates for customers.
  • Lack of Resources: They are spread too thin and lack the capacity to actively engage with all but a few customers.
  • Enter Too Late: They are not introduced early in the sales process, which is a great way to demonstrate commitment to the prospect’s success if they select you as a vendor.
  • Stay Low in the Org Chart: They do not develop relationships beyond a small operational team, limiting executive visibility and expansion potential.
  • Ad Hoc in Nature: They lack formal processes, including detailed documentation, that help ensure consistency and continuity over time.

How to Position Your Team for the Win

  • SWOT: Review your strengths and weaknesses. Why do companies buy from you? (or, what are you really selling?) What are you known for? What do people like and appreciate? Where do you fall short? (opportunities for others) Accentuate the positive and focus on improvements where needed.
    • We often received customer feedback that when they called our support team, their problem was solved on the initial call. With other vendors, it often took 2-3 people to reach someone knowledgeable who could help. We promoted this when selling and reinforced the importance of maintaining this positive image to our internal teams.
    • We also received feedback that some of our technical features were lagging behind the competition, so my team and I helped identify the most critical features, then worked with Engineering to prioritize them and focus on bringing in new customers who needed them. It was a win-win.
  • Be Proactive: It is often possible to anticipate problems or make improvements based on your understanding of the customer and their history. Being part of the solution means that you don’t wait for the next problem to engage.
    • When I had my consulting company, we provided managed services for several large companies. We had proprietary monitoring tools that reported conditions that often led to outages if left unchecked. We addressed the issue and informed the customer once it was resolved. Our monthly summary report listed the likely outages avoided, the average duration of similar outages, and the cost avoided (based on the hourly cost of downtime). Key people saw our value at least monthly, so when it came time to renew our service, the process was fast and painless.
  • Become the Internal Liaison: The customer success team should serve as the main conduit for information. Introduce your Services or Engineering teams to the customer early. This doesn’t just solve problems; it uncovers new opportunities to provide value (and sell additional services) that position the customer for even greater success. Engagement and a sense of partnership go a long way.
    • I will often introduce the Services team when problems or needs arise. Their expertise and insights can be very valuable, often leading to services that position the customer for even greater success.
  • Go Above and Beyond: People remember that. Teams begin to rely on you. And Executives begin to see your company and products as critical to their success. This creates long-term value for your company.
  • Focus on the Future: Ask your customers, “How can we help with your upcoming initiatives and projects?” This is a great way to learn what they will be working on, to show your interest in their success, and to identify how your company and products can help them achieve it.

These are things that have been very successful for me when I was leading two large global regions, when I was a top Account Executive at a company with a small customer success team, and as a Consultant. I set expectations, led by example, and they began doing much more of what I expected from the customer success team. We started seeing improvements in the first 30 days.

While leadership doesn’t have to come from designated leaders, cultural changes usually require the commitment, involvement, and support of the organization’s top executives. Everyone can positively influence a company’s direction and success.

When the customer wins and views you as a key partner, your concerns about churn become minimized.

Lessons Learned from GTM Consulting

Posted on Updated on

For the past two years, I have performed part-time, contract go-to-market consulting. My wife had a surgery that went wrong 18 months ago, so I needed something that would allow me to take care of her, stay sharp, earn money, and help companies grow. What I encountered was quite different from what I expected, so I thought I would pass it along.

A generated image of a male consultant working with a sales team.

Most of the work was with small to midsize companies, but the problems and needs mirrored what I have encountered at larger companies. The main difference is that large companies tend to look to software to address problems. In contrast, smaller companies often lack the budget for what they view as a solution that increases complexity.

Here are my Top 5 findings:

  1. GTM plans are often developed at the highest levels, often in isolation, without market testing and validation.
    • An interesting aside is that the company is often really seeking sales optimization but believes it is doing things “well enough” today and therefore needs to focus on new offerings and revenue streams.
    • New perspectives on past performance and failures are well received but more surprising than anticipated. This leads to a better understanding of needs, which builds consensus moving forward.
  2. Sales teams are sometimes pitted against one another, rather than working together to help everyone achieve more (Coopetition – “A rising tide lifts all boats.”)
    • Sometimes the competing team isn’t sales, but support. The team wants to help the customer (which is great), but works outside its defined scope instead of bringing in the services and sales teams to work jointly to solve the customer’s problem.
  3. Sales teams are focused on selling features rather than solving business problems.
    • Training those teams on solution selling and understanding the prospect’s needs pays off.
  4. CRMs are not consistently used and often reflect idealized fiction rather than reality.
    • Old, dead, or unqualified opportunities; lack of recent contact or interaction; deals that have slipped more than once; and a lack of understanding (company, needs, players, business environment) all point to an unrealistic pipeline.
  5. Sales management and teams are not leveraging AI to help focus their efforts.
    • Conversely, they may view AI as a panacea, investing time and money in tools that supplement a strong team rather than focusing on strengthening the team.

Here are the related Lessons Learned:

  1. Selling is a byproduct of problem-solving. You can’t solve problems if you don’t know what they are. Every interaction with a prospect should focus on gathering information, building trust and relationships, and leveraging prior interactions to demonstrate that your solution will solve their problem and ease their pain.
    • Here’s solution sales again. Teaching teams to ask better questions, listen more, and validate their understanding increases their standing with prospects.
  2. Identifying common business problems and describing how your product or service solves them should be the foundation of the plan.
    • Perform market analysis. How do other companies describe those problems? Their terminology, often found in job postings by competitors and your target audience, can help create effective messaging that resonates. Work to become the natural fit for what your prospects are seeking and the problems they are likely dealing with.
  3. Individual contributors get paid to win, but sales management needs to create incentives for collaborative efforts that lead to both wins and ongoing customer growth.
    • Paying sales teams for net new business only causes them to ignore install base expansion opportunities. And, if another vendor solves their problems, it is only a matter of time before they replace you.
    • For one company, I convinced them to implement a 2% SPIV (like a SPIFF, but team-focused) for every team member who actively contributed to team improvement. SPIV payments were quarterly, and there was a running total so the team could see the fund growth. Initial indications of a positive impact are good.
    • Another benefit of collaboration is that it helps teams focus on approaches that work due to ongoing testing and refinement. Collaboration also helps teams focus on a more accurate ICP (ideal customer profile). Sales management can then feed their findings back to Marketing to tailor and fine-tune their efforts.
  4. CRMs often either lack information or are full of wishful thinking. They focus on activities, and not progress and next steps.
    • Using MEDPICC as a foundation for qualification is a much better start.
    • Sales managers need to validate the information independently to ensure their teams are upfront and honest. Trust, coaching, and collaboration work together for the win.
    • Chasing deals that are unlikely to close wastes valuable resources.
  5. AI is not a panacea, but it is very effective for research, market validation, prospecting, and meeting preparation.
    • Going in prepared builds respect and credibility, saves time, and helps you quickly qualify prospects in or out.
    • There may be opportunities to nurture prospects who have potential but aren’t qualified for immediate deals, seeding the pipeline for future opportunities. This could be a great place to leverage AI for personalized journeys with highly relevant curated content.

So, what are your thoughts? Have you seen some of these problems yourself? How did you handle them? Let me know in the comments below.

And if you are looking for assistance with your business, contact me.