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

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 t...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...

Application Development Done Right

In a previous article, entitled DevOps as the Ultimate Panacea? , I described how developing code without thinking about the current needs of the end user as well as the future needs once they've become accustomed to using your application ends up not only frustrating them but also can result in customer churn and ultimately lower revenues.  In this article, I'd like to describe something simple that I came across today that shows a definite degree of effort to do quite the opposite. Recently, we had a severe snowstorm, one with blizzard-like conditions, which is unheard of in central New Jersey.  Being responsible adults, my wife and I went to the grocery store to stock up on essentials (read:  chips, chocolate, etc.) in case we get stuck at home. As we were ringing up our order, the cashier mentioned to us that the store has a mobile application.  Since both of us are in technology oriented professions, we were skeptical about the need for a grocery store mob...