Conviction versus Confidence
AI creates polished documents giving the appearance of conviction. But there's a difference between an idea you're confident about and a pressure tested belief to act on
A strange thing happens when everyone can create a strategy document in five minutes. I’m learning that sometimes all it takes to make people take an idea seriously is clean headings and organized sections.
AI creates a lot more polished ideas than should be taken seriously. The idea jar fills up with clean-room opinions hiding sloppy arguments.
A lot of product work used to stall because people could not get the first version of an idea out of their head and it’s genuinely useful to have something like AI to get past the blank page. Used well, AI helps explore more options, find missing pieces, and make rough thinking easier to inspect.
But with AI, easier done than said.
Polish is not a substitute for building conviction
Good work starts as an idea. The job great product work needs to continue doing is turning raw ideas and opinions into beliefs worth acting on.
It becomes believable when its put under pressure. The more pressure and scrutiny, the more useful it becomes.
A clean document that hasn’t been scrutinized presents a weak opinion like a coherent belief. More opinions just create more interpretive labor for everyone else.
An idea is simply a possibility. It says, “This might matter.” An opinion goes further. It says, “I think this matters.” A belief worth acting on says, “I have enough reason to ask other people to spend attention, time, or tradeoffs on this.”
You cannot jump straight to that last step through better formatting. The belief has to be tested before the organization should be convinced.
The old constraint was effort. Any reasonable plan took time. A strategy, roadmap, implementation plan, or architecture all had to be thoughtfully drafted. In that processes some bad opinions died.
That was never a perfect filter. Plenty of bad ideas survived because the person behind them had authority, stamina, or a better slide deck, but the effort did create friction. It forced at least some thinking before an opinion became material.
A clean artifact can make unfinished thinking feel more complete than it isAI weakens that friction. Now anyone can show up with an attractive argument for almost anything, and quickly. The danger is not that these outputs are useless. The danger is that they are plausible enough to believe in before you should.
Recently, I heard about an AI-forward leader who joined an company and immediately criticized engineering practices, then began sending out AI-generated plans at a pace the organization could not absorb.
I don’t know the exact contents of every proposal, and I think the issue was that they were not thought through more than they were obviously terrible. The plans sounded coherent, but they assumed too much about how the company worked. They leaned on assumptions and details that were incorrect.
At first, people treated the plans seriously. Architects and technical leaders could see the gaps and tried to respond with the same rigor they would bring to any proposal. But the volume kept increasing. By the time someone was ready to discuss one plan, the author had moved on to another.
After more than fifteen proposals in a few weeks, people stopped engaging. Eventually, technical leaders said out loud that they were not going to entertain these plans anymore.
That is the second-order cost. Bad AI output does more than waste the time spent reading it. It burns the trust required for the next idea to get a fair shake.
Ideas Are Cheap. Beliefs Have a Carrying Cost.
There is nothing wrong with having more ideas. Most teams need more of them, not fewer. The problem starts when every idea arrives dressed as if it has already been vetted.
Product work has always involved turning opinions into something more useful. You need to understand why a problem matters to a customer, to interpret market changes, and to evaluate the opportunity when someone suspects a feature will change behavior.
A belief worth acting on carries more weight because it asks something from other people. It may ask a team to change direction, a leader to spend political capital, an engineer to absorb complexity, or a customer-facing team to explain a shift they did not choose. If the belief is wrong, time gets wasted, attention gets spent, opportunity gets lost, and other people live with the consequences.
Conviction is what forms when a belief has been through that because it’s purpose is to ask the organization to carry more. A conviction has come out the other side of being exposed to reality, absorbing objections, and meeting challenges. It has changed shape after contact with people who do not already agree.
That is why conviction is different from confidence. Confidence can come from fluency, status, repetition, or the pleasant feeling of seeing your own thought reflected back in better prose. Conviction has a history. It’s more visceral.
When someone has conviction, they can explain not only why they believe something, but what would make them stop believing it. That is one of the simplest tests. If an argument has no possible disconfirming signal, it may be an identity, a preference, or a political position. It is not yet a belief worth acting on.
The old world rewarded confidence too much
I’m tempted to romanticize the old world because the new one is noisy. But the ways of working before AI way had plenty of weaknesses I’m happy to leave behind. Writing effort filtered out some shallow thinking, but it also filtered out people who had good ideas and less time, less confidence, less status, or less skill turning messy insight into executive prose.
There is an obvious counterargument here: organizations were never great at distinguishing conviction from performance.
So many companies already over-reward confidence. The person who speaks clearly often beats the person who understands the problem better. The person with the crisp narrative often beat the person carrying messy but important nuance. Product teams have always been vulnerable to well-packaged opinions.
So the problem is not entirely new. AI did not invent shallow certainty. What it changes is the amount.
There’s a famous quote about how communicating something simply is hard because you have to understand it at a deeper level. Those same principles make sense here when building conviction. a clean document used to suggest that someone had done some work and dedicated some combination of time, skill, access, and preparation. Now the polish is cheap. Those signals no longer mean as much.
It’s easier to create ten plausible strategy documents before the team has one serious conversation about what problem it needs to solve.
This is the second-order effect: AI doesn’t just generate more artifacts. It lowers the trustworthiness of artifact quality as a proxy for judgment. That should make teams more careful about what they reward.
Plausibility is costly
Plausibility is generally a good indicator whether an idea is worth looking at more deeply.
The leader who sending fifteen proposals probably believed they were increasing optionality. In one sense, they were. Each document represented another plausible direction, another angle, another chance to improve something. But organizations do not experience optionality as a pile of documents. They experience it as attention cost.
Every plan asks something from its readers. It asks them to understand the claim, check the assumptions, map it against existing work, identify consequences, and decide whether to respond. A plausible plan consumes a surprising amount of energy because serious people do not want to dismiss something too quickly.
Historically, plans need to be evaluated and given the benefit of the doubt. But tomorrow, where the next plan arrives before the last one has been digested, the best practices are different.
That is the part leaders often miss. Credibility is not spent one bad idea at a time. It is spent through the pattern of asking other people to do interpretive labor you have not done yourself. If you repeatedly hand people polished ambiguity, they learn that your documents create work rather than clarity. Once that association forms, even your better ideas arrive damaged.
A Belief worth acting should imply accountability
AI is not the source of bad documents. A thoughtful human can write a lazy strategy. A careful person can use AI to sharpen a serious one. Conviction comes from the process of scrutinizing ideas and beliefs. It’s a relationship between belief and accountability.
For a rough idea, accountability can and should be light. “I’m playing with a thought. Can you help me see what I’m missing?” That is a perfectly good use of AI-assisted thinking. It keeps the artifact in the right social posture. It invites critique instead of pretending the idea has already earned commitment.
For a plan, the accountability bar is higher. A plan needs show the work and make the causal chain visible. If we do this, what changes? Why do we believe that change matters? What are we choosing not to do? What evidence do we have? What would we watch first to know if we are wrong?
For a strategy, the bar is higher still. Strategy requires attention across an entire organization. It changes priorities, creates winners and losers, and asks teams to align their local judgment to a shared bet. A strategy document that has not been vetted is not neutral, it creates drag.
The answer is not to avoid AI-generated drafts. That would throw away the useful part.
The answer is to use AI earlier in the thinking process and be more disciplined about what gets promoted into organizational material.
Use AI to explore the idea before you believe it. Ask for counterarguments, what assumptions are doing the most work, or what evidence would change the recommendation. Ask for three versions of the argument aimed at three different skeptical audiences. Ask where the plan is likely to fail in a real organization.
Then do the human part. Talk to the people who know the terrain. Check the constraints. Look at the history. Compare the idea against the work already in motion. Decide what you actually believe after the easy fluency has worn off.
The mistake is using AI to skip the discomfort where conviction forms. That discomfort isn’t wasteful, it’s the part of the process where a person becomes responsible for the belief.
A useful rule is to label the maturity of the artifact before sharing it. Is this an idea, a draft argument, a recommendation, or a decision proposal? Each one deserves a different response. If you send an idea with the costume of a decision proposal, you create confusion. If you send a recommendation that has only done the work of an idea, you create mistrust.
Teams need these distinctions more now because the artifacts all look increasingly similar. The formatting no longer tells you how much thinking happened.
Scarcity is a new discipline
When documents were expensive, scarcity was built into the system. You could still misuse attention, but the cost of creating material slowed you down. Now scarcity has to be chosen.
That means being more careful about what deserves a meeting, what deserves review, and what deserves a request for other people’s time. Attention as a shared asset, not an infinite inbox. Leaders have to model restraint, because leaders can turn their unfinished thoughts into other people’s work faster than anyone else.
It also means teams need permission to say, “This is not ready for review.” when the belief has not yet been made accountable enough to justify the attention it is asking for.
That sentence may feel harsh in a culture that wants to encourage ideas. But encouraging ideas does not mean accepting every polished artifact as a serious proposal. In fact, the best way to protect good ideas is to keep the early ones in a form where they can be improved without pretending they are ready.
There is a difference between “help me think” and “please evaluate this plan.” AI makes it very easy to blur that difference. Healthy teams will make it explicit again.
The Test
Before sharing your next plan, especially and AI-drafted one, ask a few questions:
What do I actually believe here?
What evidence, experience, or constraint makes me believe it?
What is the strongest argument against it?
What would change my mind?
Who will have to spend attention because I shared this?
If those questions feel annoying, that is probably a signal. They are the friction that used to be hidden inside the effort of making the document. Now the document is easy, so the friction has to move into judgment.
AI can help create more ideas. That is useful. But an idea is only the beginning of product work. The real work starts when you and others decide the idea matters enough to test, shape, defend, revise, or abandon.
That is the difference between an idea and a belief worth acting on. Between confidence and conviction. One can be generated in minutes. The other has to be earned.