1

I am the leader (say, level 3) of a small team of engineers (level 4), one of many in our project.

A couple of months ago, our management (level 1), together with HR, has announced plans for a new organisational policy that has been met with a high degree of criticism from levels 3 and 4 (and so far, at least one senior employee of two decades quitting in response).

Many people in levels 3 and 4 in my circle of contacts - including myself - strongly oppose the policy and do not consider the reasoning put forth by level 1 to be sensible.

Our level 2 managers have explicitly confirmed level 1 management see no problem with our current work output and the change in policy has nothing to do with any issues on that end. Further, these level 2 managers have assured us their support in helping us bring forth some alternative solutions for fulfilling level 1 management's underlying wishes (if only we can figure out what these are).

Now, several months of discussion between level 1 management and various internal parties have passed. Level 1 management and HR have finally announced they are going to impose the policy regardless, all the arguments against are considered irrelevant. Fair enough, their prerogative.

Here's the problem: Level 1 management and HR have now informed levels 2 and 3 that we are now supposed to enforce the policy toward our reports. In particular, our instructions are (paraphrased):

Do not shift responsibility to someone else by pointing e.g. to management or HR. Tell your direct reports that you want them to adhere to the policy and justify to them, why this makes sense.


EDIT: To clarify: I understand the above in such a way that I have to convey the new rules and the reasoning behind them as provided by management, but without saying these rules and the reasoning come from management. In my opinion, if I cannot say "rule X is necessary because of Y, according to management", but only "rule X is necessary because of Y", that leaves no other interpretation than that I personally believe in that justification.


How do I handle this without blatantly lying to my team members' faces? As mentioned, my reports are very much aware I oppose this policy and see the reasons listed by level 1 as baseless.

9
  • Watch the first episode of Futurama. “You gotta do what you gotta do”, it’s a great episode and saying, and it sounds like it’s both justification and not lying in a case like this. Commented yesterday
  • 1
    I don’t see why you think you have to lie. Your stated instructions are with respect to adhering to the policy, not the policy itself. Not violating company policy is generally a good idea to stay employed… Commented yesterday
  • @MisterMiyagi: I do not just have to announce and enforce the policy. I am supposed to express that I want my reports to adhere to the policy, not because it's a policy, but because I personally agree with the stated reasons. Commented yesterday
  • @user139158 That would be quite useful to have in the question explicitly. Commented yesterday
  • 1
    @MisterMiyagi: Thank you for pointing that out. I have added a hopefully clarifying statement to the question. Commented yesterday

6 Answers 6

8

The best way to handle diverging opinions is to "Disagree and Commit". No company decision is ever going the please everyone, so the people who don't like it still need to get on with the program. It's perfectly ok and healthy to voice your concerns and disagreement during the decision making process, but once the call is made, it's time to move on.

How do I handle this without blatantly lying to my team members' faces?

At this point you need to push back on HR and management. Asking is someone to lie is absolutely not ok. You can say something like:

While I disagree with the policy and I'm not aligned with the reasoning, I'm happy to implement as best as I can if that is what the company has decided to do. However, I can and will not openly misrepresent facts to my people. We need to come up with a messaging strategy that allows me to maintain my professional and ethical integrity and that does not contain factual inaccuracies.

At this point you can make a message suggestion based on what you are comfortable saying while leaving out any blame. Perhaps: Something like "Starting Jan 1st, everyone is require to be in the office twice a week. I know this is controversial, but it's the new policy and we will comply and get on with it". I'm sure there will be questions, but you should also ask HR to come up with an FAQ script or website. That's best practice anyway, otherwise you end up with a dozen different answers to the same questions.

If you want to strengthen your case, you can elicit a few of the other level 3/4 managers, that feel the same way. A single concern is easy to dismiss but a broader uprising in the ranks is something that HR is afraid of.

If HR or senior management keeps pressuring you to "sell" the policy in a way that requires you to lie, you have a hard decision to make. For me, that would be a trigger to start looking for a new job. Asking someone to lie is unethical and if they are unethical on this occasion, chances are they will be unethical to you and others in the future. That's not a good long-term outlook.

6

New policies are invented for a reason: to reduce costs, improve quality, increase customer satisfaction, deliver faster, retain good employees, etc etc. You don't make it clear in your question what your issue is with this policy. It will fail to achieve those aims? It will introduce negatives that outweigh those aims? The company doesn't need to achieve those aims? There are different policies that would achieve those aims with less negatives?

It's important that you understand the purpose of the policy (eg to reduce costs) and exactly why you oppose it (we don't need to reduce costs, it won't reduce costs, there are better ways to reduce costs) before speaking to your people.

Once you understand that, your instructions are, sticking with the example of reducing costs, to tell people "I want you to follow this new policy, which is being introduced to reduce costs" and not to include "even though I don't think we need to reduce them at all" or "even though I think it will fail to do so" or "even though many better options exist to reduce costs." Just give the high-level reasoning behind the policy. Passive tense ("is being introduced to") will do a lot of work for you.

Saying things like "I know this is foolish but management insists on it" will help no-one. You don't need to provide a zillion details of why this is the best policy ever. You also don't need to say you fought it, you tried, "sorry team I didn't want this but we're stuck with it" or the like. While it feels like lying to omit these sentences, they make things worse. If you truly feel "Fair enough, their prerogative" then you have to walk that walk. Folks with more experience and possibly more information than you believe that policy A will achieve aim B, and that aim B is worth achieving. That is the message you are being asked to deliver.

When people tell you "but it won't reduce costs!" or "but our costs don't need to be reduced!" or "wouldn't it be better to do this other thing instead?" you don't need to either agree or disagree with them. You can say something as simple as "this is the new policy and I am asking you to follow it."

8
  • 2
    ... As a result, the risk of losing key resources and thereby endangering the existence of our products. I appreciate the reference to passive tense; that does sound like a helpful strategy to avoid poisoning morale in my team and bridge the time until I have found a new employer and can get out. Thank you! Commented 2 days ago
  • 1
    @user139158 - All those issues are your managers and their managers problems to solve. Individuals can be replaced. Pipelines of gadgets to make your gadget can be replaced. All of those considerations were either discussed and answered or they were not but regardless the changes are still happening. Your job assigned by your manger is to implement the change Commented yesterday
  • 2
    @Donald: Also re "All those issues are your managers and their managers problems to solve." - I am afraid before it gets to that, they will very much be my problems to deal with first. Because I'll be at the frontline to deal with disgruntled reports first, I'll have to keep up our productivity despite a challenging work environment, and I will have to (personally!) do the work that is not done when my key resources leave the team. So, yes, they are, at first, very much my own issues to solve, and I have thus a very personal motivation to keep my team happy. Commented yesterday
  • 2
    @user139158 - As a manager, you have to accept that not every problem is your problem to solve. Sometimes, you have to accept that fact, and explain to your team that things are going to change. Commented yesterday
  • 2
    @user139158 "and I will have to (personally!) do the work that is not done when my key resources leave the team" - In that case you are working in a hugely dysfunctional organisation, and your best bet is to get away from it as soon as you can. Commented yesterday
3

“I have been told to tell you that I want you to adhere to this policy, and justify to you why this policy is right. I have not been told in any way by upper management to tell you this, and I will not tell you in any way to believe that upper management has anything to do with it”.

In other words, lie to your staff in the most transparently obvious way possible.

2

I feel you. More precisely I feel like you are my boss. Because I just read the announcement of how we have a new Return-To-Office policy from our coprporate overlords. And how this is a great chance for us to finally... grow together as a team even more (official fairy tale) or more realisticly hate each other because we will now be penned up in bunches of 4-6 in a room with no air condition and constant phone calls that we took about an hour of traffic to even reach. Compared to the previous years of single-person air conditioned offices with no distractions at our respective homes with zero traffic.

I don't think there is a good way to transport this decision, simply because it is not logical or in the best interest of the product the company is making.

Write an official communication (E-Mail, MS Teams, whatever your official channel is) doing exactly what your bosses want. Give it your best sugar coating. Bring all their arguments and "explain" how they make total sense. It doesn't matter that it is total bullshit. You don't believe it, your coworkers don't believe it, it doesn't matter. These were your orders, you follow them.

Before you post that, call in a team meeting with no notes and no recording and tell your team that you think it sucks and you fought it, but weren't successful. Your job now is to make it work and take a boatload of lipstick to the pig. Tell them you will post that after the meeting. And if they want to bitch and moan about it, they will need to do it the old fashioned way, with a coffee in the smokers corner outside the office building. You will be there to listen and maybe chime in.

Then post it.

Whether you want to look for a better job is up to you. I'm not entirely sure myself yet. Do not make the mistake of actually trying to do what your bosses told you. You cannot. Trust is the only thing you have in terms of respect from your coworkers. Don't throw it away. They know it sucks. They know you know it sucks. You don't have to rile them up and pour gasoline into the fire, but don't sugar coat it any more than you officially have to to comply with the bosses request.

1

There does exist a risky option, that if you have a leader that frequently pivots to new things, or people cycle in and out of that position every few years, then this may be viable:

Ignore, Delay & Bypass

I witnessed something similar to this situation where an executive was pushing a bad decision, and the people several levels below who would be implementing it were killing over laughing at how absurd it was. So with their immediate leader's support they ignored it.

When higher ups asked them for status on their integration of it, they seemed to always have very high priority tasks from customers coming up that were delaying their availability to implement the changes, or they could not risk making any changes while they were in the middle of a critical deployment. It was impressive watching said lead's ability to come up with excuses to kick down the responsibility down the road by a month or two.

Eventually the executive moved on to the next initiative and thus no one was pushing or checking on that bad decision. Other groups in the organization quickly reverted back, mean while their group continued on as nothing had happened.

One key aspect of this strategy is delaying. Even if you eventually have to come in line with a decision, you can take lessons from other groups and mitigate some of the negatives. Also if other groups go through the painful transition first and leadership can see the fallout of the decision they may relent before your group is forced.

Then the last aspect is bypassing. A former coworker once had a requirement pushed upon them that thou shall use a specific framework. Problem was said framework was never intended for said product. So they used it for small portion while using a different framework that actually did the job. I will note this did carry a huge additional drawback: The leadership thought their decision worked and did not learn from their mistake and thus were likely in the future to do the same thing again.

-3

The boss gets to tell workers what to do.

Managers are expected to implement the decision without saying "the boss says you have to do this." This is Management 101, someone should have taught this to you. There is nothing controversial about this. If you are expected to give a reason then read the one they gave you. If not then just don't give one. "This is the new policy."

Your recourse if you don't like it is to find a new boss.

4
  • I fully expect of my reports (L4) that if I (L3) impose a policy (of my own making, for my team) on them that clashes with their work to speak up, to discuss with me why the policy doesn't work the way I thought it would, so we can develop an alternative solution that fulfils both my requirements and theirs together. If our L2 manager imposes such a policy, they expect us L3 team leads to do the very same thing and come back to them with an alternative plan that we have developed on our own or possibly together with our reports. For this purpose, transparency about where a given policy ... Commented yesterday
  • 1
    ... originates is crucial, and the knowledge that one's concerns are heard (even if ultimately overruled) is the foundation of trust between reports and their manager. (Trust, incidentally, being one of the main pillars L1 management likes to promote as a core value of the organization.) I think this is also Management 101. We are engineers, and if I impose some rule, I am expected to list good reasons for it rather than just tell my reports "Do it that way." That is why I consider it controversial to deliberately misrepresent who gives what reasoning for this policy. Commented yesterday
  • @user139158 that's a lot of words to say you don't like it. Commented 19 hours ago
  • "Managers are expected to implement the decision without saying "the boss says you have to do this." This is Management 101" No, it's not. It's standard procedure to tell people at what level a decision was made. Commented 18 mins ago

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.