A Ten-Day Crisis That Ate Months: Why Delegation Needs Exit Dates

By Olivia Hart

A ten-day crisis taught one lender's team a lesson that took months to undo. The author of a first-person account published on Entrepreneur writes that after a key hire quit mid-project, he pulled three routine decisions — pricing exceptions, vendor swaps, the weekly staffing puzzle — back onto his own desk "just until we stabilize." The crunch lasted about ten days. The habit lasted months.

The tell was not the scramble but the silence that followed. "People stopped bringing recommendations. They brought questions," he writes. "I had taught them, without meaning to, that judgment lived upstairs again."

The author runs B:Side Capital, a mission-driven Small Business Administration (SBA) lender and certified community development financial institution (CDFI), and teaches management and entrepreneurship at Arizona State University's W.P. Carey School of Business. He says the same pattern recurs across restaurants, contractors, clinics and software shops: when pressure arrives, the owner becomes the decision system, and nobody writes the date when that arrangement ends. That claim is anecdotal, drawn from his own observation, and he does not pretend otherwise.

What does the data actually say?

One number in the piece carries external weight. Gallup finds that employees whose manager involved them in setting goals were nearly four times more likely to be engaged than others. Yet only 30% of employees experience that basic expectation — roughly three in ten, meaning seven in ten do not. Involvement, the author argues, dies first when every hard call routes back to one desk.

His own confession is blunt: "I used to treat the pull-up as proof I was carrying the load. Wrong lesson." Carrying the load can be necessary, he concedes. Teaching the company that only you may decide is optional — and expensive.

Who owns each recurring call?

His first prescription is a decision map. List the calls that repeat weekly: pricing exceptions, hiring offers inside a band, vendor changes under a dollar threshold, schedule swaps, customer make-goods. Write who may decide, what they may trade and when the call must move up. His verdict on the alternative is sharp: goals without owners are theater.

He tested this at BodeTree after another stretch where every exception landed in his inbox. "The map was ugly in its simplicity," he writes. "Ambition had concentrated judgment in one person, and I had been calling that leadership."

The self-audit is concrete. Pick five recurring calls and put a name next to each. If your name appears four times, you have a concentration, whether you plan to grow or not. A restaurant owner might find one person owns menu specials, vendor credits and the Saturday floor; a SaaS founder might find discounting, enterprise renewals and production access share one login.

What makes delegation complete?

Authority without a return path is half a handoff, the author argues. An escalation path must define the triggers, the response time and what context travels with the issue. Skip it, and you get silent overreach or habitual upward deferral — "both train the wrong muscle."

He admits he resisted writing triggers because they felt bureaucratic. His correction: they are a boundary, not a binder. Escalate when risk crosses the band, purpose conflicts, spend exceeds the limit or two teams need the same scarce resource. The script is plain: "You own this up to X. Escalate when Y. Bring the context, not just the question."

Why exit conditions matter most

The sharpest point targets temporary power grabs. The moment an owner pulls a decision upward, the author says, they should state what would let it move back down: a date, a restored capability, a risk threshold or an information flow that no longer needs their desk. "A pull-up without an exit condition is a theory of leadership in disguise."

He also warns against a measurement trap: review capability against decisions people actually got to practice, or the exit test measures deprivation of opportunity as if it were incapacity. Waiting until things "felt normal" failed him. "Feelings are a weak criterion," he writes. Returning authority, he notes, requires a second act of courage: trusting judgment you recently starved.

His closing test for readers: list every decision reclaimed last quarter "just until we stabilize," and write one sentence on what would justify giving it back. The calendar, not ambition, gets the veto. The unstated risk is the one he lived — that the quiet nod-along of a centralizing owner, not the crisis, is what quietly sets company culture.