Skip to main content

Growth by acquisition

When Oracle announced in late April that it would buy Sun Microsystems it shocked more than a few people. Tom In, Managing Director and Portfolio Manager at Alkeon Capital Management, obviously had his own thoughts on the matter. Paraphrased, he recalled to me over lunch the other notable acquisitions that Oracle had made: Primavera, PeopleSoft, and BEA to name a few.

During our discussion, we noted several possible combinations of acquired assets that could be used depending on what their corporate strategy is. Oracle is hardly the first company to take this approach either. BMC, HP, CA, Microsoft and several others have been known to base their growth on the purchasing of other companies rather than grow organically. Why do this? Generally, their mindset in situations like this is that it's quicker to buy than build; if you purchase companies that are best in their respective fields you can fill holes in your corporate strategy much more quickly.

On a personal level, we all have goals we have set for ourselves. But instead of learning from corporate America, I have frequently found that people rarely give any consideration as to how they intend to reach those goals. I'm sure you all know where you want to be, but do you have any idea how you will get there?

In the game of 8-ball (pool), the prevailing philosophy is that you start from the end of the game and work backwards, i.e. determine what shot you need to make so that you can make the winning shot; then determine what shot you need to make to make the previously mentioned shot; etc. If you know where you want to be in 5, 10, 20 years, doesn't it behoove you to figure out how to position yourself to be there at that time and then work backwards?

As a specific example, suppose you envision yourself as the CEO of a company but you are "only" in IT at the moment. What "shots" do you need to make, i.e. what types of skills do you need to acquire, to move yourself into a position to actually grab the brass ring?

After you've answered that, you need to determine how you plan to acquire those skills. Will you go back to school and get your MBA? Take different types of jobs to get Business Development, Sales, Marketing, etc. experience? The choices are yours to make, but until you not only make those decisions but also execute them successfully you won't go anywhere quickly.

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