Work boundary script: practical guide
Work boundary script is a concise way to state a current commitment, a capacity constraint and an alternative when new work arrives.
Quick answer
Say: I am committed to [deliverable] by [time]. Adding this means changing [scope or date]. Which should take priority?.
What this guide is best for: readers who need to make a concrete decision about work boundary script.
How do you put this into practice?
Use the following sequence as a starting plan, then adjust it to the work you are responsible for.
- Say: I am committed to [deliverable] by [time]. Adding this means changing [scope or date]. Which should take priority?.
- Use the script to make a tradeoff visible to the person authorized to choose it.
- Record the action you chose, its intended result and the next occasion on which you will check it. Keep the record in a place you can return to without rebuilding your setup.
How do the options compare?
| Checkpoint | Record |
|---|---|
| Starting condition | Say: I am committed to [deliverable] by [time]. Adding this means changing [scope or date]. Which should take priority? |
| Failure to avoid | Do not promise both deadlines when you already know the capacity is unavailable |
What would this look like in practice?
A designer tells a lead that an urgent slide update will delay the approved mockup and asks which output is needed first. This is an illustrative scenario, not a customer result or evidence of a measured improvement.
Which planning principle supports the method?
The National Cancer Institute’s archived implementation-intentions resource describes if–then plans that connect a situational cue with an intended action. Spry’s examples here are editorial applications of that planning idea, not evidence that this particular guide or product produces a measured outcome. The source is retained for reference and is no longer maintained.
Source reviewed 2 November 2026.