Tag Archives: team alignment

When there’s no right answer: get input, get commitment, then decide

Calls about who the team counts on for what are hard. Leaders worry about making valued people feel overlooked or diminished. Direct reports mostly want clarity, fair reasoning, and as much scope and recognition as they can reasonably earn. This post offers a way to handle those tensions: get input one-on-one, secure commitment to support the outcome, then decide and lead alignment.

Before you decide on a consequential call about who the team counts on for what, check in one-on-one with those who will be most impacted. Use these 1x1s to get their best thinking and secure an explicit commitment to support the outcome, whichever way you go. Then decide, own it, and lead everyone to align and execute. Remember: there is no single “right” organization. What works is what your team commits to make work. Don’t chase the perfect answer; make a sound call and then make the call right.

Start each 1×1 by setting context. Explain the decision you have to make and why it matters now. Ask them to set aside self‑interest and give you their best view of what to do and why. Probe for what you may be missing, the main risks, and how they would mitigate them. Listen hard. You are not asking them to decide for you; you are gathering the input you need to make the decision you are accountable to make.

Close every 1×1 with a clear ask for commitment to support whatever you decide. Say plainly that it is your job to decide and that, when you do, you expect full support either way. Make sure they know that support means words and deeds, in the room and outside the room. If they hesitate, stay with it. Surface concerns now, while you can still use them. If after a real conversation they cannot commit, that is useful data about whether they are on this team for this next phase.

After you decide, announce the decision and the reasoning at a level that lets reasonable people understand how you got there. Remind the team of the commitments made in 1x1s. Set the expectation that leaders will be visibly and consistently supportive, especially when they share the decision with their teams. Organizations change best slowly because change is hard on people, so favor steady, incremental moves and keep everyone clear on what is happening, why, and what you need from them. Sometimes it is better to roll out a major change as a series of smaller changes over a longer period.

If support slips, use a three‑step response that matches the moment:

  • First slip: private reset. Meet one-on-one to reaffirm the decision and what support looks like—words and deeds, in the room and outside the room. Ask for explicit recommitment. If they hesitate, stay with it. Surface concerns now, while you can still use them. Leave with a clear “yes.”
  • Second slip: public correction. In the moment and in front of others, restate the decision and the expectation to align. Keep it short, neutral, and firm. Move the conversation back on track.
  • Third slip: in or out. Meet privately, with your inner circle if helpful, and make the choice explicit: be fully in and support the path we chose, or step out. This is about whether they are part of the team that moves forward in a specific way. If not, help them out.

Two mindsets make this work. First, own the call. Do not attribute the decision to advisors, the board, or the market. Once you know, own it. Second, get help without becoming dependent on it. Invite strong input and dissent, and then decide. Disagreement before the decision is input. After the decision, alignment is the standard.

How organizations evolve

Organizations are not fixed. Treat structure and roles as means to an end, and expect them to change as you grow.A short script you can adapt

  • I need to make this decision. Before I do, give me your best thinking—what do you recommend and why? What am I missing? When I decide, can I count on your full support either way?
  • If you can’t commit, tell me now and we’ll address it. After I decide, we speak with one voice and execute.

Why this works is straightforward. Everyone is heard and treated with respect. Commitment is explicit, not assumed. You show up as decisive and fair. And if misalignment appears, you handle it quickly and cleanly.

Next steps

  • Run the 1x1s. Use the script above. Capture each leader’s recommendation and explicit commitment in writing.
  • Book an IntelliVen workshop for your ELT. A focused 60–90-minute session to practice the Input → Commitment → Decide method on a real decision. Includes prep and a follow‑up plan.
  • Enroll in Manage to Lead (MtL) training. Apply the seven truths and the W‑W‑W framework to your strategy and org design.
  • Share the “How organizations evolve” section with your ELT. Ask each leader to name one risk and one action to support the change.
  • Set a cadence checkpoint. For the next four ELT meetings, include a 10‑minute alignment check on this decision.
  • Want help? Invite IntelliVen to facilitate your first round of 1x1s or the in‑or‑out conversation.

Get Clear. Align. Grow.

Process Maps Turn Confusion Into Clarity

Participants in IntelliVen’s Manage to Lead (MtL) program sometimes ask: “Why do we need to work on process maps?” It’s a fair question. The answer is that process mapping is not theory or busywork — it’s a practical tool you use on your own organization to turn hidden confusion into shared clarity. What follows explains how and why it works.

Every team member operates with their own mental map of how work gets done. The problem is, those maps rarely match. When they stay hidden, confusion builds, errors repeat, and opportunities slip away. Process maps transform scattered assumptions into one clear picture everyone can see, use, and improve together.

Turn Individual Mental Maps Into One Shared View

Organizations are an ecosystem of activities. Sales, delivery, support, finance, and HR leaders each hold pieces of the whole. Ask ten people how a key workflow happens across functions—say, onboarding a new customer—and you may hear ten different answers.

The same fragmentation shows up inside functions too: two sales reps handling similar opportunities may qualify leads or prepare proposals in completely different ways, even though the organization has learned a best practice for how it should be done.

When leaders work with their teams to draft a process map, a good first step is for each person to draw their own version of how the work gets done. Those maps reveal the similarities and differences in how people think the process works.

Looking at them side by side sparks discussion and exposes assumptions that would otherwise stay hidden. Collaborating to reconcile those views into a single, explicit picture reduces misunderstandings, strengthens alignment, and sets the stage for systematic improvement.

This aligns with the IntelliVen “Get Clear” truth: clarity is the first step to higher performance. Without it, even the best strategy gets lost in translation.

Make Handoffs, Gaps, and Choke Points Explicit

Once the flow of work is on paper (or screen), weak spots stand out. Teams can see:

  • Handoffs where work might fall between the cracks.

  • Gaps where no one is clearly responsible.

  • Choke points where one role or tool becomes a bottleneck.

  • Redundancies where two people are doing the same thing.

  • Error-prone steps where mistakes often creep in.

  • Measures—formal or informal—that indicate whether things are on track.

In day-to-day operations, these issues hide in plain sight. People learn to work around them. But a process mapping exercise surfaces them for open discussion.

This step mirrors the “NOW” stage of IntelliVen’s Change Framework. Leaders and teams must start with a clear-eyed view of how things currently work before they can chart a better “NEXT.”

Examine for Potential Breakthroughs

Mapping processes is not just about fixing problems. It’s about discovering opportunities.

When the whole flow is visible, leaders can ask:

  • What would happen if we automated this step?

  • Could two teams combine efforts to reduce time and cost?

  • Are we measuring what matters most?

  • Where could a small shift create disproportionate gains?

Sometimes, the exercise reveals breakthroughs. For example, moving a routine approval up in the process can cut cycle time in half. Or spotting a recurring customer question may inspire a new self-service product feature.

Organizations that grow successfully over time are those that consistently find and exploit such breakthroughs. Process maps are a tool to make them visible.

Ensure the Whole Team Plays the Game the Same Way to Win

Strategy is about how to win. Operations is about how to play the game. To succeed, the two must connect.

Process maps make the “playbook” explicit. They allow everyone—leaders, managers, staff, and partners—to see the same game board and understand their role on it. This alignment ensures:

  • Consistency: Consistency makes it easier to ensure everyone follows best practices and onboard new people. Consider an organization where half the professionals operate at peak effectiveness while the other half lag. If the whole team consistently applied the practices of the top performers, overall output and impact would rise dramatically. Process modeling is a step toward making that possible.
  • Efficiency: A shared map keeps teams from having to inventing steps or duplicate effort which frees time and energy for higher-value work. Efficiency in this sense isn’t just about speed — it’s about reducing rework, avoiding missteps, and channeling resources where they matter most.
  • Accountability: With a clear, shared process, everyone knows what’s expected of them and when. Instead of relying on memory, assumptions, or informal workarounds, roles and responsibilities are visible. This makes it easier to spot when something is off track and to coach or support people in real time, building trust and confidence across the team.

  • Scalability: Growth is hard when every new person has to “figure it out” on their own. A well-documented process gives newcomers a tested playbook so they can contribute faster and more reliably. It also allows leaders to delegate with confidence, knowing the approach will hold up even as volume increases or teams expand.

In IntelliVen terms, process maps help teams collaborate to “Get Clear and Get Aligned.” They make it easier for leaders to contract with their teams, govern effectively, and review performance against clear expectations.

Practical Tips for Leaders

If you’re considering introducing process mapping, here are some practical guidelines:

  • Start with one important process. Don’t try to map everything at once.

  • Involve people who do the work. They know the reality better than managers.

  • Keep it simple at first. Boxes, arrows, and labels are enough to start.

  • Use present tense. Describe how things actually happen now, not how they should.

  • Capture both formal and informal steps. Workarounds often carry key insights.

  • After mapping, ask: “What can we stop, start, or change to improve performance?”

  • Revisit maps as your organization evolves. A process that works today may need adjustment tomorrow.

Closing Thought

Working on process maps is not busywork. It is a leadership act. It shows commitment to clarity, alignment, and continuous improvement. It turns hidden assumptions into shared understanding. It shines light on bottlenecks and opportunities. And it ensures that your whole team is indeed playing the same game, the same way, to win together.

In short: process maps help leaders Get Clear. Align. Grow.

Put These Ideas Into Practice

In the Manage to Lead (MtL) program, you don’t just study tools like process mapping — you apply them directly to your own organization. YOUR CASE IS THE COURSE. By working hands-on with proven frameworks, you and your team surface hidden assumptions, sharpen execution, and accelerate performance. Learn more about the MtL program here »