Why do you work? Do you believe that what you do in your professional life has a meaning? What do you tell to your friends that you do? And more importantly what are you telling yourself on daily basis to get out of bed and to the office?
You hear it more and more. To be happy at your work you need a purpose, you need to understand what the meaning of your work is. Daniel H. Pink popularized this concept in his book “Drive: The Surprising Truth About What Motivates Us”. Motivation in modern economy comes from three sources: Autonomy, Mastery and Purpose. Let’s focus on Purpose. Do you believe that for your life to have a purpose or a meaning you need to do something larger than life? I don’t think so. Whatever your job is, as long as it fulfils a need of “someone” it has a purpose. The real question is: are you able to formulate the meaning in a way that will be motivating for you and that you can be proud of?
Have a mission statement
I used to be a software developer who at some point in my career figured that I like working with people more than with code. I will show you on my example what a professional mission in the life of a manager and a software developer can look like and what type of stories I tell to myself to keep loving what I do. My current professional mission statement reads like this:
“I’m an experienced engineering and operations leader passionate about setting up offices, building teams, growing people and solving difficult business problems.”
In this one sentence I tell you (and myself) how I want to be seen and what I believe the mission of my professional life is. When you ask me what I do, this is the answer you get. It doesn’t talk about specifics, company, role, or job title. These are just monikers people hide behind. If I told you I’m “director of engineering” or “operations manager”, what exactly would you learn about me? And more importantly, how exactly is that supposed to motivate me personally? The mission statement needs to tell you and those around you who you aspire to be, what your core values are, and what value you bring to others.
Let’s say you are a software developer. Could your mission statement read for example like this? “I’m an enthusiastic hacker and geek who enjoys solving hard business and technical problems by producing state of the art software.” Or if you want to be more specific about a particular domain “I’m an experienced software engineer with a knack for building well designed, scalable and easy to use IT management software that gives other IT professionals opportunity to have unparalleled view of their environment and helps them to easily solve complex IT problems.”
If I were a developer and self-talked to myself like this, I would be certainly proud on what I’m doing and saw a real purpose in my professional life. The great thing is that this is completely under your control! No more complains or excuses that “there is no vision”! You don’t rely on your company’s CEO to show you a great vision of the future and on your HR department to paint a company mission on the wall. Regardless of what the company does, or what your role is, you can create a mission statement for yourself that will make you feel valuable.
Have a story to tell
But it doesn’t end here. To have a one-line sentence with the mission statement is nice but it is pretty much an advertisement that may not provide enough insights into details of what you do and why you should be proud of it. It is a good reminder for you to know the big picture but having a story or two that document your successes, career high-lights, or things you are particularly proud is important to show who you truly are.
In my case I could for example look at some of the offices and teams I built over the years and summarize it in a short one paragraph story. It should be short for two reasons. First, it will force me to focus on the key aspects of why this particular time of my professional life is note-worthy. Second, it can be a good overview that won’t bore the listener for too long, being it a friend or an interviewer. I believe your story needs to have four parts: what happened, how it happened/what role you played, what were the results, why it was important for you personally and for others.
“[What happened] In 2008 I joined a small US based software development company with the mission to build a strategic R&D center in the Czech Republic. [How it happened] Coming from much bigger corporate environment I had the opportunity to build a new office and engineering teams from scratch. I interfaced with colleagues in the US and Ireland to get support and the company’s know-how. We hired the best software developers and QA engineers we could find and built a motivated high-performing team. I played not just the role of an engineering manager but also an office leader, a part-time HR and recruiter, interacting with recruitment agencies, vendors, universities and government agencies. [Results] Initially the team started small but eventually took on more and more work and responsibilities. Today majority of company’s key and most revenue generating products are built in the Czech Republic by a team of several hundred engineers. [Why it is notable] This project allowed me to build something new. It gave me the opportunity to improve my interviewing and people management skills and it gave me a chance to contribute significantly to the future success of the company creating career opportunities for hundreds of people.”
So what would your story be if you were a developer? I will use one from my previous life when I was still a geeky software developer.
“[What happened] In 2003 I joined a small US-based start-up that was a pioneer in building games for mobile phones. I was the only C/C++ developer with the mission to port some of the existing games to Palm OS and write new ones for an emerging technology – smartphones with Symbian OS. [How it happened] Having no previous experience with embedded systems and mobile devices I had to re-learn several programming languages (Symbian OS run a particularly nasty version of C++), I acted as the designer, architect, developer and tester and even created my own graphics. [Results] I built several games that showcased what can be done with modern technology utilizing smartphones, Bluetooth connections, and wireless data transfer in times when few other people have done so. Ultimately the start-up failed not getting investment it needed to operate. [Why it is notable] During this time I became one of the most experienced software developers building applications on Symbian OS platform. This fact would eventually lead me to become one of the key contributors to Symbian OS communities run by several large mobile phone vendors like Nokia and Siemens allowing me to share my knowledge and help others be successful.”
Words, stories and even short mission statements have a powerful spell. The way we talk to ourselves determines how are brains are being wired. When you come up with a story that focuses on your strengths, using positive language, and sprinkle some successes with a bit of vision of who you want to be chances are that you will eventually get there. As you probably noted from my two stories the mission of my professional life has obviously shifted as I moved from being an engineer to being a manager. Don’t be afraid to be flexible and change your mission as you grow both professionally and as a human being, but be very careful not to mix the mission with a short-term promotion or monetary rewards. Ultimately your mission need to give you the intrinsic motivation that no external stimuli can do.
So what will you tell your friends next time they ask you what you do? And what will you tell yourself tomorrow morning when your sleepy self asks you why you should get out of the bed and to the office? And remember, your work does have a meaning, you just need to take the initiative and put it to words!
Do you have a mission of your professional life? What is it? Do you believe that having a meaning at your work is important?
Originally published at LinkedIn.
