The document discusses leadership in IT service management. It emphasizes that leaders inspire people through passion and motivation, while managers focus more on organization and control tactics. Successful ITSM requires leadership to empower people and create an environment where teams are willing to change and take risks to continuously improve processes and technology. True leaders leverage people's strengths rather than just administering processes.
Lead success, don’t manage failure! The virtues of successful executives are those that express confidence, trust, stability and leadership. These virtues are not things that come with an executive title but more importantly are gained by the job they actually perform and honest relationships they foster. We see today, television shows that go to the extreme of inserting the most senior individuals undercover amongst the rank and file of their organizations to once again capture the pulse of the business which they have lost. A pulse that once gone, could be the catalyst that leads to the demise of a great organization. Embarking on the Service Management path requires executives to be fully committed to the cultural transformation they are asking of their organization. They must be active participants in that journey much like the captain of ship in rough waters. They cannot be bystanders mailing in instructions from afar on how to avoid the turbulent waters, an approach that will surely run the ship aground. In our session, we will discuss some challenges that organizations encounter when implementing a Service Management strategy while identifying tell tale signs of where a program might be going astray. We will talk about how crafting the delicate balance between People, Process and Technology can be the difference between success and failure. Lastly, we will review some tactics that will help to avoid making classic and typically fatal program mistakes. The session will prove to be valuable only with the audience’s participation and viewpoints so everyone is asked to think of the characteristics that have been successful and unsuccessful in the past so that they can engage in the discussion with their peers.
Last Update: 8/28/2012
MetLife – IT Planning in PMO for $3.4B IPO Two previous companies One generated ~$3M in annual revenue in 2 nd year Value based: Not looking to take over. Just educate and move on.
When presented with a new challenge by your superior… When you see opportunity to take the initiative on something for your superior…. Do you take into account whether they are a Leader you follow or a Manager you work for?
More characteristics like Creativity. Words are NOT specific to any one person on slide
Management focuses on work. Leadership focuses on people.
Management focuses on work. Leadership focuses on people.
We need both. But are you performing the role your organization needs you to?
Management focuses on work Assigns blame Takes Credit “ I” kept it on-time / on-budget Leadership focuses on people Takes blame Gives Credit “ They” delivered on-time / on-budget
Are your subordinates following your direction OR executing your orders?
Management is the foundation on which everything is built
Leadership sets the direction… It’s an Arrow pointing in the direction you need to go
You need the Pillars sitting on a solid foundation with a clear direction of where to head
Think about those images of rockets on TV toppling over and exploding TOO MUCH thrust from underneath
When leadership undermines the foundation, it’s like trying to push a rope You have no idea which direction it’s going to head in
Culture and cultural transformation is embedded in ALL aspects of an ITSM adoption
Leaders Within > Unfound leaders at all levels waiting for the opportunity > Challenge, sense of worth, learning, personal dev., autonomy, pay, praise, promotion opportunity (Money and promotion usually rank low when all things are considered ) > Make sure they know you have their back. Will stand with them and not throw them under the bus Environment of Success > Do people feel they have a chance of actually doing their best or will the culture prevent it? > They need to feel they have opp to learn from mistakes. Encourage them to share what they learn > People must feel they’re important to the success. Reward them with greater challenges (that they want)
We need both to succeed If you “manage” to often, you may no long be viewed as a leader If you need to, manage in private to protect your “leadership” image
Born in 1906 Graduated 1928 from Vassar College with Mathematics Degree ( Women gained right to vote in 1920 ) Master and Doctorate from Yale University. PhD in 1934 ( 1862 – 1934, only 1,279 PHDs had ever been awarded ) Voluntarily joined WAVES (Women Accepted for Volunteer Emergency Service, a part of the U.S. Naval Reserve) in 1943 Commissioned a Lieutenant (Junior Grade) 1944 and assigned to the Bureau of Ships Computation team at Harvard to work on Mark I Computer 1945 – Age of 40 - WWII ends and she has to leave active duty because of age but remained in reserves 1945 - Continued working at Harvard on Mark Computer series One day a computer failure had Hopper and her team baffled. Finally they opened the machine -- a moth had gotten inside! Hopper taped the offending creature into her log book and noted beside it, "first actual bug found." She is credited with the terms "bug" and "debug" for computer errors and how to fix them. 1949 – Joins J. Presper Eckert and John Mauchly and helps develop Univac, a computer that recorded information on high-speed magnetic tape versus punch cards 1966 - Retires as Commander from Naval Reserve 1967 - Recalled to active duty and assigned to the Chief of Naval Operations' staff as Director, Navy Programming Languages Group 1969 - She was voted "Man of the Year" by the Data Processing Management Association 1973 - Promoted to Captain, Commodore in 1983 and Rear Admiral in 1985 1992 - Passed away at 85 while still serving as a senior consultant to Digital Equipment Corporation 1997 - The USS Hopper is commissioned and named in her honor. 1953 – Invents Compiler ( translates English instructions to Machine instructions ) She did this, she said, because she was “lazy” and hoped that “the programmer may return to being a mathematician.” Her work on compilers and on making machines understand ordinary language instructions led ultimately to the development of the business language COBOL. http://www.pbs.org/wgbh/aso/databank/entries/btmurr.html If she was NOT a Leader, could she has succeeded as she did in a time that women were still NOT very well regarded in business and military?