The Question You Answer Twelve Times a Week Is a System Waiting to Be Built
"Can I give them 15% off?"
You've answered this one before. Last Tuesday. And the week before that. And probably four times the month before.
The person asking isn't new. They're not incompetent. They just don't have a framework for when 15% is fine and when it isn't.
So they ask you. Every time.
The hidden cost isn't the interruption
Yes, the interruption is annoying. You're in the middle of something, your phone buzzes, and suddenly you're context-switching to approve a discount for an order you'll forget about in ten minutes.
But that's not the real cost.
The real cost is what happens when you're not available. The hesitation. The deal that sits for six hours because someone didn't want to make the wrong call. The customer who went elsewhere because your team was waiting for permission that didn't come.
Or worse: the person who guesses, gets it wrong, and now you're dealing with a margin problem or an angry customer.
The question isn't the problem. The missing framework is.
What a decision framework actually looks like
A decision framework isn't a policy document. It's not "refer to section 4.2 of the pricing guidelines."
It's a simple set of rules that let someone make the call themselves, confidently, without checking with you.
For the discount question, it might look like this:
Order value under £200: No discount. Full price or walk away.
Order value £200-500: Up to 10% at your discretion. No approval needed.
Order value over £500: Up to 15% at your discretion. Flag it in the weekly sales summary so we can spot patterns.
Anything above 15%: Check with [name] before confirming.
That's it. Four lines. Fits on an index card.
Now the question stops arriving in your inbox because the person asking doesn't need you anymore.
Finding the questions that deserve frameworks
Spend one week writing down every question someone brings to you that you've answered before.
Not new problems. Not genuine edge cases. The repeats.
"Should I expedite this order?" "Can I refund the shipping?" "Do we work with this type of client?" "Is this ready to send?"
By Friday, you'll have a list. Some will be one-offs. But three or four will show up multiple times. Those are your candidates.
Pick one. The one that interrupts you most often, or the one where hesitation costs you the most.
Building the framework in thirty minutes
Pull the last five or six instances where you made this decision. Look at what you actually considered.
For the discount example, maybe you were weighing order size, whether it's a new customer or existing, whether it's a product with tight margins, whether they're likely to reorder.
Write those factors down. Then write the thresholds.
Don't aim for perfect. Aim for "covers 80% of cases." The remaining 20% can still come to you — that's fine. You're not trying to eliminate judgment calls. You're trying to eliminate the obvious ones that don't need you.
The part where most people stop
Writing the framework is easy. Getting it used is harder.
Here's what works: the next time someone asks you the question, don't just answer it. Walk through the framework with them. Out loud.
"Okay, order value is £350, so you've got up to 10% discretion. New customer, so maybe worth using it to get them in the door. Your call — what do you think?"
Do this three times. By the fourth, they'll stop asking.
The shift that matters
When you answer the same question repeatedly, you're not being helpful. You're being a bottleneck disguised as a resource.
The team learns to wait for you. Decisions slow down. And you stay stuck in the operational weeds because you've accidentally made yourself essential to things that shouldn't need you.
One framework won't fix everything. But it's a crack in the pattern. Proof that decisions can happen without you in the loop.
Then you build another. And another. And gradually, the questions that used to interrupt your Thursday afternoon just... stop.
If you've got a list of questions like this — the ones that keep landing on your desk when they probably shouldn't — that's exactly the kind of thing we help untangle.