Skip to main content

Me! Me! Look at me!

"Me! Me! Look at me!" How many times has this been you at work? Never? I'm not surprised. Few people like to call attention to themselves at their place of employment; this is doubly so during times of economic turmoil where the job market is tough. Yet this is exactly the time to call attention to yourself.

Let's face it: anonymity gets you nowhere. Even were the economy booming and the job market rife with new opportunities like a newly sodded, fertile garden, it is the early bird that gets the worm; the squeaky wheel that gets the oil; the ambitious professional that gets the raise or the promotion.

Before continuing, the obvious should be noted: there is such a thing as good attention and bad attention. This isn't Hollywood where any media presence is good for your career. In fact, bad attention can be disastrous for you in certain situations.

So how do you stay on the radar of those around you that have the ability to influence your professional career? Here are a few thoughts culled from my years of professional experience.

Do be an entrepreneur. I'm not suggesting for a moment that you should quit your job and open up that coffee shop in the empty corner store that you've been eyeing for years. What I am suggesting is that you keep your eyes open. If you see something that needs to be done; you have the ability to do it successfully; and it is something that has a quantifiable amount of value to your department, division or company then do it as long as it doesn't affect your ability to fulfill your normal, day to day responsibilities. (I stress the word "quantifiable" so that you can use it to justify your next raise. See my blog entry Everyone is in Sales for more on this topic.)

Do ask for additional responsibility. Whenever I think of this, I involuntarily cringe at the vision of working until 10pm or later every night, akin to first year law students who burn the midnight oil or get dropped from the program. This isn't so. In fact, if you find that you are playing Flow, Ikariam, or other games during the day then you probably already have the time to do something extra to highlight yourself in the eyes of your boss.

Don't point out problems. Simply highlighting a deficiency in the work environment does nothing but make you look like a complainer. However, if you have a possible solution in mind then be sure to bring up both parts of this equation to the appropriate individual. Be prepared, however, for them to think they have a better solution and to assign the task of implementing their solution to you.

Don't assume that these thoughts are an elixir for your career. It is critically important that you realize that every situation is different. As such, any advice you receive should be viewed in the light that it may be spot-on, may need some adaptation, or may not work in your specific situation. Caveat emptor to be sure, but if you have the motivation then maybe some of these ideas will help you get ahead in your current job and in your career

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