Concept
Setting Boundaries
Setting boundaries means deciding in advance what you will and won't give your time and attention to, so other people's urgencies can't quietly rewrite your day.
Greg McKeown treats boundaries as a form of editing. Without them, every request gets judged in the moment, when the asker's urgency is loud and your own priorities feel abstract. You usually lose that fight. A boundary moves the decision earlier. You decide once, calmly, what serves your essential intent, and afterward the rule does the declining for you. Good boundaries aren't walls against people. They state clearly where your yes is already spent. They are also kinder to others: "I don't take calls after 7" beats a resentful yes followed by half-hearted effort. The test isn't whether a request is good, because most are. The test is whether it serves the point. Cutting good options is what leaves room for the essential ones.
A real-life example
Maya, a product manager, spent her mornings answering "quick" Slack questions. She set one rule. Until 11 a.m. she works on the roadmap, and she answers messages at 11 and at 4. She put it in her status and told her team why. In the first week two colleagues grumbled. By the third, questions arrived in batches, and the roadmap draft that had stalled for a month was finished.
How to use it
- 1List the three kinds of requests that most often hijack your week, and decide now what your standing answer to each one is.
- 2Write each boundary as a rule with a time or condition ("no meetings before 11", "Thursday afternoons are closed"). Tell the people it affects once, and give them the reason.
- 3When a request crosses the line, point to the rule and offer the nearest alternative instead of renegotiating from scratch.