Skip to main content

Management 101

William Hammer, who is a good friend of mine as well as the founder of Vanderbilt Securities, once told me (paraphrased): "it's a Management 101 concept to stipulate a 'due date' whenever you need something to be done. Otherwise, there will be a lot of hemming and hawing, and you'll never get the information you need."

I couldn't agree with him more, but since he said this to me about 10 years ago I'll take it a step further: with the sheer number of hawkers vying for one's attention it's tough to stay focused. In fact, it's so tough that you cannot rely on someone to remember something they promised much less deliver it when you need it.

When I was a senior at Clemson University, I had already spent two, seven-month periods working as an intern at IBM's Application Systems Design Lab in Cary, NC. But I had set my sights on their T. J. Watson Research Center for my last seven-month stint before my graduation. My soon-to-be manager, Jerry Cuomo, wanted to fly me up for an interview but was unable to justify to his boss why they should do so since I was "just an intern."

In the end, he hired me for that internship. When asked for clarification, he said that it seemed that I would be a contributor and, more importantly, he liked my determination. (For the record, what he really was saying was that I was a pain in his ass during the decision process. But I digress...)

Determination can be annoying to others, but only when they don't properly appreciate the gravity of the situation. This was alluded to back in my first blog entry, Everyone is in Sales!, where I stated that the onus is on you to convince others of your cause. Beyond this, there is also the question of "what's in it for me?" or, put another way, "why should I help you?"

The point that I'm trying to make here is that your goals will rarely be unilaterally executed, i.e. you'll always need help from others. Those goals may be short term, tactical ones like liaising with another division in your company so that you can answer a customer's question; or they may be strategic ones like finding a new job that moves you along the career path that you've envisioned for yourself. To make these goals reality, then, it is important to remember the following things (summarized from above):

Sell your need. Properly convince others of the importance by ensuring they realize the benefits they'll receive from their efforts. It may be altruistic, i.e. "the company benefits" (vs. them benefiting personally), but that's okay too.

Set deadlines. Part of the "sales" aspect is explaining the due date for the action (unless the importance of the item in question is extremely low) and why that due date needs to be adhered to. This avoids the instance where someone will abdicate themselves from the responsibility of doing their part because "you didn't tell me you needed it yesterday!"

Be determined. I'm not condoning riding someone like a horse until they finish their part in the task, but you should definitely take an active interest in their progress. Be compassionate, though - they have other things that are demanding their attention.

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