How to stop being your team's on-call problem solver

Executive overview

If your day is full of "hey, boss, got a minute?" interruptions, you haven't got a people problem — you've got a systems problem you created. Most team members default to escalating because it's faster and they've been rewarded for it. The 333 model installs three filters that force self-sufficiency before any problem reaches you.

Stop being the first step. Become the last.

The three-minute Google-first rule

• Before asking anyone, team members must spend three uninterrupted minutes finding the answer themselves — Google, ChatGPT, internal SOPs.
• 80% of questions are answerable this way; they just haven't tried.
• When someone brings you an unanswered question, ask: "What searches have you already done?" If the answer is none, send them back.
• Do this even when you know the answer — you're training behaviour, not just solving the problem.
• Builds resourcefulness; skipping it builds learned helplessness.

The three-peer rule

• If self-research fails, the team member must consult at least three peers before escalating to a manager.
• Peers can be colleagues, Slack channels, another department, or an external forum or Reddit thread.
• Simply articulating the problem out loud often surfaces the solution.
• Collaboration should happen horizontally first; vertical escalation is the fallback, not the default.

The 1-3-1 format

• Only after steps one and two are exhausted can someone bring the problem to you — and they can't arrive empty-handed.
• One problem: state the issue clearly in one to two sentences.
• Three possible solutions: proves they did the research; forces them to think before asking.
• One recommendation: they must have an opinion, plant a flag, and say why.
• No hypothesis means no learning, even when the answer is wrong.
• Ask for the 1-3-1 in Slack or email before any meeting — most of the time you can reply "proceed as you recommend" and skip the call entirely.