My 1st Question
The first time I talk to a business owner, before I open a spreadsheet, sit in on a meeting, or ask to see an org chart, I ask the same question. It costs nothing, takes no preparation, and usually gets answered in under 1 minute.
"If you stepped away for a month - no laptop, no wifi, no phone calls - what would break first?"
I've asked this question across media houses, radio stations, law firms, healthcare, technology startups, family businesses - different businesses, different stages - some long in the tooth others finding their footing. But, Different businesses, the same pause.
That pause » someone trying to figure out a truth they've never said out loud.
Why I ask it before anything else
Most audits start with documents - process maps, org charts, financial statements. Useful things, but they describe the business as it's supposed to work. My question gets to the real heart of your business and how it actually works, because it forces you to test your assumptions live, with no notes, no paperwork.
And let’s be clear - there is no "correct" answer. There isn't one. I'm listening for what your answer points to - a person, a process, a system. Oftentimes, that’s the whole diagnosis, right there, in the first question and one response.
What the answers usually reveal
Typically, the answers cluster into process, people, and systems. And the answer is the information that points to the first move.
"Honestly? Payroll wouldn't run." This is a process gap wearing a person's clothes. Somewhere, a step that should be documented and delegable is living entirely in someone's head instead - often it’s yours.
You can start here: write the steps down, even roughly, even in a messy list on your phone. That's the whole first move, and it's usually a twenty-minute job that's been avoided for years.
"My ops manager would keep it going." Better, but this is a dependency and needs a second question: what happens if your ops manager is the one who steps away? If the answer is "the same thing happens again, one level down," the dependency hasn't been removed. It's been relocated.
You can start here: ask your ops manager the exact question I ask you. Their pause will tell you where the dependency actually sits.
"Clients/customers wouldn’t know X,Y,Z , because they only really deal with me." This is a relationship-based risk, and it's common in service businesses that grew on the strength of one person's reputation (which is exactly how most good businesses start). It’s not a problem that it started that way, it’s a problem if it's that way years later.
You can start here: pick one client relationship and introduce a second point of contact this month - it doesn’t have to be the whole account, just a single touchpoint. A call they get cc'd on. A check-in someone else makes.
"Honestly, probably nothing. The team's got it." This one is rare, and worth celebrating when it's true. But I've learned this answer should get treated the same way I would with anyone who says they never argue - I ask a few more questions before I believe it.
You can start here: ask two team members the same question, separately, without telling them what the other said. If their answers match, you likely do have what you think you have. If they don't, that gap identified is worth more than the original answer, and that is the truth.
Founder dependency isn't a personal failing
I don't ask it to catch anyone out, I know my first question can feel exposing.
Founder dependency isn't a character flaw; it's naturally occurring when someone builds something.
You're the fastest decision-maker, the most complete source of institutional knowledge, and the person everyone defaults to when something's unclear. That's not dysfunction - it’s what founding a business looks like in year 1, year 2, sometimes year 5.
It’s only a point of concern when that’s still the reality after your business has grown bigger than what one person can hold in their head.
You want a process, not a person.
A fragile business is one where the answer to "what breaks first" is a name.
A resilient one is where the answer is a process - something documented, delegated, and tested, that would run whether that person was on a beach or in the building.
That distinction is the entire difference between a business and a demanding job.
Systems aren't admin. Properly built they protect the one asset every other asset in the business depends on: each team member’s capacity to think clearly, without holding everything in their head at the same time, and allows folks to breathe without the concern that it will all fall apart.
That's what the question is really asking. Not "what would break" — but "how much of this business is currently living inside you or someone else, and what would it take to get it living somewhere more tangible?"
DIY
You don't need to book a month away to get useful information out of this and I wouldn't recommend testing it at full stakes as your first attempt anyway.
Here's the no consultant required version. ✅ #winning
Pick your week. Not a full disappearance, just a genuine stepping-back from being the default answer in three areas.
1️⃣ a decision that usually comes to you,
2️⃣ a client or supplier relationship you usually manage personally,
3️⃣ and one operational task you usually handle yourself.
⇢Hand each one off deliberately
and
✖︎ Don't quietly check in behind the scenes.
At the end of the week, ask three questions:
⓵ Did it get done, and how?
⓶ Did the person handling it know what to do, or were they guessing?
⓷ Is there anything written down - a process, a note, a template - or did it only work because you were there to explain it?
If the honest answer to that last one is "nowhere, it was just in my head," that's not a failure. That's your starting point.
You've just found the exact place your business is currently held together by your presence rather than a process. Write it down. That's the first system you build.
✶
Your DIY will tell you where the gap is; closing it so it doesn't reopen in six months will require a slightly more specialised skill - that’s where I come in. 👋🏾
take care of you,
ZB.
Wi,Mi is based in Trinidad and Tobago and works with SMEs across the Caribbean and internationally. If your business is ready for that work, wherever you are, the conversation starts via 📋contact form, 📧 email hello@whatismustis.com or 📆 book a chat one time.
