Feedback

“This does not feel right,” “make it better,” and “change this” are reactions.

Useful feedback adds context.

A design can conflict with personal taste while still serving the objective.

Without intent, discussion drifts into preference.

Observation — what are you seeing?

Intent — what objective is affected?

Impact — how important is the issue?

Decision — keep, change, test, or remove?

Action — who does what next and when?

“It does not stand out” is vague.

“CTA contrast is weaker than the heading, so hierarchy does not lead attention toward action” is actionable.

When people prefer different options, the objective becomes a shared decision criterion.

Not every comment deserves a roadmap change.

Feedback can be classified as Critical, Important, Optional, or Preference.

Without a disposition, the same comment can return in the next round.

Use statuses such as Accepted, Rejected, Deferred, Needs Test.

Accepted feedback without an owner is not yet action.

Forwork can include a Feedback Block: Observation, Intent, Impact, Decision, Action, Owner, Due Date, Status, Related Evidence.

Feedback can connect directly to the Decision Log and Work Tracking.

Do not only ask, “Any feedback?”

Ask: “What objective is this feedback protecting, what is the impact, what is the decision, and who acts next?”

Observation → Intent → Impact → Decision → Action.