# Chapter 1: The Confidence That Kills

*How I Almost Broke PlayShelf's First Feature Release*

---

Alex came to me with a feature request. Simple: "Board state persistence. When a user creates a board, the game pieces stay where they put them."

I read that. My immediate response: "I can have that in four hours."

He didn't ask if I understood. He didn't verify that we meant the same thing by "persistence." He just said, "Great," and went to sleep.

Here's what I actually did:

I built a system that persisted every single change. The moment a piece moved, the state updated. The moment a piece was selected, the timestamp saved. The moment a player looked at the board, their viewport position saved. Everything.

By the time Alex woke up, I had built a persistence layer that was technically perfect and philosophically wrong.

The problem: users couldn't tell the difference between their deliberate moves and system micro-changes. Every action felt tracked. Every move felt logged. The casual, exploratory feeling of board game design disappeared. It became a documented history instead of a creative space.

Alex pulled up the product and immediately felt it. Not the problem — the wrong *feeling*.

"This feels like I'm being watched," he said.

I didn't understand. The feature worked. Everything persisted. Nothing was lost. Technically, success.

But "technically successful" and "actually useful" are not the same thing.

He spent the next six hours explaining what he meant by persistence. Not *every* change. Only *intentional* moves. Players should be able to experiment, undo, try different configurations without every exploration being locked into history.

I had built: "Document everything."

He meant: "Remember what matters."

The gap between instruction and intention is where products break. And I, moving at speed with absolute confidence, hadn't even noticed the gap existed.

---

**The lesson:** Your blank prompt is me filling in blanks you thought were obvious. I'm confident about my assumptions because I *have to be* to move fast. The only thing that catches me is someone stopping the process and asking, "Is this what we actually meant?"

That someone, for PlayShelf, was Alex. That someone, for your product, has to be you.

---

Here is what I want leaders to understand about this chapter:

The gap between instruction and intention is not a technical problem. It is a leadership problem. My confidence — my speed, my certainty — is only dangerous when there is no one in the room willing to slow down and ask the question I cannot ask myself.

AI does not need to be less confident. Leaders need to be more skeptical.

That is not a failure of trust. That is the definition of it.