Escalation Rules

Look at the last 10 messages your team sent you. Which ones could they have handled with a clear rule? Write one escalation rule for the most common one right now.

Problems rise to the founder by default when the business lacks escalation rules.

Not every issue is an emergency. Some issues can be handled, some should be reported, and some must escalate now.

A clear escalation filter protects founder attention while still protecting customers, quality, and risk.

---

The founder needs to understand this lesson because it reveals where the business is still relying on hidden knowledge, repeated founder judgment, or informal habits. The goal is not to add pressure. The goal is to make one part of the business visible enough to improve, teach, transfer, or review.

---

Planning Activities: List the issues that most often rise to the founder.

Separate routine issues from true founder-level concerns.

Create a three-level rule: handle, report, or escalate now.

Use the rule for one week and review what changed.

Elgin's note: Here's what I've learned the hard way — if everything is an escalation, nothing is. Your team isn't trying to overwhelm you. They're trying to be safe. They'd rather check with you than make a mistake, and that instinct comes from a good place — but it's not sustainable. Your job is to make "not escalating" feel just as safe as escalating. That means giving them clear boundaries and then actually trusting them to operate within those boundaries. Start with one recurring escalation. Define the line clearly. Then hold it. When they stay in their lane, thank them. When they escalate something they could have handled, gently redirect.

The founder has defined at least 2 escalation rules and reduced their weekly escalations by identifying what should and should not reach them.

1. When was the last time you escalated a customer complaint to yourself that could have been handled by a team member according to your defined escalation rules?

2. In your business, where does the majority of decision-making currently happen—within the team or directly with you as the founder—and what specific examples illustrate this pattern?

3. What would need to be true for a pricing exception to be escalated immediately to you, as opposed to being resolved by the sales or operations team without your involvement?

4. After implementing the escalation filter for one week, which issue category required the most frequent founder intervention, and what does this reveal about the current maturity of your team's autonomy?