Structure in Threes: Change Management and Adoption

Wednesday I went back to Microsoft main campus to meet with friends, colleagues and management for a potential new role.  Had several interesting discussions with each.  The curious take away I came up with was a feeling of Déjà vu.  Like other enterprises I’ve designed and installed processes in, the real challenge is not design and development.  Though considering the aspects that improve adoption early in the design process is necessary but not sufficient, the hard part is adoption management.  That set of planning and execution activities that help organizations move from current state to transition state to new status quo.  There are many models and books on the market about change management.  Some of my favorites are those by Harvard Professor Kotter.  Other authors such as Hiatt (ADKAR), Association of National Advertisers (DAGMAR), Cialdini (Influence: Science and Practice) ,and Bosworth & Eades (Solution Selling) are divided into the marketing or behavior sciences realm.  The unfortunate aspect of most of these books is the practical application of these theories is left to the reader.

I can understand why this is; people are not machines that work in a repeatable and predictable manner.  While they may have tendencies to act a specific way there are no guarantees, if there were a magic formula Crossing the Chasm or finding the Tipping Point would be easier to do.  Given that people and organizations are a complex interaction of entities with conditions and events finding the right formula of activities to allocate funds to oft times becomes a quest for the holy grail resulting in analysis paralysis.

Those organizations that try the shotgun approach (throw everything at it and see what sticks) are on the other side of the spectrum.  Both approaches are less successful, typically achieving success due to chance rather than design.  Examples being those enterprises that spent so much time analyzing the Internet, they missed the bubble then later claim brilliance and insight for not investing rather than painfully slow processes. Or those ventures that charged ahead and as luck would have it had some measure of success then collapsed as the items that stuck did not constitute a sustainable business.

Change and adoption is similar in that either end of the spectrum may have some success by chance during a specific set of conditions and events.  However, when the conditions change or a new event occurs, snapback to the old way of doing things happens and one finds out that the organization really did not change how it was operating it just put a new veneer on over what it really was doing.  I call this the Jell-O Pyramid model.  Often leaders and change agents think they are being successful as they view the change from the top where they are applying pressure.  This bends the point of the pyramid in the direction they would like to go.  However, once the pressure is removed unless sufficient pressure was exerted long enough to move the base, the  pyramid snaps back to its original shape and position.  This suggests the need for a measurement and monitoring system similar to those pointed out in Stafford Beer’s research.  However, I’ll leave that for another blog post.

For the pragmatics of adoption I found a model in the small business arena of business development.  A book by C.J. Hayden, Get Clients Now!.  The book does not claim to be a master’s thesis in change management or sales.  What is does do that other books do not with its system, is move one from formula and theory or strategy to tactics.  In other words she’s created a system of strategic execution if I throw a Harvard label on it.  The book does not profess to tell you do A, then B, the C and get result D.  What it does do is show you tactics that have some strong correlation to success for various aspects of moving from one stage of business development to another.  She does not tell you specifically do A, but provides a list of potential “A”s, “B”s, and “C”s  that have had success for others.  These are tactics you can look at and quickly execute and measure results.  She continues with here system by having you measure both executing these tactics and the results.  This becomes the feedback system so important to ensuring you are actually doing something planned verses just doing everything.

I bring up this book as an example as I see this as the model to be used for change and adoption management, then after considering this I saw a similar pattern of execution management –without the list of tactics– in using Hoshin Planning.  I expect that the change and adoption planning section of the book with merge these two concepts.

Managing the change and adoption process suggests one measures current state, activities and reactions and sentiment

Structure in Threes: Modern IT Portfolio Management

This morning I’ll tackle the rest of my wiring closet, then local phone company to come by to determine why primary line is continually business which is what kicked off relocating and revising wiring closet.  In the meantime, I’m back to researching using Candlestick Charting as a means for the Modern IT Portfolio Management concepts I’ve been developing the past years.  I’ve been keeping tabs on the options theory materials I’ve deployed at former employers and clients.  The results infer the approach works well; the clients that I monitor have been reporting increased business capabilities at a faster rate than prior and improved business results in the line of businesses that were supported.

I wouldn’t go as far as saying this is conclusive evidence that the portfolio approach I deployed was causal for improved business results –some of the contribution loop training I received long ago– but I do see a correlation and would conclude effective IT Portfolio Management contributes to improved business results.  The South African engagement I supported remotely for a client would have been a good test case; however, we didn’t have the time nor client have the funding to do a baseline for analyzing the effects creating BI and Collaboration capabilities in the enterprise.  I did specify how they could automatically track results and use predictive analytics backwards to create a baseline for analysis later.  I’d be interested in tacking a trip there one day to see the results and add the marketing analytics they wanted to do in phase two.  In the meantime its off to brainstorming about what indicators to use for IT Ecosystem Candlestick charting.

Satory Global makes #233 spot on INC Magazine’s Top 500 list for 2011

I’m Jazzed!  After three full years of the team’s hard work, Satory Global is getting recognized.   The company made the INC 500 list, placing a respectable #233 out of all the applicants nationally for the Inc 500/5000.  

http://www.inc.com/inc5000/profile/satory-global

http://www.satory.com/about/press/Pages/default.aspx

The big question will be can we do it again next year.  The team is pumped and looking to expand into others areas like Cloud enablement services after attending Microsoft’s WorldWide Partner Conference previous month (WPC).  Previously started reviving my Enterprise Architecture book efforts via posts on this blog, expect to add some innovations on Business Architecture to Cloud Design materials soon.

First have to finish my ITIL enablement using SharePoint white paper for SharePoint 2011 in Anaheim and process models for a hoped for demo with an ISV partner.

Using SharePoint to enable ITIL: Consequences of unmanaged services

Since technology appears simple to operation the assumption is that it’s simple to build and manage.  What isn’t seen by end-users today is all the complexity behind a product or service.  The consequences of operationally mature, technically naïve stakeholders and end-users are having to justify investments in information technology.  While it’s not unreasonable to ask for such, it’s difficult due to the complexities and variables of how the services are created and used.  Adding to this complexity, the financial measurements and analysis is still an immature field.  Accounting systems only within the past few decades have started addressing services and other abstract assets.  However how to measure benefits still raises strong disagreements between CIOs and CFOs.      

In addition the expectation of I.T. Services is that they are as stable and reliable as other mature services telephone, water and electricity.  As a result organizations have moved past I.T. as a “tool” that is adjunct to how work is accomplished and have or are weaving information technology into the very fabric of the business and in some cases integrating I.T. into the products and services they deliver.  Two examples: First look under the hood of any automobile lately you’re faced with a mass of connections, even that mechanic that tune up your car now plugs it into a diagnostic computer.  Second want to deal with the government or a financial institution, you’re likely to either go online for forms or visit an ATM.  When was the last time you actually saw and spoke to a teller?

The level of integration of computer technology has skyrocketed and with it the dependency upon services hosted on them via various network connections and backend infrastructure, including the people that support all the onboarding, operations and creation of these services.

Thus this dependency has created increased risk.  United Airlines recent reservation systems outage cost them dearly, not only in operations costs, but good will, penalties and legal issues from passengers denied access to their flights.  An estimate of the damage has not been publically announced but you can be sure it was significant.  

Without a good handle on managing services I can foresee a day when a business fails due to service interruption or I.T. failure.  Imagine how long it would take Amazon to crash if its infrastructure failed.  For Amazon, I.T. failure cannot be an option, they don’t have a physical storefront and they are totally reliant on technology to point them to where the closest inventory is to fulfill and order.  I would expect a 12 hour failure like United’s would be deviating to the bottom line.

I.T. Product and Service failures could in the future lose the shield from disclaimers and fitness of use loopholes.  The end user licenses that have been used to limit liability may eventually be used as evidence that the product is unsafe or unfit to be sold or that the company has engaged in false advertising.  Thus I.T. Management may have legal exposures similar to Senior Corporate Executives via SOX and GAAP regulations.  

Some of these service issues have gotten management mindshare and attention; witness the strong efforts around I.T. Governance and service delivery models.  Still other efforts to cobble together some form of service agreements and measurements.

While customers (internal and external) are judging them on their own performance criteria which may or may not match up to Service Level Agreements (SLAs) these organizations have stitched together often on criteria that customers do not see and therefore do not measure against  [i.e., network or server availability vs. service availability –what good is either to measure if they are not in sync to allow me to utilize the service e.g., the server was up 20 hours a day and the network was up 21 hours a day, however combined the complete service that required utilization of both was up only 18 hours (only 1 hour of the network outage overlapped the hours of server outage).  Server and Network availability where reported a poor 84% and 88% respectively, however the Service Availability the customer experienced was a dismal 75%.  That’s a quarter of the time a customer cannot use the service. Think of it as one in four times you go to use your car it wouldn’t work or worse yet, 6 out of every 24 hours a plane flies it just stops –hope you’re not over the Rockies during that window.  

Thus the consequences of having unmanaged and poorly managed I.T. services are increasing.

Technology Adoption vs. Information Management

One of the things I’ve realized over the years, popular technology adoption does not equate to business productivity. It may actually be the reverse; when a technology becomes all the rage and takes on fad-like status, it rapidly gets out of control resulting in all manner of side effects.

SharePoint is one such example. Being touted as the application backlog silver bullet: “End-Users can build their own collaboration applications themselves leaving I.T to work infrastructure an enterprise applications. I think I heard this story before with MS Access and Excel. Now CIOs and Business Executives are left with thousands of unmanaged applications with critical corporate information distributed on workstations and laptops across the enterprise.

This is not a critique of MSOffice or SharePoint far from it, it’s more of a condemnation of how adoption is managed or rather mismanaged in organizations.  Despite all the talk of governance and adoption maturity levels most of these are applied to the installation of the technology not its productive use.   I watch as technologist, I.T consultants, and sales representatives promote technology virtues with all sorts of hyperbole in amazement knowing that an organization is lucky to get one fifth of those benefits.  Not because the technology can’t deliver, but rather the organization can’t incorporate usage best practices as well as installation best practices. 

A simple proof point how many MS Access and Excel spreadsheets are used in your organization to manage core work?  How many are managed as a critical asset?  How much of the information is duplicated in some form or version of the truth?  And now you’re going to enable end users to do the same in SharePoint by creating their own sites?  

This is not a call to ban end-user site generation, more so a suggestion that education and training on information management for information workers (i.e., most of us now) is becoming a critical need more so than simple computer literacy.  Either we learn how to manage our information better or we’ll drown in a information glut of our own making.  Consider joining organizations such as AIIM and DAMA are providing some thought leadership in this area.

Satory Global LLC
Twitter: @bseitz
www.satory.com

Brian Drain -reposted

Ayn Rand foreshadowed it in her bestseller, Atlas Shrugged, but what can be done about brain drain? The NEO model offers a new kind of vision for leveraging intellectual property and assets During the past twenty odd years I have held various titles and positions – almost always with the same small twist to them. I am typically asked to take on the most troublesome areas of a business or project. Part of this is by choice and part of this is by reputation. In days past, people like myself were called corporate troubleshooters or consultants. We had very vague titles and charters to go forth and do good work fixing whatever we saw as a problem within the business. It is from that perspective, as a dispassionate observer, that I offer the following thoughts on business practices today.

Nowadays in the fast paced dot.com and the post-large corporation world, the apparent need for deep knowledge, skills and refinement appears to have vanished. If a process or product doesn’t work right out of the gate, the rationale goes something like this: patch it quickly, if it doesn’t survive in the market, dump it fast. Businesses have become the ultimate example of what was called the disposable generation, tossing products, companies, and people like used Kleenex

However, like all trends and fads, this too shall pass. As corporations like Microsoft, Boeing, CISCO, and Sun Microsystems field new technologies and other corporations wish to field the same; the need for skills beyond typical project management competency becomes more apparent.

Shortage of Skilled Workers

For evidence of this, we need look no further than the advertised shortage in the I.T. field. The statistics you see from Gartner Group, IDC and the like all show the same painful result. The majority of IT projects fail to meet expectations of the business, and in too many cases just plain fail in some technical aspect. While internally this failure is rationalized away by statements like “the technology just wasn’t available yet” or a plethora of other excuses, the simple fact is that the deep knowledge and skills, those that make a employee part of the enterprise versus just another set of arms and legs, are not there anymore. Neither is the commitment of employees to develop such deep knowledge since corporations are increasingly taking a short-range view and as a result, have broken the perceived employer/employee bond.

Corporations are reaping what they sowed years ago as they broke faith with employees. As such, employers are now forced to not only compensate higher, but in addition give a piece of the pie away also, just to attract or retain the basic or core skills needed to produce. Industrial karma you might say.

Atlas Shrugged

What isn’t showing, but was foreshadowed in Ann Rand’s book, Atlas Shrugged, is what has been labeled brain drain at various corporations. This occurs within a business’s lifecycle when the perceived full motivating factors verses the de-motivating factors such as lack of freedom, interest & fun in the job and low to average financial compensation do not add into a net sum gain in the technical employee’s eyes. What occurs is compliance to rules and measure, but not commitment to the business’s success as they see no linkage to their efforts, business performance, and their professional success. This results in not only the mass trend that employers are seeing now -difficulty in finding needed skills-but a more wicked issue hiding like an undercurrent in the visible employment waters above.

Essentially, the best and brightest are voting on a corporation’s perceived short & long viability with their feet. Look at the dot.com phenomena; shortly after many of these companies IPO, the intellectual horsepower in the corporation leaves and the company falls. Mergers and acquisitions are another area in which these conditions abound. In days past, smart businessman knew enough to insist that the key talent and staff stay long enough for the company to be assimilated. This at least gave it a fighting chance to survive. However, these organizations too are now suffering the realities of the shift in the power in the employment contract they pushed to change to.

The Matrix (I’m going to show you a new world…)

What does that mean? A new business model is needed. One that truly integrates employees and employers in a common purpose and direction. Enter NEO, a code name for a new collaborative environment named for a character in the pop film, “The Matrix”.

The interesting aspect about the NEO model is that it is not “a” model per say but several models integrated into a dynamic context. This context is the recognition that the electronic infrastructure (a.k.a. the WEB) is a vehicle to link people together enabling them to collaborate. This collaboration occurs in three parallel dimensions: E-space, Pspace, and I-space.

E-space is the rushing world of bits and bytes, the data processing and telecommunications that the I.T. community submerge themselves into divorcing themselves from the rest of the world. It can be characterized by the terms access, connectivity, and bandwidth.

P-space is that physical world we all belong and are aware of. It contains the phenomena that scientists spend their days describing and engineers capitalize upon to build products that the rest of the world finds value in.

I-space is that abstract dimension of ideas, information, knowledge, and principles. It is the area where creativity and imagination live. It is less investigated and documented than the other dimensions and therefore harder to understand the rules and laws that governs this environment. NEO operates on all three planes; however, it is primarily an I-space entity which is manifested in P-space via the E-space entities that represent I-space properties and behaviors.

So what does all this 2nd year philosophy rhetoric have to do with how an engineering service company works? To quote the movie, The Matrix, “Imagine a world…” NEO is a set of rules describing how an enterprise without boundaries works, an enterprise based upon several simple principles. 1) People should be compensated on the value they bring to the corporation, not the time they dwell. 2) Knowledge and information are the means to collaboration and have a measurable value just like P-space entities (ie. copyrights, patents, and other intellectual property.) 3) Value is in the eye of the recipient. That is what I value may not be the same as you or have the same priority.

Having shown you the linkage between philosophy and business management, the extension of this yields several models which describe how this boundary-less enterprise is structured and behaves. First is a model of compensation called “Personalized Employment™”. Next is a model of intellectual capital called “the Registry™”, which is intimately tied with a model of how to manage all assets whatever class they are called Interlocking Portfolio Management™’

Glimpses of this model have been seen within the technical community during the past decade.

Show Me the Money (Personalized Employment)

Devices like options, grants, incentive pay, and improvement & performance bonuses are now part of the typical high tech compensation plains. Each has its pros and cons.  For employers, options, grants and incentive pay represent a way to motivate an employee risking very little up front. This compensation is based upon demonstrated performance of the company, the employee or both. In many new companies this is the way to attract new talent or retain talent without having to lay out significant cash. This works well as long as the corporation is on a fast growth path. However, just like other forms of compensation this can setup an internal competition between employees as they via for a share of the pie. Look at the exodus from corporations once their double digit growth is over.

For the employee, these devices can also be boom or bust. If the corporation does well, your performance is perceived well and critical to the success of the company, gold flows into your pockets or at least the promise of gold. Options valued at x dollars may not be worth a tenth of that when it is time to exercise them. Witness Microsoft’s recent drop and the adjustment it made to their stock options plan needed to retain employees.

Compensation within NEO is characterized by the concept of personalized employment.  Similar in principle to the cafeteria style benefits program that many large corporations have instituted, but extended to create a flexible total compensation package. Remember value is in the eye of the recipient. This is balanced against the value contribution an employee makes to the corporation.

Within NEO, each contributor is compensated in several ways according to the value-add they bring to a project. The first level of compensation is on a deliverables basis, no different than work for hire or other contracted labor. The difference is that the compensation is for that unit of work only. If someone can do the job, with the same quality, in one day verses two weeks it makes no difference. The compensation is for the result, not the level of effort. The next level of compensation is a little trickier to follow. It is based upon the original value-add a contributor creates and value added beyond the project or other corporate assets outside the scope of the original work unit. That value-add is determined as a percentage of the project’s entire value-add. A portion of the revenue generated from the project’s life is segmented into a pool for contributors to share. That pool is distributed to contributors based upon the value-add percentage determined earlier. In effect, the contributor now has a royalty check or annuity for the life of the project.

Asset Management (The Registry and Interlocking Portfolio Management)

NEO takes advantage of a unique asset management technique called Interlocking Portfolio ManagementTM (IPM). Unlike the typical view of asset management, NEO views almost every object or entity as an asset which potentially should be managed. This includes physical, fiscal, and intellectual types of objects. These assets are classified and categorized into subsidiary portfolios to be managed. Each portfolio then is also managed and cross analyzed to identify opportunities and liabilities within the entire portfolio (i.e., synergy).

The way this is achieved is through a classification matrix and assessment of the value of this assets in an economic context. Thus each asset is monitored as to its past, present, and future value singularly and jointly when combined with other assets. This is done through a dependency analysis and several other proprietary economic models.  These results are then displayed on what’s called an Enterprise Dashboard so that portfolio managers can make decisions as to what positions should be taken regarding these assets. These positions can be to divest, retain, or reinvest in these assets.

The primary function of the registry is to provide a means to capture, encode and disseminate information, the knowledge within the NEO sphere of influence. Thus the Registry and IPM represent a new kind of knowledge-based system – one that is capital-driven. (And, as such, one that we might expect capitalist Ayn Rand to advocate as a viable means of combating brain drain.)

Of course, it isn’t Rand who is responsible for attracting the brainpower necessary to fuel innovation in your company and it isn’t Rand who is the one prepared to offer her brainpower at some agreed upon ‘price.’ But maybe one of these scenarios describes you. If so, and if you’re interested in learning more about how the NEO model works, contact the author at briankseitz@earthlink.com, or check out the Intellectual Arbitrage Group’s website: http://www.intelarbgrp.org http://home.earthlink.net/briankseitz.

Originally Published in MCADCAFE August 2000

SharePoint as an ITIL Implementation Tool > Why should I care about ITIL? > Business Environment

Why should I care about ITIL?

[CxOs especially CIOs should care in the wake of rising I.T. costs, the strategic importance of I.T. as an enabler, and the growing chasm between business needs and I.T. provided capabilities]

Business Environment

Information Technology has evolved from the automation of financial transactions, once called EDP, into a strategic component of most businesses and in many cases part of the products and services the company delivers.

The computer industry has matured over the decades from EDP to MIS to now I.T. During that evolution the communities that the technology has supported has widened and deepen, to the point where almost every function and role within an enterprise has been touched by it.

Computer Technology initially automated repetitive accounting tasks, increasing the productivity of the accounting department. In the next generation of adoption (MIS), managers were able to create and monitor finance plans; the computer was still being used to “crunch” vast quantities of numbers. During this and previous generation computer resources where typically big centralized mainframes.

The next generation of Information Technology adoption came with the advent of microchips and the microprocessor making workstations and personal computers possible. Select members of the company staffs now had two sets of resources; mainframes and personal workstations. While the tools were initially primitive a larger pool of professional and amateur focused upon creating a richer and more flexible suite of function. Ushering in the personal productivity initiatives that still dominate the market today.

From here variations on the theme of connecting computers together created the next generation (network). Computers were either connected peer to peer or in a client server model. These enabled people to copy content around the network to share with others.

These advancements in usage however came with some liabilities; more effort was needed to maintain multiple computers, software and the network connections.

While the product development process for information technology industry has evolved over the past several years attempting to catch up with demand, the operations area has not kept pace.

Most I.T. operations are little more advanced than where they started. Instead of using JCL or Exec, Operations now using scripting languages. The model for delivery is after Q.A. install, run, optimize and stabilize. There is a natural tension between development and operations due to the differing roles, responsibilities and measurements.

As such many of the applications that were create years ago are still in operation, patched together when they should have been sun-set or displaced by others. A lesson hard goods manufacturing has learned: Not too many manual laths and milling machines around anymore. After its effective life these tools are salvaged and replaced. I.T. has not adopted a real lifecycle model yet, expect where purchased software is concern. The end result of this is a legacy wake of support that keeps growing.

As more solutions involve a configuration of multiple components end users are experiencing increasing amounts of operational brown and blackouts. These service interruptions however are not noted effectively in the statistics presented to the user community as compared to what they experience. This discrepancy is due to the difference in how services are measured. For the end user service is an end to end process, while most I.T. organization report on individual components.

A simple example: The Server CPU was up 99.9% of the time, the Storage Area Network (SAN) was on-line 97%, the Network 96%, the application 95%, the DBMS 98%. The logical assumption is the user experience 95% service availability. What the user actually experienced was 86.6%. This is due to the fact that availability is the results of all the components operating. Thus any break in the availability chain results in a loss of service. The formula for calculating this:

Service Availability = Σ Server × SAN × Network × DBMS × Application

Thus the management of technology vs. the mechanics of technology is becoming a critical set of skills. The business skills needed to understand and manage risk, finances, communications and customer relationships have become critical success factors for technologists.  It’s no longer enough for a Programmer or DBA or System Administrator to just have technology competency.

  As technology becomes easier to operation from an end-user perspective, stakeholders slip into a complacency regarding the effort needed to develop, operate and manage the complexities behind the apparently simple application.  Thus the magic user button proves it’s easy for anyone to build the system; since operating it is so simple, building it must be also.   

An overused example but still relevant; how many people really understand the technology needed to operate a car, not even a current model car with all its electronics.  Yet, people dismiss the amount of complexity that is inherent in the automotive transportation system from vehicle to fuel distribution to roads and traffic control systems.

Each of the components of system are also complex systems also and coordinating the interfaces, interaction and operations of these becomes an ever increasing task which has not received the same attention to automate or innovate as line of business applications, though information technology is now a line of business application unto itself.   

Delivery of I.T.’s value is evolving in advanced organizations from a product development to a service performance model.

Prior to the introduction of I.T. as a service this past decade, I.T. organizations were modeling themselves after product factories focusing on such metrics as: speed to market, product features, product robustness, and cost.  When it came to the operational and support side minor efforts have been made.  However, as with physical products, the glory and rewards have traditionally been on the creative and design side of the equation along with the funding.  It’s not too often that support or operations gets much accolades, it’s usually on the side of being asked to squeeze out one more cycle from an underpowered system.

Thus those in the know kept a fair distance from being on support or operations.  If you were a new employee chances are your first assignment was in operations or helpdesk with the rationalization that it would give you a will rounded view of how the organization worked.  As such it became the dumping ground or was thought of as the dumping ground for novice and underperforming employees.  This was a similar fate to mechanical engineers who were sent off to manufacturing rather than design roles.  

This scenario may change soon.  As in the engineering environment, the democratization of design (e.g., mass customization) has created a situation where the tools at hand can enable end users to create their own solutions.  This change in dynamics is occurring rather rapidly in the I.T. environment as well.  SharePoint is such a platform that is changing the game.

What that means is I.T. organizations will have to rethink value and how that value is delivered. 

SharePoint as a Service Catalog

I.T. has traditionally worried about backlogged projects, now the tide has shifted in that I.T. must prove value.  It is no longer enough to say I put up an application or a server it’s someone else’s problem now.

One of the concepts that is hard to grasp for many I.T. staff when switching to a service orientation is the recognition that in order for these services to be consumed these must be known. 

For service to be known some form of marketing and advertising is needed.  The business community does not have time to visit multiple sites and explore technologies like the I.T. staff.  They need a simple location to find potential information solutions already fielded, a service catalog if you will.  That catalog like product catalogs should be searchable, provide a description of the service, define its benefits, costs and specify how to order the service.   

SharePoint can be used as a repository for these definitions of services as well as the bill of materials required for the service to be provisioned. This same repository can be published to potential and existing customers to enable them to understand services available to them, how to order, service to be expected, know which services they’ve purchased as well as introduce new services that are to become available.

While SharePoint is not a Relational Database, which is needed to manage the configuration of applications, hardware and processes needed to support service catalog functions, Business Connectivity Services and PerformancePoint provide the means to integrate and augment current CMDB functions in System Center Operations Manager and System Center Configuration Manager.

With each Service defined as a configuration of these components, a Bill of Material can be generated from a request for validation and provisioning in a more efficient manner.  An “onestop” shop for both End User and Service Operations Manager.  Instead of having to discover an End User doesn’t have a prerequisite component the Bill of Material acts as a checklist of accounts and permissions needed to be in place.

Additionally as Businesses move towards a Service Orientation billing for these services accurately become critical.  The Bill of Materials for services provides an accurate categorization of billable items the end user can understand.

Outline Section 4: SharePoint as an ITIL implementation tool

Building an ITIL implementation in SharePoint

SharePoint with its flexibility as a collaboration and workflow platform can assist in creating the enabling infrastructure for ITIL.  Many of the point solutions that have been developed can be integrated (loosely coupled) through SharePoint features such as Business Connectivity Services (BCS).  An “Active” Service Catalog, one that end-users can browse and select from can be created from lists, document libraries, InfoPath forms and simple workflows.  Monitoring and Reporting of disparate systems can be integrated into a Service Dashboard using PerformancePoint.  These are just a few of the components that have been prototyped and piloted which had been the genesis of this white paper.   Below is more detail descriptions of the components previously mentioned.    

SharePoint as a Service Catalog

SharePoint can be used as a repository for the definition of services. This same repository can be published to potential and existing customers to enable them to understand services available to them, how to order, service to be expected, know which services they’ve purchased as well as introduce new services that are to become available. 

Service Configuration Management Data Base (CMDB)

With a minimum effort SharePoint workflows can be configured into a Service Order Entry System that will enable prospective customers to configure and order a service, submit, track and confirm delivery of services from the catalog.

 SharePoint as a Customer Account Management

SharePoint can be configured into a Customer Account Management system that will keep track of customers, customer orders, order status and services provided thus giving I.T. Service Management Staff a complete picture of the services and performance a customer is receiving.

SharePoint as Technical Issue Knowledgebase Management

Self-Help and Technical Issue Knowledgebase Management

  • Explain benefits of how to create a FAQ and Issues Knowledge Base

Help Desk Automation (ticket tracking)

  • Explain benefits of how to create a help desk ticket management system

SharePoint as a Performance Management System

Technology Monitoring and Reporting

  • Explain how SharePoint Dashboard could be used to display status of Servers and Applications from System Center and with additional programing display status of Business/IT Services [Performance Point and System Center Integration ]

Policy Deployment Management (Hoshin Planning)

  • Explain how Hoshin Planning can assist in more effective deployment of ITIL and IT/Business Alignment
    • Explain what Hoshin planning is and how it helps align and manage strategy deployment
      • Hoshin Planning is a Strategic Planning technique developed in Japan during the TQM and Management by Objectives initiatives of the 1960s
      • Unlike many other planning techniques, Hoshin, provides a means to link Strategy to Execution
        • Hoshin Planning uses a set of cascading and interlinked matrices to refine strategic objectives into greater detail and actionable tasks throughout the organization.    
  • Explain how to use SharePoint / PerformancePoint KPI rollup features to enable Hoshin Planning
    • SharePoint PerformancePoint provides the ability to roll-up Key Performance Indicators (KPIs) measurements and associate them into higher level KPIs. 
    • This feature makes SharePoint’s PerformancePoint feature an excellent candidate as the technology infrastructure to support Hoshin Planning

 

 

 

 

Outline Section 1: SharePoint as an ITIL implementation tool

What is ITIL?

ITIL stands for the Information Technology Infrastructure Library

[ITIL stands for the Information Technology Infrastructure Library]

The Information Technology Infrastructure Library (ITIL) is a set of concepts and practices for Information Technology Services Management (ITSM), Information Technology (IT) development and IT operations.

ITIL gives detailed descriptions of a number of important IT practices and provides comprehensive checklists, tasks and procedures that any IT organization can tailor to its needs. ITIL is published in a series of books, each of which covers an IT management topic.  The names ITIL and IT Infrastructure Library are registered trademarks of the United Kingdom‘s Office of Government Commerce (OGC).  –Wikipedia

What does ITIL do?

[ITIL is a set of best practice areas for managing I.T. as a service.  These best practice areas follow the lifecycle of a service.  These practice areas are: Service Strategy, Service Design Service, Service Transition, Service Operation, and Continuous Improvement]

  • Model of how service is measured and managed

ITIL provides a conceptual model of the service lifecycle.   

  • The model defines major components that enable a service to be designed, developed, deployed, operated, optimized and eventually retried when the service provides a minimum of utility
  • These components are further divided into practice activities that support practice area goals

The model details practice area activities to a level that enables processes to be developed supporting practice area goals

  • Each practice area activity is defined by objectives and an operational description

The model describes how service is measured and managed.

Why should I care about ITIL?

[CxOs especially CIOs should care in the wake of rising I.T. costs, the strategic importance of I.T. as an enabler, and the growing chasm between business needs and I.T. provided capabilities]

Business Environment

  • I.T. has evolved from financial automation to strategic component
    • Information Technology has moved from financial automation (DP) to management information (MIS) to productivity enablers
      (Desktop and Network) to Strategic infrastructure and embedded products during the past thirty years
    • Production, Operation and Support productivity for I.T. has not kept in sync.  While product creation has improved with various techniques, the legacy wake of support and operation continues to grow.
    • End users en-mass are now experiencing brownouts and blackouts, more so as technology becomes more interconnected, and are questioning I.T. Management and I.T.s ability to manage the technology. –
      Business Skills are becoming critical to I.T. staff
    • As technology becomes easier to use on the surface, end-users and executive management see less value and more impediment from I.T. organizations. (i.e., I.T. is just magic that anyone can do).
  • The delivery of I.T. has evolved from a product to a service orientation
    • While I.T. always had a services component (operations and support) it was considered as the last and least important loop in the chain.  Still today service portions of most I.T. organizations are thought of as a place for novices, low skilled and performing staff
    • Service delivery and management has not kept pace technologically or through process maturity.  A Capability Maturity Model (CMM) was only introduced less than a decade ago and its orientation was managing outsourcing rather than the service delivery itself

Consequences

  • I.T. is being asked to justify ROI on a regular basis.
  • Service interruptions effect company bottom lines more directly and on a larger scale (it will not be much longer before reason for a company failure is correlated directly to an I.T failure)
    • Product/Service liability may materialize shortly after such
      • I.T. Executives could be exposed to financial liabilities for business damages as well as Business Executives
      • This has left I.T. organizations that recognize the need trying to cobble together or build from scratch their own model of a service delivery and management
      • While customers (internal and external) are judging them on their own performance criteria which may or may not match up to Service Level Agreements (SLAs) these organizations have stitched together often on criteria that customers do not see and therefore do not measure against  [i.e., network or server availability vs. service availability –what good is either to measure if they are not in sync to allow me to utilize the service e.g., the server was up 20 hours a day and the network was up 21 hours a day, however combined the complete service that required utilization of both was up only 18 hours (only 1 hour of the network outage overlapped the hours of server outage).  Server and Network availability where reported a poor 84% and 88% respectively, however the Service Availability the customer experienced was a dismal 75%.   That’s a quarter of the time a customer cannot use the service. Think of it as one in four times you go to use your car it wouldn’t work or worse yet, 6 out of every 24 hours a plane flies it just stops –hope you’re not over the Rockies during that window.