Feedback workflow board

The outcome

The outcome of the feedback workflow board is a repeatable path through this question: What states and transitions make feedback processing visible and accountable? The working view makes intake, needs information, and acknowledged visible so discussion can move from general opinion to a specific action or decision.

When to run it

Run the feedback workflow board when work in feedback and customer insight repeatedly crosses the same stages or handoffs and variation is causing delay, rework, or unclear ownership. Focus the first version on intake, needs information, and acknowledged rather than documenting every possible exception.

How the process works

The feedback workflow board is a controlled sequence with explicit entry conditions, stages, handoffs, outputs, and exit criteria. Its core working elements are intake, needs information, acknowledged, and assessed. Those elements belong together because each changes how the others should be interpreted or acted on.

Process stages

1. Intake

Capture intake only at the level needed to answer: What states and transitions make feedback processing visible and accountable? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the feedback workflow board, connect this entry to needs information so the relationship can be reviewed rather than inferred.

2. Needs information

Capture needs information only at the level needed to answer: What states and transitions make feedback processing visible and accountable? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the feedback workflow board, connect this entry to acknowledged so the relationship can be reviewed rather than inferred.

3. Acknowledged

Capture acknowledged only at the level needed to answer: What states and transitions make feedback processing visible and accountable? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the feedback workflow board, connect this entry to assessed so the relationship can be reviewed rather than inferred.

4. Assessed

Capture assessed only at the level needed to answer: What states and transitions make feedback processing visible and accountable? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the feedback workflow board, connect this entry to committed so the relationship can be reviewed rather than inferred.

5. Committed

Capture committed only at the level needed to answer: What states and transitions make feedback processing visible and accountable? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the feedback workflow board, connect this entry to in progress so the relationship can be reviewed rather than inferred.

6. In progress

Capture in progress only at the level needed to answer: What states and transitions make feedback processing visible and accountable? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the feedback workflow board, connect this entry to resolved so the relationship can be reviewed rather than inferred.

7. Resolved

Capture resolved only at the level needed to answer: What states and transitions make feedback processing visible and accountable? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the feedback workflow board, connect this entry to backlog so the relationship can be reviewed rather than inferred.

8. Backlog

Capture backlog only at the level needed to answer: What states and transitions make feedback processing visible and accountable? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the feedback workflow board, connect this entry to terminal reasons so the relationship can be reviewed rather than inferred.

9. Terminal reasons

Explain which evidence and criteria were decisive, which trade-offs were accepted, and why the rejected alternatives were not preferred. Within the feedback workflow board, connect this entry to backlog so the relationship can be reviewed rather than inferred.