Consensus at Work: Meaning, Examples, and How to Build Agreement

Published:
Last Updated:
Category: Work Styles
Authors: Shusaku Yosa
Consensus means agreement or a shared understanding among people involved in a decision. In Japanese business, you may hear phrases meaning “gain consensus on the direction” or “build consensus with the relevant departments.”
The practical goal is to clarify what people have agreed to and what remains unresolved. Everyone does not need to feel exactly the same way. This guide explains the terminology and how to turn an agreement into action.
Consensus and related business terms
Consensus can describe agreement in a meeting or alignment across departments. The required participants and decision-making procedure depend on the organization and situation.
Term | Main meaning | Workplace example |
|---|---|---|
Consensus (コンセンサス) | Agreement formed among relevant participants | Sales and development agree on launch timing. |
Goi (合意): agreement | Parties agree on specific content | Parties agree on contract terms. |
Doi (同意): consent or assent | Accepting an opinion or condition presented | Someone agrees to a proposed policy. |
Nemawashi (根回し) | Consultation and coordination before a formal decision | Concerns are discussed and a proposal revised before a meeting. |
Kessai (決裁): formal approval | A decision by an authorized person | A department head approves a budget. |
Commitment (コミットメント) | A promise or involvement in execution | An owner undertakes to complete a task by a deadline. |
Nemawashi is a way to help build agreement, rather than the agreement itself. Even if participants share a direction, a separate formal approval or contractual process may still be necessary.
Is consensus the same as unanimity or majority voting?
Majority voting follows a rule based on votes. Consensus building emphasizes discussing concerns and conditions to find an acceptable way forward. Some groups require unanimity; others record objections and let an accountable decision-maker decide.
Silence does not necessarily mean everyone understands or accepts a proposal. People may find it difficult to speak, or their responsibilities may be unclear. For important decisions, document the agreed content and confirm it. Uses of consensus in distributed computing or international meetings have their own technical or procedural meanings.
Examples for meetings, emails, and chat
Coordinating before a meeting
“I would like to build consensus with the relevant departments on the implementation schedule before next week's meeting.”
State the subject on which agreement is needed.
Checking an agreement
“Are we aligned on starting on June 1?”
Confirm a specific decision rather than asking about the project in general.
Reporting an unresolved issue
“We have agreed on the objective, but the budget allocation is still under discussion.”
Separate agreed points from open issues.
Asking another organization to review a proposal
“Could you review the proposed scope internally and share any concerns?”
Make the action you are requesting clear.
Responding to an objection
“Given the concern about the deadline, I would like to compare narrowing the scope with postponing the launch.”
Turn the concern into options for revising the plan.
Confirming a decision in chat
“My understanding is that we will proceed with option A. Please let me know by noon tomorrow if anything remains unresolved.”
Record the option and the response deadline. For important decisions, do not assume that no response automatically constitutes consent.
In Japanese, expressions such as konsensasu o toru, eru, or keisei suru mean reaching, gaining, or building consensus. When the loanword is unclear, use a more direct expression describing the action: agree on the proposal, align our understanding, or obtain approval, as appropriate.
Four steps to building agreement
1. Define the scope and decision-making authority
Explain what needs to be decided, whose input is required, and who makes the final decision. Break a broad project direction into scope, start date, and budget to reduce misunderstandings.
2. Listen to concerns
Consult affected departments and people responsible for the work before finalizing the proposal. Ask what might prevent implementation, rather than only whether they agree.
3. Share options and evidence
Compare costs, timing, quality, and workload, and explain where changes are possible. Record why an option was not selected so the same issue does not repeatedly reopen without new information.
4. Record decisions and next actions
A direction alone does not enable execution. Assign owners, deadlines, and a way to check progress. Keep unresolved items separate from decisions.
A template for recording an agreement
- Subject: Trial release of a new service.
- Decision: Start on June 1 with ten existing customers.
- Open issues: Pricing for the full release and expansion of the customer group.
- Owner and deadline: Sales will propose customers by May 15.
- Preconditions: Development testing and support procedures must be ready.
- Reviewers and approver: Sales and development leads review; the business lead gives final approval.
- Reasons to revisit: Defects, excessive workload, or significant customer concerns.
Adapt this illustrative record to the decision at hand. Make sure the people named understand their responsibilities.
Common pitfalls
- Opinions differ: Check whether people are using the same criteria, and compare the benefits and burdens of each option.
- Nobody makes a decision: Separate matters requiring group agreement from matters an accountable person must decide.
- Nothing happens after agreement: Check that owners, deadlines, and support needs are shared.
- Nobody speaks in the meeting: Ask about concerns individually and create room for people to express views without being dismissed.
Avoid treating silence as proof of agreement or confusing a discussion with formal approval.
Frequently asked questions
Does an objection prevent consensus?
The level of agreement needed depends on the situation. Do not ignore an objection and label the matter agreed. Identify acceptable conditions and unresolved issues, then follow the agreed decision-making process.
Is a manager's approval enough to establish consensus?
Formal approval and a shared understanding among the people doing the work are different matters. Even after approval, explain the content and responsibilities to the departments involved.
Consensus becomes useful when people can explain the agreed scope, outstanding issues, and next actions in the same way.




