The Best Documentation Feedback Often Starts With One Question

“What Gets in the Way?” Is Better Than “Do You Like It?”

People can usually think of one moment when a documentation process slows them down: a field that doesn't fit the situation, an unclear handoff, a login that expires mid-visit, or a task that appears in two places. Asking “Do you like the system?” tends to produce a thumbs-up or a shrug. Asking where the work gets awkward gives you something to investigate.

Ask in a way that feels safe. Make clear that feedback is about the process, not a hidden performance review. Invite staff to describe a recent example without sharing more personal information than the review needs. If someone mentions an immediate risk, use the provider's escalation route rather than waiting for a workflow meeting.

Close the Loop, Even When the Answer Is No

Group comments by the underlying issue: training, unclear instructions, duplicate entry, access, or a genuine system limitation. Then tell staff what will change, what cannot change right now, and why. Silence after a feedback session teaches people not to bother next time.

Try one small adjustment and check whether it helped. If it added a new step somewhere else, say so and revisit the design. For a quick team discussion format, see our article on a documentation huddle that respects the shift.

Use your provider's approved staff-feedback, privacy, and incident-reporting channels for sensitive or urgent matters.