Tool

Executive Alignment Score

An eight-question scorecard that tests whether your executive team has actually aligned on a decision, or has simply stopped arguing about it.

Score the specific decision your team believes it has agreed. The questions and points are fixed, the result is calculated in your browser, and nothing you answer is stored.

Last reviewed 3 July 2026 · Free and ungated

Pressure-test this decision

Your team has settled on a position; the score only measures how hard anyone has pushed against it. Have selected senior operators from the Global Board push harder, confidentially, before it is announced.

Pressure-test this decision

How a client brief works · What you receive

Fixed questions · no AI · nothing stored

Run the scorecard

Answer for the decision your team last discussed together, as honestly as the corridor conversations would.

0–39 Misalignment likely 40–59 Surface alignment 60–79 Working alignment 80–100 Genuine alignment How our tools are scored
  1. Shared definition of the decision Would each executive describe the decision being made in the same terms?
    • Ask three executives and you would hear three different decisions
    • The headline matches, but scope and stakes are described differently
    • Everyone states the same decision, scope and stakes
  2. Agreement on success measures Has the team agreed how the outcome will be judged?
    • Success has not been defined beyond general intent
    • Measures exist, but each function privileges its own
    • Agreed measures, with one set of numbers everyone will be judged on
  3. Problem agreed before the solution Did the team agree what problem this solves before choosing an answer?
    • The solution arrived first and the problem was written to fit it
    • The problem is broadly shared, but was never examined together
    • The problem was agreed and documented before options were compared
  4. Where dissent is expressed Do disagreements surface in the meeting or in the corridor afterwards?
    • The meeting agrees; the corridor conversations do not
    • Some objections are voiced, but the sharpest ones are saved for later
    • Disagreement is aired in the room, on the record, and worked through
  5. Functional priorities surfaced Has each function stated what it needs from this decision?
    • Functional agendas are guessed at, not stated
    • Some functions have declared their priorities; others are staying vague
    • Every affected function has put its priorities on the table
  6. Deal-breakers stated Does anyone hold a red line they have not declared?
    • Nobody has been asked what would make them oppose this
    • Deal-breakers were asked for, and the answers were diplomatic
    • Each executive has stated what would make them withdraw support
  7. Alignment on timing Does the team agree on when this must be decided, and why?
    • The urgency belongs to one sponsor; others see no deadline at all
    • Rough agreement on timing, driven by the calendar rather than argument
    • The team agrees on the timing and on the reasons behind it
  8. Alignment on who decides Is it clear whose call this finally is?
    • Several people believe the decision is theirs to make
    • The decision-maker is named, but others expect a veto
    • One agreed decision-maker, with everyone else's role explicit
Reading the score

What the result bands mean

0–39: Misalignment likely

On these answers, the agreement in the room is thinner than it looked. Each executive is carrying a private version of the decision, and execution will surface the differences at the worst possible time: after budgets are committed and positions are public.

40–59: Surface alignment

The team agrees on the headline and diverges underneath it: on success measures, on timing, or on who finally decides. Decisions in this band leave the meeting looking approved and then slow down in execution, as each function delivers the version it thought it endorsed.

60–79: Working alignment

Most of the foundations of genuine alignment are present, and the gaps that remain are specific: usually an undeclared deal-breaker, or a disagreement about timing that has been politely deferred. Teams in this band can proceed, provided the open items are named rather than left to surface mid-delivery.

80–100: Genuine alignment

The team has done the unglamorous work: a shared definition, agreed measures, dissent aired in the room. What a high score cannot rule out is comfortable convergence, where a team aligns quickly because its members have grown alike in how they read the market.

The gap between agreement and alignment

Executive teams rarely leave a meeting misaligned on purpose. The pattern is more comfortable than that: the meeting closes on a form of words everyone can accept, each function reads its own priorities into that wording, and three months later two departments are executing two different decisions under one name. By the time the divergence shows up in delivery it looks like an execution problem, which is why the alignment failure that caused it is almost never diagnosed.

Who should score alignment

  • Chief executives testing whether their team's agreement will survive contact with delivery.
  • Sponsors about to commit budget on the strength of an executive meeting's nod.
  • Chairs and non-executives wondering whether a united presentation reflects a united team.

When to run it

The most revealing moment is between agreement and announcement: the decision feels made, but nothing external has locked it in yet. Run it again if the team changes, because alignment belongs to the people who built it. A new CFO or divisional head inherits the decision without inheriting the agreement.

How the scoring works

Eight questions, three fixed answers each at 0, 5 or 10 points, normalised to 100 and mapped to four bands. Two people scoring the same decision differently is not a flaw in the tool. The gap between their scores is the misalignment, measured.

Frequently asked questions

Should the team score this together or separately?

Separately first, then compare. Scoring together reproduces the meeting dynamics the tool is trying to see past: the same voices carry, and the same silences pass for agreement.

Our team debates hard and still scores low. Is that a problem?

A team that argues openly and scores low is in better shape than one that scores mid-range through politeness. Low scores from honest debate identify real work; comfortable scores from avoided debate hide it.

What if the misalignment involves the chief executive?

That is the most common and least discussable case, which is why the written-paragraph test works better than another meeting. It lets disagreement with the most senior person in the room surface as drafting feedback rather than confrontation.

Alignment that was never tested is a bet, not a plan.

Pressure-test this decision