When Ego Gets in the Way of Building Something That Matters
What years in startups taught me about leadership, culture, listening to customers, and remembering the people behind the numbers.
The danger of being too sure
Over the course of my career, I have worked with a lot of startups, founders, executives, and teams. I have seen talented people build impressive things, and I have seen promising companies struggle for reasons that had little to do with the technology or the market. One pattern has stayed with me: when a leader's ego gets in the way of listening, the whole organization can pay the price.
Ego is not automatically a bad thing. Founders need confidence. They need conviction when the path is uncertain, and they need enough belief in an idea to keep going when other people are skeptical. But there is a difference between believing in your vision and believing that your vision cannot be challenged.
When a leader becomes so attached to being right that they stop hearing other people, confidence turns into a blind spot. Customer feedback becomes an inconvenience. Employees learn to keep their concerns to themselves. Decisions become about defending the original idea instead of solving the problem in front of the company.
When customers tell you what they need
Early in my career, I worked at a startup where I was the first person on the go-to-market team. The founder had a strong technical vision for the platform and was determined to build it in a particular way. The technology was designed around advanced, real-time correlation and in-memory processing.
I brought him to New York City to meet with actual customers and buyers. The feedback was consistent. They did not need every part of the system to work in real time. What they wanted was to know about a potential threat or breach before they learned about it from a third party, potentially months after the fact. That need was also consistent with what industry reporting, including the Verizon Data Breach Investigations Report at the time, was highlighting about how breaches were discovered.
I brought that feedback back to the company. I also assembled a customer advisory board and brought those customers to headquarters. They repeated the same message: help us find out sooner. We had room to explore different ways of solving that problem, but the feedback was not getting through. The founder remained committed to the technical approach he had envisioned.
I want to be careful not to pretend I know exactly what was driving his decisions. I cannot know what was in his head. What I could see was the result: the people closest to the customer were telling us what mattered, and the organization was not adapting to what we were hearing.
Ultimately, the company went through roughly $30 million in venture capital without delivering a working product. That outcome was about more than one person's ego, and startups can fail for many reasons. But the experience left a lasting impression on me. Technical ambition is not a substitute for solving a real customer problem. A vision has value only when you are willing to test it against reality.
The cost of building a hierarchy instead of a team
I have seen another version of the same problem in organizations where leaders seem focused on building layers of hierarchy beneath themselves. An org chart can become a symbol of status rather than a tool for getting work done. As the layers grow, the distance between executives, employees, and customers can grow with them.
Those layers can create silos. Marketing blames sales. Sales blames customer success. Customer success blames renewals. Everyone has a reason the problem belongs to another team, and everyone is busy protecting their own territory. Meanwhile, the customer experiences one company, not a collection of departments.
The customer does not care which team owns the handoff or which executive owns the metric. They care whether the product works, whether the service delivers, and whether the company does what it said it would do. If the teams are not working toward that shared outcome, the org chart may look organized while the customer experience feels fragmented.
Healthy organizations need accountability, clear roles, and good management. The answer is not to eliminate structure. It is to make sure structure serves the mission instead of serving someone's need for status. The best leaders reduce unnecessary barriers between the people building the product, the people selling it, the people supporting it, and the people using it.
Culture is built in the moments when people speak up
Culture is not just a set of values printed on a wall or a slide in an onboarding deck. It is what happens when someone raises a concern, challenges a decision, admits a mistake, or brings difficult customer feedback into a meeting.
If people believe they will be dismissed or punished for speaking honestly, they will eventually stop doing it. The leader may still receive updates and dashboards, but the information becomes less useful because people are filtering what they say. Silence can look like agreement from the top of the organization. Often, it is simply a sign that people no longer believe speaking up will make a difference.
When people feel heard and valued, they are more likely to bring forward ideas, identify problems early, and care about the outcome beyond their individual job description. That commitment can be contagious. People who believe in the mission often bring more energy to the work, and customers can feel the difference in how a company treats them.
A positive culture does not mean everyone agrees all the time. It means people can disagree constructively, challenge assumptions, and remain focused on the shared goal. A leader should not need to be the smartest person in every room. A leader needs to make it possible for the best thinking in the room to be heard.
The reputation that follows you
Unchecked ego can damage more than a company's results. It can affect the people who work there and the leader's own career. People remember whether they were listened to, whether their contributions were respected, and whether a leader took responsibility when things went wrong.
Over time, patterns become reputations. If someone repeatedly creates toxic cultures, dismisses feedback, or treats colleagues as pieces on a chessboard, changing companies does not necessarily change the pattern. Different logos on a résumé do not erase the experiences people have had working with you. A reputation can arrive before you do.
That is one reason humility matters. Humility is not a lack of confidence or the absence of strong opinions. It is the willingness to recognize that your perspective is incomplete, that other people have expertise you do not, and that the mission matters more than your need to win an argument.
Remember the humans behind the metrics
I understand why leaders focus on numbers. Revenue, growth, retention, pipeline, and profitability matter. They tell us whether the business is healthy and where attention is needed. But the numbers are the result of people doing work together. They are not a replacement for those people.
Every company is made up of human beings with strengths, blind spots, ambitions, pressures, and room to grow. People want to know that their work matters, that they can be honest, and that they are contributing to something bigger than a departmental scorecard. Leaders have to make time for those conversations, especially when the demands of running a business make it tempting to stay buried in the spreadsheet.
As I continue building KARSA, I keep coming back to how much a company depends on people working toward a shared purpose. We are building wellness technology intended to make it easier to sanitize, dry, transport, and store the gear people depend on. The product matters, but so do the people who design it, build it, support it, and help customers understand its value. No founder can do all of that alone.
The work of leadership is not just setting the vision or tracking the numbers. It is creating the conditions for people to do their best work together, to be honest about what is not working, and to stay connected to the people the company exists to serve.
Build something people want to be part of
Ego can help a founder take the first step. It can provide the confidence to pursue an idea that does not yet exist. But when ego becomes more important than curiosity, listening, and respect, it can turn into a barrier between the company and the people who could help it succeed.
Customers are telling you something. Employees are telling you something. The market is telling you something. The question is whether you are willing to hear it, especially when it challenges what you wanted to believe.
A founder's job is not simply to build a business. It is to build an environment where people believe in what they are building together. That starts with remembering that titles and org charts do not make anyone more or less human. We all have strengths. We all have flaws. We all have something to learn.
So take a beat. Look up from the spreadsheet. Talk to the people doing the work and the people using what you make. Listen without preparing your rebuttal. Make it safe for someone to tell you something you may not want to hear.
The best leaders are not the ones who never get it wrong. They are the ones who stay approachable enough to learn, humble enough to change, and focused enough to remember what matters most: the people, the culture, and the value the company creates for its customers.
