Editorial review: 9 October 2026
Reconcile stakeholder requirements before making a commitment
Stakeholder management includes identifying who needs an output, understanding their actual requirements and establishing who can decide when requests conflict. A friendly conversation is useful, but it does not by itself approve an artifact, confirm missing information or authorise release.
This guide works through one complete original example with different audiences, incompatible wording requests, an authorised decision and an unfinished dependency. The people and visitor activity are fictional. The example is not a universal organisational policy or a claim that a meeting guarantees stakeholder satisfaction.
NASA's technical-requirements guidance describes communication and iteration with relevant stakeholders to establish mutual understanding in its engineering context. The narrow principle is useful here; NASA's process does not assign authority in this fictional workplace. The exercise explicitly supplies that authority separately.
Identify the audience and decision owner
Farah is preparing a draft card for an invented visitor activity. Omar represents the visitor-facing desk and wants a brief card. Priya reviews the underlying information and wants unresolved questions visible. Elena is the activity coordinator and is expressly authorised in this scenario to decide the required deliverables and approve release.
Their requirements are:
| Person | Actual requested output | Decision responsibility supplied |
|---|---|---|
| Omar | One visitor card, at most 12 words, containing only the confirmed meeting instruction | Represents the visitor-facing request |
| Priya | The same card must include two questions verbatim, in addition to the meeting instruction | Represents the review request |
| Elena | Decide how the audience requirements are reconciled | Owns deliverable and release decisions |
| Farah | Draft and record the requirements and decisions | No independent release authority |
The confirmed meeting instruction is: “At 10:00, please meet the guide at Desk B.” It contains nine space-separated words. Priya's required additional questions are: “Who confirms the guide name?” and “Where is the approved contact listed?” They add eleven words. Including all three pieces verbatim would require 20 words, exceeding Omar's 12-word limit.
The guide's name and approved contact are not supplied. Their absence is an information gap. It is not evidence that any particular person forgot them or that Farah may invent replacements.
Describe the conflict precisely
“Omar and Priya disagree” is less useful than recording the incompatible requests. One shared card cannot both contain all 20 required words and remain at most 12 words under the exercise's stated counting method.
Farah can identify that contradiction without deciding which audience matters more. Neither Omar's brevity requirement nor Priya's review requirement is automatically unreasonable. They serve different uses of the information. What needs a decision is whether one artifact must satisfy both uses or whether the deliverable arrangement should change.
A complete draft clarification note is:
The visitor request limits the shared card to 12 words and confirmed meeting information. The review request adds two verbatim questions, producing 20 words with the meeting instruction. Those requirements conflict for one card. The guide name and approved contact remain unknown. Please decide whether the review questions belong in a separate internal note or whether the visitor-card requirement should change.
This note is an editorial original. Drafting it does not prove it was sent, read or accepted. It presents a specific decision and an unresolved dependency to the person who owns the decision in this exercise.
Compare alternatives without calling them approved
There are at least two proposals consistent with the available information:
- Keep the nine-word visitor instruction and put the two questions in a separate review note.
- Change the visitor-card limit and content requirement so the questions can remain on the shared card.
The second option would require an actual authorised requirement change. The first would require permission to create separate deliverables. Farah cannot treat either as accepted simply because it appears to resolve the word-count problem.
Nor does the first proposal answer the guide-name or contact questions. It changes where they are recorded. Resolving an audience conflict and obtaining missing source information are different pieces of work.
Apply the supplied owner's decision
The fictional exercise now gives Elena's actual decision: prepare a visitor-card draft containing the confirmed meeting instruction only, and a separate internal review note containing Priya's two questions. Both remain drafts until Elena gives release approval. Elena does not supply the missing name or contact.
Farah's resulting documents are:
VISITOR CARD — DRAFT, NOT RELEASED
At 10:00, please meet the guide at Desk B.
INTERNAL REVIEW NOTE — DRAFT
Decision owner: Elena, activity coordinator.
Decision: separate the visitor instruction from the review questions.
Visitor instruction: confirmed 10:00 meeting at Desk B.
Questions still requiring authorised information:
Who confirms the guide name?
Where is the approved contact listed?
Guide name: not supplied.
Approved contact: not supplied.
Release approval: not supplied.
The visitor text meets the supplied nine-word content and 12-word limit. The internal note preserves the review questions instead of silently deleting them. Neither document is claimed as released, and neither resolves the missing information.
An actual production workflow may use different statuses and approval rules. Here, the status follows the exercise's explicit instruction. Do not assume a general internet guide determines who can approve a document in your organisation.
Distinguish acknowledgement from acceptance
The next supplied event is Priya's reply: “I see my two questions in the review note.” That establishes acknowledgement of their presence. It does not approve the visitor wording, confirm the guide name or authorise release.
The status record should therefore say: “Priya acknowledged that her questions appear in the separate note. Elena's deliverable arrangement is recorded. Missing source information and release approval remain pending.” It should not say “all stakeholders signed off.”
If Omar later asks whether the activity has been published, Farah can answer from this record: the visitor draft is prepared, but no release approval or publication event is supplied. Giving that answer does not require inventing a reason for the pending status.
Handle a new requirement as a new decision
For a separate hypothetical variation, suppose Elena changes the visitor requirement to include the guide's name and supplies the authorised name “Guide R.” That would allow a revised draft based on the new information. It would not retroactively prove that the original nine-word card contained the name or had already been released.
If the new text exceeds the existing word limit, identify that conflict again rather than quietly ignoring the limit. Check the complete revised requirement set, not just the newest field. A later change can invalidate a previously suitable draft.
This variation is practice for reasoning about a change. It is not a later event in the original scenario or evidence that the unknown guide name was resolved there.
Use the record to explain your contribution
In an interview, Farah's supported account is: “I identified incompatible wording requirements, presented the specific word-count conflict to the authorised coordinator and prepared the two draft documents according to the supplied decision. I kept the unanswered source questions and release status visible.”
That account shows useful coordination work without claiming universal influence, stakeholder satisfaction or a successful visitor event. It also names the owner's decision rather than taking credit for authority Farah did not hold.
The organizational-skills guide addresses a different issue: capacity, deadlines and missing inputs. The teamwork guide helps distinguish individual contributions from shared work. Keep stakeholder requirements and decision ownership visible alongside those related skills.
Frequently asked questions
Does every stakeholder have approval authority? No such rule is established. Identify the actual decision and release responsibilities.
Does recording a concern mean it is resolved? No. A recorded question, a source answer and an approved decision are different events.
Can I split a shared artifact whenever requirements conflict? Present it as a proposal and obtain any required decision. In this exercise Elena expressly authorises the split.
Does an acknowledgement establish sign-off? Only report what the acknowledgement actually says. Priya confirms that her questions are present, not that the whole activity is approved.