CA Community






This Blog

August 2011 - Posts

Innovation - How to Make this Buzz Word a Reality in your IT Organization

Published: August 31 2011, 02:16 PM | 2 Comment(s)
by Rich Graves

Thanks to fast moving technology companies like Apple and Google the IT world is now obsessed with innovation. Not to say innovation has been unimportant in the past, but it's now a close second in the techie buzz word dictionary only to "cloud." However, it's hard to say "innovate" without giving employees at least the right environment to do so. After doing some reading on the topic I thought I would share my thoughts on ways to get your IT organization to at least start sharing ideas that could form a good foundation for innovation.

First I highly recommend watching Steven Johnson's amazing TED talk on innovation titled "Where good ideas come from." He tells a humorous and thought provoking story on how ideas can connect, mature and eventually flourish. If you find the talk interesting then go out and buy his book of the same name (or you can watch this 4 minute video overview of the book). The book covers in much greater detail what types of environments help foster innovation.

Openness serves ideas better than walls - This is often a tough one in traditional IT departments. There is a strong belief that the thoughts and ideas in your head (tacit knowledge) are your intellectual property and by keeping it to yourself you stand to gain more by sharing it. This is the classic job protectionist line of thinking. But when it comes to innovation it just doesn't have the same rate of success as sharing ideas and being open. A team that openly shares their ideas is a team that will be more successful. Ultimately ideas that work are often ones that connectd with other ideas.

Ideas are hungry for other ideas - As said above many individuals' ideas aren't fully formed and they need to connect and be discussed to become a reality. Johnson likes to use the coffee house as an environment that generates informal discussion. It's a comfortable environment where people can talk freely and allow their thoughts to connect and form new ideas. Try to create an environment during team meetings that promotes free form discussion where you don't have the formal organizational structures (i.e. judgment and hierarchy). This could be literally going to a coffee house, a team lunch outside the office or a walk around the office park.

Follow the improv rule of "yes and" - If you know anything about improvisational comedy then you are well aware of the most important rule "yes and". Meaning you don't disagree with your fellow actor but rather agree and add onto that thought and push the scene/plot further. This is a great rule to follow in a team meeting by taking a suggestion or idea and pushing it further. It also promotes openness.

Put all your junk on the table - In Johnson's book he talks about the movie Apollo 13 and how the team on the ground that is trying to save the astronauts puts all their spare parts on a table and are told "figure it out." Put all your components, systems and processes on the conference room table (virtually that is) and think about where they either work well together today or are disconnected. What are the biggest problems for the business or IT right now? Can these parts be put together in a different way to solve it? Do we need all these parts?

Are there leftovers? Can we make a soup? - My grandmother could always make a great soup out of last night's leftovers and available items in the kitchen. Like soup, some of the most amazing innovations have come from what many see as junk or waste from an existing product or process. From an IT perspective what waste or noise do your applications or processes generate that could be used in other processes or applications? Is there gold stored in those log files or data exports that we could use if we mine it?

Innovation in IT is often about automation - The low hanging fruit for innovation in an IT organization is usually automation. It could be automating a manual process, or even getting rid of an expensive or unnecessary process. Don't feel that innovation can only be achieved by buying a new piece of technology. Instead look at ways to get rid of technology that isn't adding value or could be slowing your team down.

Share this post:  

 

By: Rich Graves
Rich Graves is a Senior Principal Product Manager at CA Technologies. Rich works on a team focused on strategy and innovation for the Service & Portfolio Management Customer Solutions Unit. During his eleven-plus years at CA, he has focused entirely on the Service Management and support market segments...
Read More..

Are 10,000 Incident Categories too Many? Four Simple Rules for Managing your Categories

Published: August 29 2011, 04:29 PM | 7 Comment(s)
by Rich Graves

Hopefully your answer to the above question is a resounding YES. If not then I'm not sure this blog can help you but maybe an episode of "Hoarders" can.

I have worked with many IT support organizations through the years and the quantity of categories in a classification structure is often a hot topic. However, recently I met with one organization that had more than 10,000 categories. And if that's not bad enough the categorization list was growing at a rate of one new category per a day. When I asked how analysts filtered through the list to find the category they wanted to use the response I got was Dilbert-worthy - "whatever category they used last." My favorite follow up question is one that I can guess the right answer to with almost 99% accuracy: "What category do end users choose most frequently in the self-service interface?" (drum roll) "Other" is the most often cited response. Let's step back and think about it. The organization has more than 10,000 categories but only a handful are being used. I'm sure the structure frustrates both IT users and end users and ultimately slows down the incident management process.

Although there is no simple answer to how many Incident categories are right for your organization, there are four simple rules you should always consider:

  1. NO, NO, maybe- Make them ask three times - When someone suggests that we should add a new category, no matter how good of a suggestion it is or who it comes from in the organization, always say no. If they come back and ask again say no again. But if they come back a third time then sit down and discuss it. Everyone can have an idea for a new category off the top of their head but the overwhelming majority of the time it's for an odd case and not something that the organization needs long term. By not responding to each random idea you are ensuring that it is a category that is really required before anyone spends any time thinking about how to implement it best.
  2. If you aren't reporting on it you don't need it - This is a great way to either avoid creating new categories or clean up the existing list. If the organization isn't demanding a report on that specific category and the key metrics for it (i.e. MTTR), then you don't need it.
  3. If you haven't used it in the last six months, you never will - Like my mother always said when we did spring cleaning, "if you haven't worn it in the last year you won't wear it again." From a categorization perspective I would use the rule of six months. Just like spring cleaning there are some exceptions (i.e. ski pants and bad island-themed shirts) that you may keep for emergency situations but otherwise get rid of them. Start by running a simple report on the number of Incidents created (or closed) in each category over the last 12 months. Twelve months is ideal for the first review as to not scare away any IT pack rats. With this report you can quickly see trends and pick out categories that are never used. After initial cleanup schedule a review of your categories every six months and clean away. Trust me it's even more liberating than cleaning out the attic or that old closet at home.
  4. Focus on your audience- Many IT organizations forget that categories should be focused on the end user and therefore should be in their language. Additionally end users don't want a massive list of categories to choose from, so focus on a small number of top level categories (10 to 20) and hopefully no more than 100 total exposed to the end user. Of course you can have more complex categories behind the scenes just for IT, but keep the front end simple. There are plenty of fields in the Service Desk that aren't exposed to end users where you can store complexity. For more thoughts about "knowing your audience" see one of my previous blog posts.

Think about your categorization structure (can be problem and change to) and ask yourself which ones are used most by analysts and end users? When was the last time we did a review and clean up? Trust me it's time to get cleaning.

Share this post:  

 

By: Rich Graves
Rich Graves is a Senior Principal Product Manager at CA Technologies. Rich works on a team focused on strategy and innovation for the Service & Portfolio Management Customer Solutions Unit. During his eleven-plus years at CA, he has focused entirely on the Service Management and support market segments...
Read More..

Are you being seduced by metrics?

Published: August 22 2011, 10:22 PM | no comments
by Robert Stroud

I recently hosted a panel at the itSMF Australian Conference on linking data and metrics to the business to show business value. The standing room only crowd asked questions for the whole hour including: "how do I get metrics from the cloud?" or "how do we not become data junkies?" and "how do I show metrics that relate to the business?" There also was the noteworthy comment of "metric reports are not worth the trees that they kill."

One of the challenges of being the moderator is that you don't get to answer the questions in the session, so I will take this opportunity to give offer my own view to the key questions asked in the session.

Cloud - How do I show metrics?

Great question and one that I hear constantly as folks look to leverage the cloud.  Many of you already leverage some aspect of the cloud whether it is SaaS, PaaS, IaaS or any of "as a service," and if you check with the provider you will note that there are many metrics provided. The reality of these metrics is most of them are irrelevant to the information you need to verify the health of the business service being delivered. When using cloud, we need to a better job to identify and document the metrics required and incorporate them into contracts.

What do we do with the plethora of metrics that we are currently exposed to?

Throw them away! We need to identify the metrics that make sense to aggregate and expose to the business in business terms and use the remainder as support.

How do I show metrics that link to the business?

Visit the ISACA website and download COBIT 4.1 (freely available), Appendix 1 and 2 will lead you through the development of a balanced scorecard. The scorecard can link to the IT processes. and ultimately to a series of metrics which should have some connection to the business. It's a great starting point!

Consistency will be king moving forward!

There were many other questions and comments during the session with the comment of the session being how we can ensure consistency of service. The analogy given was that if your bus arrives 10 minutes early or late you can adjust your behavior to ensure that you can make the bus - but if it is 10 minutes late one day and 10 minutes early the next, the variance is totally frustrating. This is typical of IT where we are rarely consistent. This is where we should be using our technical metrics to assist in understanding the consistency of our business delivery. Once we get consistent, we have a platform from which to drive forward.

 

Share this post:  

 

By: Robert Stroud
Robert Stroud serves as VP and as Service Management, Cloud Computing and Governance Evangelist at CA Technologies. Robert also serves as an International vice president of ISACA, is part of the Framework committee and was the former chair of the COBIT Steering Committee. Robert also serves on the itSMF...
Read More..

Effective, Efficient and JUST ENOUGH Service Management!

Published: August 18 2011, 12:15 PM | no comments
by Robert Stroud

I ran into a former colleague at the itSMF Australian conference and he shared with me the challenges that his "ITIL" program was having. There were complaints that it was taking too long to promote change to production, that there was too much paperwork (electronic of course) and the fact that "problems" were associated with servers rather than business services were causing major concerns.

Recently he had discovered that the implementation of virtualization had led to developers having access to production systems and they were avoiding operations totally. The first that Operations knew was when there was a major failure and the problem team identified all the components involved.

 ITIL was designed to put effective process in place, and the interesting challenge is that some practitioners are focused on the process and not the objective - that the business service being efficient, effective and delivering customer delight.

At the itSMF event I spoke on "Efficient, effective and 'just enough' Service Management to deliver business value!"  This speech has been given globally and is designed with the purpose of ensuring that the Service Management program of work is not "process for process sake."  Rather implementation of Service Management is about reducing the cost, decreasing the time and increasing the satisfaction of the business in delivering IT enabled business services. To do so, the ITSM program of work must be:

  • An ordered and finite project with a defined beginning and end
  • Returning more resources than it consumes to fuel the execution
  • Sustainable with the processes staying in place after the completion of the program of work!
  • Deliver factual reporting and attestation to support and drives data driven decisions!

But what about those great metrics that you are currently reporting, server performance, storage capacity and so, those "IT" metrics that are not about business value, throw them away! It's time to deliver metrics to the business that drive value and are about the business and in business terms!

Often I use the example of driving my car. It delivers many metrics, but what is important is that I get to my destination at the appropriate time, driving the most effective route and the cost are within the realm of expectation. Metrics, such as my tire pressure, oil temperature and so on, are important to ensuring the car is operating effectively and if one of them is going to impact my journey, then it will inform me if I should turn the engine off and call a taxi.

In short, ITIL, ITSM, MOF are good tools, but when you are more focused on the framework than the business, you are lost and its time to get out the compass and reset!

Share this post:  

 

By: Robert Stroud
Robert Stroud serves as VP and as Service Management, Cloud Computing and Governance Evangelist at CA Technologies. Robert also serves as an International vice president of ISACA, is part of the Framework committee and was the former chair of the COBIT Steering Committee. Robert also serves on the itSMF...
Read More..

Changing role of IT!

Published: August 17 2011, 09:55 AM | no comments
by Robert Stroud

Demand on IT is increasing while at the same time the funding for IT is flat and the time to value is shrinking. This is not dissimilar to the changes we saw in manufacturing in the past where manufacturers have moved from cranking out huge inventories to "just in time' production to meet demand. The role of IT is transitioning to managing the business value of IT and toward providing transparency into the business.

To meet this transition, the IT organization must fundamentally change. Instead of having armies of developers and operations staff the organization will facilitate the just-in-time delivery of IT enabled business service with a team who convert business requirements into technology capability delivery within their extended partner network. This team will incorporate the coordination of suppliers, internal capabilities, cloud, and outsourcers and so on. This will mandate a series of new skills within IT to deliver these roles including financial, negotiation, communication and supplier management. 

Activities undertaken will include:

  • What services does IT power the business to deliver
  • How do we manage and demonstrate financial transparency
  • Determining demand, resources and portfolio prioritization
  • Ensuring compliance with metrics such as licenses, legal matters and third party agreements
  • Effectively managing risk, not simply mitigating
  • Ensuring the quality of service being delivered to the business in line with their agreed expectations
  • Managing the financial expectations including budgeting, accounting, cost allocation and chargeback
  • Performance management, measurement and benchmarking

In short, IT will need to know their costs, align to performance expectations and manage the total demand to ensure work is prioritized with agreement across the organization and priorities given based on business value.

As I have learned in 30 years in the business, the one constant is change and we are approaching a time of structural and cultural change in IT, are you ready?

Share this post:  

 

By: Robert Stroud
Robert Stroud serves as VP and as Service Management, Cloud Computing and Governance Evangelist at CA Technologies. Robert also serves as an International vice president of ISACA, is part of the Framework committee and was the former chair of the COBIT Steering Committee. Robert also serves on the itSMF...
Read More..

More Posts Next page »