Better Service Visibility = Better Delivery!

Service disruption occurs when change and release management collisions occur.

How do we prevent these collisions from occurring in the first place?

Even the most sophisticated teams are subjected to these problems; why?

No matter how much planning and automation you have, there are still outages!

Now the service desk is getting hammered with calls and a VP is irate over not being able to reach his “key” system. No one is happy. The world is on fire!

We planned. We strategized… We have GREAT tools! We have GREAT PEOPLE! We AUTOMATE!!!

Why? Why me? Why us?

While you may have planned accordingly, followed the good practice handbook to the letter and thought you understood the decisions in the CAB, you still had collisions. Why?

Because you made decisions based on incomplete information.

There are MANY systems of record that hold critical information related to service delivery. That information is often not all in a single database — such as your ITSM system.

Vacation and business event information? It’s in your messaging system (Exchange).

Customer specific case information? It’s in your CRM (Salesforce.com).

Release information? It’s in your ITSM system (ServiceNow).

If key data related to change/release decisions is not all in the same system, the effort to correlate it may be painful and time-consuming, but; ultimately it is worth it if service is improved. Figure out how to get it correlated — even if it is a spreadsheet. Reduce the risk by knowing what is what.

calendar-video-preview-1
1:56 — A demonstration of a unified calendar view.

We built Kinetic Calendar to enable real-time visibility into key data from multiple applications. it’s more important than ever to be able to cross reference data from those systems. Request a free demo here.

Your Next ITSM Tool Should be Neither

TL,DR; decouple IT operations from customer service and development. Then realize the incredible savings and benefits thereof.

The term “ITSM” has always bugged me, and I think I know why.

The primary customer of ITSM is IT; everything else is lumped into “customer service” and “customer experience”.

ITSM_WikiEven Wikipedia says there are too many “fluff words” and that ITSM has an unclear definition.

But in IT, we know better. We understand what we’re talking about when we say Service Management. It’s a standard way of operating so we don’t fail.

So why would any business person buy Service Management?

To keep the lights on.

“But that’s what we hired you for! We don’t care what you call it. We don’t want to buy it, we want you to DO IT!”

Then I’ll need $1.5m every three years to replace my tools, redesign processes and…

Wait, $1.5m? Don’t you remember when last year we were managing changes via email? Don’t you remember the spreadsheets of Assets? Why $1.5m?

Technology has become complex and our colleagues want to reduce risk. Some also want to understand the value and depreciation of assets. ITSM is just IT Operations Management + Customer Service.

DING DING DING DING DING DING – we have a winner! Here’s your $1.5 million. But why every three years?

Think of ITSM tools like a car lease. Three years comes along, and it’s time for a fresh smelling one, the latest one with all the bells and whistles.

Do the bells and whistles keep the lights on?

No.

Then why keep upgrading and rebuilding your operations empire?

The tools and practices that surround Service Management change, and they change often.  Have you considered who benefits from that change?

Consider separating your systems of operation from your systems of service. It gives you the freedom to change platforms without impacting your customers.

The impact of this is far greater than you realize. We believe in building systems of engagement separate from systems of record. To understand the nature of this problem:

 

systems-of-recordDoes this image describe your problem? If so, you’ll be interested in understanding our approach to enterprise software. Read more here, or just call us directly: 1-651-556-1030

New Definitions Added to the Ultimate ITSM Glossary

As noted here previously, there are numerous words, phrases, and acronyms which are either unique to the IT service management and ITIL world, or have a specific meaning within those contexts.

To help clarify these terms and concepts, Kinetic Data has compiled definitions for nearly 60 items in our ITIL – ITSM glossary.

ITSM-ITIL glossary - new terms addedBut the IT discipline is constantly evolving, with new practices, technology, concepts, models, trends and ideas being introduced. Reflecting these ongoing changes, four new entries were recently added to the glossary of ITSM terms.

DevOps

Few terms in the realm of ITIL and IT service management are as controversial to define as DevOps; there seem to be nearly as many definitions as the number of people trying to define it. Continue reading “New Definitions Added to the Ultimate ITSM Glossary”

The Ultimate ITSM Glossary

There are many words, phrases, and acronyms that are either unique to the ITIL / IT service management world or have a specific meaning within those contexts.

To help clarify these terms and concepts, Kinetic Data has compiled definitions for almost 60 items in our IT service management glossary.

ITSM GlossaryHere are a few sample definitions from the glossary of ITSM terms.

Agile Service Management

A methodology for providing users with the ability to order and obtain physical items or resolution of issues in a manner that permits new offerings to be defined and added to the system quickly; that makes it easy to change existing items; and that allows new items to be added iteratively, starting with one or a small set of offerings and scaling to large numbers of varied items. With an agile approach to service request management, new service items can be defined an added to the system iteratively, allowing for “quick wins,” rather than requiring an extended effort followed by a “big bang” release of a large, complex catalog of business services all at once. Agile service request management also provides the flexibility to easily accommodate changing user needs, such as modifying or expanding existing service offerings to support mobile users.

Business Service Catalog

Extending the concept of providing a portal interface in which physical items or issue-resolution processes are defined and can be requested by users, from IT-related items only to all functional departments across an organization. Though the concept of service catalogs began in IT as a recommendation of ITIL, these are now evolving into enterprise or business service catalogs per Forrester Research. Accordingly, the architecture of enterprise service catalogs is evolving to accommodate a wider range of service offerings than just IT services; to enable non-technical business function managers to define and optimize their own service fulfillment task workflow processes; and to scale to the enterprise level. This evolution extends the benefits of service catalogs across the business.

BYOD

Acronym for “bring your own device,” this is one manifestation of the consumerization of IT, the trend for users to prefer their own smartphones and tablets over company-issued phones and bulky laptops, and to use a single device for both work and personal purposes rather than managing applications and data sharing between multiple pieces of hardware. Enterprises are adapting to the BYOD phenomenon by creating policies and procedures that provide employees with flexibility while protecting corporate data and application access, and shifting to schedule-based rather than queue-based support services to better accommodate mobile workers. By adopting processes such as simple BYOD device registration and remote installation of required software, organizations can benefit from both lower overall support costs and happier employees.

IT Infrastructure Library (ITIL)

Variously defined as an integrated set of IT best practices recommendations, a framework for accepted IT service management best practices, and a set of documents designed to improve IT service delivery. ITIL provides an extensive set of IT management procedures designed to improve the efficiency, timeliness and quality of IT services delivery. The library was first developed by the Central Computer and Telecommunications Agency (CCTA), a U.K. government agency. It is now managed by the U.K. Office of Government Commerce (OGC). ITIL V3 consists of five core documents: IT Service Design, IT Service Introduction, IT Service Operations, IT Service Improvement and IT Service Strategies. One key element of ITIL service delivery recommendations is the establishment of an easy-to-use, dynamic IT service catalog; Kinetic Request service catalog software supports implementation of an enterprise-wide service catalog by providing service request management functionality coupled with backend process automation via Kinetic Task.

IT Service Management (ITSM)

An approach to managing large-scale IT systems and processes focusing on the customer perspective of service delivery (as opposed to technology-centric), and promoted by ITIL best practices. ITSM is a framework for continual improvement in the IT services delivery process, much as CMM is focused on application development. Effective IT service management integrates technology with people and processes in a manner that supports industry best practices, such as implementation of a service catalog.

Check out the ITSM glossary for the full set of definitions.