I am currently in the infancy of exploring Knowledge Management as a research topic using design thinking, specifically the problem relating to imminent retirements of many experienced contract & commercial managers coupled with the new gig economy and the different ways gen y & z embrace learning and governance.
Ie How do you capture this experience before it is gone and then bottle it for transmission in such a way that the new generations will utilise it to the fullest to ensure good governance and business efficiencies are maintained.
For IT services agreements I generally rely on the framework of ITIL ( Information Technology Infrastructure Library) - this informs on the various processes within IT and will give you a starting point to understand what needs to go into your playbook. It deals with both the vendor/customer aspect as well as for procurement.
In addition to all your suggestions, I would think that a self certification from all the stakeholders would serve as a good base for your update to the management unless of course you are using a contract management software that allows you to generate compliance reports.
I´d strongly encourage you to raise this question also within the IACCM technology network, which is a micro-community, where you will be able to get insights to new trends in this specific field and where I am sure you´ll have the opportunity to share ideas regarding the topic you have brought:
Also, please check our library: www.iaccm.com/resources/ where, you will find some articles about 'escrow agreements' for the software arena and other topics associated with risk management in the hardware world as well. By analogy you will explore ideas regarding hardware coming from best practices and escrow programs with the goal of risk mitigation
Hi Michelle - saw your post. For hardware: having a refresh plan with your supplier following a bit of a mutual benchmark, to see how best to provision for your upcoming capacity needs, might give some assurance. For services or subscriptions-based tech: having a documented 'cookbook' of key players and tech needed to recreate the service, including a list of any solutions 'not commercially available' or not easily re-purchased in Canada updated, might also be helpful to gage the difficulty of transitioning off your current tech,if needs be.
Those two governance-type processes, along with the typical supplier obligation to reasonably cooperate with any successor and to provide some mutually-agreed orderly termination assistance, might serve you well (outside escrow for software). Hope that offers some ideas...good luck. Cheers, Robin
We generally maintain a "benefits tracker". This tracker is maintained on a real time basis for all the tangible benefits delivered by the contract management team. This could be complex negotiation, CCNs, renewals, commercial support etc. This gets validated by business leaders. At the end of the year, we say $xxx value delivered to business by the contract management team.
Usually split into few areas: risk management and compliance, performance of vendors and cost management and savings
Agree - this was quite an insightful article. I've always believed that it should work in reverse - that you should set the objective and then leave it up to individuals to work out how to get there, which is what the article says except for specifying that their roles need to be clear. I believed that if roles were less clearly defined then it gave people scope to expand their remit, however I can see why this can cause confusion.