Two departments use the same term differently. How do we prevent errors?
Shared-language ambiguityCreate a short working glossary for terms that affect decisions, data, or acceptance. Use concrete examples to confirm meaning instead of assuming familiar words are shared definitions.
What to do now
- Identify terms causing disagreement
- Collect examples from each department
- Agree the intended meaning in context
- Use the glossary in requirements and tests
When to escalate
Escalate when
Ambiguity affects financial, safety, or acceptance decisions.
Who decides
The stakeholder decision owner and project sponsor
Example
Active customer is defined consistently before departments compare their reports.
Mistake to avoid
Writing a large glossary nobody applies.
Prevent a repeat
Check stakeholder understanding at important decisions rather than counting messages sent.
Suggested ApprovedFlow setup
- Projects
- Documents
- Approvals
Keep stakeholder decisions and supporting records with the project and assign follow-up actions to named owners. See the platform
Related cases
- Stakeholders want different levels of detail in the same meeting. What works?Mixed-purpose governance meeting
- How can we tell whether stakeholder engagement is working?Activity-focused engagement measures
- Two departments are funding the same initiative. Who owns the project?Split sponsorship
- A shared specialist is needed by two projects on the same day. Who decides?Contested scarce capacity