Read a sample: 1. The Uneasy Space Between Assignment and Result
On Monday morning, Maya asks Jordan to prepare a summary for a client meeting on Thursday. The summary needs to bring together information from several project updates, highlight unresolved questions, and be ready for Maya to review Wednesday afternoon.
Jordan says, “Sure. I’ll get started today.”
For a few minutes, Maya feels pleased. She has been supervising the team for only a month, and assigning the summary seems like the right use of everyone’s time. Jordan knows the project, and Maya has other work that needs her attention.
Then Maya returns to her desk.
What if Jordan uses an old version of the project notes? What if the unresolved questions are buried at the bottom? What if the summary is technically complete but not useful in the meeting? Maya could ask how Jordan plans to approach it. That would be reasonable, wouldn’t it?
She sends a message: “Let me know if you need anything.”
Jordan responds with a thumbs-up. Maya tries to move on.
An hour later, she remembers that the client has been particularly interested in one issue. She sends another message. Then she opens the shared folder to see whether Jordan has started a draft. There is no new document. Maya tells herself that Jordan may be gathering information first, but she looks again after lunch.
By Tuesday morning, she has drafted an outline of her own. She could send it as a helpful suggestion. Or she could use it to finish the summary herself. That might be faster, and she would know it had been done the way she wanted.
Nothing has gone wrong yet. The deadline is still ahead. Jordan has not asked for help or signaled a problem. Maya’s discomfort comes from a less visible place: she is responsible for an outcome she cannot produce by personally guiding every step.
If that sounds familiar, you are not alone in finding this transition unsettling. Becoming a supervisor often changes what it means to do a good job. You may still be answerable for the quality and timing of the work, but someone else now does much of the work itself. Between assigning a task and seeing the result, there is room for other people’s choices, competing priorities, questions, and surprises. There is also room for your imagination to fill in what you cannot yet see.
This chapter is an invitation to notice that uneasy space. You do not need to eliminate it before you can supervise well. You can begin by recognizing what happens in it: what you fear, what your body tells you, and what you tend to do next.
Before becoming a supervisor, you may have built confidence by being dependable with your own work. You knew where to find the information, how long the task usually took, and which details deserved a second look. If something seemed off, you could investigate immediately. If a deadline was close, you could rearrange your day and push through.
Those habits may have served you well. They may also make it difficult to hand an assignment to someone else.
When another person takes on the work, you lose some of the immediate feedback you once had. You cannot feel their progress in the same way you felt your own. You may not know which source they are reading, what problem they have just solved, or whether they have noticed an inconsistency. Even when they are working steadily, their process may be mostly invisible to you.
At the same time, your responsibility has not disappeared. A manager, customer, colleague, or team may still look to you for the outcome. That combination—less direct control with continuing responsibility—can make an ordinary gap in information feel urgent.
Imagine that you assign a colleague to organize materials for a staff presentation. Two days pass without an update. Several explanations are possible. They may be making good progress. They may be waiting on information. They may have misunderstood the scope. They may have been pulled into another priority. At that moment, silence alone does not tell you which explanation is true.
An anxious mind may settle quickly on the explanation with the greatest perceived danger: They have not started, and I am going to find out too late. That thought can feel like a warning, even though it is only one possible interpretation.
This does not mean your concerns are foolish. Sometimes silence does signal a problem. Sometimes an assignment needs a clearer deadline or an earlier review. The aim is not to dismiss every concern; it is to learn how to tell the difference between a useful need for information and the discomfort of not having it immediately.
Repeated checking is not always dramatic. It can be woven into ordinary, reasonable-looking actions.
You might send a quick message asking for an update shortly after an assignment has been accepted. You might open a shared document several times to see whether the word count has changed. You might ask a teammate for the same status in a meeting after they already sent it by email. You might make “small improvements” to their draft without discussing them, or quietly begin a backup version in case theirs is not ready.
Taking the work back can happen gradually, too. First you offer an outline. Then you rewrite a section to show what you mean. Then, because you are already involved and the deadline is approaching, you…