Showing posts with label Management. Show all posts
Showing posts with label Management. Show all posts

Sunday, January 24, 2016

A model to evaluate your work motivation levels

The following are my own personal views and do not represent the views of my current or past employers or affiliated organisations.
A while ago, there was a survey 'what motivates you at work?' that I was invited to participate in. This also had a reward of recognition for contributors attached to it. So, motivated ;^) I set to think about the topic and search for answers. Finally, it evolved into a model that perhaps someone else can also use to their own situation.

When one searches on the web one can find a ton of information on this topic. Mostly, there is a lot more information on systematic studies for 'how organisations can motivate individuals' as compared to information on 'how I as an individual can evaluate my own motivation' at my workplace, within my team and within my department/organisation and it's place in the world.

So, here is a very minimalist model that I eventually came up with to support those who want to evaluate/understand their own motivational levels they experience within their team/department/organisation. The goal being that this model would eventually guide one to understanding why they are where they are on the motivational plane.

The premise is that 'motivation' can come from within and also from the environment one is placed in. The centre peice of this model is the person (the 'ME') that is undergoing this self-evaluation.

The text within the boxes are just some guiding examples, fill them with your own.

Evaluating motivation within, starting with ME as a point of reference

ME

In my opinion, the two layers of basic needs psychological and safety/security from Maslow's heirarchy find their place here. These are similar to what is referred to as Hygeine factors (status, job security, salary, continuity etc.) in Frederick Herzberg's two factor theory.

MY TEAM/DEPARTMENT/ORGANISATION

For the perspective on motivation at the workplace/department/organisation level, this cool animation made by adapting Dan Pink's talk is definitely worth a watch. In this short talk he mentions about the motivational model that is harnessed by the open source revolution (linux in particular) and summarizes take away lessons.

Although, the main focus of Dan Pink's talk seems to be 'how organisations can motivate individuals' and 'make the world a better place' one can relate to that from a 'ME' point of view of evaluation as well (and the animation is well .. 'engaging' .. keeps you motivated to continue watching till the end).



MY WORLD

Being in touch with the world or a community is very livening, crucial and nurturing after the mastery stage in a person's evolution to continue to stay highly motivated and evolve further. In a lot of ways this is analogous to the 'social needs' that are at the top of Maslow's heirarchy.

In my opinion, a major factor that fueled the open source software revolution is this influence and feedback mechanism it enabled a software developer to have with the world. In this case, maybe with a developer and user community to begin with. The world is larger than and is a super-set of an organisation. This means the potential of influence a master developer can have is exponentially larger than he/she could have on the world at large from within an organisation. This factor enables skilled software developers to be 'engaged'.

On this particular topic, Eric S Raymond's book 'The Cathederal and Bazaar' is worth reading where he talks about his experiences with fetchmail as open source software. Although the book's rights are with O'Reilly you can still read the original essay and listen to the stand-up talks from the link above.

REFERENCES

Saturday, November 16, 2013

Management Versus Engineering - Star Trek Style

The Problem:
Two warring worlds: the Troyians and the Elasians
Their planets located right in the region disputed between the Federation and the Klingon Empire.

These two worlds have had enough of warring and are ready for peace and progress. It is of utmost importance at the moment. These two worlds have developed weapons of total destruction in their recent advancement in weapons technology.

The solution:
A marriage between the ruler of Troyius and 'Her Glory' Elaan the ruler of the Elasians

The Troyians engage the Starship Enterprise for this diplomatic mission. As a representative of the Federation, the Enterprise is obliged in the hope to gain favor of these planets in the disputed region over the Klingons. The Troyians send their Ambassador Petri to receive the extremely arrogant 'Her Glory' Elaan (Queen and ruler of the Elasians) to take her to her wedding with the ruler of the Troyians.

Ambassador Petri's Requirement: The voyage to his planet must be smooth and very slow!
Reason:  To give Petri enough time to tame the shrew (Elaan) aboard the Enterprise ! And to educate her with the ways of the Troyians people or at least civilize the raging woman to become an acceptable queen to the Troyians. Or else this might cause war even earlier.

Now let's  map these characters to roles in a Industrial Project connect with the subject Management Versus Engineering.

Petri is the Customer with requirements, He is a customer of the Federation which you can consider as the company. Petri is interfacing with Captain Kirk who is obviously Management of the Starship Enterprise. Not yet introduced, the Starship Enterprise's engineer Scotty who is representing Engineering.

Star Trek Customer, Manager and Engineer
It is an interesting interaction between the three of them at the start of the voyage from Elasian to Troyian (the goal of the Project). More interesting is that it depicts the well known problems in interaction between the management and engineering disciplines.

Petri to Kirk: "We will go back to Troyius, but .... slowly Captain I will need time. Before we reach there she (Elaan) must be taught civilized manners. In her present condition, my people will never accept her."

Kirk agrees and goes towards the bridge. On the bridge the captain orders the helmsmen to lay a course to Troyius on impulse speed. Here, non-Trekkies must understand that impulse speed is far far far far less than the top speed the Starship Enterprise can handle with its warp drive!!!

The Starship USS Enterprise
TOP: Customer <---> Manager
BOTTOM: Manager <---> Engineer
Scotty, the ship's Engineer is also on the bridge when the Captain is passing the orders. He is unaware of Ambassador Petri's requirement.

So he comes up to the Captain's station surprised and asks "Captain, will you not be using the ships warp drive?!".
Kirk says "No!".
"All the way to Troyius Captain" Scotty persists.
"Yes!" says the Captain.
"Hmm .... that'll take a great deal of time!" says Scotty sarcastically.
"Are you in a hurry, Scotty?" says the Captain.
"No" says Scotty walking away shaking his head quite not understanding the Captain's ways.
Captain Kirk looks on and smiles. 

It seems like the 'communication gap' between Manager and Engineer has not been bridged even on the bridge of the Starship Enterprise in the year 2266 which is the timeline of Star Trek :-) !

You can watch a preview of this episode (Season 3 Episode 13) below:

References
[1] Timeline of Star Trek - http://en.wikipedia.org/wiki/Timeline_of_Star_Trek
[2] Preview of the Episode - http://youtu.be/oAmh-AvCcUU
[3] The Episode details on Wikipedia - http://en.wikipedia.org/wiki/Elaan_of_Troyius