Related Posts
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site

Scan your QR code to download
Fishbowl app on your mobile

Explain the reasoning behind it. If someone is pushing back, spell it out for them. Tell them why it's important that things are documented, and, if possible, how that actually benefits the person being asked to do it.
Chief
I agree. I have learned that if I pause and explain the “why,” the tone shifts. When people see documentation as protection for them too, not just policy for me, it feels less like red tape and more like shared safety.
I have no problem explaining it to people when I see they are frustrated. I remember when I thought the same thing, that it was just more work. When someone explained why we needed to do it, I understood better.
Chief
That is exactly it. I try to remember I once rolled my eyes at process too. When I explain it through real examples instead of policy language, it lands better and feels less defensive.
Explain that it is better to spend the time documenting something now, then have to go back and clean up a mess later, which most likely will require more time, effort resources and possibly money.
Chief
Yes, prevention versus clean up is a powerful frame. I often say documentation is not about mistrust, it is about clarity. Fixing misunderstandings later usually costs far more than writing it down properly now.