Be Careful What You Ask For. You Might Get It Forever.

Marcus set a threshold.

A contractor had been hired at a rate nobody had approved, so he asked that anything over five thousand dollars come to him for sign-off first. Not forever. Until finance finished the new vendor process, which was maybe a quarter out.

It worked immediately. Two bad line items got caught in the first month, and the vendor process shipped that spring.

The threshold is still five thousand dollars. It has been five thousand dollars for seven years.

Nobody Decided to Keep It

There was no meeting where somebody argued for continuing. There was no meeting at all.

The vendor process went live on a Thursday. Somebody on the team thought about asking whether the sign-off could come off now, worked out that raising it would take longer than just sending the next request, and did not ask. The next Monday two requests came through, Marcus approved them, and the rule acquired another week.

That is the whole mechanism and it takes about ten days. The only decision anybody made was a decision not to raise it, and that decision took four seconds.

Marcus asked a question. Answering it took real work. And instead of the answer being delivered and the work ending, the answering went into the workflow.

Acute Work Has a Finish Line. Rote Work Has a Cadence.

The two look identical for the first three deliveries.

Acute work ends when the question is answered. Finance ships the vendor process, the gap that let an unapproved rate through is closed, and the sign-off has nothing left to catch.

Rote work ends when somebody stops it, which is to say it does not.

The conversion happens in the gap between those two sentences, and it is invisible because the first three deliveries are genuinely useful. By the time they are not, the thing has a form field, a routing rule, and seven years of everyone assuming somebody meant it.

What Seven Years Does to a Number

A threshold does not hold still. The world moves underneath it.

Five thousand dollars in 2019 buys about four thousand of today's dollars. Meanwhile the team grew, the work got more vendor-heavy, and a number that once caught the occasional unusual purchase now catches roughly fourteen requests a week.

Marcus spends about ninety minutes a week on approvals he has never once declined. That is the cheap half. The expensive half is that seven hundred requests a year each wait around two days, and the people waiting are not in his organization and do not know who to ask about it.

Call the direct time somewhere north of thirty thousand dollars a year. The delay does not appear on any ledger at all.

The Eleven Words That Would Have Prevented It

Marcus's request was one sentence. It could have been one slightly longer sentence.

Route anything over five thousand to me until the vendor process is live.

Eleven extra words, and the thing ends itself. The condition sits inside the request, so nobody has to be the person who cancels it later, and that is the part everybody avoids.

Notice what it does to a conversation that now never has to happen.

Last spring a new manager asked, in the polite way people ask these things, what the five thousand dollar rule was for. The answer she got was that Marcus wants it. Which was true in the sense that Marcus had once wanted it, and not true in any sense that would survive being said out loud to Marcus. So she started routing her requests through him, and the rule acquired one more department that had never met the question it was built to answer.

With the condition in the request, that exchange has nothing to say. The rule ends itself, and nobody has to walk into Marcus's office to suggest his idea has outlived its reason.

You Cannot Set the Condition Afterward

This only works at the moment of asking, and that is the uncomfortable part.

Once the rule exists, adding an end condition means proposing to end something. Different conversation, different temperature. You are no longer setting a term, you are canceling somebody's control, and now their judgment is on the table next to your suggestion.

Ten seconds at the start. A meeting and a small argument at any point after.

Finish the Sentence

So the next time you ask for something standing, finish the sentence.

Until the vendor process is live. Until the migration lands. Until we have three clean months. Through Q3, and then we look again.

None of those is a big ask, and all of them do the same thing. They make the rule responsible for its own ending.

And if you cannot finish the sentence, you have learned something more useful than the control was ever going to catch. You do not yet know what you are trying to prevent.

Marcus has approved every request that crossed his desk for four years. He is not a bottleneck because he says no. He is a bottleneck because somebody, once, was right about something, and never said when being right would stop mattering.

Eleven words, seven years ago, and there would be nothing to dismantle.

-BZ