A change conversation becomes useful when people can examine the work it would alter.
Use a fictional planning discussion to move from a broad ambition to a specific task, a visible dependency and a next decision.
An original discussion exercise. No interview, quotation or organisational transformation is reported.
Replace the slogan with a concrete question
Imagine a fictional planning discussion about making internal requests easier to handle. The phrase ‘transform the workflow’ gives the participants little to examine. A more useful question is whether a person receiving a request can identify the needed information without returning it for clarification. That question points to a particular moment in the work and a result another person can recognise.
Describe an ordinary request and one that arrives with missing information. Ask what the requester knows, what the recipient needs and which uncertainty prevents the next step. Do not assume that generating more text will resolve the gap. In this example, the problem might be an unclear request form or an instruction that does not explain which details matter.
Bring the receiving side into the description
A proposed change may look convenient from the point of view of the person submitting a request while adding work for the person reviewing it. Include both perspectives in the description. The receiver may need a source link, a clear statement of the decision requested or an explanation of why an exception applies. Those requirements should not be discovered only after the change is introduced.
Use the fictional examples to expose a disagreement about what ‘ready for review’ means. One participant might consider a completed form sufficient; another might require confirmation that an attached document is current. Write down that difference without inventing agreement. A useful conversation can reveal that the process needs a shared definition before any proposed automation is evaluated.
Leave with a decision and an open question
The discussion should end with a decision small enough to act on and a record of what remains unknown. For example, the next step might be to rewrite one ambiguous instruction and ask a reviewer to try it against the fictional requests. That exercise can clarify the requirement. It cannot establish that an entire organisation has changed or that a proposed tool will deliver a broad benefit.
Keep the next question visible alongside the decision: whether the revised instruction covers the missing-information case, whether a source is available or whether another role needs to be consulted. Record what would cause the proposal to be revised or set aside. The value of this illustrative discussion is its connection to reviewable work, not a claim that a real conversation or transformation has taken place.