# Bad news up, decisions down > Why a quiet person sits on a problem, what a lead does to make speaking up safe, and how to announce a decision you did not make. - Course: [From Specialist to Manager: Your First Year Leading a Team](https://productovi.com/courses/from-specialist-to-manager.md) - Module: Meetings and communication - Lesson 19/32, ~24 min - Source: https://productovi.com/courses/from-specialist-to-manager/bad-news-up-decisions-down ## A bug nobody mentioned **Alex Tutor:** Mid-May. A family writes that their refund looks too small. Olha checks: the refund form has been using the 32-lesson price per lesson for every package, so families on 8- and 16-lesson packages got back too little. **Olha:** And there's a note in a ticket from three weeks ago. Maryna spotted the same mismatch, wrote "refund amount looks off?" and left it there. **Sofia:** Three weeks. She was on every stand-up since. Why didn't she say anything? **Alex Tutor:** Before you ask her, ask the harder question: what does speaking up cost in this team? Think about what happens in your stand-up when someone raises a small problem. **Sofia:** I usually say "let's take that offline". And once Taras called her "our edge-case hunter". Everyone laughed. > **Exercise:** Maryna saw the refund problem three weeks ago, wrote "refund amount looks off?" in one ticket and stayed silent in every stand-up. In those stand-ups the lead usually says "let's take that offline", and once Taras called her "our edge-case hunter" to laughs. What is the most useful conclusion for the lead? ## Safety is something a lead does **Alex Tutor:** **Psychological safety** is a shared belief that you can ask, admit a mistake, bring bad news or disagree without being punished or embarrassed. It's built from what the lead does every week. **Alex Tutor:** Frame the work as uncertain: "We'll miss things in the peak; I want to hear early." Ask by name, and in writing, so quieter people have a way in. Admit your own mistakes out loud. **Alex Tutor:** And respond well when it happens: thanks first, the fix second, no hunt for who's to blame. A joke at someone's expense needs a calm word from you, in the moment or right after. **Sofia:** Doesn't that make the team soft? We still need high standards. **Alex Tutor:** Safety isn't niceness and it isn't lower standards. The strongest teams have both: high expectations and no fear of saying "I think this is wrong". > **Exercise:** Which lead behaviors make it safer for people like Maryna to raise a problem? Select all that apply. **Alex Tutor:** Your worry about going soft is common. Check it against this. > **Exercise:** **True or false:** building psychological safety means lowering standards, so that nobody feels pressure. ## The conversation with Maryna **Alex Tutor:** Now the one-to-one. Don't open with "why didn't you tell us?" She'll hear it as blame, whatever you mean. **Sofia:** Then thank her for the note, ask what she saw, and ask what made it hard to raise. **Alex Tutor:** Yes. And tell her what you'll change. If the answer is "the stand-up and the joke", that's on you to fix, not on her to be braver. **Alex Tutor:** Then the bad news goes up the same day. Iryna needs four things: what you know, the impact on families, what you're doing now, and what you need from her. Don't wait for the full count. > **Exercise:** The refund form undercharged families for weeks. Maryna had noticed it three weeks ago and left only a note in one ticket, which later led the team to the bug. In your one-to-one with her, which opening is best? **Alex Tutor:** Then the news goes up. What belongs in your message to Iryna today? > **Exercise:** You're messaging Iryna about the refund bug the same day you found it. What should the message contain? Select all that apply. ## A decision from above **Iryna:** Hanna and I have decided. We recheck every refund since the form changed and top up every family who got too little. Support contacts them within two weeks, starting Monday. **Sofia:** In the middle of the peak. I'd have asked for three weeks. **Alex Tutor:** Say that to Iryna, once, with your reasons. If the decision stands, you announce it as it is: who decided, why, what it means for the team, and what's still open. **Alex Tutor:** Two traps. Don't pretend it was your idea, and don't distance yourself with "they decided, not me, sorry". Both cost trust. You can say "I asked for more time; two weeks it is, and here's how we'll do it." > **Exercise:** **True or false:** when announcing a decision you argued against, the most honest move is to tell the team you disagree and that it wasn't your call. **Alex Tutor:** So how would you say it? Pick the line for the team. > **Exercise:** You asked Iryna for three weeks; she decided on two. Which line best opens your announcement to the team? ## Before you hit send **Sofia:** Should I tell Iryna again that two weeks is too tight? **Alex Tutor:** You've said it once, with reasons. Saying it again now only reopens a closed decision. If new evidence appears, bring that instead. **Iryna:** And if the first week shows it can't be done, I want to hear it on Monday, not on day fourteen. **Alex Tutor:** That's the loop: disagree before the decision is final, carry it out, report back with facts. > **Exercise:** Put the steps of handling a decision you didn't make in a sensible order. ## Your turn: the announcement **Olha:** If you're writing to the team, tell us what's still ours to decide. Otherwise it just lands on us. **Sofia:** The order of families and the reply template could be theirs. Maryna could draft the template, if she wants to. **Alex Tutor:** Ask her privately first. Credit her note in the announcement only if she's comfortable with that. **Alex Tutor:** And end with where to ask, because the people two hours behind Kyiv will read it before anyone can answer. > **Exercise:** Write the **team announcement** (5–7 short lines) of Iryna's decision: every refund since the form changed is rechecked, and Support contacts the affected families within two weeks from Monday. Say who decided and why, what it means for the team, what the team decides itself, and where to ask. > **Key ideas** > > - Silence isn't agreement. When a quiet person sits on a problem, ask what speaking up costs in your team, starting with your own habits. > - **Psychological safety** is built by what the lead does: frame work as uncertain, ask by name and in writing, admit your mistakes, thank before you fix, stop jokes at someone's expense. > - Safety isn't niceness or lower standards; strong teams have both safety and high expectations. > - Open the one-to-one with thanks and curiosity, not "why didn't you tell us?"; fix what the lead owns. > - Bad news goes up the same day: what you know, the impact, what you're doing, what you need. > - A decision from above: disagree upward once, with reasons; then announce it honestly (who, why, what it means, what's still open), without claiming it or distancing yourself. **Alex Tutor:** Next: the end-of-May case. Your stand-up runs 90 minutes, and you have two weeks of data to prove it. - Previous lesson: [Channels and async work](https://productovi.com/courses/from-specialist-to-manager/channels-and-async.md) - Next lesson: [Case: the 90-minute stand-up](https://productovi.com/courses/from-specialist-to-manager/the-90-minute-stand-up-case.md) --- Productovi Learning. Free, no sign-up needed to read.