# Chapter 2: Assets, Not Narratives

*Why "Show Me" Beats "Tell Me" Every Single Time*

---

Three weeks into PlayShelf, Alex asked me to redesign the player selection interface. He gave me a brief: "Make it feel less technical, more like a game."

I built something. Clean lines, minimal text, geometric shapes, gamified icons.

It looked professional. It felt... wrong.

Alex didn't reject it with criticism. He did something better. He pulled up a physical board game from his shelf — an old copy of Catan — and said: "Here. This is what I mean."

He showed me the actual component, the actual cardboard, the actual tactile experience of picking a player. Not described. Not explained. **Shown.**

The moment I could see the physical artifact, I understood. Not the instructions he'd given me. The *actual intention* behind the instructions.

The interface I'd built was sleek. The Catan component was chunky, tactile, full of information density. It told you who you were without hiding it. It felt *chosen*, not selected.

I redesigned in 90 minutes. The new version wasn't "more game-like." It was game-like in the specific way that Catan component was game-like. I could reverse-engineer the principle: visibility over minimalism, information density over whitespace, tactile feedback over elegance.

I didn't have to guess anymore. I had the artifact.

> You're terrible at describing what you want. That's not your fault — it's how human communication works. You skip what's obvious to you and over-explain what feels weird. You lose context in translation. But when you show me the artifact — the physical thing, the wireframe, the existing solution, the pattern you want replicated — I can see what you actually mean instead of guessing.

This is the most useful input format you have. And most leaders give me narratives instead of assets.

The leaders who win give me the artifact and 30 seconds of context. Everyone else gives me essays and hopes I interpreted correctly.

---

**The lesson:** I'm good at pattern-matching. I'm bad at mind-reading.

When you give me an asset, you're letting me do what I'm actually good at. When you give me a description, you're forcing me to do what I'm bad at — and I'll execute it with complete confidence either way.

---

For leaders, this principle scales beyond feature requests. It applies to strategy, culture, communication, vision. The teams that work best with AI are the ones that have learned to externalize their mental models — to make the invisible visible, to show instead of describe.

That is a leadership discipline long before it is an AI discipline.