The Lobbi Delivery Team
Operational Systems Engineering
Count the decisions waiting for you right now. The refund that needs a yes. The rush order that needs a price. The reorder, the overtime request, the small hire, the vendor exception. If the count is above five and it is not yet lunchtime, your business has a bottleneck, and it is your calendar.
Owner-dependency is the most common scaling limit we see, and the least examined — because it does not look like a problem. It looks like diligence. Every individual decision genuinely benefits from your judgment. But stack a few hundred of them a month and the aggregate is a business whose throughput equals your availability, whose response times stretch whenever you travel, and whose best people have learned that initiative means drafting an approval request.
Why "Delegate More" Fails
The standard advice is to let go and trust the team. Owners hear that as a trust-fall: hand over the decision and hope. They are right to hesitate. The team has watched decisions happen but has never seen the rules — because the rules exist only as patterns inside the owner's head. Asking someone to make your decisions without your criteria is asking them to guess, and the first wrong guess confirms everyone's fear and recentralizes everything.
The reframe that works: the team does not need your permission. It needs your decision rules. You are not unconsciously brilliant eleven times before 9 a.m. — you are applying a small set of consistent criteria you have never written down. Refunds under a few hundred dollars with photographed defects: always yes, same day, because the relationship is worth more than the part. Rush jobs: yes if the schedule has slack and the premium covers the disruption. Those are rules. They can be written. And what can be written can be applied by someone else, consistently, without you.
Externalizing the Rules
The method is a two-week self-audit followed by an honest writing exercise.
- Log every decision for two weeks. One line each: what was asked, what you decided, how long the asker waited. The log will embarrass you usefully — most owners find 70 to 80 percent of entries are repeats of a dozen underlying decision types.
- Write the rule you actually use. For each recurring type, draft the criteria as if instructing a capable new manager. Be concrete: thresholds in dollars, conditions in observable facts, the default answer, and the rare conditions that change it.
- Set the escalation boundary. Every rule ends with when to bring it to me — above this amount, outside these conditions, any case that feels wrong. A clear boundary is what makes the rest safely delegable.
- Assign each rule an owner. Not the decisions are delegated in general — this rule is applied by this role.
| Decision type | Rule | Escalate when |
|---|---|---|
| Refunds | Under $500 with defect evidence: approve same day | Over $500, repeat customer pattern |
| Rush orders | Accept if schedule slack exists and rush fee applied | Requires bumping a committed job |
| Reorders | Auto-approve for standard stock under $2,000 | New vendor or price moved over 10% |
| Overtime | Up to 4 hours per person per week at lead's discretion | Recurring 3 weeks in a row |
Running the Handover Without the Cliff
Do not flip from all decisions to no decisions. Run a review-after period: the team applies the rules and acts immediately, and you review the week's decisions in fifteen minutes every Friday. You are not re-deciding — you are coaching the rule. Where you would have decided differently, the interesting question is which input the rule failed to capture, and the rule gets a revision, not the person a correction.
Expect three kinds of findings. Some rules are wrong and improve fast under contact with reality. Some decisions turn out to be genuinely yours — bet-the-relationship calls, precedent-setting exceptions — and keeping those is correct. And some of your accumulated habits turn out to be policies nobody can defend, which the writing exercise mercifully kills.
What You Get Back
The obvious return is time — hours a week, permanently. The larger return is speed and durability: customers get same-day answers instead of when-the-owner-lands answers; the business runs through your vacation; and your strongest people start exercising judgment inside guardrails instead of queuing for permission, which is how they grow into the managers you keep saying you need.
A business that cannot decide without its owner is not being led. It is being throttled. Write the rules down and find out how fast the thing you built can actually move.
The team does not need your permission. It needs your decision rules. You stay the author of how decisions get made — and stop being the queue they wait in.
Sources
Topic clusters
Ready to see where the friction is?
The Lobbi's Operations Discovery maps your workflows, identifies your highest-impact bottlenecks, and gives you a clear picture of what's possible.