Your Team Is Not the Problem

I have sat in enough post-mortems to recognise the pattern. The project misses. The output is wrong, or close to right but not quite, or right in the way nobody actually needed. The manager is frustrated.

The team is confused about why. And the debrief circles around capability, effort, attitude, every variable except the one that most often caused the problem. Nobody wrote down what good looked like before the work started.

This is the briefing failure diagnosis, and it is the most consistently avoided conversation in management. A survey of 1,100 supervisors, managers, directors, and executives by the Canadian Management Centre and AMA Global found that 72% of respondents cited communication as a critical skill gap in executing strategy.

Not budget. Not headcount. Not tools. Communication, which in most cases means the instructions that preceded the work were not clear enough to produce the work that was expected.

The gap between what a manager intended and what a team produced is almost never a talent problem.

The manager had a clear picture of what they wanted. They described a part of it. The team built to the description they were given, which was a partial approximation of the picture the manager never fully articulated. The work comes back wrong. The translation failure is diagnosed as an execution failure. The team gets the note.

The Unwritten Brief

There is a specific discipline required to write down what good looks like before you ask someone else to produce it. It forces you to answer questions you may not have resolved yet: what is the goal, who is this for, what does a successful outcome actually look like, and what are the boundaries.

Most managers skip this step not because they are careless but because the picture in their head feels clear enough that writing it down seems redundant. It is not redundant. The picture in your head is not available to the person doing the work.

MIT Sloan Management Review identifies clarity as the critical variable in effective delegation, specifically noting that vague handoffs invite confusion and rework, and that clarity should extend to the why behind the task, what success looks like, and where the team member has decision-making freedom.

These are not complicated requirements. They are the minimum conditions for the work to go right the first time. When they are absent, even strong performers will second-guess themselves, which is expensive in time and in the quiet erosion of confidence that follows repeated correction.

Research on clear communication in delegation published in Scientific Research found that unclear communication leads directly to misunderstandings, errors, and decreased productivity, while clear communication fosters employee empowerment, motivation, and project success.

The finding is not surprising. What is worth sitting with is the inverse: every time a project misses, there is an instruction somewhere upstream that was not specific enough, and the accountability for that belongs to the person who gave the instruction, not the person who acted on it.

Setting the Standard

There is a version of this conversation that most managers find uncomfortable, because it relocates the problem. The team did not fail to meet the standard. The standard was never communicated clearly enough to be met. That is a meaningful distinction, and acting on it requires a different kind of accountability than is comfortable for most people in leadership positions.

PMI’s 2025 research found that 13% of projects fail outright and 37% only partially deliver expected results, with poor communication identified as a primary contributing factor across both categories. Roughly half of all projects do not fully deliver. The briefing problem is not a marginal one.

The practical fix is simple enough to be annoying. Before the next project starts, write down what good looks like. Not the task description. The outcome. What a successful deliverable does, who it is for, what it needs to achieve, and the constraints. Share it with the team before work begins.

Ask if the brief is clear. If the answer requires a long conversation, the brief was not clear enough. Rewrite the brief, not the conversation.

The work your team produces is a direct reflection of the instructions they received. Write the brief first, and you shift the accountability to the right place, which also happens to be the place where you actually have the most control.