Workplace Communication
Two Stakeholders Want Opposite Things: Turn Conflicting Requests into a Decision
Completed fictional requirements matrix, four comparable options, decision dialogue and accepted pilot memo choose brevity while retaining support dissent and capacity boundaries.
When two stakeholders make incompatible requests, put the conflict in one shared decision question. Ask what each request is trying to achieve, which constraints are confirmed, and who can authorize the trade-off. Compare viable options with their costs and conditions, then record the authorized choice and the remaining disagreement. Avoid separately promising both outcomes when the team cannot deliver them together.
An authorized choice may leave one stakeholder’s preferred request unmet. A clear decision can still explain whose goal takes priority, what the team will give up, and when new evidence would justify reconsideration. This LandOffer.ai guide uses an entirely fictional internal communication project. No real stakeholder messages, company records, customer information, publishing, or workplace experiment is involved.

Write the conflict before proposing a compromise
Requests often arrive through separate conversations. One person asks for more detail; another asks for less. If you accept each request privately, the conflict becomes hidden work for whoever must produce the deliverable. Bring both requests into the same record so each stakeholder can inspect the costs before work is cut, added, or delayed.
Use a sentence that identifies the deliverable and the incompatible conditions. For example: “For the weekly internal change digest, should we prioritize a complete inline change list or a summary limited to 150 words, given the agreed preparation capacity?” That is a decision question. “Support and enablement cannot agree” describes the people rather than the choice.
Atlassian's clean-escalation play asks parties to align on the problem, describe viable options, understand the other side's position, and notify them before taking the issue to a relevant decision-maker. Use that method to make the disagreement inspectable. Its suggested timing is guidance for that play, not a universal deadline for resolving stakeholder conflict.
In the fictional case, coordinator Jules is preparing a pilot weekly digest about an internal testing tool. Support lead Hana wants every completed change included inline so her team can answer questions. Enablement lead Miles wants a short overview that staff can read quickly. Neither person can unilaterally allocate additional documentation work.
Jules has not promised either format. The pilot has two planned issues, September 4 and September 11. The team needs a format decision by September 2 so the editor knows what to prepare. The dates, workload and sample change inventory below are invented planning inputs, not observations of a real product release.
Translate each request into goals and checked constraints
Ask each stakeholder what problem the requested format solves, what happens if it is not adopted, and which parts could change. Do not invent a hidden motivation or assume an asserted limit is an approved requirement. A preference may be strong while still being negotiable; a genuine boundary may require someone else's approval to alter.
Atlassian's project trade-off analysis recommends examining the flexibility of project variables and being explicit about what is sacrificed. It also calls for involving leaders when they hold the decision authority and revisiting trade-offs when information changes. Use the discussion to expose priorities and explain the reasoning behind them.
Jules checks the requests with Hana and Miles and asks editor Quinn to state the preparation limit. The completed clarification record reads:
| Request or planning fact | Underlying goal or consequence | Confirmed boundary and remaining uncertainty |
|---|---|---|
| Hana: include all eight sample changes inline | Let support locate a particular change without requesting a second explanation | Complete inline coverage is Hana's preference, not an approved policy; actual question volume is unknown |
| Miles: keep the digest at or below 150 words | Make the weekly communication usable as a brief overview | Miles confirms the target applies to digest prose, not an independent reference; actual readership benefit is untested |
| Quinn: forty-five minutes available per issue | Keep preparation inside the agreed pilot allocation | Quinn and manager Rosa confirm this allocation; it is not permission for unpaid or unassigned extra work |
| Jules: eight sample changes have approved internal source notes | Permit a full-list option to be considered | This is a stipulated case fact; producing or maintaining another reference would still require work |
| Rosa: a two-issue pilot can inform a later format choice | Learn what follow-up needs the brief format leaves open | There is no commitment to a permanent format or a quantified improvement |
Hana confirms that the first row represents her concern accurately. Miles confirms the second. They agree on the problem description while continuing to prefer different outputs. Jules records that distinction so agreement on the notes does not get mistaken for agreement on the final format.
Confirm decision authority and make the options comparable
A coordinator who gathers information does not automatically gain the power to accept workload or business consequences. Ask the project sponsor or relevant owner to confirm the decision boundary. If no one has authority across both requests, resolve that ownership gap before treating the analysis as an approval.
Atlassian's DACI framework separates the person driving a decision from the approver, contributors and people informed. Its method includes decision factors, options, estimated resources, an outcome and a retained explanation. You can use those distinctions without imposing the framework as a universal company structure.
For this fictional pilot, sponsor Rosa confirms in the shared record that she owns the format and the forty-five-minute preparation allocation. Jules drives the decision. Hana and Miles contribute requirements; Quinn supplies preparation estimates. A permanent format, additional headcount or external publication is outside Rosa's pilot decision.
Jules and Quinn create the following options. All durations are fictional estimates for discussion, not timed results or a promise that work will fit. Each option identifies its unmet need.
| Option | Deliverable and estimated preparation | Benefit, sacrifice and condition |
|---|---|---|
| A: complete inline list | Eight changes with brief explanations; about forty-five minutes per issue; expected to exceed 150 words | Meets Hana's requested coverage; rejects Miles's brevity target; requires Rosa to prioritize completeness |
| B: short overview only | Up to 150 words covering three selected changes; about forty-five minutes per issue | Meets the overview target and current allocation; five sample changes are omitted; support must not treat the digest as a complete reference |
| C: overview plus separate maintained index | Short digest and linked eight-change reference; about seventy-five minutes per issue | Could serve both information needs through separate artifacts; requires thirty extra minutes and a named reference maintainer per issue |
| D: postpone the pilot | No September 4 digest; retain existing source notes while capacity and format are reconsidered | Avoids committing to an inadequately supported format; loses that pilot issue and requires Rosa to accept the delay |
Option C is a conditional proposal, not an approved deliverable. A link does not maintain itself, and having source notes is not the same as preparing a reliable reference. Jules does not hide its extra work under the word “simple.” Equally, option B is not complete coverage merely because the missing changes exist somewhere else.
Hold a decision conversation that leaves disagreement intact
Jules shares the problem, confirmed constraints and four options with both stakeholders before Rosa's September 2 discussion. The notice says that Rosa will choose within the pilot boundary. It includes both preferred options, without presenting either colleague as an obstruction.
The completed fictional conversation shows how the trade-off becomes a choice:
Jules: “Hana wants complete inline coverage so support can locate changes. Miles wants a brief overview. Quinn has forty-five minutes per issue. Is that still an accurate description?”
Hana: “Yes. I prefer A. If we pick B, support may receive questions about changes that are absent from the digest.”
Miles: “Accurate. I prefer B. I am not asking that support questions disappear; I want the overview to remain short.”
Rosa: “Could C fit without more work?”
Quinn: “Not under my current estimate. Preparing and checking the separate index adds thirty minutes per issue. I have no approved capacity for that.”
Jules: “We could reconsider C if an owner accepts that capacity and maintenance. We do not currently have either. D remains available if the missing coverage makes a short pilot unacceptable.”
Rosa: “For two issues, I choose B. We will label it a selected overview and keep the selection boundary visible. I accept the coverage gap during this pilot. Hana, what do we need to record so we can assess that cost?”
Hana: “Keep a list of questions that the digest cannot answer. I still prefer A and do not want B described as support's preferred format.”
Rosa: “Agreed about the record. Hana, can you collect those questions inside the existing support-review slot, rather than add another recurring task?”
Hana: “Yes, for these two issues. I will record the topic and whether it concerns an omitted change. That will replace the optional pilot-format commentary in that slot.”
Miles: “I accept the selected-overview description. I will review the prose for the length target within my existing editorial slot.”
Quinn: “I accept preparing B within the pilot allocation. If preparation looks likely to exceed it, I will flag the scope before continuing.”
Rosa has chosen an option that favors brevity and declines complete inline coverage. That is a real trade-off, not an assertion that everyone got what they asked for. Hana has accepted a bounded follow-up assignment while retaining her disagreement about the format.

Save the decision, acceptance and limits together
Jules writes the following completed September 2 memo in the fictional shared project record. The people involved confirm their stated commitments there; this is stipulated case material, not an actual sent or approved company document.
“Rosa authorizes option B for the September 4 and September 11 pilot issues. Each digest contains up to 150 words of prose about three selected changes, with a clear selected-overview label. This does not represent every change or replace the internal source notes. The existing note owners retain their existing responsibilities; this decision creates no new comprehensive index.
“Quinn accepts preparation within forty-five minutes per issue. Miles accepts the prose-length review within his current editorial slot. Hana accepts collecting unanswered-question topics during the existing support-review slot, replacing optional pilot-format commentary for these two issues. Jules accepts assembling those topics in the existing pilot-coordination slot for Rosa's September 15 review. No extra reference-maintenance capacity is approved.
“Hana continues to prefer option A because B omits useful detail. Rosa accepts the pilot's coverage cost. Miles's brevity preference does not establish that staff will read the digest or find it useful. Neither pilot issue has yet been prepared or evaluated.
“Reopen the format decision before expanding the pilot, if an essential internal-use case cannot be served within this scope, or if Quinn expects preparation to exceed the allocation. Rosa owns that reconsideration. Option C requires a maintainer and explicit additional capacity; it is not a standing promise. The September 15 review will consider the collected questions and preparation experience, without presuming a permanent format.”
The memo ties the choice to its authority, capacity and review boundary. It also preserves Hana’s disagreement while keeping the agreed pilot scope and reconsideration route visible. A request to change the selected format goes back to Rosa with its new information and cost.
Reopen for new evidence rather than repeat the argument
A decision record is useful when someone can tell whether the conditions have changed. If an omitted change creates a concrete need during the pilot, record the need and ask the owner to assess it. Assess each later question against the omitted information and agreed pilot purpose; an empty question record leaves satisfaction unmeasured.
For your next conflicting request, write one shared question and confirm each person's goal before adding options. Identify the owner who can accept the consequences, then record the choice, actual commitments, dissent and reconsideration trigger. You can return to LandOffer.ai for more workplace guides; the next step here is an authorized decision your team can carry out within its stated limits.
Sources and Further Reading
- Atlassian: Clean Escalations — shared problem, options, reasoning and notice before escalation.
- Atlassian: Project Trade-Off Analysis — flexibility, sacrifices, decision authority and revisiting conditions.
- Atlassian: DACI Decision-Making Framework — distinct decision roles, options and a documented outcome.


