When 300 technical professionals at a major utility were told to re-apply for jobs in their department as part of a major reorganization, they were livid.
"I've been here 18 years." (Longevity means immunity to change)
"I hired the idiot who's running this thing." (If I gave someone their job, they won't mess with mine)
"They already know what I can do." (I only have to prove myself once)
"No other utility has ever had to go through this." (This place isn't being run according to the norm)
"No one told me this could happen when I was hired." (This wasn't part of the deal)
"My wife and I have planned our retirement for 23 years." ('They' are responsible for my cradle-to-grave existence)
Danger: The "Invisible Assumed"
When you signed on with your current employer you probably discussed:
Salary, benefits, corporate vision, the marketplace, performance expectations.
Chances are you won't become really upset as a result of any of those items changing a bit. It's the ones you assumed to be true that will come back to haunt you.
You'll become disenchanted as a result of someone breaking the implicit contract .
The contract that you created in your own mind. Visible only to you.
In the real-life example above, the implicit contract had to do with the unspoken nature of Utility companies: Stable, Secure, Lifetime Employment, Methodical Career Progression...
No one ever said those things out loud. They were just "known."
Q: Do you and your spouse get upset about what you talked about before you got married or what you assumed would be true?
Tips for Employees and Employers
Employees:
1. Before you sign on the dotted line, check out your assumptions.
2. Make a written list.
3. Check out their validity with your prospective company or boss.
Employers:
1. Before introducing a change, take a look at the culture.
2. What is it that drew people to your company in the first place?
Security? Action? International travel? Work close to home?
3. If one or more of those traditional characteristics (the unspoken attraction) will change, then help neutralize the impact by discussing it openly.
Tell what is going to happen and why. Explain the reality of implicit agreements and that you realize this might be one such example. You'll give people a mental model to understand what they are experiencing.
Finally: What happened to our 300 techies?
a. They had been told before the process started that no one would lose a job with the company. They would hopefully be better matched as a result of the process. And, everyone did remain employed.
b. The department as a whole was more effective.
c. About 10% chose to retire rather than make the change.
What is your unspoken, implicit contract? How did your employer's reputation and industry culture contribute to that?













Some companies deal with employees' unspoken contracts by destroying any employee expectations of the company. When this happens, companies usually just don't care about the employees. But sometimes companies do care, at least enough to intentionally destroy expectations. Does this management style produce problems? Yes, but it also has attractions (which I'm not going to discuss for fear of luring more managers to the Dark Side).
Posted by: Steve Carrell | October 14, 2011 at 12:41 PM
Somehow, this reminds me of the movie Horrible Bosses and Kevin Spacey's character there. Great article, thanks so much!
Posted by: HR Software | October 16, 2011 at 09:54 AM
Good post i like this post. I share to my all friends. And The "Invisible Assumed, Tips for Employees and Employers, 300 techies is very nice point. Really i appreciate to this post.
Posted by: Human Resources Management | October 18, 2011 at 01:37 AM
Hi Sir Steve, I have worked in a company wherein it was bought by another company but as what I have observed there was no concrete notifications by HR as to what will happen to us back then. Can I say that I was just assuming back then? Many of my colleague were worried and assuming things and I think HR should somehow clear up our minds for us to prepare ourselves. Thanks.
Posted by: Ian Monteros | February 15, 2012 at 05:30 PM