They Said “Use Your Judgement.” What Rule Can You Actually Write Down?
Capture experienced knowledge without inventing rules. Separate supported decisions, working habits and unresolved questions before reviewing and testing the draft.

“It depends. Use your judgement.” An experienced colleague may be giving an honest answer, but the note-taker still needs to understand which parts of the task can be documented and which need a decision.
Capturing knowledge does not mean turning every preference into a rule. It means preserving the supported reasoning clearly enough that the next reader can apply it or recognise when to ask.
Ask for a specific example
Imagine a fictional agency account manager explaining how she handles an unusual client request. A broad question produces a broad answer. A recent fictionalised example makes the relevant details easier to discuss.
Ask what information she noticed, what options were available and what made this case different from the normal route. Separate the action she took from the reason she believed it was appropriate.
Do not fill a silence with a rule that sounds plausible. Mark the uncertainty and return it for review. The writer’s fluency is not evidence that the organisation has agreed a policy.
Distinguish three kinds of note
One note may capture an existing approved rule. Another may describe a colleague’s working habit. A third may identify a question that nobody has yet resolved.
Label these distinctions in the draft using the organisation’s actual review process. The final instruction should not make an informal preference look mandatory or present an unresolved question as settled practice.
Where a judgement remains necessary, explain the relevant considerations and the role authorised to decide. A useful instruction can guide that referral without claiming to replace experience.
Return the draft to the people who own it
Ask the knowledgeable colleague and appropriate owner to check the wording against the supported process. Can they recognise the intended boundary? Have you made an exception broader than they meant?
Keep the source of the decision visible in the working notes where appropriate, without collecting unnecessary personal information. Record which questions remain open and who can resolve them.
Review should happen before colleagues are expected to rely on the instruction. A polished layout does not compensate for an invented rule.
Test the boundary, not only the smooth example
Give a new reader a fictional normal case and a case near the decision boundary. Observe whether they follow the documented route and recognise when it no longer applies.
If they improvise in a way the owner did not intend, inspect the words before blaming the reader. The instruction may be missing the condition that experienced people hold in memory.
The goal is an honest piece of shared knowledge. It should carry what the team supports, preserve the questions that still need judgement and avoid making certainty appear merely because someone has written a neat sentence.
Explore the working instruction
See the related guide: Help Colleagues Find and Use the Approved Work.
- You Found the Template. Is It the One You Can Use?
- The Draft Is Finished. Who Says It Is Ready to Release?
For a written practice option, review the Team Knowledge with Matze course overview. It uses written exercises and requires your own review of the working instructions.
Check the course contents and current terms. Affiliate link: Superstore may earn a commission if you buy.




Discussion 0
What did this article make you think about?