Why I Ask About Your History Before I Ever Sketch a Coin
Every mission that comes to me arrives with a shape already, whether the partner sees it yet or not. A unit's history, a leader's philosophy, the thing that carried someone through a deployment or quietly built into a chief's daily judgment calls: that shape exists before I ever open a sketchpad. My first move is never a design. It's a conversation.

I ask about the plaque no one mentions, the phrase a commander repeats until it stops sounding like advice and starts sounding like identity, the small habit that explains twenty years of decisions. None of it looks like design input. All of it becomes the design.
Skip this step, and you get a coin assembled from a catalog: a rank, a motto, a border, put together fast and forgotten faster. Sit in the conversation first, and something different happens. The eagle isn't generic. It's the one from a specific squadron patch a partner wore for a decade. The line of text isn't inspirational filler. It's something they actually said, about something that actually happened to them.
I call this stage Discovery, though the name matters less than what it protects: the discipline of listening before I know what I'm going to make. Understanding always precedes design. Everything that follows this conversation is translation, not invention.
In practice, most partners don't actually know how to put what's in their head into words, and that's the real work of Discovery. Part of my job is walking through the idea with them and pulling out pieces they wouldn't think to mention, details they don't consider important to the bigger picture. Those overlooked moments, in my experience, are exactly what take a coin from being just something handed out to something that actually tells a story.


Comments