Stop Answering the Same Question Three Times

Brooks Duncan has a simple rule. If you make the same mistake twice, like spilling coffee in the same spot, you don’t need a third time to know a systemic change is required. The root cause is often the environment or the process, not just the person. Fix the layout. Fix the system. Do it after the second occurrence.

Most people would double down on being more careful. The better move is to change the setup so the spill is hard to repeat.

Does this sound familiar?

You keep answering the same email. You keep chasing the same deadline. You keep sitting in the same 60-minute meeting that needed 25. Then you treat it as a discipline problem and try harder.

Brooks’s version fires at two times. For managers, the inbox usually hands you a third data point. That’s the tell. Look at last week’s mail. What’s repeating?

When the same question shows up three times, stop answering it

If you receive the same question from different team members three times via email, that’s a signal to fix the system, not just answer the question. Create a knowledge base article. Update onboarding training. Improve documentation so the information is self-serviceable.

Audit your inbox for the most repeated question and create a one-page FAQ for it. Then send the link instead of rewriting the same paragraph.

Every email needs a destination

Effective managers never let an email sit unprocessed. Every message gets one of four actions immediately:

Delete. It’s done. It’s gone.

Defer. Put it on a task list so the inbox isn’t storing the work.

Delegate. Forward it with context. Context matters. A naked forward just moves the confusion.

Do. If it takes less than 2 minutes, handle it now.

That’s the Four D framework. Copy those four actions onto a checklist and process mail against it until you stop using the inbox as a holding pen. Always assign a destination. That’s how you prevent inbox buildup.

Long emails are a seniority tell

In large organizations, email length inversely correlates with seniority. Middle managers often write long emails to demonstrate thought process. Senior leaders write 3-sentence emails that get straight to the point.

As volume increases, brevity becomes a necessity for effectiveness. Shorten your next 5 emails by 50%. Cut the warmup. Cut the recap everyone already knows. Point, ask, done.

Are you writing to demonstrate your thinking, or to move the work?

You can be responsive without living in your inbox

Here’s the thing. Effective managers are highly responsive, but they do not keep their inbox open all day. They check email at fixed intervals, every hour, so the team still experiences them as available. Then they strictly block out deep work time to protect their own output.

The common fear is that managers must be always on. You can support the team and still protect individual focus. Those two jobs can sit next to each other if email happens on a schedule.

Try a 60-minute email check-in schedule for one week. Close the inbox between checks. Check on the hour. Then go back to deep work.

Follow up on the day of, not the day after

Want accountability without micromanaging? Maintain a list of all promises made by team members with specific deadlines. Check in on the day the task is due, not the day after.

That timely nudge increases the likelihood of completion. It shows you’re paying attention. Put the commitments in a task manager so you’re not relying on memory or a buried thread. The timing is the tactic. Same-day. While the deadline is still the deadline.

Got a recurring minor annoyance you’ve been ignoring? Name it. Change the environment or the process around it. You don’t need a third spill.

Make 25 minutes the default

Back-to-back 60-minute meetings create burnout and leave no prep time. Default to 25-minute meetings instead of 60. The shorter block forces agenda discipline (Parkinson’s Law). You also get a 5-minute buffer between meetings to breathe, prep, or reset. Meeting quality and energy levels improve.

Schedule your next 3 meetings as 25-minute blocks.

If you don’t need to actively lead a meeting, you don’t have to participate in the whole thing. Use an AI note-taker like Otter or Lindy as a meeting delegate. The AI joins, records the transcript, and extracts action items. You can be in two meetings at once, or attend while doing deep work, then query the transcript later for specific details instead of asking colleagues. Attending and participating are different jobs. Test one of those tools this week on a meeting you don’t need to run.

If your A-players never disagree, that’s a problem

A manager should explicitly value and request disagreement from high-performing team members. If an A-player never challenges your ideas, it’s a red flag that the team lacks psychological safety.

Invite people to poke holes in your proposals. That’s how you extract better ideas and prevent the Yes Ladder. In your next meeting, ask: “What am I missing?”

Then wait.

Stay in permanent beta

Effective leaders treat themselves as permanent beta versions. They consistently invest in their own productivity and skills (reading, courses, podcasts) not just for themselves, but to model the behavior they expect from their team. Leading by example in self-improvement is a primary driver of team performance.

Pick one learning activity for the week. One week, one change. If you want a team that invests in their craft, they need to see you investing in yours. Put the activity on the calendar for this week.

Don’t install all of this on Monday. Start with the repeat. Find the question you’ve answered three times. Write the one-page FAQ. Send that instead of another long email.