Feedback
Structured response identifying what works, what does not and why.
Specific, reasoned response — not just opinions.
What It Is
Feedback sits on the Execution side of the work, in the Process area. Stated plainly: structured response identifying what works, what does not and why.
It is an idea you reason with rather than a deliverable you hand over, so two teams can both hold it correctly and still apply it differently. That is the version worth keeping, because it survives contact with a real project.
How It's Used
In practice, Feedback shows up in project delivery, scheduling and the handover between people doing the work. It normally appears alongside Revision Round, Approval and Quality Assurance. The practical test is whether a decision changes because of it.
Why It Matters
Feedback is one of those items that only becomes visible when it is missing. When it is unclear, work still happens — it just happens twice. Clarity here removes a surprising amount of downstream argument.
Think of it as a lens. Look through it and some choices get obvious. Specific, reasoned response — not just opinions.
Termshift™
How the meaning shifts depending on who is using it, and where.
Professionally, Feedback carries the narrow meaning: structured response identifying what works, what does not and why.
Explained to someone with no marketing background, Feedback is specific, reasoned response — not just opinions.
The Bottom Line
Treat Feedback as a decision, not a description. Specific, reasoned response — not just opinions.