One reviewer wants the strategy document shorter. Another wants the opening expanded. Both comments point at the same section, and the writer has no agreed decision to implement.
Hold the disputed edit. Put both requests beside the document's objective, identify the tradeoff, and confirm who decides. Then give the writer one revision brief.
Conflicting client feedback becomes manageable when every comment has a location, a reason, and a disposition. The method below uses a comment register and a decision record. Every scenario is fictional.
Atlassian's sparring practice frames structured feedback around work in progress. Its DACI framework separates the person coordinating a decision from the person authorized to make it. The consulting workflow here adapts those ideas.
Freeze the version everyone is reviewing
Give the review copy a version identifier. Record its intended reader, approved objective, and review boundary at the top of the register. Comments need a common reference point.
Ask reviewers to identify a section and the specific passage or diagram they mean. Preserve the original wording of each comment before summarizing it.
If someone comments on an older copy, record that version. Compare the passage with the current one before treating the comment as unresolved work. The requested change may already exist.
Keep one current register. A message thread can supply a comment, but it should not become a second instruction list for the writer.
This workflow starts after feedback arrives. The consulting project management guide covers the broader delivery process. Here the job is to turn incompatible comments into executable decisions.
Separate five kinds of feedback
Classify comments before deciding what to revise. Classification describes the issue; it does not establish that the reviewer is correct.
| Type | What to look for | Next check |
|---|---|---|
| Defect | Output fails an agreed condition | Compare the current version with that condition |
| Factual correction | A checkable statement may be wrong | Open the supplied evidence and verify the correction |
| Preference | A reviewer favors a style or presentation | Compare the preference with audience and purpose |
| New scope | Request adds an output or changes the boundary | Separate it from the current revision decision |
| Conflicting direction | Two requests cannot both be implemented as stated | Name the conflict and obtain a decision |
A missing appendix that was agreed at kickoff is a possible defect. A request for a new regional analysis may add scope. Confirm the original boundary before classifying either.
A factual correction needs evidence. If a reviewer changes a date without supplying a source, record the proposed correction and its unresolved verification. Do not replace one unsupported assertion with another.
Preferences can still matter. A document designed for executives may need a shorter opening. The decision should name the audience need rather than treating personal taste as a measured defect.
Some comments fit more than one category. A request to replace a recommendation may challenge its evidence and change the assignment's objective. Split those questions into separate rows.
Build a register the writer can follow
Assign each comment a stable identifier. Preserve the reviewer and original comment, then add fields that explain its effect on the document.
| Field | What belongs there |
|---|---|
| Comment ID | Stable reference used in decisions and revision notes |
| Source location | File version, section, passage, and comment origin |
| Reviewer | Person who supplied the feedback |
| Original comment | Received wording, separate from interpretation |
| Objective affected | Agreed reader task or acceptance condition |
| Proposed change | Specific edit or question suggested by the comment |
| Conflict | Incompatible comment ID and the tradeoff involved |
| Owner | Person responsible for resolving the question |
| Disposition | Pending, implement, decline, defer, or superseded |
| Decision reference | Decision, reason, approver, date, and affected version |
Keep “received” and “implement” distinct. A comment enters the register when it arrives. It becomes an instruction after its disposition permits implementation.
Use “defer” only with a destination or unresolved dependency. A deferred comment without an owner or next decision remains an open issue.
Record uncertainty directly. If no decision owner has been confirmed, write “owner unconfirmed.” The consultant should not infer authority from a title, the loudest message, or the latest reply.
Work through a fictional strategy disagreement
Assume a fictional team reviews a strategy document for an internal pilot decision. The agreed audience is a steering group. The approved objective is choosing which of two approaches deserves a bounded pilot.
The review copy is Strategy v3. Its opening contains a comparison, recommendation, and supporting detail. Two stakeholders comment on that opening.
Reviewer A asks for a one-page decision summary. Reviewer B asks for the complete research method and every source in the opening. Both describe their request as necessary for approval.
Preserve both requests. Then describe the incompatibility: the same opening cannot remain one page while containing all the requested research detail at readable length.
| ID | Source location | Objective affected | Proposed change | Conflict | Owner | Disposition |
|---|---|---|---|---|---|---|
| C-11 | Strategy v3, opening | Steering group can compare pilot options | Limit opening to one page | C-12 requires full research detail there | Review coordinator | Pending decision D-04 |
| C-12 | Strategy v3, opening | Decision has inspectable evidence | Put full method and sources in opening | C-11 limits opening length | Review coordinator | Pending decision D-04 |
Do not describe either reviewer as obstructive. The comments identify competing information needs. The decision concerns where that information belongs and what the opening must accomplish.
Prepare two options. One keeps a short decision summary with references to a method appendix. The other expands the opening and removes the one-page constraint.
Explain each consequence in terms of the approved reader task. Ask whether the steering group needs to read the method immediately or inspect it through a clear reference.
Do not create a compromise by shrinking the type or deleting supporting evidence. Those changes avoid the visible conflict while leaving the underlying reader needs unresolved.
Confirm decision roles before making the call
DACI names four roles: Driver, Approver, Contributors, and Informed. The Driver coordinates the decision. The Approver makes it. Contributors provide input, and Informed participants receive the outcome.
These are Atlassian's documented DACI roles. In this proposed workflow, the client confirms who fills them for the disputed document decision.
The consultant may coordinate the register without owning the client's final choice. A reviewer may contribute subject knowledge without having authority to accept the whole deliverable.
For the fictional example, assume the client explicitly confirms a sponsor as Approver and a project coordinator as Driver. Both reviewers remain Contributors for decision D-04.
The sponsor selects a one-page summary with references to the comparison and method appendix. Record the decision, rationale, approver, and date. Then connect C-11 and C-12 to D-04.
C-11 receives “implement.” C-12 receives “decline” for the requested opening placement, with D-04 as the reason. Add C-13 for the approved appendix change and mark it “implement.” Link C-13 to C-12 so the original request and the approved alternative remain visible.
If the authorized person cannot decide, keep the contested section pending. Complete unrelated edits only when they do not depend on the unresolved choice. Record the effect on the next review.
Use a focused feedback exchange
Structure the exchange around the document and the decision needed. Supply the objective, current version, conflicting comments, and specific options before asking for further input.
Atlassian's sparring play provides a reference for reviewing work in progress through structured feedback. The register and decision questions here are editorial adaptations, not requirements imposed by that play.
Ask what the intended reader must understand after the opening. Ask which evidence must be visible there and which evidence can sit behind a clear reference.
When a reviewer proposes a new direction, ask which approved objective it serves. If it changes the objective, record that as a separate decision rather than silently revising the assignment.
Keep the scope boundaries discussion connected to added work. A missing explanation and a newly requested research program require different responses.
An asynchronous decision can use the same fields. The async communication guide supplies broader written-work context. Keep this decision request bounded to the conflicting comments.
Write one final revision brief
Turn accepted decisions into a short instruction set tied to the current document version. The writer should be able to execute it without reconciling message history again.
For Strategy v3, the fictional brief identifies D-04 as the controlling decision and C-11 and C-13 as approved edits. It requests a one-page summary containing the two options, recommendation, key uncertainty, and references to supporting evidence.
It places the full method in an appendix and preserves the sources there. It names the sections affected and identifies the conditions the reviewer will check in Strategy v4.
Include comments declined or deferred, with their reasons. Otherwise a later reviewer may treat an intentionally omitted request as an overlooked task.
State what remains unresolved. If the sponsor has not chosen the pilot approach, the writer can present options without inventing a choice. Record that decision as pending in the revised document.
Attach the brief to the register. Keep the raw comments available for context, but mark the approved brief as the current revision instruction.
Preserve superseded comments and obtain explicit approval
Keep earlier versions available. Record which version each decision applied to and which revision implemented it. A superseded comment should point to its replacement or controlling decision.
When a reviewer withdraws a request, preserve the withdrawal with its date. Do not silently delete the original and leave the writer guessing why an expected change disappeared.
After revision, check the affected sections against the brief. Record implemented changes and any deviation requiring another decision. “Edited” does not establish that the chosen direction was followed.
Request explicit approval for the identified version through the agreed client process. In this workflow, silence leaves approval pending. A comment resolved in the register does not imply acceptance of the entire deliverable.
Store the approved version with its decision record. Later feedback begins from that version and names the new request. The earlier record remains available without silently governing a different document.
Give the writer one decision to execute.
Sources
- Atlassian: Sparring, for structured feedback on work in progress.
- Atlassian: DACI, for decision coordination, confirmed roles, and recording the outcome.