Best Practices: Are Your Company's Processes Mature?
The Capability Immaturity Model can help smaller businesses understand what is preventing their organization from establishing effective processes
The Capability Maturity Model (CMM) is a well-known process that's frequently used to determine the "maturity" level of an area or department within an organization. Within the IT world, the model is employed to help companies measure their ability to create, manage, and refine good processes for software development and other process-oriented work on a scale of 1 through 5.
For instance, companies that are creating processes on the fly with success only coming through the heroic efforts of its IT staff are in the initial, or first, phase of the model. Companies with processes that are well-established and are being followed are in the defined, or third, phase of the CMM. The core of CMM is the establishment of processes, following them, and refining them.
Critics of the CMM say that it does not encompass all the other areas that can impact the ability of an organization to establish and manage IT processes. One attempt to correct that is the Capability Immaturity Model (CIMM), conceived by Capt. Tom Schorsch. While it is a bit cynical and written in a tongue-in-cheek manner, everyone has probably experienced, at one time or another, individuals within their organization who matched one of these descriptions.
In the CIMM, there are four levels in which an organization can fail at establishing processes both passively and actively. These may help you in identifying and communicating just what keeps your organization from establishing and following good processes:
In a negligent organization, the desire is stated to do better, but the follow through is lacking. Multiple attempts are made at introducing established processes, but each equally impressive announcement is met with an equally impressive lack of follow-through. Has your organization decided to implement something like ITIL, Six Sigma or COBIT, only to abandon it later because no one is following it? Then your organization is negligent in its ability to improve processes. When there are no actions to meet stated desire, the stated desire is usually not actually a desire. Correcting this sort of behavior requires serious leadership ability and discipline. If possible, leading by example is the best way to demonstrate necessity and how improvements can pay off. Sometimes incentives need to be put in place to make actually following a new policy or process worthwhile.
"We've always done it that way." How often does change get met with that sort of response? It can happen often, especially when you have change-averse employees or someone who has been doing a specific task for a long time. This is difficult to overcome because the people blocking implementation have usually convinced themselves that the way things are working is fine and that any change could risk breaking things needlessly. Since the phrase "if it ain't broke, don't fix it" comes to mind here, the best course of action is going to be to find areas of the current process (or lack of process) that could be improved incrementally. With some incremental steps, it can be demonstrated that just because the current way is what has been done for years, it does not mean it is the best way.
5 Top Federal Initiatives For 2015As InformationWeek Government readers were busy firming up their fiscal year 2015 budgets, we asked them to rate more than 30 IT initiatives in terms of importance and current leadership focus. No surprise, among more than 30 options, security is No. 1. After that, things get less predictable.
Join us for a roundup of the top stories on InformationWeek.com for the week of April 24, 2016. We'll be talking with the InformationWeek.com editors and correspondents who brought you the top stories of the week!