What Your Gut Knows That Your Team Doesn’t
How instinct becomes a system, if you slow it down just long enough to transfer it
This week is Part 2 of Codify to Multiply™ - a series on how to turn the judgment in your head into an actual system your team (and AI) can run with. Because instinct is the start of pattern recognition that can be transferred.
Do you remember that moment when your team asked why you made that call… and you didn’t really have a neat answer?
You weren’t winging it.
You just knew!
It was that internal click. A YES you felt before you could explain.
You’d seen this pattern before.
The timing, the tone, the weight of the variables - they all pointed one way.
And you trusted it.
That’s what it feels like when instinct is running the show.
It’s fast, quiet, and usually right.
But to everyone else watching, it looks like magic. Or chaos.
Intuition vs. Instinct (And Why It Matters)
Let’s name something clearly here, especially for my readers who are deeply intuitive (like I am):
Not all “gut” is the same.
Intuition is the kind of knowing that goes beyond logic.
It’s spiritual. Energetic. Often felt, not learned.
It’s not something we’re trying to codify, and honestly, it’s not something that can be.
Instinct, on the other hand, is fast pattern recognition.
It’s built from experience. It’s what your brain knows how to do from years of processing situations quickly and unconsciously.
And that can be observed.
Which means it can be transferred.
Why It’s Worth Slowing Down
Instinct is built to move fast. But if you never pause to see what’s actually driving it - what filters, standards, or red flags are hidden inside - it stays trapped in your head.
Which means your team can’t learn it.
Your tools can’t mirror it.
And your impact stays capped.
This is one of the reasons so many founders end up stuck in “final filter” mode.
Because they never translated their instincts into something others can use.
Think Like A Michelin-Star Chef
A Michelin-star chef can plate a perfect dish from muscle memory.
They don’t need a recipe - they taste, feel, and adjust in real-time.
But if that chef never writes down the recipe - how they season, test, and time the dish…
no one else in the kitchen can replicate it.
Even if they’ve watched it a hundred times.
It’s not enough to observe the what.
To transfer excellence, you have to reveal the why and how beneath the what.
The Research Backs This
Gary Klein, a cognitive psychologist who studied decision-making in high-stakes fields (think firefighters, military ops, ER teams), coined the term recognition-primed decision making.
His research showed that the most experienced people make fast, high-stakes calls not because they’re guessing, but because they’re unconsciously comparing what’s happening now to hundreds of past patterns they’ve stored over time.
In other words, the “gut” isn’t mystical.
It’s your brain accessing deeply trained judgment in a flash.
That means it’s not just trustable.
It’s transferable, if you take the time to see what it’s really doing.
Codifying Instinct Is How You Teach Nuance
This is what most founders skip.
They’ll hand off tasks.
They’ll delegate decisions.
They’ll even write out the “why.”
But the nuance - the “when it’s this kind of yes” or “this shade of red flag” - never gets named.
Because it lives in instinct.
So what happens?
When It Doesn’t Get Codified…
You approve a hire that feels like a fit.
You can’t fully explain it, but something about the way they ask questions, the energy they carry, the timing of their responses - it all just clicks.
But because you never broke down what made it a yes… your team can’t use that judgment the next time.
So every hiring decision comes back to you.
Every launch question.
Every copy edit.
Every conflict resolution.
They’re lacking your filters (not skills), and those filters are invisible unless you name them.
You become the only person in the business with full access to the nuance, and that’s neither sustainable nor scalable.
It’s Not Just Business. It’s Every Relationship You Mentor.
This is something I’ve used in every corner of my life, not just in consulting.
I use it as a parent.
When my children ask questions about how I know something, or when teaching them a new perspective on something they’re facing, I take the time to explain not just the action… but the judgment behind it.
They’re not just learning what to do.
They’re learning how to think.
And that’s the difference between replicating and evolving.
Your Move
I want you to bring to mind one decision you made this week that felt instinctive.
Then pause and ask:
What triggered that decision?
What patterns or red flags did I recognize (even if I didn’t say them out loud)?
What made it feel like a “yes,” “no,” or “not now”?
Could I explain that logic to someone else, without diluting it?
You don’t need to codify it perfectly.
You just need to observe it.
That’s where transfer begins.
See you next week for Part 3!



I love how she names it so clearly — she really does nip it in the bud. Over the years I’ve grown much more conscious of my own instincts and have made a point of reverse-engineering my decision-making so I can better support my team.
It’s not easy work, especially in the fast-paced environments many of us operate in. Our insights come from such a wide range of sources that it’s not always possible — or even useful — to map it all out.
For me, the practice has been to keep things simple: extract the essence, let go of the unnecessary details, and trust that clarity serves better than complexity. With my own leaders, I guide that same transition by asking powerful questions that help them name the instinct they’re drawing from.
A great piece — thoughtful, grounded, and immediately applicable.