“I Think So-and-So Knows How to Do That…”
Why That Phrase Is Quietly Costing Your Company Thousands
Let me guess — you've heard this one before:
“Oh yeah, I think so-and-so knows how to do that…”
It’s one of those phrases that sounds harmless… until you realize it’s actually a giant neon sign blinking: “WE HAVE NO IDEA HOW OUR OWN SYSTEMS WORK.”
I’ve heard this line in fast-growing startups, legacy enterprise orgs, lean agencies, and chaotic RevOps teams.
It always means the same thing:
👉 Tribal knowledge is running the show.
And when that’s true, your team’s operational integrity is held together by duct tape, Slack DMs, and the sheer willpower of one or two “hero employees.”
Let’s unpack what that really means — and how it quietly destroys scale.
👻 What “So-and-So” Really Means
When someone says “so-and-so” — they’re referring to that one person who knows how everything works.
Every company has one:
That person becomes the human API for your business.
Everyone else?
They ping. They guess. They wing it.
And here’s the issue...
What happens when So-and-So goes on vacation? Gets sick? Quits? Takes another offer?
💣 Boom. Instant chaos.
😬 The Real Cost of “Just Ask So-and-So”
This isn’t about being disorganized.
This is about risk. Real, measurable, expensive risk.
Here’s what’s happening behind the scenes:
🧠 This Isn’t a Tech Problem. It’s a System Problem.
You’re probably already using some of these tools:
And yet… it’s still chaos.
You don’t need more tools. You need a system. A playbook. A structure your team can follow.
🔁 The Difference Between Documentation and Enablement
A lot of teams think:
“Well, we made some SOPs last year…” “There’s a doc somewhere in Notion…” “We recorded a Loom on that once…”
Cool. But here’s the truth bomb:
Documentation is not enablement.
If your knowledge isn’t:
…then it’s not helping your team. It’s just more noise buried in a folder no one can find.
🚨 How You Know You’re in the “So-and-So Trap”
Here’s your quick self-check.
If you’ve heard more than 3 of these in the last month:
You’re not alone.
You’re just at the breaking point of scale.
🧩 The Fix: Knowledge Enablement As A Service
That’s exactly why I built this.
It’s not consulting. It’s not training. It’s not just writing SOPs.
It’s a done-for-you infrastructure layer that:
✅ Audits your current chaos
✅ Prioritizes the biggest knowledge gaps
✅ Builds clear, clean SOPs and walkthroughs
✅ Structures your documentation into a real enablement hub
✅ Maintains it as you grow
Think of it like hiring a personal trainer for your internal operations.
No more guessing. No more “Just ask So-and-So.” Just clarity.
📅 Ready to Ditch the Chaos?
I’m opening a few pilot spots right now — founder-rate pricing, full system audit, and custom playbook builds.
On a 30-minute call, we’ll:
🔎 Identify your internal friction points
📉 Uncover the hidden cost of “we’ll figure it out later”
📈 Map out your enablement strategy — tailored to your team
✅ Show you what a real knowledge system could look like in your org
If you’re scaling and feeling the cracks, let’s fix it before it breaks.
Let’s make “I think so-and-so knows how to do that” disappear forever.
Not sure if it’s worth it yet? Ask yourself this:
“If [insert name] left today, what would break?”
If the answer is “a lot”… You already know.
Let’s clean it up.