Sometimes you sense that something isn’t right at work. You suspect that your finance colleague might be fudging numbers, your boss isn’t telling his manager the truth about an important project, or your co-worker is skipping out of the office early but leaving her computer on so it looks like she’s just down the hall. How do you know when it’s worth speaking up or not? Can you you protect yourself from potential consequences of calling out bad behavior? And when you do decide to say something, what do you say and to whom? What the Experts Say Watch for
rationalizations Consider what’s really at risk Understand why people are acting the way they are Weigh the pros and cons Talk to the perpetrator first Rehearse Ask questions, don’t accuse In the best-case scenario, your colleague may respond by saying, “Wow, I haven’t thought about it that way,” and change his behavior. Problem solved. Or he may start to rationalize his actions: “This is always how we’ve done it.” “You’re not seeing the big picture.” In this case, you want to align yourself so he doesn’t feel accused. Detert suggests saying something like “I just asked because I’m concerned about you and I wouldn’t want you to get in trouble” Or “I know we share the same overall goals, I just wanted to help make sure we were on track” or “I wanted to be sure we protect the organization’s reputation.” If your colleague believes you’re on his side, he’s more likely to be open to changing his mind about his behavior. Escalate
when necessary Protect yourself Principles to Remember Do:
Don’t:
Case Study #1: Test the waters
before speaking up But Sharon was worried that when the customer got the first invoice, things would blow up, and she was right. A month after the contract was signed, the CEO called her into his office and explained that the customer was upset about the invoice and felt deceived. Sharon explained what had happened. The CEO told her that wasn’t how their organization did business and asked her to push back in the future. “He knew that [Kim] was tough and understood why I hadn’t stood up to her,” Sharon says. But she still felt as if her reputation had been damaged and regretted not saying anything. “It was valuable lesson for me. If the same thing happened now, I would just tell her, ‘We can’t do that’ and give her alternatives,” she says. Case Study #2: Stand your ground when necessary “I put my foot down and simply said that I would only share my own observations as a bystander,” she says. The decision was driven not only by her personal values but also her concern that the organization could be sued should the private information have any impact on the employee’s salary, benefits, promotion potential, or future employment. As she suspected, her stance did have consequences. Her boss and one member of the executive team “became much more guarded” with her. But she still has no regrets: “I knew I was doing the ethical and legally correct thing.” *Names and details have been changed. |