Classify and bound the change requests

Packaged know-how that tells an agent how to do a job well.

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

Separates deliverable change requests from unrelated meeting discussion, tags each as must-have or preference, and flags which fall outside agreed scope.

Trigger: Use to turn raw meeting feedback into a defensible, bounded change list before agreeing it with the client.

I/O: Raw session feedback notes → Classified change requests (in/out scope, must-have vs preference)

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