by: Brian Alvo

‍

A project launches with energy, then drifts into a familiar pattern. Two groups solve the same problem in parallel. A “quick update” meeting swells into an hour because people keep discovering missing backgrounds. Decisions stall because nobody knows who owns the call, what constraints matter, or what the work connects to upstream.

Teams rarely fail from a lack of effort. They fail from a lack of shared meaning about the effort.

‍

Make context a daily leadership practice

Context feels like something you either have or you do not. That framing sets leaders up to chase the wrong solution, usually more updates, more channels, more decks, and more meetings.

Brian Alvo, a Six Domains of Leadership Certified Coach who works with managers, directors, and executive teams, sees the issue differently. He describes contextual leadership as “the hard work of focus, simplification, and coherence.” People struggle to distill messages into something simple, and they struggle to help teams feel the impact of their work on the broader organization. That gap shows up as friction that nobody can quite name, even as everyone feels it.

The good news is that context is a leadership behavior that you can practice, measure, and improve. With it, you can help your team align faster, decide with less drama, and understand how today’s tasks connect to tomorrow’s outcomes.

‍

‍

Treat missing context as a system problem you can fix

Context disappears in predictable ways. It fades when teams grow, when work distributes across time zones, when tools multiply, and when priorities shift faster than leaders translate them into meaning people can use.

Leaders often respond by pushing harder on communication volume. The better response starts with diagnosis. Context gaps leave fingerprints in how work feels, how decisions move, and how people talk about priorities.

It is important to recognize the specific places context collapses in your organization so you can fix the system instead of blaming individuals.

‍

Name the three signals that context collapsed

Duplicated work offers the clearest signal. Two competent teams rarely choose to redo each other’s work; they do it because they never shared the same picture of the goal, the constraints, or what “done” means.

Another signal shows up as stalled decisions that look like over-collaboration. People keep “aligning” because they do not trust that the decision connects to the larger plan. They request one more stakeholder, one more review, one more meeting, then call it risk management.

A third signal shows up in morale. Teams start describing their work as task completion rather than problem solving. People stop saying what they learned, what changed, and what tradeoff they made, then they start saying what they finished. That language shift tells you the work lost its story, which means the team lost context.

‍

Track where context leaks in hybrid and fast growth

Remote and hybrid work increase your dependence on intentional context-sharing. Informal repair loops shrink. A hallway chat that used to correct a misunderstanding never happens, so the misunderstanding ships.

Fast growth creates another leak. You add people and teams quickly, then you assume onboarding covers the gaps. Onboarding rarely carries the nuance of why the organization chose a path, what it tried, and what it will not do again. That history holds critical context, and leaders often keep it in their heads.

Silos also hoard context in plain sight. Teams can share data and still hide meaning. A dashboard can tell you what happened without telling you what matters, what changed, and what leaders plan to do next. Context leaks when you share artifacts without sharing interpretation.

‍

‍

Stop rewarding speed that creates rework

Many organizations reward fast shipping in ways that quietly punish context-building. Leaders celebrate the person who “just got it done,” even when the work creates downstream confusion that someone else cleans up later.

That celebration creates a hidden cost. When speed becomes the visible metric, people start saying yes to everything rather than risk looking slow, and they rarely say what they're trading off to hit the deadline. Brian sees this often with high-achieving leaders: they take on too much, then feel disappointed when something slips, without realizing the real problem was an unstated tradeoff rather than a lack of effort. 

Context fixes this because it forces tradeoffs into the open. When priorities stay implicit, teams treat every request as equally urgent, which is exactly what produces the rework leaders are trying to avoid in the first place. Speed stays valuable, yet it becomes reliable only when leaders pair it with clarity about what's being protected and what's being sacrificed to get there. 

‍

‍

Build contextual leadership that people can feel

Contextual leadership can sound academic until you translate it into what teams experience day to day. Brian reduces it to a few practical ideas: focus, simplification, coherence, and helping people register the impact of their work.

Teams rarely need more information. They need fewer, clearer messages that survive retelling, plus shared agreement about what matters, what changes, and who decides.

It is important to know how to communicate context in forms your team can reuse, repeat, and act on.

‍

Simplify until the message survives retelling

A message has context when someone can retell it accurately two levels away from you. That becomes a useful standard because it forces leaders to separate signal from noise.

Start with the single sentence that answers what the team needs to accomplish and why it matters to the organization this quarter. Leaders often add three more sentences, then five qualifiers, then a list of edge cases. The result feels “thorough” while becoming unusable.

Simplification also means you choose language that matches how people talk. The model's category names — personal, relational, contextual — are useful in a debrief, but most teams move faster with plain speech: personal becomes 'what you're responsible for,' relational becomes 'who else this affects,' and contextual becomes 'what's actually going on around this.' When your words reduce translation effort, context travels farther. 

‍

Connect work to impact instead of reciting the why

Many leaders share the why and still miss context. Teams nod at purpose statements, then return to tasks because the purpose never touches their daily decisions.

A more practical move connects today’s work to impact in the broader organization. People want to know that their work matters, how it changes outcomes, and what it enables for the next team downstream. That explanation takes time and attention, which makes it rare, which makes it powerful.

This also changes how you run updates. A status report that starts with “what changed in the environment” and “what we learned” carries more context than a list of completed tasks. It gives people the logic of the work, which lets them make better decisions when you are not in the room.

‍

Clarify decision rights so teams can move

Context includes authority boundaries. When people lack clarity about who decides, they fill the gap with consensus behaviors that slow everything down.

Decision rights sound formal, yet they can stay simple. Teams need to know who recommends, who decides, who must contribute input, and who needs to stay informed. Leaders often assume everyone understands this, then discover the confusion only after a missed handoff.

This also reduces politics. When decision paths stay unclear, people escalate to power instead of process. Clear decision rights give teams a shared map, and that map becomes a form of context that prevents rework and resentment. With that foundation, context can cross silos through relational habits rather than heroic effort.

‍

Give the team an identity, not just a task list

Context also includes identity: a shared answer to the question "what kind of team are we?" Without it, people borrow their sense of purpose from job titles or whatever's on the sprint board, which gives them little to hold onto when priorities shift.

Identity doesn't require a slogan or an offsite. It shows up in language a leader repeats often enough that the team starts using it to describe themselves. A leader might say, "We're the team that catches problems before customers see them," or "We're the team other departments call first when something's on fire." That sentence becomes shorthand for standards, priorities, and even what gets recognized in a performance conversation.

When a team can name its own identity, individual tasks stop feeling like isolated items on a list and start feeling like contributions to something specific. That shift is what eventually turns coordination into community — which is really the point of contextual leadership in the first place.

‍

Use relational habits that carry context across silos

Context rarely moves through systems alone. It moves through people who trust each other enough to ask, clarify, and challenge. That places relational leadership right next to contextual leadership.

Brian notes that many developing leaders score strongly in relational and supportive domains, yet they still struggle with inspirational and contextual behaviors. That makes sense: relationship skills can keep work pleasant while context problems keep work inefficient.

‍

Slow down enough to earn curiosity and candor

Relational leadership often starts with pace. Leaders rush, then they skip the small moments that build familiarity, which makes real clarification feel risky later.

Slowing down does not require long conversations. It requires a consistent willingness to ask and listen, even briefly, so people experience you as approachable. That increases the chance they will share early signals, including the uncomfortable ones that prevent bigger problems.

Hybrid work raises the bar here. Without in-person connection, you need extra effort to build relationship. That effort pays for itself when someone flags a misunderstanding early rather than letting it grow into a cross-functional conflict that burns a week.

‍

Invite feedback that improves the work without harming trust

Many leaders receive feedback better than they give it. They want to improve, and they avoid harming relationships by delivering tough messages. That pattern keeps teams polite while context remains fuzzy.

A practical move involves normalizing feedback as part of the work instead of a special event. When a leader says, “Tell me where this plan feels unclear,” they create a channel for context repair without implying someone failed.

360° assessments can help because they gather perspectives across peers, direct reports, and supervisors. The Six Domains of Leadership Survey (SDLS) offers behavior-focused feedback built from more than twenty years of research at Duke University’s Fuqua School of Business, led by professors Sim Sitkin and Allan Lind, and it has logged more than 15,000 assessments. Still, the real win comes when leaders turn feedback into conversation, then make the group part of the growth cycle.

‍

‍

Make delegation explicit so support feels real

Supportive leadership often breaks down when leaders fear overloading people or fear disappointment. They “delegate,” yet they carry an unspoken preferred method, then they correct after the fact. People experience that as hovering.

The fix starts with clarity. When you hand off work, name what outcomes matter, what constraints exist, and where the person has freedom. That frames context and support in one move.

Low-risk delegation offers a strong entry point. Leaders can choose one task that matters but will not sink the project if it goes imperfectly, then let the person own it end to end. That tests assumptions and builds confidence, which makes deeper contextual work easier because people start taking initiative instead of waiting for instruction.

‍

Use responsible leadership to raise accountability without blame

Context gaps often turn into accountability fights. Someone misses a deadline, another team feels blindsided, and leaders search for the person to correct. That approach lowers trust and teaches teams to hide uncertainty.

Responsible leadership offers a better route. It focuses on stewardship, ethics, and ownership, and it gives leaders a way to hold standards while protecting people from scapegoating.

Good leaders know how to raise accountability in ways that strengthen context rather than erode it.

‍

Protect people while still raising the bar

Many leaders protect their teams well. They avoid pointing fingers upward, and they absorb pressure. The harder move involves holding the team accountable inside the group through direct, respectful conversations.

This matters because context requires candor. People will not share what they do not understand if they think confusion will get punished. When leaders separate blame from responsibility, they create room for early clarification.

A useful habit involves naming the standard in behavioral terms, then asking for a plan. Leaders can say, “Our partner team needs a one-page summary of assumptions and constraints before build starts,” then ask, “What will you change so we do that every time.” That sets accountability as an operating rhythm rather than an emotional event.

‍

Replace vague standards with observable behaviors

Leaders often talk about fairness, respect, courage, and integrity as if everyone shares the same definition. Brian points out that words like fairness and respect carry deep, personal interpretations shaped by experience and upbringing. That ambiguity turns values into conflict.

Observable behaviors reduce the ambiguity. “Listen without interrupting” carries more meaning than “show respect.” “Explain the tradeoff you made” carries more meaning than “be transparent.” These behaviors also travel well across teams because they require less interpretation.

The Six Domains framework helps when leaders translate domain language into visible actions. A team does not need to debate whether someone demonstrates contextual leadership if the team agrees that every project kickoff includes purpose, constraints, decision rights, and what success looks like.

‍

Make ethical tradeoffs discussable before they become crises

Ethics rarely show up as dramatic dilemmas. They show up as small tradeoffs about speed versus quality, customer promises versus internal capacity, and short-term wins versus team health.

Leaders can make ethics discussable by naming tradeoffs early. That acts as context because it explains why a decision looks the way it does and what the organization values in practice.

This also improves motivation. People feel safer and more committed when leaders show stewardship, even during pressure. That sets up the final piece: using feedback and measurement so context-building stays real rather than aspirational.

‍

Use 360 feedback to turn confusion into a growth cycle

Many leaders avoid 360° feedback after one bad experience, and executives often hold strong preferences for how they want feedback delivered. That makes sense: feedback can sting, and senior leaders carry a long memory of tools that felt political or unhelpful.

Still, behavior-based feedback offers one of the clearest ways to locate where context breaks between intention and impact. The Six Domains of Leadership Survey focuses on observable actions across personal, relational, contextual, inspirational, supportive, and responsible leadership, which helps leaders talk about what changed rather than argue about personalities.

The SDLS gives 360 feedback in a way that produces action without overwhelming people.

‍

Choose a small set of changes that matter

A data-heavy report can overwhelm a high achiever. Brian encourages people to focus on one or two things, which often leads to meaningful progress. That restraint matters because context grows through repetition, not aspiration.

Leaders can choose priorities by anchoring them to the leader’s real goals and stakeholder input. When a manager says they want to build stronger cross-functional partnerships, and peers say they often lack clarity about priorities, contextual leadership becomes a natural target.

Small scope also helps you prove progress quickly. A leader who commits to one habit, such as sending a weekly “what changed and why it matters” note, can create visible improvement in how the team coordinates within a month.

‍

Upgrade written comments so they guide action

Quantitative scores show patterns. Written comments supply the explanation. Many 360° processes underdeliver on comments because raters stay vague or polite.

A simple improvement involves prompting raters to include a “because” statement. “You communicate clearly because you summarize decisions at the end of meetings” gives the leader something to repeat. “You cause confusion because priorities change without explanation” gives the leader a behavior to change.

Leaders also need help reading comments well. The goal involves spotting themes rather than litigating each line. A coach can reinforce positive patterns too, since many leaders fixate on what went wrong and miss the behaviors they should continue.

‍

Recheck progress through conversations, not constant surveys

Teams often assume measurement requires repeating the same assessment quickly. Many leaders can learn faster through direct conversations with the people who experience their leadership daily.

A leader can return to the group and ask for one suggestion tied to a specific theme from the feedback. They do not need to identify who wrote what. They only need to make growth visible and shared.

This creates a virtuous cycle. Feedback becomes a normal part of work, context becomes easier to repair, and leadership development becomes less about theory and more about the daily behaviors that make teams coherent.

‍

Turn context into an operating rhythm

Context feels missing when leaders leave it to chance. It returns when leaders treat it as a practice: simplifying messages until they travel, linking work to impact so it matters, clarifying decision rights so work moves, giving the team an identity worth repeating, and building relationships strong enough to carry hard conversations across silos.

The Six Domains of Leadership Survey and similar tools help when they translate ideals into behaviors and open better conversations. The most durable fix still comes from what you do every week with your team: the moments when you slow down, connect the dots, and make meaning shareable.

If you want a structured way to identify where intention and impact diverge across your team, schedule a consultation call to explore whether a behavior-based 360 such as the Six Domains of Leadership Survey fits your current goals and team realities.

‍

‍

Brian Alvo

Brian Alvo is a Six Domains of Leadership Certified Coach and the founder of NextGen Center, a leadership development company that works with organizations of 25 to 500 employees across industries ranging from technology and biotech to insurance, construction, and consumer products. He earned his MBA from Duke University's Fuqua School of Business, where he first studied the Six Domains framework academically, and spent time across the public sector, corporate roles, and startups before launching NextGen Center roughly a decade ago — after noticing how often first-time managers were handed bigger responsibilities with little training or support to match.

Brian works primarily with directors, managers, and executive teams who are stepping into larger leadership roles, focusing on the interpersonal skills and self-awareness that formal training often overlooks. He is credentialed through the International Coaching Federation (PCC)

‍