2learn

Keeping people aligned and informed

What it is

Keeping people aligned is a plan, not a feeling: for each stakeholder, what they are told, in what form, how often, and who tells them. It includes the decisions they are asked to make and the date by which they have to make them.

Why it matters

Alignment decays. A decision made in a meeting in March is remembered differently by April, and by June the person who was not in the room has a different understanding of what was agreed. Regular, short, specific communication is cheaper than the renegotiation it prevents. It also makes silence visible: a stakeholder who has not responded has not agreed, and treating no answer as consent is how a surprise rejection arrives at the worst moment.

Core ideas

One line per stakeholder: what, when, by whom

Write the plan as a table and keep it short enough to maintain.

Who      What they get                          When       From
Maya     sign-off request with the risk note   before build  PM
Tom      one-line architecture impact note     monthly     tech lead
Priya    what changes for her team + FAQ       two weeks before release  PM
All      one-page status, decisions made       fortnightly PM

Note that each row names a decision or a change, not “an update”.

Ask for decisions, not for approval of a done deal

Bring the choice while it is still a choice. A stakeholder asked to approve something already built will either raise an objection that is now expensive or approve resentfully.

Surface disagreement early and in the room

If two key people disagree, get them into one conversation before the disagreement hardens into positions. Notes from separate conversations always diverge.

Record what was agreed, who was there, and what was rejected

One short note per decision, sent to the people in the room and the ones who were not. It is the only reliable protection against divergent memories.

Watch for silent stakeholders

Track who has not responded, not only who objected. Non-response is the commonest form of unmanaged risk.

Practice

Write a one-page communication plan

Produce the table above for a live piece of work, with a decision or a change in every row.

Done when: every stakeholder from the map has a row, and each row names a decision or a change rather than a general update.

Send a decision note and check it landed

Record a decision, send it to those present and those absent, and ask the absent ones to confirm or object.

Done when: at least one person replies with a correction, or all of them confirm in writing.

Common mistakes

  • Treating no answer as agreement — the objection arrives after the build; fix: track silence and follow it up.
  • Updates instead of decisions — nobody knows what they are being asked to do; fix: state the decision or the change in each message.
  • Asking for approval after the fact — the choice is gone and only resentment remains; fix: bring the options while they are still options.
  • Managing disagreements in separate conversations — the accounts diverge; fix: get the two people into one room.
  • No written decision note — memories diverge within weeks; fix: one short note per decision, to the room and the absentees.

Go deeper

Worked examples

Analytics cookies are set only if you allow them. Nothing is loaded, and nothing is sent, until you choose.