Skip to main content

Happy vs. Content

Some time ago, my manager at the time was having 1-on-1 calls with each of his staff to do a routine temperature check.  During my call with him, he asked me a common question:  are you happy?  This is not an uncommon question, to be sure, but I wanted to use this blog entry to highlight the difference between being happy and being content in one's employment situation.

You may accuse me of splitting hairs, but the answer I gave to my manager highlights the difference between the two states.  I said to him, "I am definitely happy in my job.  You are a great manager; you have earned my respect as a business professional; and you allow me some latitude to do things that are outside of the scope of my responsibilities, which keeps my job interesting."  And then I continued, "but am I content with my role?  No."

Three parts to this recipe
How is it possible for someone to be happy but not content?  You can look up the definition of the two words if you wish, and argue the philosophical aspects of this question over a cup of camomile tea, but a more practical definition is needed if it's to help you actually get to a state of contentedness.

So what is required for someone to be content?  I came up with three components:

Responsibility.  People like to know that they are valued.  And there is no greater indicator of this than to have responsibilities beyond the mundane.  There will always been the mindless activities to do, whether you are entering time in Salesforce, mopping the floor at your after school job, etc.  But to have something beyond the mundane shows a level of trust in your capabilities for which there is no substitute.

Impact.  However, responsibility alone is not sufficient.  For if the task given to you has no real impact on your group, division, business unit, or company then it's easy to come to the conclusion that the sincerity behind the assignment of the task is superficial.  In other words, it's easy to imagine the following conversation:

Manager 1:  who do you think we can convince to paint the roof?
Manager 2:  ah, let Larry do it.  If he messes it up, no one will notice.  After all, who looks at the roof?
Manager 1:  Larry!  Come here!  Boy do I have a great job for you!...

Compensation.  This final component is probably the least surprising.  Nothing will get someone riled up more quickly then finding out that their peers who have similar sets of responsibilities are being paid more than they.  I cannot count how many conversations I have had with coworkers where they have complained that they were the least paid of anyone in their role.  (Whether they were in reality is another point entirely.)  I, myself, have also had pains of jealousy when I felt I was underpaid.

There are myriad articles on the Internet about discussing compensation with one's manager, but I would argue the same principles apply to the other two components described above.  And while these discussions are not always easy to have, the possible reward of true, long term contentedness are worth overcoming the resistance you may have to sitting down, talking about your desires, and setting mid- to long-term goals for the future that allow you to reach this state of nirvana.

Popular posts from this blog

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message . Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle. (For the curious, the title says " Do you speak the same language? " in pinyin, which is a transliterated Mandarin Chinese.) Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice. I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket. "A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attemp

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ