Your team is making decisions every day. Do they have the context they need?

Every employee makes decisions. Not just the big visible ones that land in a meeting agenda, but the dozens of small ones that happen constantly — what to prioritize, how to handle a conflict, when to escalate, how to make a trade-off between competing goals.

Most managers assume their teams have what they need to make those decisions well. Often, teams don't. Not because they lack skill or judgment. But because they don't have enough context to make them.

What context actually is

Context is not information. It is the specific framework that allows an employee to use their judgment in a way that is aligned with the organization's strategy and their manager's intent.

It answers the questions employees are constantly — and often silently — asking: Why does this work matter? How does what I do connect to what others are doing? What should I do when priorities conflict? What is happening in the world around us that I need to factor into my decisions?

When context is clear, employees can make good decisions independently. They don't need to escalate constantly. They don't need to be micromanaged. And they don't need to guess. 

Of course, clear context doesn't make decisions easy, and isn't the only thing that needs to work well to ensure employees can make good decisions. Complexity, uncertainty, the pace of change, and competing priorities don't disappear because context is clear. What changes is the quality of the information you're working with — and that shifts the odds.

On the other hand, when context is missing or unclear, the gap gets filled by assumptions, by whoever has the strongest personality in the room, or by nobody at all. That's when alignment breaks down, coordination fails, and managers find themselves pulled back into decisions they thought they had delegated.

The four types of context every manager needs to set

Context is not a single conversation. It has four distinct dimensions, and each one addresses a different gap in how employees understand their work.

Upward context is the why

It connects the work employees are doing to the strategy and priorities of the organization above them — the mission, the business goals, the manager's own vision and plan for addressing the challenges their team faces. Upward context answers the question employees rarely ask out loud but always need answered: why does this matter, and why now? When it is clear, employees can make trade-offs intelligently. When it is missing, they default to their own priorities — which may or may not align with the organization's.

Team context

It is about how the immediate team works together. Every manager with direct reports needs to ensure that team members understand what each other is accountable for, how their work intersects, and what it means to deliver on their own goals in a way that supports the best outcome for the whole team rather than just their own function. This is the context that prevents the quiet fragmentation that happens when people are technically working toward the same goal but operating in parallel rather than in coordination.

Cross-functional context 

It addresses the lateral relationships that cut across reporting lines — the interactions between employees who report to different managers but who need to collaborate to get work done. This is one of the most common sources of friction in organizations, and it is almost always a context problem rather than a people problem. When employees don't understand the accountabilities and authorities of the roles they need to work with, or the criteria by which trade-offs should be made, they are left to negotiate all of that themselves in real time. The results are predictable: slow decisions, strained relationships, and outcomes that reflect what people could agree to rather than what would actually serve the organization. Cross-functional context is covered in more depth in a companion article.

Environmental context

It is the most overlooked of the four. It is about what is happening outside the organization — in the market, among competitors, in the broader economic, social, and technological landscape — that should be informing how people think and decide. Senior leaders in particular need to be proactive about seeking and sharing this context, because without it, employees are making strategic decisions in a vacuum. Environmental context is what allows an organization to be responsive rather than merely reactive.

Context cascades — or it doesn't

Setting context is not a one-time event and it is not the exclusive responsibility of the CEO or the senior leadership team. It is a managerial accountability at every level of the organization.

Context starts at the top and cascades downward, with each level translating and adapting it for the level below. A senior leader sets upward context for their direct reports. Those direct reports set it for theirs. By the time it reaches the people doing the day-to-day work, it should be specific enough to be actionable — connected to the broader strategy but expressed in terms that are directly relevant to what that team is working on.

When this cascade works well, employees at every level have what they need to make good decisions without constantly escalating upward. When it breaks down at any point — because a manager didn't fully understand the context they received, or didn't take the time to translate it for their team — the gap compounds at every subsequent level.

By the way, the structure doesn't have to be a traditional hierarchy. In matrix organizations, this cascade runs along multiple axes simultaneously — functional and project, for instance. The principle holds regardless: whoever holds broader context is responsible for translating it for those who need to act on it.

The most visible symptom of a broken context cascade is a manager who complains that their team keeps making decisions that don't align with the strategy. The less visible cause is usually that the manager never gave their team the context that would have made alignment possible.

The diagnostic question

If you want a quick read on whether your team has the context they need, ask yourself this: if a member of my team had to make an important decision without being able to consult me, would they have what they need to make a good one?

If the honest answer is "probably not" — that's not a performance problem. That's a context problem. And it's yours to fix.