A meeting with no objections can feel efficient. Everyone understands the direction, the decision closes quickly, and the next steps seem obvious. It can also mean that the people who noticed a problem decided it was not worth raising.
The cardboard copies in our illustration would make an exceptionally agreeable team. They would contribute no independent judgment. Real engineering teams need room for a different interpretation, especially when a leader has already invested in the preferred answer.
Separate agreement from silence
You cannot establish healthy disagreement by counting objections. Some plans are straightforward. Some teams have resolved concerns before a meeting. The better question is whether people can explain how a concern travels from discovery to a decision.
Ask for a recent example: who raised the concern, what evidence supported it, and what happened afterward? If nobody can remember an idea changing, investigate the process before assuming that every original proposal was excellent.
DORA's work on generative organizational culture connects healthy information flow with organizational and delivery capabilities. It is not proof that a specific meeting exercise will improve your results. It does provide a useful reason to examine how inconvenient information moves.
Collect independent views before announcing yours
Try asking participants to write down assumptions and risks before you present your recommendation. Give them enough context to form an informed view, and distinguish between a decision that is still open and a direction that has already been set.
This avoids an unhelpful performance in which a leader asks for feedback but expects everyone to endorse an irreversible decision. When constraints are fixed, say so. People can still improve the implementation without pretending the original choice is available for debate.
Invite the strongest counterargument, then respond to its substance. A useful objection names the consequence, the evidence, or the uncertainty. It does not have to arrive in the same style or vocabulary you would use.
Show what happened to the objection
Record the decision and why it was made. If the team accepts a risk, name the person watching it and the evidence that would trigger reconsideration. If the objection changes the plan, make that visible too.
People learn from the response, not from the invitation alone. Someone who is publicly thanked and privately penalized for disagreeing will notice the difference. Likewise, a colleague who raises the same issue after a decision needs a clear route for new evidence rather than an endless reopening of settled discussion.
Include partners in the conversation
An external engineering team may be especially cautious about challenging a client. Make clear where its expertise is expected to influence decisions, who can raise concerns, and how those concerns are reviewed.
EnzRossi's technical and soft-skill screening is intended to support that kind of working relationship. Build a team that can contribute judgment, with senior LATAM engineers who understand the work and can discuss its tradeoffs. Alignment becomes useful when it reflects a decision people have examined, not merely a room that went quiet.
