We Need to Get Better at Being Wrong
Tatiana Jordan
I have led projects that exceeded every expectation. I have also led projects that did not go the way any of us expected.
The second kind taught me more.
Not because failure is somehow more noble than success. It is usually just more revealing. When a project is going well, everyone can look aligned. It is when the assumptions start falling apart, the timeline slips, or the outcome does not match the effort that you see how a team really works.
Do people say what they are seeing? Do they stay engaged when the work becomes uncomfortable? Can they admit they were wrong without making it someone else’s fault?
These questions have always mattered. AI is making them harder to avoid.
We are being asked to move quickly with technology that is still changing underneath us. Teams are learning by doing because there is no realistic way to understand all of this from the sidelines. That means we are going to make some bets before we have enough information to know whether they are right.
Some of them will not be.
I think we need to get much more comfortable saying that out loud.
Not every difficult project started with a bad decision
There is a tendency to look back at a project that struggled and assume someone should have known better.
Sometimes that is true. A concern was ignored. The evidence was weak. People said yes because saying no felt harder.
But sometimes a reasonable decision simply meets reality.
The technology does not perform as consistently as it did in early tests. Customers respond differently than expected. Priorities change. Key people leave. Ownership becomes less clear. Dependencies that looked manageable become the work.
I have seen all of those things happen.
Part of leadership is knowing the difference between a careless decision and a reasonable bet that did not work. If we treat every disappointing outcome as proof that someone failed, people will stop taking thoughtful risks. They will also get very good at protecting themselves.
That is where the language starts to change: “They decided.” “That was not my part.” “We delivered what we were asked to deliver.”
Sometimes those statements are true. They can also be signs that people are stepping away from an outcome they once helped create.
I do not need every bet to be right. I do need people to stay connected to the work when it is not.
Challenge it before we commit
The best time to be honest is before an idea has a budget, a roadmap, and a room full of people attached to it.
I want people on my team who will question the premise, not just improve the execution. If the problem is unclear, say it. If the evidence does not support the enthusiasm, bring that forward. If AI is adding complexity without improving the experience, we need to talk about it.
That requires some courage. It is easy to welcome dissent when it is theoretical. It is harder when it disrupts momentum.
As a leader, I own my part in that. I cannot say I want candor and then become defensive when I hear it. I cannot reward quick agreement and wonder later why no one raised the obvious risk.
At the same time, challenge is not a permanent escape hatch.
Raise the issue. Make the case. Help the group understand the tradeoff. Then, once the decision is made, commit to making it work unless new evidence tells us we need to reconsider.
Being willing to challenge a decision and being willing to own one are not opposing qualities. I want both.
Stay when the story gets messy
Every project has a version of the story that made sense at the beginning. We believed customers had this problem. We believed the approach would solve it. We believed we could deliver it.
When the project starts to struggle, there is a strong temptation to rewrite that story. People remember their doubts more clearly than their support. Decisions that were made together become decisions made by someone else.
I understand the instinct. No one wants to be attached to a visible miss.
But accountability is not proving that you were right all along. It is being able to say:
“This is what I believed at the time.”
“This is what I got wrong.”
“This is what I think we should do now.”
That is the conversation I want to have. What happened, what did we learn, and what do we do next?
Sometimes the answer is to adjust. Sometimes it is to give the work more time. Sometimes it is to stop.
Stopping can be the hardest decision because it makes the loss visible. Continuing preserves the possibility that the original idea will eventually prove itself. But continuing simply because stopping is uncomfortable is not accountability. It is avoidance with a budget.
Accountability has to go up, too
Leaders set the conditions around the work. We approve the investment. We decide how much evidence is enough. We create the deadlines and make the promises. We influence whether a concern is treated as useful information or resistance.
If a project was under-resourced, if ownership was unclear, or if the timeline was based more on pressure than evidence, that is part of the story. It does not remove the team’s responsibility, but it cannot be edited out of the retrospective.
I have made decisions I would make differently now. That does not mean I was careless. It means I have information now that I did not have then.
The point is to use it.
I expect people on my teams to own their judgment and their work. They should expect the same from me.
Being wrong is part of doing new work
AI is going to create more experiments and more decisions made with incomplete information. That is not a reason to become cautious to the point of paralysis. It is a reason to become better at being wrong.
We need people who care more about getting to the right answer than being the person who had it first. And we need leaders who can hear “this is not working” without treating it as disloyalty.
I do not expect every project to be a slam dunk. Real work is messier than that.
I do expect us to be honest about what we believed, what actually happened, and what we are going to do now.
That is what accountability looks like when the answer was never obvious to begin with.