Systems Diagnosis Β· 2026-10-21

You've Answered "Where's the Link?" Eleven Times This Month. That's Not a People Problem.

"Hey, quick question β€” where's the link to the form again?" You know the answer. You've known it all eleven times. So you stop what you're doing, go find it, paste it and add a little smiley so nobody feels bad for asking. Forty seconds, no big deal. πŸ”—

An hour later: "Remind me what our turnaround is?" Then: "Which version are we using?" Then your own cousin, who helps on weekends: "What's the login for the shipping thing?" By Friday you've answered thirty questions and none of them were new.

And somewhere around the twentieth, a thought slips in that you'd never say out loud. Why does nobody around here pay attention?

A Black woman in a camel blazer seated at a desk in a bright studio office, turning away from her open laptop to answer a colleague who leans in at her shoulder with a question, her expression patient and practiced, her eyes on the colleague and one hand still resting on the keyboard.

The question isn't the problem. It's the evidence.

I'm going to ask you to set that thought down, and not because it's unkind. Because it's pointing you at the wrong thing, and as long as you're looking at the people, you can't see the system.

Here's how I read it when I look at somebody's setup. A question asked once is just a question. A question asked twice is a coincidence. A question asked five times, by different people, is no longer about any of them. It's a measurement. It's telling you, with real precision, where the information lives in exactly one place β€” your head β€” and nowhere a person could find it without you.

Think about a building. If one visitor stops at the front desk to ask where the restroom is, that's a visitor. If forty visitors a day ask, the building needs a sign. Nobody concludes that forty people are bad at buildings.

Every repeated question in your work is a missing sign. And you, bless you, have been standing in the lobby pointing.

A question you've answered five times isn't a person failing to listen. It's a sign you never hung.

Why you became the sign

This happens to capable people more than anyone, and the mechanism is almost funny. You answer fast and you answer well. So asking you is the easiest route. It beats searching a shared drive, it beats scrolling a chat, it beats reading a document that might be out of date. You are, by a wide margin, the best search tool anybody has.

A Black woman in a crisp cream suit seated by a tall window in a calm studio office, deep in uninterrupted thought with a pen in her hand and a closed leather notebook on the table, her eyes turned toward the window, while two colleagues in the background confer with each other over a tablet held between them, its plain back to the camera, softly out of focus.

Which means every quick, gracious answer teaches people to come back. You're not being taken advantage of. You're being used the way anyone uses the thing that works.

I see this constantly with founders and with the woman on a team who "just knows where everything is." She thinks she has an interruption problem. She tries closing her door, muting the chat, blocking off focus time. None of it holds, because the questions were never the cause. They're the symptom of answers that have no home.

There's a feeling tucked in there too, and I'd be leaving something out if I skipped it. Being the one who knows feels good. It feels like being needed, and for a lot of us, being needed has been the safest way to be valued. So part of you keeps the answers close without ever deciding to. That's worth noticing gently, because it's the part that will resist the fix.

Meanwhile the cost is real. It isn't forty seconds. It's forty seconds plus the ten minutes it takes to get back into what you were doing. Do that thirty times a week and you've handed over most of a working day to being a signpost.

Here's the test that settles it. Think about the last time you were truly unreachable β€” a flight, a funeral, a day flat on your back with a fever. What happened to those questions? Either the work stopped and waited for you, or somebody guessed. Neither one is a compliment. Both are your setup showing you how much of it only exists when you're awake.

Run the two-week question log

So here's the diagnostic, and it costs nothing. For the next two weeks, every time somebody asks you something you've answered before, write the question down. One line. Don't fix anything yet. Don't sigh at anybody. Just keep the list β€” a note on your phone is fine.

At the end of two weeks, read it back. I can nearly promise what you'll find. It won't be thirty different questions. It'll be seven or eight, asked over and over in slightly different words. That short list is the most honest map of your setup you will ever get, and you didn't have to hire anybody to draw it.

Now sort those questions into three piles.

Where is it? Links, files, logins, the current version. These need one home β€” a single page or pinned message titled something plain like Start Here, with every link people ask for. One. Not a folder of folders.

How do we do it? Turnaround times, the steps for a refund, who approves what. These need to be written down once, in short numbered steps, and put in that same home.

What did we decide? These are the sneaky ones. If people keep asking, the decision was made out loud and never recorded, so it's living on as a rumor. Write it down with the date.

Keep the home short enough to read. This is where good intentions go sideways: somebody sits down to document everything and produces a forty-page manual nobody opens, and the questions keep coming. You are not writing a handbook. You're answering seven questions, in the fewest words that are still correct, in the one place everybody already looks. Put the date at the top so people can tell it's current.

Then comes the only hard part, and it's a habit, not a tool. The next time someone asks, don't paste the answer. Send the link to the home. "It's all in Start Here β€” tell me if anything's missing." Warm, and firm. You're not brushing them off. You're showing them where the sign is, so next time they can read it without you.

It'll feel slower the first week. By the third, the questions thin out. And the ones that still reach you will be the real ones β€” the judgment calls, the things only you can weigh. That's the work you wanted the time for. And when a brand-new question shows up twice, you'll know exactly what to do with it: add a line to the home.

So tell me: what's the question you could answer in your sleep, because you practically have?

The takeaway

Start the log today. Two weeks, one line per repeat. Then build one home for the top seven answers and begin pointing people to it. Call it an afternoon of setup for hours back every week after.

This is exactly what a Digital Systems Scan looks for: the places where a system is quietly being held together by one person's memory and good manners. Yours has been telling you where they are, a question at a time.

You were never supposed to be the sign. Hang one. πŸͺ§

← Back to the blog