Bad news up, decisions down

When a problem surfaces late, the first instinct is to ask why someone didn't speak. The more useful question is what speaking up costs in this team. People weigh it every time: will I be brushed off, laughed at, or seen as unsure because I'm the newest person?

Maryna noticed the refund mismatch three weeks before anyone acted. She wrote "refund amount looks off?" in a ticket and said nothing in any stand-up. Look at what the stand-up taught her: the lead's habit of "let's take that offline" pushed details away, and a joke about her being "our edge-case hunter" got a laugh. Raising a small problem looked costly and a little silly.

So silence isn't agreement, and it isn't a personality flaw. Labelling Maryna as too shy, or assuming the team was fine because nobody objected, fixes nothing. The lead's own habits set the price of speaking up, which means the lead can lower it.

Psychological safety is a shared belief in a team that you can ask a question, admit a mistake, bring bad news or disagree without being punished or embarrassed. It isn't a mood; it's built from what the lead does every week.

Four habits do most of the work. Frame the work as uncertain: "We'll miss things in the peak; I want to hear early." Give quieter people a way in: ask by name, and in writing, such as a thread before the stand-up: "Anything that looks off this week?" Admit your own mistakes out loud, so the team sees it's survivable. Respond well when it happens: thanks first, the fix second, no hunt for who's to blame.

And deal with the small moments. A joke at someone's expense needs a calm word from the lead, in the moment or right after. "Let's take that offline" with no follow-up teaches people their details don't matter. A blame hunt after a mistake teaches everyone to stay quiet next time.

A common worry: if the lead works on psychological safety, the team goes soft. The worry mixes up two different things.

Standards are about what the team expects: accurate refunds, careful replies, first responses within 45 minutes. Safety is about what happens when someone notices a problem, makes a mistake or disagrees: are they punished or embarrassed, or heard? You can have any combination. High standards with low safety produce a team that performs while hiding mistakes, which is how a refund bug sits in a ticket note for three weeks. Low standards with high safety are comfortable and don't get much done. The team you want has both: high expectations and no fear of saying "I think this is wrong".

Safety also isn't the same as niceness. Saying "the refund form is wrong, and it was my review that missed it" is uncomfortable and kind of blunt. What makes it safe is that it leads to a fix, not a hunt for someone to blame.

After a problem someone saw and didn't raise, the one-to-one decides whether they speak up next time. Don't open with "why didn't you tell us?" However you mean it, it lands as blame.

A better opening has three moves. Thank them for what they did do: Maryna's ticket note was the first signal and led the team to the bug, so the thanks is true. Ask what they noticed: that gets you the facts, and she may have seen more than the note says. Ask what made it hard to raise: that finds what the lead has to change.

Then say what you'll change. If the answer is the stand-up and the joke, the fix is on the lead, not on Maryna to be braver. Two other openings miss: "don't worry, it's not your fault at all" is kind but skips the learning, and "next time, please speak up more" puts the whole fix on the quietest person in the room.

Bad news gets worse with every day it waits. The refund bug sat in a ticket note for three weeks; once the lead knows, it goes up to Iryna the same day, before the full picture is in.

A useful message has four parts. What you know, and what you don't know yet: the refund form used the 32-lesson price for every package, so families on 8- and 16-lesson packages got back too little; the number of families is still being counted. The impact: who was affected and how. What you're doing now: Olha is listing the affected refunds. What you need from her: a decision on topping up families, and who contacts them.

Two habits ruin it. Waiting for the complete count feels thorough, but it delays the decisions only Iryna can make. Naming who missed the bug turns the report into blame, and the next person who notices something odd will think twice before saying it. Report the system's failure, not a person's.

When you disagree with a decision from above, there's a right time and a right audience for it: before the decision is final, to the person who makes it, once, with reasons. The lead would have asked for three weeks to contact families instead of two, in the middle of the peak. That's worth saying to Iryna, plainly and with the reason.

Once the decision stands, carry it honestly. It's tempting to tell the team "I'm against this and it wasn't my call", and it feels honest. But it invites the team to resist a decision they can't change, and leaves them without a plan. You can still be truthful about the process: say who decided, and that you asked for more time.

Repeating the objection after the decision only reopens a closed question. What reopens it properly is new evidence: Iryna asks to hear on Monday, not on day fourteen, if the first week shows it can't be done. That's the loop: disagree before, carry it out, report back with facts.

Decisions often come from above, and the lead is the one who tells the team. A good announcement has four parts: who decided, why, what it means for the team, and what's still open for the team to decide.

Iryna and Hanna decided to recheck every refund since the form changed and top up every family who got too little, with Support contacting families within two weeks. The lead had asked for three. That disagreement can be mentioned honestly, in one clause: "I asked for more time; two weeks it is, and here's how we'll do it."

Two traps cost trust in opposite directions. Claiming it ("I've decided…") falls apart the moment people learn who decided. Distancing yourself ("they decided, not me, sorry") invites the team to resist something they can't change and leaves them without a plan. Leaving out the reason is a quieter version of the same mistake: people fill the gap with guesses. And Olha's point: say what is still the team's to decide, such as the order of families and the reply template, or the decision just lands on them.

Put the pieces of this lesson in order and you get a loop a lead can run on any decision from above.

1. Raise your concerns with the decision maker, once, with reasons, while it's still open.
2. Accept the final decision and plan how the team will carry it out.
3. Announce it: who decided, why, what it means for the team, what is still open.
4. Give the team the choices that are theirs: here, the order of families and the reply template, which Maryna could draft if she wants to (ask her privately first, and credit her note only if she's comfortable).
5. Report back with facts, early, especially if the plan can't hold.

End the written announcement with where to ask, because people two hours behind Kyiv will read it before anyone can answer.

How it fits together: silence is a price people pay, safety is what the lead does, bad news goes up the same day, and decisions come down honestly with the team's part named. Next, the module's case, The 90-minute stand-up: two weeks of meeting data.