This essay expands on the “Boundaries and Responsibility” thread in Management Retrospective.
Many people mistake busyness for responsibility: reply to every message, attend every meeting, and refuse no opportunity. I’ve been through that phase myself, believing that “catching everything” was what being dedicated meant. The result is usually that no single important thing gets enough investment, while commitments quietly break down—when you say yes to too much, you end up either slipping deadlines or lowering quality, and both erode trust.
“Saying no” isn’t avoidance; it’s acknowledging that time, attention, and the radius of your responsibility all have limits.
Start with Roles, Not Preferences
The same task doesn’t carry the same priority for different roles. Someone responsible for a module should put most of their energy into delivery quality and risk; someone responsible for a direction has to reserve time to understand goals, develop owners, and handle cross-team dependencies.
When your role changes, your old investment habits have to change with it. A new manager who still keeps all the complex implementation for themselves may look highly efficient, but in reality they may be holding the team back—they save their own time while taking away the team’s chance to practice. When the role changes, the way you allocate time has to be recalculated.
Every “To-Do” Should Be Matched With a “Not-to-Do”
Here’s a simple exercise: list your three most important commitments for the week, and ask what each one costs—what meetings will I cut, what exploration will I postpone, and what ad-hoc requests will I refuse to make it happen? If you can’t answer, the priority isn’t a real priority yet.
For example, a team is planning to fix long-standing stability problems while three urgent small requests come in at the same time. Rather than promising to “finish everything as soon as possible,” it’s better to say it openly: this week we’ll protect the two fixes with the greatest user impact, and give the remaining requests a clear time for their next evaluation. There will still be disappointment, but trust won’t be consumed by vague promises—the biggest cost of a vague promise is that no one knows you actually can’t deliver.
Reprioritize Regularly, Not Once and for All
A “not-to-do” always comes with a time horizon. Something that doesn’t matter today may become worth doing because the risk, the window, or the context has changed. The key is to reassess regularly rather than treating a past ordering as permanent truth.
Being able to explain why you’re not doing something—and to choose again when conditions change—is what a boundary that’s responsible to both yourself and your collaborators looks like. Review once a week: has the role changed, does the investment still match, and which commitments should end or be renegotiated.
Finally, make it concrete: put the ordering on your calendar rather than leaving it in wishful thinking. A “not-to-do” that isn’t written into the calendar is just talk; only once it’s written in does the boundary actually take effect.