Classify and bound the change requests
Separates deliverable change requests from unrelated meeting discussion, tags each as must-have or preference, and flags which fall outside agreed scope.
In / outRaw session feedback notes → Classified change requests (in/out scope, must-have vs preference)
You might say…
“The feedback capture from that session is a mess — half of it isn't about the deliverable. I need to know what we're actually committed to changing.”
What it does
Given raw feedback captured from the session, separates deliverable change requests from unrelated discussion, tags each as must-have or preference, and flags which fall outside agreed scope. Used to turn messy meeting feedback into a defensible, bounded change list before agreeing it with the client.
Trigger: Use to turn raw meeting feedback into a defensible, bounded change list before agreeing it with the client.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation