|

 

Emtecinc.biz

Crawl, Walk Run Approach to Building an IT Service Catalog Tips and techniques to build out your service catalog - in smart, easily digestible pieces. TABle of ConTenTS TABLE OF CONTENTS . 2 ExEcuTivE Summary . 3SErvicE PorTfolio vS. SErvicE caTalog . 5WhaT DiSTinguiShES ThE BEnEfiTS of a SErvicE caTalog . 6a ruSh To juDgEmEnT . 7a Painful craWl . 8collaBoraTivE craWling . 9STEPPing in ThE Wrong DirEcTion . 11Walking Tall . 12running on EmPTy . 13running To DaylighT . 14concluSion . 15BioS anD rESourcE linkS . 16aBouT uS . 17 exeCuTIve SummARy "People don't want drills . They want holes!" These wise words neatly summarize the value of service catalogs. in the best of possible worlds, an organization's service catalog is rolled out to their end-users (we prefer to call them "customers") in a "service-centric" manner as opposed to one that's "iT centric." is there any difference? We strongly feel there is, especially from the customer perspective.
When we meet with members of a tech-centric culture, we sense an "inside out" mentality. The iT department is viewed as a cost center, focused on optimizing assets. But they perform as silo-based operations. They concentrate internally on function, skills and/or platforms. yet, they don't necessarily incorporate customer needs in their planning and deployment.
at Emtec, we transform companies from "iT-centric" to "service-centric," and the optimal oversight of service catalogs contributes greatly to the transition. This model helps customers thrive via an "outside in" iT management philosophy. Service-centric organizations are very customer/process-friendly. They seek to align technology with strategic goals and daily functions to increase competitive advantage. one key distinguishing factor: unlike the iT-centric way, the service-centric iT department finds ways to meet or exceed expectations without customers shouldering the full burden of specific costs or risks . in a service centric approach it is about what my customer needs rather than an iT-centric focus of what applications, hardware…etc.
hence, service-centric iT divisions provide the "holes," not a drill.
here's another appropriate analogy: Think about how much the online shopping experience has reduced the quality of "dread" often encountered when buying a roomful of furniture. in the past, you'd visit the store and your feet would get sore just from walking the entire floor to find what you like.
if the store didn't ship products, then it was time to call that brother of yours who had the pickup truck, hoping you could borrow it.
Then came the actual moving of the furniture from the store to the home. aspirin for that aching back, anyone? The service-based quality of the online shopping model has changed all of this. you're buying what you seek: a dining-room table set. The purchase does not include the burden of visiting a store and moving the furniture. if the delivery person gets injured, you're not liable. The service provider assumes that risk. hence, you're getting your holes without buying the drill.
crawl, Walk run approach to Building an iT Service catalog - version 1.0 in reading this paper, you'll discover best practices to develop and present a service catalog that positions your iT department as service-centric, maximizing customer satisfaction levels. you will understand the differences between the service catalog and service portfolio – they're not the same, although many believe that they are.
as in prior Emtec papers, we'll frame this discussion within our "crawl, walk, run" approach, which enables an iT department to pursue other business objectives without major disruptions to day-to-day operations. The infrastructure Executive council (iEc) has found that 65 percent of service catalog efforts fail to meet objectives. This phased-in approach significantly increases your chance for success by helping you avoid many of the pitfalls in service catalog development. crawl, Walk run approach to Building an iT Service catalog - version 1.0 SeRvICe PoRTfolIo vS. SeRvICe CATAlog as indicated, you should not confuse a service catalog with a service portfolio. The service portfolio exists within the Service knowledge management System (SkmS), and contains the complete set of services managed by the provider. it consists of three main elements: the service pipeline, retired services and the service catalog.
Service Pipeline This refers to any services that are proposed or in-development.
Retired Services These are services for which the lifecycle has entered the completion stages.
The catalog describes all "live" iT services, meaning those available for deployment. There are two kinds of catalogs here – one outlining business services and the other specifying technical services. customers only have access to the former, to help them understand how the organization will be supported. your iT team, however, will also have access to the technical-service catalog, which details the applications that will carry out the business services.
The service catalog contains information about all live iT services, including those available even if not necessarily deployed. it includes information about deliverables, prices, contact points, ordering and request procedures. Which means, to the customer, ordering iT can be very much like our example of ordering furniture from an online retailer: your end-users would choose the services they need from what is available. The catalog also covers how security policies impact usage, and how to get support. it explains clearly in "everyday" language where to turn to if there's a problem with the service. crawl, Walk run approach to Building an iT Service catalog - version 1.0 WhAT DISTInguISheS The BenefITS of A SeRvICe CATAlog? What are the advantages to this? your service catalog helps you map expectations against capabilities, as well as streamline how services can be deployed. if developed wisely, the service catalog will avoid prospects of either over-delivering or under-providing. customers also appreciate the qualities of "routine" within the catalog experience, how they go to the same place every time for applications, and use the same passwords to acquire them. Their satisfaction levels elevate. They're less worried about how to get what they seek, and can concentrate on doing their jobs instead.
as for the organization? it prospers from reduced labor costs, as services are now conducted in a uniform, managed manner. There is less manual coordination involved and more automation. The iT department does not have to spend hours on the phone with customers because these customers are going right to the web. This is how the service catalog establishes credibility within the iT department. in fact, the iEc reports that 63 percent of cios with high-impact service catalogs say the catalogs create more productive conversations with partners about the value of an iT service provider.
crawl, Walk run approach to Building an iT Service catalog - version 1.0 A RuSh To JuDgmenT unfortunately, too many businesses never reach the point of having a high-impact service catalog. They rush forward, failing to define their service portfolio before launching a service catalog. according to gartner, 70 percent of iT organizations with a service portfolio project will develop the catalog as a customer-ordering mechanism before documenting their iT service portfolios.
clearly, these companies could use some advice about crawling before they walk or run. We've seen service catalogs that are clear results of a "do it now!" mindset, leading to poor design and services described in such a technical manner that customers can't make sense of it. or the catalog doesn't reinforce service management, by properly designating configuration items (cis) for the service to link to incident/change. They don't introduce a consistent service definition, with metrics and reusable service models.
in other words, they're "iT-centric" instead of "service-centric." The vast majority of these catalogs fail the first time for this very reason. if this is your experience, don't lose heart. it takes a while to make the transition from producing a catalog meant for "iT people" to one that best supports customers. crawl, Walk run approach to Building an iT Service catalog - version 1.0 ok, you're at the crawl stage now. you probably have services available but never formalized a list. now, you want to move forward from here. here are typical out-of-the-gate mistakes to be avoided: IT-Centric mentality it's understandably difficult for an iT team to evolve from a iT-centric to a service-centric one. members have spent their entire careers in iT and this "silo" mentality encourages a glut of tech-laden descriptions without any consideration for the business view. The document reads like a foreign language for intended customers, who abandon it. also, applications are interpreted as services. But applications are not services. not for the customer, at least. "Tracking packages," for example, is a business service. But many organizations list the application that enables the tracking aS the service. They focus on the tool before thinking about its capabilities and the value it provides the business.
The iT team wants a complete and thorough list before moving forward with the catalog. This isn't necessary. you can always add items to the list as you go forward. holding off for an indefinite period means that the information that customers need to do their jobs will remain unavailable for the long haul.
as opposed to stalling, managers take the opposite approach and rush the catalog into play. Without a service-management plan, a deployed catalog is doomed. focusing on the Tool you pursue a complete tool to manage the service catalog before you actually launch the catalog. This too is somewhat backwards-thinking. you shouldn't buy a tool until you really understand what the services are and why they perform a critical business function. Don't get us wrong, we love technology and we advise our clients to acquire some kind of automated-management tool for their catalog- but just not in the crawl stage.
crawl, Walk run approach to Building an iT Service catalog - version 1.0 CollABoRATIve CRAWlIng for the purposes of our "best practices" summarized in the crawl, walk, and run stage discussion, we consider each in terms of the "strategic," "tactical" and "operational" perspectives. These categories provide milestones and possible courses of action for an organization to move from one stage to another, avoiding pitfalls.
Strategic – Strategic Promotion The crawling stage is the time to begin shifting mentalities, to establish your service-management model as a pro-active communications tool to be part of your overall communication plan. People must understand through your promotional efforts that services now drive iT. This will clearly require additional work within iT. your iT team will have to keep doing things the "old" way while transitioning to the new way. help them understand the importance of the role they're playing within the larger context. make it clear that they are valued players in this effort – specialists who are very good at what they do. With this kind of purposeful orientation, it will be much easier to motivate your teams to put in the hard effort ahead of them.
Tactical – establish Baselines When the transition to that of a service organization is well underway take some time to examine and document current processes, especially Service request management and the Service Desk function. it's good to understand this at the "crawl" stage because in the future when you're introducing new, service-friendly features to customers like self-service portals – you'll have a good way to compare and track improvements. you will also know how your iT services are supported by your current process and therefore what to adjust when introducing new ones. appoint an iT services manager to oversee this transition, to play the role of iT a service-center ambassador. his role is to manage the end-to-end lifecycle of one or more services and to start and or maintain the relationship with the business representative. This manager should know the difference between corporate services that remain basically "functional" (like e-mail) and services that help achieve organizational strategies. The iT services manager oversees all iT efforts to business processes, collaborating with members of multiple departments to develop an agreed-upon summarization of valuable services. crawl, Walk run approach to Building an iT Service catalog - version 1.0 operational – Assemble Service list With the steps above already taken, a list of iT services can now be assembled. it's fine at this stage if these are the more "basic" corporate/infrastructure services. This is the time to agree upon what the fulfillment of a service request exactly is, in a way that makes sense to the customer. in a service-centric culture, a request is fulfilled when the customer's intended outcome is reached. in the iT-centric organization, it's fulfilled when an application is deployed. lastly, the service manager should define the service-request model and how service-requests will be fulfilled. is this done online? What happens when the request is first made? What mandatory steps will the help desk take in response? What are the required follow-up procedures after the request has been addressed? Which teams are involved? again, these models should have the customer/business perspective foremost in mind.
crawl, Walk run approach to Building an iT Service catalog - version 1.0 STePPIng In The WRong DIReCTIon you're now walking. you've introduced service-level management as a communications initiative. you have a list of services, and are about to define service capabilities. you can group them together in various service-line categories and you have started formalizing service descriptions. you may think you're doing everything right. But you still can encounter problems.
Reinforcement is lacking The iT staff still lacks awareness of how the technology support function links to business services. managers have communicated these concepts, but they take time to sink in at a cultural game-changing level. The message hasn't gotten drilled in enough. it's not being reinforced in hallway conversations, workshops or department-wide email updates. This means certain staff members take on roles as agents of resistance instead of catalysts for change. iT Service teams will be impacted, and they need to understand why and how they will work with the changes in the future. Several layers start unraveling you fail to properly assign the service-level manager role – perhaps it's one of many hats this staffer now wears and the significance of this role isn't taking hold. applications begin to drive the iT catalog's construction instead of services. inaccuracies are discovered within the publicized pricing. all of these trouble spots lead to poor acceptance of the catalog in its early stages.
The Devil is in the Details There is continued inaccurate data in the service list. information conveyed within is too high-level, or too detailed for customers to make sense of – with no logical grouping of categories to help them navigate. customers sigh at the prospect of scrolling through 60 unorganized service listings to find out what they want. all focus is on tool development rather than how these tools support business functions. applications start getting selected with customers having no genuine understanding of what services they're getting. People who have had no involvement with the publication of this catalog now openly question the information, threatening to rip the entire project apart before it's had a chance to take off.
all of the above problems lead to this unfortunate outcome: The catalog is static. no one is really making actionable use of it in a meaningful way. This is because no one has ever validated the intent of its productive purpose with customers. no one has ever asked them, "What does services mean to you?" or "how can we make this list of services actionable for you?" crawl, Walk run approach to Building an iT Service catalog - version 1.0 Strategic – Communicate your vision Drive home the principles of your service-level management vision. Break down walls of resistance by getting service-desk staff fully involved. have them examine the developing list of services, as well as the grouping of services, and invite feedback. Encourage them to think like the customer in these sessions, based upon "real" customer feedback. in doing so, you'll establish clarity where there once was confusion. This, in turn, enhances the cultural change you seek. Tactical – Build a Service model Build a service model that distinguishes between business/corporate and technical services. an exchange server that runs e-mail does not perform a business objective, it's a tech service. if your company makes widgets, then designing widgets can be the business service delivered. for a retail organization, a service model is based upon the phases of "shopping, selection, assistance and shipping." These phases are underscored by additional services such as "assist shopper in selecting," "answer questions," "present shipping options," "confirm details," etc. note the focus on action here, not the tech applications that make the action possible.
operational – Zero in on Service Targets managing your customer's demand for your services is a large part of this, with absolute clarity of service capacity, requirements and capabilities. This kind of estimation matches service investments with service needs. Then, cultivate understanding of how cis support all of this. By the end of "walk," you're not only illustrating service expectations, but what services are supposed to look like . crawl, Walk run approach to Building an iT Service catalog - version 1.0 congratulations, you're ready to run. you have a catalog that's packed with relevant services. you have service level agreements (Slas) assigned and reviewed and can even start thinking about automating the catalog to reap the rewards of cost savings, as this is the stage where you fine tune metrics to measure impact.
it's too early to pop open the bubbly. not when these common mistakes loom: no ownership of the Catalog yes, there is the iT services manager. But with so much of the catalog now completed, this manager is subjected to other duties/distractions. The catalog loses a sense of governance. The organization is now ready to nominate Business relationship managers that will ensure the iT service provider is satisfying the business needs of the customers….we need to reinforce the Service level manager role and ensure he/she meets the customers on a regular basis to review the services performance according to the Sla in place.
iT service providers (The iT Team) underestimate the impact of this groundswell of change. They don't realize how this "business first" mindset completely revolutionizes the way they handle service requests. They confuse Slas with service targets. They are not one and the same. The Slas contain little more than service expectations. That's not enough.
garbage in, garbage out listed services aren't kept up to date. no, they won't get outdated in a year. But over time, the offered services will mature and the catalog should grow to embrace these changes. This is the same time period when service-request systems get antiquated as well.
Too many Tools in the Shed it's overwhelming for customers to get their arms around it all. on top of this, they can't adequately exploit self-service features of the catalog because these haven't been sufficiently planned out.
Relationships in Disarray The relationship among the configuration management database (cmDB), service desk and service catalog is muddled. in decomposing these functions, the business payoffs are not primarily considered, to effectively break down the services that drive outcomes. you can do this, and you don't need a cmDB for it either. if you grow your catalog, you'll end up documenting more and more service-connected technology assets (configuration items) that help meet business objectives. When you have compiled enough of these assets, then it's time to pursue a cmDB.
crawl, Walk run approach to Building an iT Service catalog - version 1.0 RunnIng To DAylIghT Strategic – Rationalize your service agreements. Whether you examine them through the prism of your service view or customer perspective (or both), come up with a blueprint that pinpoints where these agreements fit within your structure. also, start looking at which metrics you'll use to calculate total cost of ownership (Tco) verses value. again, you have to include the benefit to customer services within these metrics to establish this value.
Tactical – formalize roles External service owners and the internal managers who must oversee business relationships need to have their roles formalized. These managers should be responsible for reviewing Slas and making sure they remain current with company goals. This is all part of introducing a Service catalog management process that fosters the ownership of processes to make it all work. it needs constant re-evaluation and refining.
operational – Software takes hold you should have an iT Service management (iTSm) software tool in place by now. make sure it links incident/problems called into the help desk to services (as opposed to cis), to enhance a systemic approach to response deployment. at this point, the service manager is overseeing end-to-end provision here, taking on the needed ownership of the catalog. and don't forget that a completely automated web-service portal must be available to all customers at this phase. crawl, Walk run approach to Building an iT Service catalog - version 1.0 let's boil down the launch and implementation of a service catalog to these simple questions: What services do customers want? When do they want them? What service-level components are required to deliver them? how do we collect meaningful data on the status of each component, as measured over time? Then, keep in mind how these questions are addressed within the crawl, walk, run approach: What services do our customers want? When do they want them? This is how the very initial version of a basic service catalog is framed. its service-level requirements and agreements are all dictated by this customer-centric view.
What service-level components are required? We outline our available cis and designate teams responsible to deliver these in a manner consistent with customers' service expectations. We have operational-level agreements in place and underpinning contracts to support them. how do we collect meaningful data on the status of each component, as measured over time? This involves both Sla monitoring and reporting. Does our measurement data cover the customer experience? Does it include business-driven metrics? Drill deeply for this kind of quantitative framework, then record results for longevity.
That's because, in the end, your service catalog should never appear static. it is an organic, work in progress. But it is one that's assembled and constantly refined for you to achieve maximum benefits for the long haul.
crawl, Walk run approach to Building an iT Service catalog - version 1.0 Renee-Claude lafontaine Senior Adviser in IT Service management & ITSm Center of excellence lead ms. lafontaine has over 20 years experience in the field of iT service management. She has provided strategy consulting for clients large and small, offering guidance with mandates including evaluating the process maturity of iT service management, development and implementation of management processes based on iTil. Andrew Braden IT Service management Advisor mr. Braden is a Senior Technical, Process and Business analyst with over 25 years of progressive experience in the information technology industry. he is focused on value Based management initiatives, guided by the internationally accepted standards for iT service management best practice reference models: iSo20000, information Technology infrastructure library (iTil), control objectives for iT (coBiT), val-iT governance architecture (gEiT) and capability maturity model integration (cmmi).
• www.isaca.org (COBIT, VAL-IT, Risk-IT) • www.pmi.org (PM-BOK) • www.sei.cmi.edu (CMMI) • www.iso.org (ISO20000, 27000) crawl, Walk run approach to Building an iT Service catalog - version 1.0 Emtec is a provider of technology-empowered business solutions for world-class organizations. our local offices, highly-skilled associates, and global delivery capabilities ensure the accessibility and scale to align your technology solutions with your business needs. our collective focus is to continue to build clients for life: long-term enterprise relationships that deliver rapid, meaningful, and lasting business value. our mission is to help our clients improve iT systems and processes – to transform iT into an investment that returns true value to their respective organizations. for more information visit: www.emtecinc.com.
crawl, Walk run approach to Building an iT Service catalog - version 1.0

Source: http://www.emtecinc.biz/assets/uploads/whitepapers/Emtec_ServiceCatalog_wp.pdf