I thought, "What a great blog!", after reading Graham’s piece on management. It brought to mind Colin’s Powel’s (CP) lessons on leadership which I’m reproducing here as extracts in a two part blog. Part I appeared on Tuesday. Here is Part II of this series.
All of them apply to IT Managers. I have added a few words of interpretation to each as I see them.
Stephen Ibaraki, FCIPS, I.S.P.
CP 10: "Never let your ego get so close to your position that when your position goes, your ego goes with it."
You and the value and resources you represent are not defined by your role. Look to continually grow your skill sets, and the differentiation and value that you provide. Over time, this builds your value and it’s not role dependent.
I have blogged about this in:
Career Tip: Change or Stagnate! – Personal SWOT Analysis for Career Growth
Moreover look towards your next position and moving forward. Develop your team to take over your current duties.
CP 11: "Fit no stereotypes. Don’t chase the latest management fads. The situation dictates which approach best accomplishes the team’s mission."
In talking with many senior executives, I find they follow a series of core or basic principles and then keep to them. They add to this core due to insights they develop over time however they don’t make a wholesale shift in their core views. They also are agile in their ability to assess threat and opportunities and to react quickly which is essential to survival and growth today. If you get a chance, look at some of the writings/views of Warren Buffet.
CP 12: "Perpetual optimism is a force multiplier."
If the nearly 300 interviews I have conducted since 2001 with the top authorities in business and technology, this is one common attribute--continual optimism including under the most serious challenges. As a manager, motivation is driven by taking a forward looking view of enablement and success for your team. And encourage an entrepreneurial risk taking approach or continual innovation, even incrementally.
CP 13: "Powell’s Rules for Picking People." "Look for intelligence and judgment, and most critically, a capacity to anticipate, to see around corners. Also look for loyalty, integrity, a high energy drive, a balanced ego, and a drive to get things done."
I find that attitude and approach are the best predictors of future success for picking your team and those you want to engage with on a long-term basis.
The rules say it all!
CP 14: "Great leaders are almost always great simplifiers, who can cut through argument, debate, and doubt, to offer a solution everybody can understand."
There are various indices for writing where the writing level is measured. One example is the FOG Index. The key is to simplify and it’s a rule for general publication writing too.
These principles apply to any kind of communication. If you can’t communicate your ideas simply, no matter how great they are, you will lose your effectiveness and this will delay your career.
One side note: It is always good to contribute to a discussion through new research, experience examples, and summarizing existing arguments. Simple agreement and non-agreement is not enough. I call this dynamic learning. You will notice that Graham Jones in his blogs and comments is always looking to add value. The famed, Gary Kawasaki, talks about this too.
CP 15: Part I: "Use the formula P=40 to 70, in which P stands for the probability of success and then numbers indicate the percentage of information acquired."
Part II: "Once the information is in the 40 to 70 range, go with your gut."
This is the most common challenge I encounter with ICT professionals. It is easy to get into ‘preparation paralysis’ where you put something off since you are not 100% ready. I use a mountain analogy sometimes to describe what I mean. Imagine it’s dark and you have to get to the mountain top. You can’t see the entire path but you can make out the next 50 meters which is the extent of your flashlight. So go the 50 meters and you will see the next 50 along the path to the top. You will get there if you are patient and keep trying!
CP 16: "The commander in the field is always right and the rear echelon is wrong, unless proved otherwise."
One of early lessons I learned is that you need to reach out to your team and listen to their views. They are on the front lines and can give you a perspective from actually being involved directly and on a day-to-day basis with your products, services, and with customers/clients. I have seen companies fail when this continual interaction and communication is not occurring with the team—the front lines. I recommend this approach no matter what level of management you reach. As a board director, I found it of great value to talk with developers and project managers. You get insights that you can not get any where else.
CP 17: "Have fun in your command. Don’t always run at breakneck pace. Take leave when you’ve earned it: Spend time with your families. Corollary: surround yourself with people who take their work seriously, but not themselves, those who work hard and play hard."
This blog from Barnaby speaks to this
CP 18: "Command is lonely."
Ultimately it’s your responsibility and this entails making the hard decisions. However it always helps to be an inclusive as possible and to have transparency in dealing with associates. Be up front but also solicit valued input.
"Leadership is the art of accomplishing more than the science of management says is possible."