You can't declare a Why. You have to go find it.

🔥

I forced a Why once. It didn't work, and it took me about a decade to understand why.

I'd seen Simon Sinek's "Start With Why" talk when it came out, the Golden Circle, Why-How-What. That's not my idea. It's his. And it's a good one, which is exactly why we grabbed it. This was back at an agency I worked at, and we used Why-How-What as a culture thing. We sat down to declare our Why because it sounded good, because it was the kind of thing a sharp agency was supposed to have. We were copying what other agencies were doing. We weren't that mature at the time and thought we could just invent these things. So we did. We wrote one down. It read fine. It moved nothing.

Then I left, went into the consulting world, and Why-How-What went dormant for me. I didn't think about it for years. It wasn't until about ten years later that it came back through Tom.

When Tom started doing brand work for our clients, he kept saying two things. The first: "You are what your customer says you are." The second, the one that actually reordered how I think about this: "I want to find out for myself, from the customer."

That's when it clicked. Not because the framework was new. I'd had the framework for a decade. It clicked because Tom wasn't declaring anything. He was going to look.

The mistake I made at the agency was treating the Why like a mirror. Sit down, look inward, write what you see, call it true. What you get is a reflection of what you already assumed about yourself, dressed up well enough to sound like a discovery.

What Tom does is turn the mirror into a window. He says it plainly: "If it sounds to me like you're looking in the mirror, turn that mirror into a window and look through it and see the customer or the user or the audience on the other side and talk to them about them."

He doesn't ask the brand what it believes. He goes to the people who buy and finds out what they already know. The Why was never inside us waiting to be phrased correctly. It was on the other side of the glass the whole time, in the customer's own words, and the work was going to find it instead of inventing it. Tom puts the reason bluntly: "Few people care about you when they're reading or consuming or viewing or deciding and shopping. They care about themselves."

So the Why was never ours to declare. It belonged to them.

This is the part that matters now, because the same mistake is everywhere in how people build with AI.

The default move is to write a posture into the system because it sounds right. "You are a helpful assistant." You declare what the thing is supposed to be, the same way we declared what our agency was supposed to be, and for the same reason: it sounds good and everyone else is doing it. Copied, not excavated. Invented, not found. It reads fine. It moved nothing.

When I built Duke, the orchestrator that runs my firm's operating system, I didn't get anywhere by declaring his character. The character came out of the actual decisions, the real client work, the corrections I gave him over and over, the way the firm actually behaves under pressure. The Brand Guardian we build for a client works the same way. It isn't a posture we assigned. It's the customer-validated reason people buy, excavated and written down so the system can hold to it.

AI did not generate it. AI revealed it.

Go look. Don't guess. I spent years thinking a Why was something you sit down and write. It was the thing I copied, the thing I tried to invent, the thing I then forgot about for a decade. The day I stopped declaring it and started finding it was the day it got real.

That's the whole reason this season of Bullhorns & Bullseyes is built around Solve for Why. Not declare it. Not phrase it well. Solve for it, the way you solve for anything you don't yet have: by going to where the answer actually lives and bringing it back.

12 comments

You can't declare a Why. You have to go find it.