I have created a post (Part 5.0) which contains the list of major documents that are necessary to run an ARIS Competency Center but this can be applied to any major competency center.
When you are buying a tool or creating a competency center - it is a method to secure the knowledge so that if any particular employee leaves the company then the tool does not become useless. The idea is that knowledge can be inherited organically without elaborate KT etc.
But there is a bigger role of these documents - what is that role?
Answer: Help the enterprise to get the ROI out of the tool. if we cannot achieve this then we have really not achieved anything. The ROI can be financial, which is very tangible, but it can also be in terms of social and other economic affect which does not affect the balance sheet directly.
Example: If you can provide a report which identifies all the hardware associated with a particular value chain or sister enterprise in 3 minutes instead of 17 days of research then you have really helped accomplish something. Remember its all about the output from the tool so the competency center should be geared towards supporting the outputs more than anything. If your customers do not get any ROI then they have no reason to provide any input.
Some of the companies I engage with do not have a requirements document or a ROI sheet. The chances of success of ARIS in such environment are pretty thin.
Hi Pinaki...
Your ARIS CC series is really comprehensive. Thanks for sharing it with us. However, in this article you have mentioned that "Some of the companies I engage with do not have a requirements document or a ROI sheet. The chances of success of ARIS in such environment are pretty thin"....what do you mean by this...Could you elaborate.
Thanks.
Deepti
Hello Deepti,
I will give you an example
When you buy a cooking tool you know exactly what you are going to do with it or sometimes you are going to learn to do something with it. But the point is that you have a plan. Rarely you go out and buy an extremely expensive cooking tool which you have no use for. Example: Somebody living in the city never buys a deer skinning knife unless they go hunting.
Similarly when you buy ARIS you are essentially buying a database so you must know the outcome you are trying to get. Its all about the output from the tool that is what makes the tool so special. You must know what kind of output you are looking for.
In future you can get more outputs and develop more solutions with the tool but that happens as you mature with the tool.
Over time in ARIS (or any repository based tool) you library size increases and that helps you to do more analysis and produce more results
