Decision forum operating guide

The outcome

The outcome of the decision forum operating guide is a repeatable path through this question: How should a recurring decision forum prepare, decide, record, and follow through? The working view makes purpose, entry criteria, and pre-read visible so discussion can move from general opinion to a specific action or decision.

When to run it

Run the decision forum operating guide when work in decision systems repeatedly crosses the same stages or handoffs and variation is causing delay, rework, or unclear ownership. Focus the first version on purpose, entry criteria, and pre-read rather than documenting every possible exception.

How the process works

The decision forum operating guide is a controlled sequence with explicit entry conditions, stages, handoffs, outputs, and exit criteria. Its core working elements are purpose, entry criteria, pre-read, and roles. Those elements belong together because each changes how the others should be interpreted or acted on.

Process stages

1. Purpose

State the intended contribution in plain language and distinguish the enduring purpose from the current plan. Within the decision forum operating guide, connect this entry to entry criteria so the relationship can be reviewed rather than inferred.

2. Entry criteria

Define the standard before judging the work, and make each criterion specific enough for two reviewers to apply consistently. Within the decision forum operating guide, connect this entry to pre-read so the relationship can be reviewed rather than inferred.

3. Pre-read

List the minimum complete inputs, their owners and due dates, and what happens when an input is late or unreliable. Within the decision forum operating guide, connect this entry to roles so the relationship can be reviewed rather than inferred.

4. Roles

Assign one accountable owner and distinguish final accountability from contributors, reviewers, and people who must be informed. Within the decision forum operating guide, connect this entry to agenda so the relationship can be reviewed rather than inferred.

5. Agenda

Define the intended output, required preparation, decision roles, time allocation, and record created at close. Within the decision forum operating guide, connect this entry to decision capture so the relationship can be reviewed rather than inferred.

6. Decision capture

Name the decision, the person or body with final authority, the date, and the rationale that should remain visible later. Within the decision forum operating guide, connect this entry to actions so the relationship can be reviewed rather than inferred.

7. Actions

Write a concrete next action with one owner, a due date or trigger, and a visible completion condition. Within the decision forum operating guide, connect this entry to service levels so the relationship can be reviewed rather than inferred.

8. Service levels

Capture service levels only at the level needed to answer: How should a recurring decision forum prepare, decide, record, and follow through? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the decision forum operating guide, connect this entry to health review so the relationship can be reviewed rather than inferred.

9. Health review

Set a review rhythm and define the evidence, threshold, or event that should trigger an earlier review. Within the decision forum operating guide, connect this entry to service levels so the relationship can be reviewed rather than inferred.