AI Is Extremely Confident. That’s the Problem.


Something strange has happened to product development.
Not long ago, building something new followed a familiar rhythm.
A sketch on a whiteboard. A prototype. Weeks of implementation. Then the slow realization that something in the original idea didn’t quite work.
Now the timeline looks different.
Days instead of months.
And strangely… the same mistake can repeat much faster.
The New Product Loop
Lately my workflow often looks like this:
- I write a PRD or propose a structural change.
- AI jumps in with full confidence.
- We start implementing immediately.
The response is almost always the same.
Totally solvable. Here are three great options.
Option #2 is amazing. Let’s do it like iOS.
It sounds convincing.
It often looks convincing.
So we build.
And then the loop begins.
- Iterate → Not quite right
- Iterate → Still not there
- Iterate → Maybe this version works?
- Iterate → Nope
The iterations themselves are incredibly fast.
That’s the magic of AI-assisted development.
But speed has a hidden side effect: you can iterate on the wrong idea much faster.
AI Is Confident by Design
Large language models are optimized to produce coherent and convincing answers.
Uncertainty rarely appears in the output.
Which means the system often behaves like the most confident engineer in the room.
Even when the underlying concept is flawed.
That creates an interesting dynamic in AI-driven development:
- AI accelerates execution
- Humans must detect flawed direction
In other words:
The bottleneck has moved from building things to recognizing when not to build them.
The Real Skill: Interrupting the Loop
The most valuable habit I’ve learned lately is interrupting the cycle early.
Instead of continuing iteration after iteration, sometimes the better move is to step sideways.
For example:
- reframing the problem
- exploring an existing library
- questioning the underlying interaction model
- asking whether the idea itself is wrong
A small nudge can change the trajectory dramatically.
One surprisingly effective prompt I've used:
Explore React libraries that already mimic the behavior you just described.
Instead of reinventing the wheel through endless AI iterations, you suddenly discover a solved problem.
Loop broken.
Faster Iteration Means Faster Wrong Turns
AI hasn’t eliminated product risk.
It has compressed it.
Ideas that previously took months to validate can now fail within days - which is actually a huge advantage if you notice early enough.
The challenge is recognizing the moment when you should stop iterating and rethink the premise.
Because the AI will happily keep going forever.
Human-in-the-Loop Is Not Optional
AI can generate solutions at incredible speed.
But it cannot reliably detect when a problem framing is wrong.
That part still belongs to humans.
Which makes the modern product workflow look something like this:
- Human → defines problem
- AI → proposes solutions
- Human → challenges direction
- AI → accelerates implementation
- Human → decides when to stop
The irony?
AI didn’t remove the human from the loop.
It made the human judgment step more important than ever.
The New Product Manager Superpower
In the age of AI-assisted development, the most valuable skill might no longer be writing specs or coordinating teams.
It might simply be this:
Noticing early when the idea itself is wrong.
Because once AI starts building, it builds fast.
And confidence comes included.
Curious how others handle this loop in AI-assisted development.
Do you interrupt early — or iterate until it works?
Related Posts
The Five Meters Back
A few weeks ago I gave in and built a Jira integration into the product I am building. I did not want it there. It points backwards, into the way of working I think is ending. For a while I filed that work under waste, until I heard what I was actually claiming: my thing is right, so the market should do the walking.
Nobody Asked Me to Write That Down
I used to take my backend developers into customer interviews. The understanding lived in the room, and we never wrote it down. It worked beautifully, and it left almost no trace. Product teams document their output obsessively and their reasoning almost never, which is why a strategy can walk out the door with one person.
I Made My People Good Enough to Quit
It sounds like a contradiction and it was the best retention strategy I ever had. You find the one thing someone is genuinely better at than you and you hand it over. The part I did not plan for is that it keeps working long after the job ends, and no performance review I ever filled in was able to see it.