What three weeks of postponing one conversation did to a team — and how ordinary the conversation turned out to be.
A grounded workplace narrative: a team lead avoids one difficult conversation for three weeks and finds the real thing far smaller than the dread. On avoidance, control, and plain speech, through a Stoic lens.
On a Tuesday in March, Maya added a thirty-minute hold to her calendar titled "Chat w/ Daniel." She moved it to Thursday before it arrived. Then to the following Monday. By the time the conversation actually happened, the hold had been rescheduled seven times.
Maya led a six-person platform team at a mid-size software company. Daniel was a capable engineer who had, over about two months, started missing handoffs — small things at first. A migration script left half-finished on a Friday. A code review sitting untouched for three days while two other people waited. Each gap was minor. Together they had begun to reshape how the team worked, and no one had said so out loud.
What Maya did instead of talking to Daniel was manage around him. She quietly reassigned the stalled review to someone faster. She picked up the unfinished migration herself one evening rather than flag it. When she messaged Daniel, she softened everything: "no rush, whenever you get a sec," "this is probably on me for not being clearer." The messages were friendly. They also said nothing true.
She had reasons, and the reasons were good enough to keep using. Daniel had seemed stretched. The quarter was busy. She did not want to be the manager who made a big deal out of small things. She told herself she was being considerate — waiting for a calmer week, a better moment, more evidence. Each postponement brought a small, real relief, and each one made the next conversation feel a little larger.
Because the conversation was growing. Not the actual situation — that stayed roughly the same size, a few missed handoffs a week. What grew was the version in Maya's head. By the third week she was no longer rehearsing "hey, I've noticed a couple of handoffs slipping." She was bracing for defensiveness, for hurt, for an argument about whether it was even fair. She was preparing for a confrontation with a Daniel who existed mostly in her imagination.
Meanwhile the team adjusted around the silence. Two engineers started routing their work to avoid depending on Daniel's pieces. Standups grew a little more careful, a little more coded. Nobody named it. The cost of the unspoken thing was being paid in small, distributed installments by people who had not agreed to pay it.
The conversation finally happened because a release slipped. A handoff Daniel owned did not land, a customer-facing fix went out a day late, and Maya had to explain the delay to her own manager. Cornered by a concrete failure, she messaged Daniel — no softening this time — and asked him to talk that afternoon.
It took about eight minutes. She named what she had seen: the specific handoffs, the dates, the effect on the team. Daniel's first reaction was not defensiveness. It was a slightly embarrassed "yeah — I know." He had been quietly buried in an unrelated system nobody had reassigned, and had been letting the visible work slip to keep the invisible work afloat. He had assumed someone would say something sooner. Part of him had wanted them to.
They sorted the actual problem in the same conversation — a reassignment, a clearer owner for the invisible system, a standing check-in. None of the things Maya had spent three weeks dreading occurred. The hard part had never been the eight minutes. The hard part had been the three weeks she spent not having them.
Marcus Aurelius, who wrote his notes to himself as a working administrator rather than a philosopher on a stage, kept returning to a plain distinction: the event is one thing, and our judgment about the event is another. Maya's three weeks were spent almost entirely inside the second thing. The handoffs were small and factual. The dread was large and invented. She had been negotiating with a story.
Underneath that sits a second Stoic habit: attending to what is actually yours to do. Maya could not control how Daniel would take it — whether he would be hurt, whether he would agree. That was never hers. What was hers was the plain account — what she saw, when, and its effect — delivered while it was still small. She had treated the difficulty of the conversation as if it lived in Daniel's reaction, which she could not govern, when the part she could govern was simply saying the true thing on time.
Avoidance is often described as a failure of courage. More often it is a quiet miscalculation. It feels like postponing a cost. It is closer to taking out a loan — repaid with interest by the people working around the silence, and by the version of the conversation that keeps growing in the dark until it barely resembles the ordinary exchange it was always going to be.
Avoidance rarely removes a hard conversation. It shrinks the conversation in the moment and enlarges it in the mind, while the real cost is paid quietly by everyone working around what was not said.
The conversation Maya dreaded and the conversation she finally had were not the same conversation. For three weeks she had been preparing for a confrontation with someone who existed only in her head.
Is there a conversation you are currently routing your work around rather than having?
When you picture that conversation going badly, how much of what you are bracing for is actually within your control?
What is the plain, factual version — what you saw, when, and its effect — that you have not said yet?
Where on your team does work quietly get rerouted around a problem no one has named out loud?
What does a team actually lose while a difficult conversation waits for "a better moment"?
Would earlier, smaller, plainer conversations be worth the discomfort of having them sooner — and what would make that easier here?