"We need to get aligned" is not a session goal

"We need to get aligned" is a symptom description, not a session goal. It says how the requester feels now, not what the group will have produced by day's end. Of the session briefs we've seen in the last 90 days, one in six named alignment as the purpose, and three in four of those attached it to nothing decidable. No choice, no commitment. Just the word.

A goal you can't check is one you can't design against. This is field-wide, not personal: SessionLab's State of Facilitation 2026 found fewer than one in three facilitators has agreed measurable indicators with their clients, and 43.5% name missing follow-up conversations as the main barrier to impact. Unclear goals sit just behind. The fix belongs at contracting, before the session.

Aligned is what it looks like afterwards

Alignment isn't an output. It's what you observe after a group has decided something together and each person can still say the same thing about it a week later. So the intake job is to find the decision underneath the request. There's nearly always one; the requester has avoided saying it, because saying it makes someone uncomfortable.

Push for the shape "We will do X instead of Y, starting when," in at most 20 words. Get that sentence and you have a session. Get "everyone on the same page about the roadmap" and you have a symptom.

The one-sentence test

A stated goal is decidable when it passes all three:

• It names a choice someone could still say no to. "Agree on priorities" fails; "Drop two of five Q4 initiatives" passes.
• It names who has to say yes, by name, and those people are on the invite list.
• Three participants, asked a week later to write down what was decided, produce sentences that match in substance.

Fail one and don't pick a format yet. Length is the usual casualty: more than half the sessions we see run four hours or longer, and a full day built on a symptom changes nothing.

Three readiness questions you can ask at intake

HBR's August 2026 piece on strategy readiness adds a second filter. Its Readiness Triad checks appetite (do people own the outcome), capacity (bandwidth to sustain it) and skillset (can they do what it demands). It cites McKinsey and BCG research finding roughly 30% of large change programmes deliver expected value, with failures tracing to one of those gaps rather than to the strategy itself.

All three are answerable in a phone call, and each turns a vague brief into a checkable condition. The tactics transfer into the agenda: tie the decision to something the group already values, rehearse at low stakes first, and name one initiative that gets postponed so this one can succeed.

Run this before you design anything

30-minute intake conversation with the requester

• 0-5 min — Describe a Tuesday. "Three weeks after the session, what are people doing differently on an ordinary Tuesday?" Write down only the verbs. Output: up to five observable behaviours.
• 5-12 min — Find the decision. "What can this group not decide right now, or what does it decide differently in different rooms?" Keep asking until you get "We will X instead of Y." Write it in 20 words or fewer and read it back. No sentence after seven minutes means no decision is available yet. Note that.
• 12-18 min — Name the deciders. Names, not roles. Check each against the invite list. Any decider missing means the session can only produce a recommendation, so rewrite the sentence to say exactly that.
• 18-25 min — Ask the readiness three. Appetite: "Who wants this outcome, and who loses something if it happens?" Capacity: "What gets stopped to make room?" Skillset: "When did this group last make a decision this size, and did it hold?" Score each yes, no or don't know. Two or more don't-knows means the session is for surfacing, not deciding.
• 25-30 min — Contract the check. Agree the follow-up date (seven days after), the method (three participants write the decision in one sentence, unprompted) and the pass mark (three of three match in substance). Then agree length: one sentence plus all deciders in the room caps you at half a day.

When there's no decision yet

Say it out loud on the intake call: "There isn't a decision here yet, so a day won't produce one." Propose the smaller session. Two hours, output a written list of the three to five positions in the room, who holds each, and what would have to be true for each to win. That list is what makes a decision session possible a month later.

Once the sentence exists, paste it into Session Studio: describe the decision in that one line and it drafts the timed agenda around it.

Sources

• Before Rolling Out a New Strategy, Assess Your Team's Readiness — Harvard Business Review, August 2026
• State of Facilitation 2026 — SessionLab, January 2026