When a Team Is Ready to Say Yes: 3 Ways to Keep a Serious Concern in the Decision

The meeting is almost done, but one part still does not add up. How do we keep it from getting lost?

Picture the last part of a project meeting in Kuala Lumpur.

The decision is nearly settled. Someone has moved to the next slide, and a few people are already checking messages before the meeting ends.

Then you notice one unresolved issue.

You cannot prove the plan will fail. You may not be the person who gives final approval.

But the unanswered point still matters.

That is where speaking up becomes harder than it sounds. A concern can be said clearly and still lose its force before the final choice is made.

The history of the Space Shuttle Challenger gives us a severe example of this problem. An ordinary workplace decision is not comparable to a fatal spaceflight accident, but the way important information can weaken inside a decision is worth studying.

In its investigation of the 1986 Challenger accident, the Presidential Commission called the launch decision flawed. The report says the key people approving the launch were not given crucial information about earlier O-ring trouble, Thiokol’s initial recommendation not to launch under the expected cold conditions, and the engineers who still opposed launch after management reversed that recommendation. An O-ring is a rubber seal placed in a joint to stop gas or liquid from passing through a gap. (Presidential Commission report, Chapter V)

So the useful lesson is not just “be brave enough to speak.”

A serious objection has to keep its meaning before approval, while it travels through the group, and after new evidence appears.

The short version

• Let’s turn the concern into one clear condition for saying yes.
• Let’s check that the person approving the plan received the same concern we meant to raise.
• Let’s agree on the evidence that would bring the choice back for another look.

1. Give your “not yet” a clear condition

Sometimes you can see a problem but cannot yet explain what would make you comfortable moving ahead.

“I don’t think this is ready” shows your position. It does not show the group what fact could change your answer.

A condition for saying yes is simply a fact that your support depends on.

For example:

“I can support this release after we confirm that the recovery copy can restore the records.”

Now there is something concrete to check. The discussion does not need to turn into a debate about whether you are too cautious.

The Challenger investigation shows the same idea under much more serious conditions. Morton Thiokol, the contractor that built the solid rocket boosters, first recommended against launch if the O-ring temperature would be below 53°F, the lowest temperature in its previous flight experience. Thiokol management later changed the recommendation, while engineers continued to oppose the launch. (Presidential Commission report, Chapter V)

The number matters because it marked the edge of the experience the engineers believed they could rely on. Their objection was tied to a condition, not only to a feeling.

Now imagine a team in Penang preparing to switch a new stock system on before the next working day.

Normal updates are working, but nobody has tested what happens when the connection drops while stock levels are being changed.

Instead of saying, “I have a bad feeling about this,” you can say:

“I am ready to support the change once we know what happens if the connection drops during an update.”

You are not claiming that failure is certain.

You are showing what information your yes still depends on. That turns a vague objection into a question the team can test.

2. Check what the person with authority actually heard

A concern can start clear and become weaker as it passes from one person to another.

“Do not approve this until we understand the recovery problem” can become “there are a few technical points to watch.” Those messages are not the same.

The Challenger record shows why this matters. Engineers raised concerns about cold temperatures, but the Commission found that those concerns were not adequately communicated to the senior NASA managers responsible for the launch. Senior officials later testified that they had not known about Thiokol’s objections before launch. (Presidential Commission report, Chapter V)

This gives us a simple check.

Before a serious decision closes, can the decision-maker—the person who can actually approve or stop the plan—describe the unresolved issue correctly?

Imagine a service team in Johor Bahru changing how urgent customer cases are passed between shifts.

One staff member says that the backup handover has never been tested. By the time the point reaches the manager who will approve the change, it has become, “There are some small handover questions.”

You can restore the original meaning without making the room hostile:

“Before we approve this, can we keep the original point clear? The normal handover works, but the backup handover has not been tested.”

The manager may still choose to continue.

The important difference is that the choice is now being made with the real concern still visible.

This is not about forcing agreement. It is about stopping useful information from becoming vague on the way to the person who decides.

3. Decide what would bring the choice back for review

Once a plan is approved, it can start to feel closed even while new information keeps arriving.

That makes the next warning easy to treat as a small inconvenience instead of a reason to look again.

A useful protection is to agree on one review trigger. That simply means a specific new fact that would bring the decision back to the table.

For a software release, it might be:

“If the same unexplained data error appears again, we pause the next stage and review the choice.”

For a supplier test, it might be:

“If the agreed test limit is missed a second time, we reopen the decision.”

These are examples, not rules for every situation. The right trigger depends on what could go wrong and what evidence matters in your case.

Picture a small online retail team in Klang preparing for a weekend promotion.

A stock-sync problem appeared during testing, the team chose to proceed, and the same problem appears again the next morning. If everyone already agreed that a repeat would trigger a review, the team has a clear reason to stop and look again without rebuilding the argument from the beginning.

The Commission also traced the O-ring danger through earlier flights rather than treating it as a problem that appeared only on launch day. It reported that NASA and Thiokol had begun accepting O-ring erosion and hot-gas leakage as an acceptable flight risk, while launch constraints tied to the issue were waived on six consecutive occasions before Challenger. The report also criticised the way important problems could drop out of the reporting system. (Presidential Commission report, Chapter VI)

Earlier flights did not prove that the risk was acceptable. The Commission found that repeatedly getting through flights without disaster had made increasing risk easier to accept.

Smaller decisions can drift in a similar way.

A warning appears. The team continues. Nothing obvious happens. The next warning becomes easier to dismiss.

A review trigger interrupts that drift.

You are saying:

“We made the choice with the information we had then. If this agreed warning appears, we look at the decision again.”

That allows the plan to move ahead without treating the first approval as permanent permission to ignore new evidence.

One concern has to survive three stages of the same decision

The first step gives your objection a clear shape. When you name the condition behind your yes, the group has something specific to check.

The second step protects the meaning while the concern moves through people. Checking what the person with authority actually heard reduces the chance that a strong warning becomes a weak summary.

The third step keeps the approved choice open to relevant new evidence. A review trigger gives the team a clear route back without treating every small problem as a crisis.

The order matters. A vague concern is hard to pass on accurately, and a decision with no clear review point is hard to reopen for a clear reason.

None of these steps guarantees the right outcome. Together, they make it harder for a serious concern to disappear simply because everyone was ready to say yes.

Move closer to the person you want to become

• Let’s turn one vague “I don’t think this is ready” into the exact condition our support depends on.
• Let’s check that the person approving the plan can describe the unresolved issue as clearly as we can.
• Let’s agree on one specific new fact that would bring the choice back for another look.

You do not have to become the loudest person in the room to protect an important concern.

Sometimes the stronger move is calm and precise: make the issue clear, help its full meaning reach the right person, and leave a clear route for new evidence to reopen the choice.

That is how disagreement can become useful information instead of background noise.

---

Explore structured learning if you want to go further

If this article makes you want to study communication, decision-making, or risk in a more organised way, a guided online course may help you practise these ideas beyond one article.