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

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