Home » Application Knowledge Becoming Extinct » Recent Articles:

1 – Critical Application Knowedge is Becoming Extinct!

“The National Aeronautics and Space Administration (NASA) spent $24 billion in the 1960’s to send twelve astronauts to the moon.  Today they have to start all over again at an estimated $100 billion to  return a man to the moon. Why?  The engineers who had the critical know-how to send astronauts to the moon have either retired or died, taking the knowledge with them.  

If IT professionals do not do something quickly, practical application support knowledge will become a statistic of the Darwin Principle – EXTINCT!

1a – Application Support Knowledge Becoming Extinct!

The baby boomers are retiring at an ever increasing rate, critical IT application knowledge is moving off-shore at an ever increasing rate, and the work force is more mobile now than it has ever been. The IT industry is experiencing an unprecedented “Brain Drain” particularly within the IT application support environment. Who is going to be left behind to mind the store? Where will all the application support knowledge go that has been accumulated over many years?

1b – Application Support Knowledge Becoming Extinct!

When “Charlie” (the go-to-guy who fixes any serious problem) is gone who will take his place? How will others learn what took “Charlie” 10 to 15 years, if he is gone and all the critical knowledge was only in Charlie’s head?  

What took “Charlie” one hour to fix, may take several people many hours or days to fix.  This can lead to serious business interruption, project schedule overruns and a dramatic increase in application support costs.  

Loss of application knowledge represents a significant business risk and should be given the same consideration as the loss of any other critical business asset.  

Many IT executives say, “We have application documentation.” What IT executives should be saying is, “We have institutionalized our critical application knowledge and it is readily available by anyone who needs it.” However, in most cases this is not the case.  In this context there is a great deal of difference between “Application Documentation” and “Application Knowledge.”  

Application Documentation – Technical design and specifications

  • Created for developing the application, not supporting it.
  • Not organized in a way that makes specific content fast and easy to find
  • Badly out of date and reflects little of what the application looks like today
  • Current version is difficult to find and in most cases even more difficult to use
  • Does not reflect what lessons have been learned by the support SME’s (subject matter experts) over years of supporting the application
  • Written in “tech speak” and has very little use outside the IT organization – very little leverage with business users.  

Application Knowledge is – What is in the employee’s head

  • Knowledge gained over years of supporting the application
  • Practical knowledge used in support of specific application functions, output and users
  • Knowledge of application trouble areas and what is necessary to fix reoccurring or intermittent problems quickly
  • Critical application processing routings and calculations
  • Personal trouble-shooting utilities or processes developed over the years that are not common knowledge within the IT department
  • Knowledge of critical application components and how they effect the application
  • In-depth knowledge of data structures, their content and how the data applies to the business function they support

1c – Application Support Knowledge is Becoming Extinct!

Before any useful application support knowledge solution can be developed a prerequisite is an in-depth understanding of the application support environment and what is needed day-to-day by those who support the application. The following represent a small sampling of items that need to be addressed when developing any application knowledge solution: 

  • What application knowledge content is most useful and relevant to those supporting the application
  • Where is knowledge-content found? In what form? Who knows?
  • Does some of this knowledge content already exist? Where?
  • Can specific knowledge content be accessed quickly and understood easily
  • Is it in a form that is easy to use
  • Do standard knowledge content templates exist that can be used across many applications
  • Can application knowledge be used by others outside IT Organization: Application Users, Business Analysts, Developers, and Executives?

Successfully implementing any knowledge capture and management solution must include processes that the keep knowledge current. The most logical place is to update this knowledge within the service delivery process. Knowledge, like the application itself is dynamic and changes very quickly over a short period of time. These changes need to be captured when they occur and reflected in the Knowledge Repository.

 Finally, the knowledge delivery mechanism and navigation should be quick and easy, reflecting the needs of all those who may need specific application knowledge at any time.

 The question that business executives must always ask “is it worth it”? Will the benefit of developing and maintaining this application knowledge outweigh its cost? There will a different answer for each business; however, the place to ask this question is of those whose job it is to support the applications. Ask them: What would happen if “Charlie” was gone?

Preserve Intellectual Capital using CAI’s Application Knowledge Capture

The CAI AKC service offering reduces business risk by protecting critical knowledge assets:

  •  AKC offers protection of strategic application knowledge assets      
  •  Overcomes current constraints and risk resulting from consultants having all of the application knowledge in their heads and prepares the  IT executives for future direction from business management or emerging business needs
  • Enables greater flexibility and reduced risk in redeploying key application knowledge workers in strategic IT initiatives
  • CAI has 20+ years experience in developing and successfully implementing AKC for hundreds of clients
  • Core Competency – CAI has been successfully doing Application Knowledge Capture for 20 years – Defined processes, knowledge  templates, and web deployable knowledge artifacts
  • Minimal Disruption to Existing Staff
  • CAI has Focused/Dedicated Resources within its AKC Practice

 

The Return on Investment (ROI) for CAI’s AKC offering:

  •  Institutionalized access to the application’s architecture, components, critical threat areas and solutions
  • Reduced learning curve for new team members, application users and operational managers
  •  The ability to facilitate cross training
  • Mitigates reliance on key team members / SME contractors for fixing problems and questions from application users

 

 Risk Mitigation

  • Increase accuracy of application enhancements / maintenance and support estimates
  • Increase accuracy, reduced time of problem of problem identification and solution implementation
  • Reduce dependency on knowledge residing solely in the heads of specific individuals (system guru’s)

                                   

 Becomes the Platform for system functionality definition if system needs to be replaced

Our Sponsors

IT Support Services Comments

  • Network Management Service: IT is connected to business. Good IT services help in business. The objectives of IT must be framed by aligning it with business requirement....
  • IT Support Services: The post is really good and is very descriptive. The discussion provided is very clear. Thanks for sharing this post regarding the IT services provided....
  • Connor: Absolutely agree with alosmt everything you wrote. And about time there was a voice of dissent as I’ve been alone in the wilderness for too long! ITIL v2 was pretty good as a framework but then ...
  • pudin: Spot on. ITIL is a load of old Tripe. ITIL is a fwremaork but it is common sense. We have stopped all ITIL training.Peer to Peer learning and focus groups have delivered better and more measurable ...
  • Woo: Stopping in for a quick hi to Mary and Lesli. Great intirveew! I didn't even know we're supposed to count our WIPs. Guess I need to pull out the ol' file.Kudos to the parents/grandparen...

ITIL V3 Application Support Q & A

If you have any question on the blog content or have some specific question on how ITSM & ITIL can dramatically improve performance and reduce the cost of your Application Support service "Ask Bob"
Question :
Answer :
Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Computer World on "How to create Meaningful IT Support SLA's"  use this link...
Question :
Answer :
Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the folks who developed the original CMM  were not really initially inter...
Question :
Answer :
Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you want to be "proactive" in stopping this practice" you must capture bu...
Question :
Answer :
Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, and how many technical support calls from users you get and the average...
Question :
Answer :
Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on their own without any instruction to do so and it affects other user...