THE FIELD GUIDE · SITUATION
Conflicting Feedback Through the Document’s Job
Conflicting feedback can represent different failure modes, not merely incompatible preferences.
The situation
You’re building a one-page proposal-submission checklist for newer team members. It gets used in the last stretch before a proposal goes out, so people need to scan it quickly. You own the draft and are expected to recommend the structure.
Your boss says: “Keep it simple. If they can’t scan it in a minute, they won’t use it.”
The person who runs proposal submissions says: “Include every exception. Missing one of these can invalidate a submission.”
Your call
How would you resolve the feedback? Decide before you keep reading.
What each reviewer is trying to prevent
Your boss
Too dense → nobody uses it.
The submission lead
Too simple → somebody misses an exception.
“The job of the checklist is not to make both reviewers happy.”
It is to help a newer teammate:
get the routine submission right;
notice when they have hit something that is not routine.
Design for the job
The checklist itself stays one page. Page one holds the normal path, plus a short STOP AND CHECK section listing the conditions that mean the routine checklist no longer applies.
The complete details of the rare exceptions live in a linked companion guide.
Then tell your reviewers why: “I kept the working checklist to one page so newer staff can actually use it under deadline. The page flags the conditions that trigger an exception, and the full exception details live in a linked reference. That keeps the routine path scannable without burying the rare cases.”
The move
When feedback conflicts, don’t average the opinions. Figure out what each person is trying to prevent — then make the work solve for that.
Boundary: If the assignment truly requires every exception detail inside one physical page, this becomes a different tradeoff. This approach assumes the one-page limit applies to the working checklist, not the whole documentation system.
A NOTE ON THE EVIDENCE
This is a practical translation of a workplace judgment problem, not a validated method.
WHERE TO GO NEXT
Related example: What Actually Matters Here?