We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byKristina Westby
Modified over 2 years ago
CIO First 90 Days The First 90 Days for New Chief Information Officers and Chief Technology Officers. † © 2008 Benjamin Lichtenwalner
About This PresentationPlease Read About This Presentation This presentation is provided as a draft example of one way in which you may choose to present similar information. The data contained herein is generic and not representative of any particular organization. If you wish to use a similar format or content, feel free, but please drop me a note (via ) so I know the example was useful. Thank you, - Benjamin Lichtenwalner † © 2008 Benjamin Lichtenwalner
Outline Introduction Background Overview Three P’s People ProductsProcess TimeLine First 30 Mid 30 Last 30 Summary † © 2008 Benjamin Lichtenwalner
Introduction Education Experience Positions Held Why First 90?A quick background on who this guy Benjamin Lichtenwalner (Lick-ten-wäl-nur) is and why he is interested in the first days for CIOs… Education Penn State University BS Management Science & Information Systems Lehigh University MBA Concentrated in Corporate Entrepreneurship Experience Fortune 500 (E-Business Division Start-up); Inc. 500 (ERP Supporting Highest Growth Phase); NPO (Scaled Technology for 50% Growth 12 months). Positions Held Support Analyst, Software Developer Roles, Technical Lead (Software design / architecture), Project Manager Roles, Vice President of Technology (CIO responsibilities). Why First 90? Seen it done right, seen it done wrong Did it right myself, did it wrong myself Lots of great books (recommended), but often not read Been through the pain, trying to spare others † © 2008 Benjamin Lichtenwalner
Introduction: BackgroundWhy the first 90 Days? Organization is waiting for your impact Change is often needed quickly Prioritization is critical So much to do… Will it vary by organization? Absolutely Just one example here Risks of unstructured plan? Poor prioritization Miscommunication Lack of organizational confidence Wasted Resources Ineffective lieutenants Unhappy technology staff Bottom line performance Your job … † © 2008 Benjamin Lichtenwalner
Introduction: OverviewFor simplicity and recollection, a framework of People, Products and Processes are addressed over 3 stages of 90 days. Three P’s People: For each stage, the people you speak with and what you focus on in those conversation should vary. Products: For the purposes of this brief presentation, products refers to anything that may be considered a deliverable of your IT department: applications, infrastructure, policies, support and so on. Yes, it is a big category. Processes: You wouldn’t be where you are today without realizing the importance of process. However, there are different degrees of attention that you should pay to process in your first 90 days. 90 Days First 30: Emphasizes high level conversations and getting to know the new organization or role. Middle 30: Digging into details. Last 30: Established what needs to be done, began the communication and building relationships. † © 2008 Benjamin Lichtenwalner
People, Products & Processes“The Three Ps” People, Products & Processes † © 2008 Benjamin Lichtenwalner
Three P’s: People Levels of Organization Technology Staff Other PeopleMost organizations large enough to support a CIO/CTO have at least 3 categories of staff: Executives, Lieutenants and Individual Contributors Executives CEO CxOs Vice Presidents (SVPs) Lieutenants Directors Managers Line of Business (LOB) Leaders Individual Contributors Technology Staff At least top 2 across As many as possible, according to size Other People Vendors / Partners Consultants / Contractors Competitors / Similar Organizations Regulators † © 2008 Benjamin Lichtenwalner
Three P’s: Products At the highest level, the key areas of Products to focus on include Infrastructure, Applications and Services Infrastructure Workstations Servers Telecommunications Applications Desktop Communication ( , Chat, CRM, Telephony…) Back Office (Accounting, Finance, Inventory, HR…) Data Stores (DBs, Intranet, Knowledge Management…) LOB Solutions (Engineering, Sales, Content Delivery…) Services Project Management Application Delivery Support / Maintenance Outsourcing Policies † © 2008 Benjamin Lichtenwalner
Three P’s: Processes There are many processes to understand in your first 90 days. Many may be just unstructured communications – but they are still processes to understand. Key here is knowing who to contact, when and how, both within IT and across the organization. Budget Tracking / Forecasting Purchase Orders / Expense Project Intake (IT) Prioritization Change Management Strategic Planning (and CIO’s Role) Support Accountability IT Organization (Scorecards) Performance Management † © 2008 Benjamin Lichtenwalner
First 30, Middle 30 and Last 30 DaysTimeline First 30, Middle 30 and Last 30 Days † © 2008 Benjamin Lichtenwalner
Timeline: First 30 Days The first 30 days emphasizes high level conversations and getting to know the new organization and / or role. Therefore, the new CIO should focus on meeting with executives and technology staff, while understanding the most critical products and immediately necessary processes. Major Themes: Research individuals Carefully prepare questions Be a sponge: listen, listen, listen and absorb Document and structure feedback By the end of the first 30 days, you should start to have a feel for the organization. There should also be a sense of where the major pain points are and an idea of where you will begin to focus your energies in the first year. Consider implementing freezes: New projects New implementations Project Requests Technology Hiring † © 2008 Benjamin Lichtenwalner
Timeline: First 30 Days - PeopleExecutives Most senior executives (CxO, SVPs) What has worked well and what has not? What are the most urgent IT needs? What are the cyclical needs? Technology Staff Gather existing performance reviews & resumes At least top 2 across (as many as possible) Similar questions Which relationships are strong / weak (internal or external) Understand responsibilities of each Individual / Role / Task alignment exercise Identify key responsibilities by individual / team Security Backups Support Telecommunications Executives Meet with most senior executives What has worked well and what has not? What are the most urgent IT needs? Technology Staff Meet as many as possible - MAY WANT TO MIX LEVELS – MAY APPRECIATE YOUR INTEREST IN MEETIN Same questions as executives Role / Task alignment exercise - WHAT YOU ENJOY DOING Squeaky Wheels (Favorable or not) Learn about the problem projects and remember them – great examples of what to avoid and support your cases for change or following process / best practices when approached for things like: Shadow (rogue) IT Projects Disconnected solutions Decentralization of IT (if you are opposed) † © 2008 Benjamin Lichtenwalner
Timeline: First 30 Days - ProductsInfrastructure Network & Telecommunications Network overview Phone systems setup Servers & Hosting Number, types and ages of servers aligned by service Hosting / Co-Lo / SaaS providers overview Workstation Environment Numbers, models, ages Mobile Solutions (PDAs, EVDO) Applications Desktop services Communication Line of Business solutions Data Map overview Services Overview of all Focus: Support / Maintenance Focus: Project Management † © 2008 Benjamin Lichtenwalner
Timeline: First 30 Days - ProcessesBudget Overview Snapshot (Product too) Project Intake (IT) New requests (Forms, approval) Strategic Planning Technology Process Support Service Level Agreements (SLAs) Request Methods (Hotline, , chat, after hours) Accountability Budget Planning SLA Tracking Scorecard Tracking † © 2008 Benjamin Lichtenwalner
Timeline: Middle 30 Days The middle 30 days emphasizes continued conversations with organization leaders and getting to know more of the Technology team. There is an increased emphasis on the products at this point – learning what exists and why. Major Themes: Meeting as many people as possible Study the products in detail Document and structure feedback By the end of the middle 30 days, you should have a good idea for the state of the union at a high level. There will continue to be a number of surprises, but the first year action plan should be coming together. By the end of this period, you will want to feel confident in your grasp of the organizational priorities as you will begin to validate your planning with the organization in the final 30 days. Consider implementing freezes: New projects New implementations Project Requests Technology Hiring † © 2008 Benjamin Lichtenwalner
Timeline: Middle 30 Days - PeopleBusiness Lieutenants Directors, Managers Same questions as executives Technology Staff Any remaining, as possible Same questions, where applicable Smaller Consultants / Contractors Insights, feedback, plans Executives Meet with most senior executives What has worked well and what has not? What are the most urgent IT needs? Technology Staff Meet as many as possible - MAY WANT TO MIX LEVELS – MAY APPRECIATE YOUR INTEREST IN MEETIN Same questions as executives Role / Task alignment exercise - WHAT YOU ENJOY DOING Squeaky Wheels (Favorable or not) † © 2008 Benjamin Lichtenwalner
Timeline: Middle 30 Days - ProductsInfrastructure Network & Telecommunications Network specifics (vendors, WAN acceleration, traffic prioritization) Security specifics (perimeter, passwords, intrusion detection, last test) Servers & Hosting Aging servers retirement plans Capacity evaluation Workstation Environment Applications Line of Business solutions (details) Data Map (details) Back Office Suite Overview Services Details of all Focus: Application Delivery Focus: Outsourcing † © 2008 Benjamin Lichtenwalner
Timeline: Middle 30 Days - ProcessesBudget Tracking Purchase Orders / Expense Project Intake (IT) Prioritization Support SLAs – Internal Accountability (Who, What, Where, When, Why, How) IT Organization (Scorecards) Performance Management † © 2008 Benjamin Lichtenwalner
Timeline: Last 30 Days In the last 30 days you begin to establish recurring conversations as you leverage the knowledge you’ve gathered to begin planning. At this point you may also want to start reaching out to larger vendors and other external contacts, such as expanding your network. Major Themes: Recurring meetings Expanding network Validating plans with leadership By the end of the 90 days, you should have a solid understanding of the first year action plan. You will want to validate these plans with leadership across the organization and once validate begin execution. As you do so, you’ll want to start contacting larger external partners and begin thinking about your longer-term strategic plans. Consider implementing freezes: New projects New implementations Project Requests Technology Hiring † © 2008 Benjamin Lichtenwalner
Timeline: Last 30 Days - PeopleExecutives Establish recurring update / meeting schedule Technology Staff Initial meetings with all remaining, as possible Same questions, where applicable Major Vendors / Partners Leverage knowledge from previous conversations What has gone well, what has not Thoughts on pricing, contracts, future needs CIOs of Similar Organizations Depending upon competitive landscape Regulators Listen carefully Executives Meet with most senior executives What has worked well and what has not? What are the most urgent IT needs? Technology Staff Meet as many as possible - MAY WANT TO MIX LEVELS – MAY APPRECIATE YOUR INTEREST IN MEETIN Same questions as executives Role / Task alignment exercise - WHAT YOU ENJOY DOING Squeaky Wheels (Favorable or not) † © 2008 Benjamin Lichtenwalner
Timeline: Last 30 Days - ProductsInfrastructure Network & Telecommunications Telecommunication contracts review Servers & Hosting Hosting / Co-Lo / SaaS providers – contracts, performance tracking Capacity forecasting Workstation Environment Applications Standards (languages, vendors, disk capacity) Back Office Suite Details (Integration, capacity, forecasting) License audit / tracking Services Details of any remaining Capacity forecasts Policies † © 2008 Benjamin Lichtenwalner
Timeline: Last 30 Days - ProcessesBudget Gap Analysis Project Intake (IT) Pending Projects Strategic Planning (and CIO’s Role) Business Change Management Support SLAs – External Tracking Vendors ITIL / Best Practices Compliance † © 2008 Benjamin Lichtenwalner
Timeline: Summary † © 2008 Benjamin Lichtenwalner
Timeline: Effort AllocationsFirst 30 People – Heavy Products – Light Processes – Light Middle 30 People – Light Products – Heavy Processes – Light Last 30 People – Light Products – Light Processes – Heavy † © 2008 Benjamin Lichtenwalner
Timeline: After the 90 DaysClear Prioritizations Develop Year 1 Action Plan Validate Priorities with Business Communicate Priorities to IT Build Consensus Across IT Communicate to Business Begin Longer-term Strategic Planning † © 2008 Benjamin Lichtenwalner
Resources for CIOs NY CTO Club (Free) NPO CIO Council (Free)Other IT Networking Clubs Technology Executive Networking Group ($) Society of Information Management ($) Association of Information Technology Professionals ($) CIO Executive Roundtable (CIO Mag.) ($$) Gartner ($$$) Forrester ($$$) † © 2008 Benjamin Lichtenwalner
A few more thoughts Many “Ah-ha” and “Gotcha” moments will follow for a long time. Key is getting started on the right foot with a solid understanding across all major areas. Never eat lunch alone* and never forget to schedule your lunch meetings. Everything will be interpreted (sometimes too much), be sure you prioritize these steps and communicate in manner you want to relay. For example, are you a top-down leader, bottom-up, or do you develop teams that lead by consensus? Inform IT staff of some guideline to your plan, for example: Over the next 8 weeks: Series of meetings on IT Services First 4 weeks, getting a grasp of basics Next 4 weeks, digging into details Ask yourself: Who is your team – executive leadership technology staff? What is the culture of the organization? Entrepreneurial? Bureaucratic? After you have customized this example or another to your specific organization, know that it will all seem to go out the window the day you start. But remember, “plan your work and work your plan”. Come back to your plan often, regardless of how many obstacles arise. I myself often eat lunch alone. Key is making time (coffee “break”?) Obviously would like to cover everything here in first 30 days and may be able to in some organizations. Objective is to be realistic and in some organizations, you may not be able to cover all this at the same level of detail even in 90 days. † © 2008 Benjamin Lichtenwalner
THANK YOU and GOOD LUCK! † © 2008 Benjamin Lichtenwalner
Technology for High Growth Organizations Presented by Benjamin Lichtenwalner † © 2005.
Chapter 3 Project Initiation. The stages of a project Project concept Project proposal request Project proposal Project green light Project.
Chapter 3 Project Initiation
Optimizing IT Department Project Portfolio Management (Concurrency Corporation)
© Prentice Hall CHAPTER 15 Managing the IS Function.
Optimizing IT Department Project Portfolio Management
Practical IT Research that Drives Measurable Results Establish an Effective IT Steering Committee.
Info-Tech Research Group1 1 Info-Tech Research Group, Inc. is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
Transport Development and Solutions Alliance (TDSA) Technology Evolving Business Functions Scott Lawton – Chief Executive Officer 7 th of August 2015.
Slide 1 of 24 Week 1: Lecture Structure Title: Managing IT –Business importance of IT –Role of CIO –Review the IS Pyramid –Top Business IT Issues –Discuss.
7-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Chapter 7 IT Infrastructures.
Army Directorate of Public Works Support Contractor of the Year Carlos Garcia Owner/CEO KIRA Maximizing Return on Investment in Business Development.
| 2012 Sheraton Dallas Hotel, Dallas, Texas | May 22-25, 2012 Are Good Proposal Managers Two Faced? Yes, and they have to be! Kristin Pennypacker, AM.APMP.
Governor’s Office for Technology Service Level Management Overview Office of Policy & Customer Relations September 21, 2001 Governor’s Office for Technology.
How to get the JOB of your CHOICE Department of Computer Science University of Karachi Engineer Humayun Qureshi March 16, 2006.
1 An Overview of Process and Procedures for Health IT Collaboration GSA Office of Citizen Services and Communications Intergovernmental Solutions Division.
Is it a struggle to keep on top of program or donor information? Are you wasting postage and effort mailing to your entire list rather than tailoring.
APRIL 18-23, 2012 PROJECT PLAN TO DEVELOP A LEARNING & DEVELOPMENT STRATEGIC PLAN FOR RETAIL EMPIRE, INC. Prepared by: Alice Monroe, Chief Learning Officer.
7-1 Chapter 7 IT Infrastructures Business-Driven Technology.
© 2017 SlidePlayer.com Inc. All rights reserved.