Consulting
Lessons Learned from GTM Consulting
For the past two years, I have performed part-time, contract go-to-market consulting. My wife had a surgery that had gone 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.
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 lack the budget for what they view as an unproven solution that increases complexity.
Here are my Top 5 findings:
- GTM plans are often developed at the highest levels, often in isolation, without market testing and validation.
- Sales teams are pitted against one another, rather than working together to help everyone achieve more (i.e., “A rising tide lifts all boats.”)
- Sales teams are focused on selling features rather than solving business problems.
- CRMs are not consistently used and often reflect idealized fiction rather than reality.
- Sales management and teams are not leveraging AI to help focus their efforts.
Here are the related Lessons Learned:
- 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 companies describe those problems? Their terminology, often found in job ads, can help create effective messaging that resonates. Work to become the natural fit for what your prospects are seeking.
- Individual contributors get paid to win, but sales management needs to create incentives for collaborative efforts that lead to wins.
- 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 improve and tailor their efforts.
- 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.
- CRMs often either lack information or are full of wishful thinking. They focus on activities, and not progress and next steps. Using MEDDIC/MEDPICC as a foundation for reporting is a much better start. Sales managers need to independently validate the information to ensure their teams are being upfront and honest. Trust, coaching, and collaboration work together for the win.
- 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 lets you quickly qualify prospects in or out. There may be a nurturing program for some of the prospects qualified out for immediate deals, but your time is valuable, and you will go hungry chasing deals you can’t close.
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 a Consultant to help your business grow or someone who can add immediate value to your team, then contact me.
Getting your Piece of the PIE
Whether you are selling, consulting, or managing, there is a foundational approach that has consistently helped me succeed. I call it PIE – an acronym that stands for Perspective, Insight, and Experience. When applied effectively, these three elements provide a robust framework for solving problems, winning clients, and leading teams to remarkable outcomes.
Over the years, I’ve taught this methodology to my teams, and it’s been a critical driver of their success. While I usually reserve it for a small circle, I believe it’s time to share it more broadly.
As an aside, years ago, I wrote a post about some of the negative aspects of the “reckless” application of PIE.
Perspective – Broaden Your View to Stand Out:
To truly differentiate yourself in any field, you need to develop a broad and informed perspective. This involves understanding the larger environment in which you operate: the market, competitive landscape, customer needs, technological advances, and regulatory shifts. A dynamic perspective evolves as you gain new experiences and encounter different approaches to solving similar problems with other businesses or in other industries.
This requires a broad understanding of the environment, market, competitive landscape, legal and technological changes, and more. It also grows and changes as you experience new and different things—especially when different approaches to similar problems are taken. It is how you start to stand out in the eyes of your prospects, customers, and team.
Earlier in my career, I taught technical courses. Two or three people usually stood out. At least one wanted to prove they were better and smarter, and usually, one discussed strange approaches to solving problems. When digging into those strange approaches, you would often identify something creative and brilliant coming from a different perspective on the problem. Curiosity and a desire to improve drive innovation.
In business, perspective becomes your differentiator. When you can see things from a broader, more holistic viewpoint, you position yourself as someone who can offer more than just solutions—you offer foresight, adaptability, and creativity. You become the lighthouse that guides your clients around tricky situations and to a better destination.
How to Apply This:
- Stay informed about industry trends, not just within your niche but across related sectors.
- Engage with diverse thinkers, challenge your assumptions, and be open to unconventional ideas.
- Regularly reassess your strategies in light of new information or shifts in the business environment.
Here is a post that discusses perspective as the starting point.
Insight – The Power of Seeing What Others Don’t:
Insight is one of the most valuable assets you can bring to any business interaction. Too often, people are trapped by existing tools, processes, and perceived constraints. Insight allows you to pierce through these limitations and identify opportunities for improvement that others miss.
Here’s where perspective plays a role in insight: the broader your view, the better your ability to generate actionable insights that can transform a business. My most successful deals and projects were not won because I followed the status quo—they were won because I brought fresh ideas to the table. By reframing the problem and presenting a path to a better solution, I created value that competitors cannot match.
How to Apply This:
- Question assumptions and typical approaches. Ask yourself, “Is this really the best way to solve the problem?”
- Look for inefficiencies, bottlenecks, and areas of waste in processes. These are often hidden opportunities for innovation.
- When engaging with clients or teams, offer insights that reframe their challenges and provide a path to improved outcomes by initially focusing on the “what” instead of the “how.”
Here’s a post that delves deeper into insightfulness.
Experience – The Foundation of Wisdom and Credibility:
Experience is the foundation that supports both perspective and insight. It’s the repository of lessons learned—both successes and failures—that shape your approach to problem-solving and innovation. The more varied and in-depth your experience, the better equipped you are to offer valuable insights and strategies.
Consulting, in particular, is a fertile ground for gaining diversified experiences. By working with multiple clients across industries, you gain exposure to a wide array of challenges and solutions. In sales, this experience translates into powerful stories that illustrate your ability to help clients achieve better outcomes. The more experience you accumulate, the more confident you’ll become in your ability to deliver meaningful results through transferable competence (taking skills and lessons learned from one domain and applying them to another).
How to Apply This:
- Reflect on your past experiences—what worked, what didn’t, and why. Use these lessons to guide future decisions.
- Build case studies from your experiences to demonstrate your expertise and credibility when engaging with clients or stakeholders.
- Continuously seek out new challenges that stretch your capabilities and expand your knowledge base.
As Albert Einstein wisely said, “The only source of knowledge is experience. You need experience to gain wisdom.” But it’s not just about accumulating experiences—it’s about leveraging them. Your past successes build confidence in your abilities, while your failures provide invaluable lessons that help you avoid costly mistakes in the future.
Never Panic!
Panic is not a good problem-solving tool, regardless of your position or role. It is especially bad when you are in charge of people or brought in for your expertise. Panic leads to a myopic view of the problem, hindering creativity.
The point in my career when this became readily apparent was when I was working for a small software company. We had a new product (Warehouse Management System) and were launching our third deployment. This one was more complicated than the rest because it was for a pharmaceutical company. In addition to requirements like refrigeration and lot control, there was a mix of FDA-controlled items requiring various forms of auditing and security and storage areas significantly smaller than previous installations. It was a challenge, to be sure.
A critical component, “Location Search,” failed during this implementation. About 10-12 people were in the “war room” when my boss, the VP of Development, began to panic. He was extremely talented and normally did an excellent job, but his reaction negatively affected the others in the room. The mood quickly worsened.
I jumped in and took over because I did not want to be stuck there all weekend and mostly because I wanted this implementation to succeed. I asked my boss to go out and get a bunch of pizzas. Next, I organized a short meeting to review what we knew and what was different from our prior tests and asked for speculation about the root cause of this problem. The team came up with two potential causes and one potential workaround. Everyone was organized into three teams, and we began attacking each item independently and in parallel.
We identified the root cause, which led to an ideal fix a few days later and a workaround that allowed us to finish the user acceptance testing and go live the following day. A change in mindset fostered the collaboration and problem-solving needed to move forward.
But this isn’t just limited to groups. I was a consultant at a large insurance company on a team redesigning their Risk Management system. We were using new software and wanted to be sure that the proper environment variables were set during the Unix login process for this new system. I volunteered to create an external function executed as part of the login process. Trying to maintain clean code, I had an “exit” at the end of the function. It worked well during testing, but once it was placed into production, the function immediately logged people out as they attempted to log into the system.
As you can imagine, I had a sinking feeling in my gut. How could I have missed this? This was a newer system deployed just for this risk management application, so no other privileged users were logged in at the time. Then, I remembered reading about a Unix “worm” that used FTP to infiltrate systems. The article stated that FTP bypassed the standard login process. This allowed me to FTP into the system and then delete the offending function. In less than 5 minutes, everything was back to normal.
A related lesson learned was to make key people aware of what happened, noting that the problem had been resolved and that there was no lasting damage. Hiding mistakes kills careers. Then, we created a “Lessons Learned” log, with this as the first entry, to foster the idea of sharing mistakes to avoid them in the future. Understanding that mistakes can happen to anyone is a good way to get people to plan better and keep them from panicking when problems occur.
Staying calm and focused on resolving the problem is a much better approach than worrying about blame and the implications of those actions. And most people appreciate the honesty.
As the novelist James Lane Allen stated, “Adversity does not build character; it reveals it.”
Understanding the Real Issue using Root Cause Analysis
Too often people, including Consultants, spend time trying to solve the wrong problem due to having incomplete or incorrect information. Once, I was investigating a series of performance problems and unplanned outages that were assumed to be two separate problems. As I gathered information, several people provided anecdotal stories of anomalous behaviors in various systems, speculation about the “real problem,” and discussions about “chasing ghosts” during previous attempts to resolve the problem.

I remember stating that I was there to solve a real problem having a serious negative impact on production and that it was not my intent to chase ghosts or do anything else that would unnecessarily waste time. Next, I outlined the approach I would use to make a Root Cause determination and that we would reconvene to discuss the real problem and potential solutions. A few people scoffed and felt this was a waste of time and money.
The process followed was simple, structured, and logical. It took everything that was known to be true and mapped it out. I looked for patterns, commonalities, and intersections of systems and events. Within two days, my team and I had identified a complex root cause involving multiple components, which we demonstrated would reliably reproduce the symptoms that our client was experiencing. From there, we worked with their teams to make minor network changes, system configuration changes, and several small application changes.
By the end of the second week, they were no longer experiencing major slowdowns or unplanned outages. Each outage cost this company tens of thousands of dollars in lost sales due to the time-sensitive nature of their product. Within one week, they had recovered the cost of hiring me and my team. What stuck with us was how many really smart people “believed in ghosts” and failed to focus on the information they already had.
A few years later, we created a white paper to potentially help others needing a simple structured approach. Below is a link to that white paper written by one of the top people on my team. We received very positive feedback then, so it seemed that this could still be useful today. Please take a look and let me know what you think.



