The moment you decide to start a company, you are bound to problems.
From that day forward, problems will be everywhere: new competitors popping up, key employees resigning, and so on. When you first start out, everything seems full of excitement: “Oh, how do I solve that problem?” Or perhaps things look even brighter: “All these venture capitalists want to invest in me!”
In the early days, you might feel great: “We just landed an incredible partnership. We’re going to be millionaires!” But negative spirals can also tear you down: “Oh no, what did Facebook just announce? We’re doomed.”
Problems seem to happen constantly. The system might have been running smoothly, but while guiding engineers on choosing frameworks it suddenly crashes, leaving developers thoroughly demoralized. For a CEO, some matters can be resolved quickly. If you have a truly phenomenal team, most issues will be handled without needing your direct intervention.
Yet even in the best-case scenario, there will be at least one thorny issue crossing your desk every single day. And these thorny problems are rarely solvable through standard, routine procedures. Day after day, fatigue sets in. Do you truly understand what running a startup means? It’s all too tempting to become the kind of CEO who simply fires off messages saying: “Don’t keep bringing me these damn problems. You’re smart—solve them yourself. That’s why I hired you.”
Surprisingly, this tactic often seems to work at first: people get down to handling their own business.
Until one day, all those hidden problems people were afraid to bring to your attention pile up, finally erupting and sending your company into a downward spiral. So what should you do instead?
1. Never become a CEO whom no one dares to tell the truth.
This means you must act like a traffic controller, listening to the problems brought before you to the best of your ability. Help your team clarify who to work with to tackle the issue. Helping others learn how to solve problems—rather than solving problems for them—is true empowerment.
2. Everything hinges on education and coaching.
You need to teach people how to spot and address problems when they first emerge, rather than letting them fester and worsen.
In my experience, the problem-solving cycle involves:
- Identifying the existing problem;
- Uncovering the root cause;
- Formulating a solution;
- Executing the plan.
Thinking through issues systematically—such as following the steps above—broadens problem-solving perspectives. Two key observations stand out:
- People often do not realize they are facing a solvable problem; instead, they simply feel frustrated.
- Problem-solving ability is closely tied to seniority.
Junior team members often fail to recognize that the friction they face is actually solvable; they merely feel defeated. I used to have the same issue. You sense that something is off, but have no idea where to start. A real problem exists, yet you haven’t identified it as such. As a result, junior members easily become discouraged, venting to peers instead of taking action. While venting, issues get magnified, and like a snowball, the friction grows bigger and bigger.
This is precisely why coaching is vital: teach people to recognize their own frustration. Frustration is a signal telling them it’s time to pause and examine the underlying cause. That realization is the very first step toward early problem identification and resolution.
If they identify the problem (Step 1) but cannot solve it on their own (Step 2), they can at least reach out to someone who can help.
I am not entirely sure why problem-solving ability correlates so strongly with seniority. It could be raw experience, but more likely it stems from asymmetries in information and influence: senior people have a better grasp of who can help them solve issues, where bottlenecks typically occur, and wield the organizational leverage required to push solutions through.
In other words, it is less about inherent capability and more about information flow, which is heavily dictated by one’s position in the hierarchy. This is why information transparency within an organization is so crucial. Understanding this empowers junior employees with greater autonomy while ensuring senior leaders recognize how essential it is to help others identify and resolve problems.
Another crucial point: once a problem is spotted, the resolution process must remain transparent. This fosters an equal partnership between you and your team. Unfortunately, people often veer in the opposite direction—pulling rank, gatekeeping knowledge, and leaving others in the dark.
A culture of mutual trust, autonomy, and collaborative problem-solving will help you build a self-motivating team. To emphasize once more: “Never run from problems; instead, empower your team members to solve them autonomously as early as possible.”
Reference: “In The Ring: Problems, Problems Everywhere”
Support Independent Perspectives & In-Depth Insights
Every thoughtful analysis and candid critique comes from our dedication to truth and quality. We choose not to follow sensational algorithms or clickbait headlines.
Sustaining independent research requires reader support. Make a one-time or monthly contribution, securely processed by Google.
Payments secured by Google · Manage or cancel anytime in your Google Account




Comments