Skip to main content

Be Your Own CEO of the Decade

Steve Jobs was deemed to be the CEO of the Decade by Fortune Magazine. As they put it, he not only revolutionized one industry, but he revolutionized four industries. And he did it when there were already other established leaders in each, unlike his compatriots Josiah Wedgwood (chinamaker), John D. Rockefeller (oil), Andrew Carnegie (steel), Henry Ford (automobiles) and Estée Lauder (make-up).

After reading the 31 page exposé about him, one thought struck me like a wall of bricks crashing down: how do I ensure that I am more than a footnote in history? Will I ever leave a lasting impression on something more than just a gravestone?

The only effect I seem to be leaving right at this moment is the effect that I'm not as good a planner as I thought I was. I intended on writing about a few things I read in Entrepreneur, but due to the fact that we are moving from Long Island, New York to New Jersey on Wednesday I mistakenly packed the issue in question away and don't remember in which box it went. This is an unfortunately good illustration of something else I read in the same issue of Fortune: "good execution beats a bad idea."

The author, Wilbur Ross (CEO of W.L. Ross & Co.), described his experience buying mediocre performing steel companies and then combining them to form International Steel and the steps he took to turn them around so that the combined strength was greater than the sum of the parts. In effect, the great execution of his acquisition plans more than compensated for the fact that the companies he purchased where not in the best financial health.

The opposite effect can be seen in my predicament for this week. I know I write a blog entry every week; I knew when I read that issue of Entrepreneur that I wanted to use it for this week's entry; yet I not only neglected to leave it on the coffee table, but I also packed it away in a box that is in a community of 7 stacks of boxes (piled 5 high) making it virtually impossible to find.

Translating this to the original question ("how do I leave a mark on the world [of business]?"), one should realize that any idea is better than no idea. After all, the quality of the idea will not amount to a hill of beans in the long run. Instead, it is the forethought that you put into the execution plan and its eventual execution that will really separate you from the rest of the pack.

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