Before You Make the Decision, Map the Context
When I work with clients, one topic almost always comes up: confidence in decision-making. I often ask:
What if you could feel confident that the decision you’re making is the right one?
Not necessarily the most popular decision. Not the easiest one. The right decision based on what you know, who will be affected and the conditions you’re working within. That question usually gets a chuckle. Because how can anyone know for sure anymore?
Priorities shift. Budgets change. New information surfaces. The people affected may see the situation very differently from those making the decision. Sometimes the problem itself changes while you’re still trying to solve it.
And they’re right. We can’t know everything. But we can make better decisions by taking the time to understand the context first.
We’re making decisions in a VUCA world
VUCA is an acronym used to describe conditions that are:
Volatile: Things can change quickly and unexpectedly.
Uncertain: We don’t always have enough information to predict what will happen.
Complex: Many interconnected factors influence the situation.
Ambiguous: The available information can be interpreted in different ways.
Most organizational decisions contain at least one of these conditions. Many contain all four. You might be deciding how to restructure a team while roles are already changing. You may be creating an HR strategy without knowing what skills the organization will need two years from now. Or you might be addressing an operational problem that looks completely different depending on who you ask.
In these situations, confidence doesn’t come from knowing exactly what will happen. It comes from knowing you used a sound process to make the decision.
We focus on the decision and overlook how we’re making it
When pressure builds, it’s easy to focus entirely on the decision in front of us:
What should we do?
But several other questions matter just as much:
Who needs to be involved?
When should they be involved?
What role should they have in the process?
What do we know, and what are we assuming?
Whose experience or perspective is missing?
What constraints are shaping the decision?
Do we have enough information to move forward?
What would cause us to revisit the decision later?
These questions help us determine whether a proposed solution is desirable for the people affected, feasible within the organization and viable over time.
They also make the decision easier to explain and defend. Even if the outcome isn’t perfect, you can show that the right people contributed, the relevant information was considered and the trade-offs were understood.
That’s a far more realistic form of confidence than trying to predict the future.
Good leadership is less like hitting a target and more like tracking one
Leaders are often told they need to adopt "Agile Leadership" skills. In practical terms, that means being willing to learn, adjust and respond as conditions change.
Imagine trying to hit a moving target. You wouldn’t take aim based only on where the target was five minutes ago. You’d pay attention to its direction, speed and the conditions affecting its movement. You would take your best shot based on the information available, then adjust as new information emerged.
Decision-making works the same way.
Being agile doesn’t mean constantly changing direction. It means staying aware of the conditions around you and knowing when those conditions are significant enough to require a change.
That starts with curiosity.
Curious leaders don’t assume they already have the full picture. They ask better questions. They seek out different perspectives. They separate what is known from what is assumed.
One practical way to do that is through context mapping.
What is a context map?
A context map is a structured way to explore what is happening around a problem, opportunity or decision. It helps a group step back from the immediate issue and examine the factors shaping it. Depending on the situation, that could include:
Organizational priorities
People and stakeholder needs
Internal pressures
External changes
Policies and regulations
Available resources
Current barriers
Emerging trends
Risks and uncertainties
Assumptions that may need to be tested
The goal isn’t to document everything that could possibly affect the organization. It’s to identify the factors that matter most to the decision you’re making.
Context mapping gives people a shared view of the situation before they start proposing solutions. It helps uncover information that may otherwise remain scattered across departments, roles or individual experiences.
It can also expose a common problem: people may agree on the proposed solution without agreeing on what is actually happening. Context mapping helps us expose our assumptions about situations, and gives us a safe and constructive environment to discuss topics that might otherwise be hard to approach.
Why I start with a context map
Whether I’m helping with an HR strategy, a leadership issue or an operational challenge, I often begin with some form of context mapping. It anchors people in their current reality.
It also challenges assumptions about what they think they know. One person may see a communication problem. Someone else may see unclear roles. A third person may recognize that the team is responding to competing priorities set elsewhere in the organization.
None of these perspectives necessarily tells the whole story. Together, they give us a much clearer starting point.
Context mapping can also create a safer way for people to surface concerns. Instead of asking someone to openly criticize a decision or a leader, you’re inviting the group to examine the conditions affecting their work.
That shift can lead to a much more honest conversation.
When to use context mapping
Context mapping can be useful whenever the situation feels unclear, complicated or open to different interpretations.
For example:
Working through a leadership challenge?
Map the conditions affecting the leader, the team and the organization before deciding what support or intervention is needed.
Making a decision that will affect your team?
Invite team members into a mapping session so they can contribute information, identify concerns and help you understand the impact of different options.
Addressing a problem that crosses several departments?
Run separate mapping sessions with different groups, then compare what you hear. The differences between their maps may reveal where the real issue lies.
Creating a new strategy or action plan?
Use a context map to establish a shared understanding of where the organization is now before deciding where it should go next.
During my time as an Organizational Development Consultant, I helped government leadership teams develop strategies and action plans. I almost always began with a context-mapping activity. It helped us get the lay of the land before setting priorities. It also gave people space to raise the pressures, roadblocks and realities that were making the
work harder.
Without those conversations, it would have been easy to create a strategy that looked good on paper but didn’t reflect how the organization actually operated.
Better decisions begin with a better understanding of the situation
A context map won’t remove every unknown or guarantee that a decision will work exactly as planned. But it WILL help you slow down long enough to understand the conditions surrounding the decision, involve the right people and identify what you still need to learn.
That’s what creates confidence. Not certainty, but a clear and thoughtful reason for moving forward.
Download the free context-mapping template
If you’re working through a complicated problem, planning a change or preparing to make an important decision, I’ve created a free context-mapping template to help.
The resource includes the template and instructions for facilitating a context-mapping session with your team.
Use it to gather different perspectives, challenge assumptions and build a stronger foundation for your next decision.
Comments