AllMeetingsDecisionsProduct

State what can still change before the meeting

A meeting wastes time when participants cannot tell which parts of the proposal are choices and which parts are constraints.

Mira sorts constraint cards with two teammates around a standing table before a decision meeting.

Before a decision meeting, state what can still change. Separate the fixed constraints from the open choices, name who can move each boundary and explain when a fixed point may be reopened.

Without that map, participants solve different problems. One person treats the launch date as immovable. Another spends twenty minutes proposing later dates. A third thinks the budget is flexible but discovers after the meeting that finance never authorised an increase.

The disagreement may look strategic. Often it is simply a disagreement about the shape of the decision.

Divide the proposal into fixed, open and conditional

Do not label the whole proposal “open for discussion.” Break it into parts.

For a pilot launch, the boundary might look like this:

PartStatusMeaning
Regulatory reviewFixedThe pilot cannot begin before approval.
Pilot audienceOpenThe meeting may choose one customer group or two.
Support staffingConditionalThe plan may change if the support lead confirms capacity.
Approved budgetFixed for this meetingA larger request needs finance approval outside the room.

These labels describe authority, not importance. A fixed constraint may be the most important fact in the meeting. An open choice may be relatively small. The point is to show where discussion can produce a legitimate change.

Avoid calling a preference fixed merely because its owner feels strongly about it. “The executive wants Friday” is not the same as “the contract requires delivery by Friday.” Name the real source of the boundary so people can judge it honestly.

Name the person who can move the boundary

Every fixed or conditional point needs an owner of authority.

That does not mean the person who wrote the slide. It means the person or body that can legitimately change the constraint: the budget holder, security reviewer, client, regulator or named decision owner.

Write the boundary in a way that exposes that authority:

The pilot budget is fixed at the approved amount for this meeting. Priya can submit a larger request to finance, but this group cannot approve it today.

Now the room knows what to do with an attractive option that costs more. It can reject the option, redesign it to fit, or create a recommendation for finance. It should not act as though enthusiasm has changed the budget.

If nobody can identify who owns a boundary, treat that as a preparation problem. The meeting is not ready to rely on a constraint whose authority is unknown.

Tell people why the constraint exists

A bare “not negotiable” invites either passive acceptance or a fight about status. Give the shortest useful reason.

Compare:

The release date is fixed.

with:

The release date is fixed because it is tied to the signed migration window. The client sponsor can approve a different window; nobody in this meeting can.

The second version helps participants design within the real limit. It also shows how the limit could change without pretending the current room has that power.

Keep the explanation proportional. The agenda does not need a legal brief for every constraint. It needs enough context to stop the meeting from repeatedly testing a locked door.

Link the supporting source when the boundary depends on a contract, policy, prior decision or technical finding. A constraint without a recoverable source becomes folklore, and folklore tends to harden long after its original reason has disappeared.

Define the reopening test

“Fixed” should rarely mean fixed forever. It usually means fixed under the evidence and authority available now.

Add a reopening test when circumstances could change:

  • reopen the audience limit if support confirms two additional shifts;
  • revisit the vendor choice if the security review finds a critical issue;
  • reconsider the date if the client sponsor approves a new migration window;
  • return to the budget if finance accepts a quantified request.

This keeps participants from relitigating the same point on instinct. It also stops the team from preserving an obsolete constraint simply because the minutes once called it fixed.

The test should name evidence or authority, not a mood. “If people remain concerned” is not a test. “If the load test exceeds the agreed threshold” is.

This is different from giving a decision an expiry rule. An expiry rule says when an existing decision stops being safe to use. A reopening test says what new fact would put a constraint back into scope.

Put the boundary in the agenda, not only in the room

Participants should see the boundary early enough to prepare useful input.

Add four lines to the agenda or pre-read:

Decision: Choose the pilot audience and support model.

Fixed: Regulatory approval must arrive first; spending stays within the approved pilot budget.

Open: One customer group or two; weekday-only or extended support.

Can change if: Support confirms capacity, or finance approves a larger request.

This complements a focused meeting pre-read. The pre-read tells people what question to answer. The boundary tells them which answers are actionable.

Invite people to challenge the map before the meeting. A participant may know that a supposed constraint has already changed, or that an “open” choice requires approval from someone absent. Finding that out in advance is preparation working as intended.

Use challenges to repair the map

When someone challenges a fixed point during the meeting, do not shut them down automatically. Ask three questions:

  1. What new evidence are you bringing? A changed fact may justify reopening the boundary.
  2. Who has authority to change it? The right evidence in the wrong room may need a recommendation and escalation.
  3. Does this block today’s decision? Some challenges can become follow-up without preventing the remaining choice.

If the challenge is valid and the owner is present, update the boundary aloud. If authority or evidence is missing, record the objection and route it. Do not quietly let a fixed point become open through persistence, and do not quietly preserve it after its basis has failed.

The final read-back should include the boundary that shaped the call:

We chose the single-group pilot within the approved budget. The budget stayed fixed because finance was not part of today’s authority. Priya will request the additional amount; approval would reopen the audience choice before the launch date.

That explanation belongs with the decision. Scripta can keep the notes, decision, reasoning and resulting actions in one meeting record. The team still has to state which constraints were real and which choices remained open.

A decision meeting needs a visible edge

Good discussion is not unlimited discussion. It works inside a boundary that participants can see, question and, when the right evidence or authority appears, change deliberately.

Before the invite goes out, mark what is fixed, what is open and what is conditional. Name the owner and the reopening test. The meeting can then spend its time on the choices it is actually capable of making.

FAQ

What is a decision boundary?
A decision boundary states what the meeting may change, what is fixed for now and who has authority to alter a constraint. It keeps advice focused on choices the room can actually make.
What if someone challenges a fixed constraint?
Ask whether they have new evidence or the authority to change it. If so, reopen it explicitly. If not, record the objection and route it to the person who owns that constraint instead of letting it consume the meeting.
Should fixed constraints appear in the meeting minutes?
Yes. Record the important constraints beside the decision and reasoning so a future reader can see why apparently available options were excluded.