How to Specify Conditions, Boundaries, and Decision Rights
Knowing what good looks like is not enough to act with confidence. People also need to know by when, within what limits, and how much they can decide on their own. This playbook gives you methods for setting the operating envelope around an expectation: explicit deadlines, clear scope, defined decision rights, and named escalation triggers, so work is safe to hand off and you can step back without becoming the bottleneck on every small decision.
Developing
Start here. Build the foundation.- 1
Give a real date or interval, never 'soon' or 'when you can.' 'Draft to me by Thursday noon' leaves no room for two different reads of urgency. If the deadline is genuinely flexible, say that too, with a boundary: 'anytime before the board meeting on the 14th.'
- 2
Name the edges of the work, what is in scope and what is out. 'Fix the checkout bug, but do not refactor the payment module' prevents both the gap and the gold-plating. You know it worked when the person starts without asking where the task ends.
- 3
State both the deadline and the scope at handoff, in writing, even after a verbal conversation. A one-line recap, 'Thursday noon, checkout bug only,' gives you both a shared reference and an early chance to catch a misread before any work is done.
Proficient
Build consistency and rhythm.- 4
Say what the person can decide alone and what needs your sign-off. 'Spend up to five hundred dollars without asking; anything above that, check with me first.' Defined latitude is what lets people move without overstepping, and what stops you from being consulted on decisions you would happily have delegated.
- 5
Name the specific signals worth a flag, so problems reach you while there is still time to act. 'Tell me the moment the vendor misses a date' beats 'let me know if there are issues,' because the first names an observable trigger and the second leaves the person to judge what counts.
- 6
Match the size of the decision right to the person and the stakes, and widen it as trust builds. Start a newer person with a tighter spending or sign-off limit and say so plainly, then expand it as they demonstrate judgment. Naming the current limit avoids both the bottleneck and the overstep.
Mastered
Operate at the highest level.- 7
Codify the default decision rights, spending limits, and escalation rules for the situations your team hits repeatedly, so you are not renegotiating the rules of engagement on every new task. You know it is working when routine decisions get made consistently without anyone asking what the rule is.
- 8
Write the standing boundaries down where the team works, a short who-can-decide-what reference, and point new people to it during onboarding. Default latitude that lives only in your head has to be rediscovered by every new hire, usually by overstepping once.
- 9
Revisit the standing rules when the team grows or the stakes change. The spending limit that fit a three-person team may bottleneck a ten-person one. Treat the boundaries as something you tune deliberately, not a set of rules that quietly ossifies.
Common Pitfalls
Avoid the common failure modes.- Using 'soon' or 'as soon as possible' instead of a real date. ASAP means drop everything to one person and when I get to it to another, and you will not find out which until it is too late.
- Leaving scope implicit and being surprised by what got included or skipped. The boundary that was obvious to you is exactly the one the other person did not know was there.
- Not stating decision rights, which produces either constant check-ins or unwanted surprises. Silence on authority does not grant it or withhold it; it just makes people guess.