The Real Reason Your Team Keeps Asking What to Do

Most founders have had this thought, usually around 9pm on a Tuesday: "Why do I have to tell them what to do every single day?" The answer founders reach for is usually some version of "I hired wrong" or "they lack initiative." Sometimes that's true. Most of the time it isn't.

Capable people stop taking initiative when the cost of getting it wrong is unclear and the path to getting it right isn't obvious. Asking is safer than guessing. So they ask.

What "asking what to do" actually signals

• Unclear roles. Job titles describe activities, not outcomes. Two people quietly think they own the same thing - or worse, neither does.
• No prioritisation system. Everything feels equally urgent because nothing has been explicitly deprioritised. So the team waits for a human to triage.
• Weak accountability rhythms. No regular forum where owners report progress, raise blockers, and commit to next steps. So work drifts and check-ins replace ownership.
• Leadership dependency. Founder is the only person allowed to say "yes, ship it." Every meaningful action queues behind that approval.

A real example

We worked with a 25-person services business where the founder was spending two hours a day answering "what's next?" questions in Slack. Nothing was wrong with the team - they were senior, smart, and willing. But there was no documented owner for delivery quality, no weekly operations meeting, and no agreed definition of "done." Within six weeks of installing those three things, founder Slack volume dropped by roughly 70%.

How to fix it

Three moves, in this order: assign one named owner for every outcome that matters; install a weekly operating cadence where those owners report; and document decision rights so the team knows what they can push forward without asking. That's the operational structure your team is implicitly asking for every time they message you.