Skip to main content

The Reign of Mayer

This is a short entry, written simply because I feel a need to document this beyond the 140 character limit on Twitter.

Marissa Mayer is great at being a reactionary leader.  She's stirred things up a bit, to be sure, but the vast majority of her work has revolved around correcting problems at Yahoo.  I am fairly certain you'll arrive at a similar conclusion after reading the very detailed and in depth history about her that was published by Business Insider a few weeks ago. 

Immediately after reading that, however, I wanted to author this but it slipped through the cracks.  This may have been to my benefit, though, given the brouhaha that has sprung up over the choice of a new company logo. Let's face it, folks:  this is a logo consisting of a five letter word followed by an exclamation point.  The most interesting thing about it is the color purple.  Why is so much attention being given to this when there isn't much difference between the proposed new logos and the existing logo?

The answer, described in the article, is that she's ultimately a researcher type.  She thrives on details, data, and the smallest minutiae.  I know the type well since I am the same type of thinker.  When I started my career at the awesome T. J. Watson Research Center I was encouraged to think outside the box but to be sure to always tie my work back to some business initiative, and that required approaching my work from every possible angle to ensure it was justified and had a high probability of generating revenue.  It's taken me a long time and a lot of effort to overcome this in order to allow me to view things from the perspective of having a longer timeline to acquire a return on whatever it is I am investing in.

So my question posed to my hypothetical audience of the Yahoo board is this:  why did you hire a COO when a CEO is needed?  I understand that Yahoo was in extraordinarily bad shape at the time and that good execution trumps a great plan, but sooner or later you will run out of things to correct and will have to demonstrate thought leadership if you want to regain the glory from days of old.  This is where I think your plan will fail, Yahoo.  With all due respect to what she's managed to accomplish in her relatively short tenure at the helm, the day is rapidly approaching when your shareholders are going to demand a greater ROE that is unattainable by correcting operational problems, and it'll be very evident on your Income Statement. 

Is this, perhaps, some conspiracy plot to correct things in the short term only to jettison her when a more strategic plan of action is ready to be started?  Who knows, but time will reveal the answer.

Thoughts?  Comments?

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