There is a lesson I have had to learn about myself, and I am still learning it.
I tend to overthink. When I am working on something important, my mind naturally goes beyond the immediate problem. I think about dependencies, edge cases, scalability, second-order effects, what could go wrong six months from now, and whether there is a better way to approach the problem.
That habit has helped me many times.But it has also created problems.Because sometimes, I was right about the risk, right about the flaw, and right about where things were heading — and yet I was still the reason the team wasn’t moving forward.
The uncomfortable realization is that being right and being useful are two different things.
The Problem: When Being Right Stops Creating Progress
Imagine a team is discussing a new approach to solve a problem.
The team has a reasonable solution. It isn’t perfect, but it is achievable. There are some unknowns, and there are certainly risks.
Then someone raises a concern.
“Have we thought about what happens at scale?”
“What about this edge case?”
“What happens if this dependency changes?”
“Didn’t we try something similar before?”
“What about the long-term technical debt?”
These are all good questions. Now imagine that person is me. The problem isn’t that I am asking the questions. The problem starts when I keep asking questions until the team reaches a point where nobody is comfortable making a decision anymore. One concern leads to another. One scenario creates another scenario. We start solving problems that haven’t happened yet.
And suddenly, the original problem is no longer moving. The irony is that the concerns may eventually prove to be correct.
Six months later, something breaks exactly the way I predicted. And I can say, “I knew this was going to happen.”But what did that actually accomplish? If the team spent three months debating instead of building, the fact that my prediction eventually came true doesn’t make the outcome successful.
This is where I have realized that overthinking can disguise itself as leadership. It feels responsible because you are trying to protect the team from making a mistake. It feels intelligent because you are identifying risks others haven’t considered. It feels like ownership because you don’t want the organization to walk into a problem that you can already see coming. But there is a point where risk management becomes risk avoidance. And risk avoidance can become inaction. The most uncomfortable part is recognizing that sometimes the organization doesn’t need another analysis.It needs someone to make a decision and move.
2. The Aspect and Perspective: Being Correct Is Not the Same as Being Effective
One of the biggest changes in my perspective has been understanding that the quality of a decision cannot be measured only by whether the decision was theoretically correct.
It also has to be measured by whether it creates movement.
Think about two teams. The first team spends weeks analyzing every possible scenario. They eventually arrive at a very well-thought-out solution, but by then the opportunity has changed, priorities have shifted, and the team has lost momentum. The second team makes a reasonable decision with the information available. They build something, learn from it, discover what they got wrong, and improve it. The second team may make more mistakes. But they may also get much further. This doesn’t mean we should stop thinking deeply. It doesn’t mean we should ignore risks or accept poor decisions. It means we have to develop judgment around which risks deserve to stop the train and which risks can be managed while the train is moving.
That distinction is especially important as you become more senior.
Earlier in your career, you are often rewarded for finding problems. As you become more senior, you also have to become good at deciding which problems are worth solving right now.That is a different skill. I have had to ask myself questions that are sometimes uncomfortable: Am I raising this concern because it genuinely matters, or because I want to prove that I can see something others don’t? Is this actually blocking progress, or is it simply different from how I would have done it? Does the team need another discussion, or does it need permission to try? If we make this decision today and it turns out to be wrong, can we learn and recover?
These questions changed the way I think about disagreement.
I don’t believe the answer is to become less opinionated or stop challenging decisions. There are absolutely times when you need to stand your ground.If something violates a principle, creates significant risk, compromises quality, or can cause serious long-term damage, speaking up is part of your responsibility. But not every imperfection deserves the same level of resistance. Sometimes you have to allow a team to make a decision that is 70% right because the cost of waiting for 95% certainty is greater than the cost of being wrong. Sometimes people need to experience a problem themselves before the lesson becomes meaningful. Sometimes your role isn’t to prevent every mistake. It is to make sure the team can recover from the mistakes it makes. That was a difficult shift for me. I didn’t need to stop thinking. I needed to become better at deciding when my thinking should influence the direction and when it should simply inform the direction.
Because leadership isn’t about eliminating uncertainty.
Leadership is about helping people move despite uncertainty.
3. A 3-Step Solution: Think Deeply, Challenge Intentionally, Move Forward
I don’t think there is a simple formula for this. It is something I continue to practice.
But three things have helped me.
Step 1: Separate “Important” from “Interesting”
When you naturally think about risks and possibilities, almost every concern can feel important. But they aren’t. Some risks can materially change the outcome. Others are interesting scenarios that may never happen. Before raising a concern, I try to ask: “If this happens, how significantly does it change our outcome? “If the answer is “not much,” it probably doesn’t deserve to block progress. This doesn’t mean ignoring it. It means putting it in the right place.Document it. Monitor it. Design around it later. Not every possibility deserves a meeting.
Step 2: Challenge the Decision, Not the People
There is a huge difference between saying: “I don’t think this approach will work.” and saying: “You’re making the wrong decision.”
The first opens a conversation. The second can turn the conversation into a battle. When I disagree now, I try to focus on the decision, the assumption, or the outcome rather than trying to establish that my perspective is superior. And once the concern has been heard and the decision is made, I need to know when to let go.
This is perhaps the hardest part.
You can disagree and still commit. You can believe the team is making the wrong decision and still help make that decision successful. And if it eventually fails, the goal shouldn’t be to say, “I told you so.”The goal should be to ask, “What did we learn?”
Step 3: Ask the Question That Brings the Team Back to Movement
This is the question I find myself returning to more often: “What would actually move the needle?”
Sometimes the answer is another analysis. Sometimes it is a difficult conversation. Sometimes it is fixing the underlying problem.
But sometimes the answer is simply: “Let’s try it.” Build the first version. Test the assumption. Put something in front of customers. Run the experiment. Make the decision. Learn. Then adjust. There is tremendous value in thinking ahead, but there is also value in allowing reality to provide information that thinking alone cannot. You cannot always reason your way to certainty.
Sometimes you have to move to learn.
The Realization
I still overthink. I still see problems before they happen. I still catch myself building scenarios in my head and thinking about what could go wrong. I don’t want to lose that ability. It is part of how I contribute. But I am learning that seeing the problem isn’t the same as solving the problem.
Sometimes the problem is the risk itself. Sometimes the problem is the decision. And sometimes, unexpectedly, the problem is that I am spending so much energy trying to prevent the problem that nobody is moving anymore. That is probably the hardest part of leadership: realizing that a strength you have built over years can become a weakness when you use it without judgment.
Being analytical can become overthinking. Being thorough can become slow. Being cautious can become avoidance. Being right can become a distraction.
The goal isn’t to stop being right. The goal is to become useful even when you are right. Because at the end of the day, leadership isn’t measured by how many problems you correctly predicted. It is measured by whether the team moved forward, learned something, and became better because you were there. You can be right and still be the problem. And sometimes the most mature thing you can do is recognize it yourself.