You Can Have a Bad Day Without Giving Your Team One
Thanksgiving is coming. And for a lot of us, that means family stress is going to start to leak into our workdays. Maybe Uncle Steve is on the fence about whether he’s going to bring all six of his new stepkids and you don’t really have space for them. Or cousin Wendy is coming back again, even after she complained all year about last year’s Thanksgiving. Or you have to travel across the country and back again in the course of three days with two toddlers.
No matter what causes your bad mood – Thanksgiving or just life in general – it’s important to know what it looks and feels like when you get hijacked so you can prevent your bad mood from spilling over into the work of your team.
Does this sound familiar? You’ve just learned that a project you championed is losing funding. Five minutes later, you’re in a team status meeting, and someone asks a perfectly reasonable question. “We’ve already discussed this,” you snap. And then it goes very quiet, and nobody asks any more questions in the meeting.
That’s spillover. Even though you’ve changed meetings, you’re still thinking about the funding. Your team is trying to figure out whether it’s safe to ask you a question. And you’re showing them it’s not.
How do you know you’re being hijacked? Bad news can make everything feel urgent. As a result, you fire off a message, demand answers before you know what happened, or make a decision just to feel like you’re doing something.
A bad mood can change the story you tell yourself. A short email reads as disrespectful. A request for clarification sounds like pushback. A minor mistake starts to look like a pattern.
The cue to watch for is: What am I suddenly very sure about? That certainty is usually an indicator to check your interpretation before acting on it.
The key is to build a buffer between the trigger and the response.
Name what you’re carrying. “I’m still rattled by that call.” “I’m worried it’s all going to fall apart.” “I’m so annoyed by him!” Even a private acknowledgment can help you catch what’s following you into the next conversation.
Separate what happened from what you’re adding. “The client asked to revisit the timeline” is a fact. “They’ve lost confidence in us” is an interpretation.
Choose what needs to happen next, not permanently. Because bad news can cause us to catastrophize, it’s a good idea to wait before you take action. You can acknowledge the news, ask one clarifying question, or tell people when they’ll hear from you. The bigger decision can wait if there’s time to think it through.
As much as you might like to, you can’t pretend your mood isn’t already in the room. I like to be upfront about it and take a moment to reset. I might say something like, “I just had a difficult conversation, and I need a second to land,” or “I’m distracted by something going on in my personal life. Give me a minute to sort it out.”
But if you’ve already snapped at someone, repair that moment as soon as you can. “I cut you off when you asked about the timeline. Sorry about that. It was a fair question. Can we go back to it?” Making sure others know that your feelings aren’t directed at them goes a long way. (Just ask my husband – when I get really upset about something, I raise my voice, and have to periodically remind him (and myself) that “I’m not yelling at you, I’m just yelling.”) The beauty of this is that the person gets to finish their thought, and the team sees that questions are still welcome.
Hopefully, this will be what starts to sound familiar: You just learned that a project you championed is losing funding. Five minutes later, you’re in a team status meeting, and someone asks a perfectly reasonable question. You want to say “We’ve already discussed this,” but instead you say, “I’m sorry, I’m distracted by something in my personal life. I want to make sure I understand what’s not clear – can you ask again?”
Here’s a question to ask yourself between meetings: What am I carrying into this room that started somewhere else?




Comments