CA Community






This Blog

Lean GRC: Focus on Individuals Who Add Value

Published: July 07 2009, 05:05 AM
by Sumner Blount


In an earlier blog posting, I introduced the topic of Lean GRC, an area that has started to get some attention recently. To summarize, it takes the principles of Lean Production (as exemplified by Toyota in the 90s), and applies them to risk management and compliance. In a follow-on blog posting, I talked about one of the most important concepts of Lean "" the elimination of waste. Many companies have significant amounts of redundancy and waste in their GRC processes, so this is an area that's ripe for improvement.

As we all know, one of the key elements of Lean Thinking is to identify process steps or processes that do not add value to the customer, and eliminate them. Very important "" but certainly easier said than done.

In this blog, I'd like to talk about another key concept of Lean "" "Focus on individuals who add value." At first blush, this might appear to be a thinly-veiled advocacy for large-scale layoffs. "Find the laggards and get rid of them!" Sounds harsh "¦ and that's not really what this principle is focused on.

The important message of this principle is that we should transfer responsibilities and ownership to those individuals who have the potential to actually add value to the process. In many cases, adding value implies that these people have information that other people might not have, or get access to the information earlier in the process than others. In GRC (as in many other areas of business), knowledge, to some extent, is power. We need to find those people who have unique information, or have it earlier, and make them "key cogs" in the GRC process that uses this information.

This implies that we need to assign GRC responsibilities to key people on the "front lines," so that their added-value is leveraged as much as possible. Let's get a bit more specific so this is clearer.

Many times, the people who are actually testing controls will have an "early warning" if there is an emerging risk related to that specific control. If, for example, they have to fill in forms or send an email to alert someone the next level up, which then gets passed along (at some point) to another layer of management, the impact of a control failure might not be obvious to upper management for awhile. In many cases, this might not be a huge problem. But, why design your internal processes in a way that doesn't effectively support the "boundary conditions" of a large control failure?

A better approach is to more directly integrate these front-line people (who have the important information) into your GRC processes. Allow them to immediately enter control results, which will then automatically adjust your overall risk and compliance profile. Upper management can then get a graphic indicator of this potentially important change in status immediately.

Controls testing is only a useful example of how this might work. Any other individuals who are key elements of any compliance process, or are the source of critical information, should also be the focus of any re-design or simplification of any business process.

This approach has a side benefit also. As we introduce GRC into all key processes, as well as focus on individuals who add value, we not only improve the quality of our information, but we help instill ethical, "compliance behavior" in employees at all levels. Some studies have shown that increased awareness of policy and ethical standards among workers tends to diminish inappropriate behavior. So, reasonable methods that accomplish this can be very effective.

In a subsequent blog, I will offer some thoughts on other key principles of Lean GRC, and you can visit CA's Lean IT site to learn more about our approach to help companies maximize value and minimize waste. As always, I'd love to hear comments, thoughts or anecdotes from your experiences that you would like to share.

*LeanGRC is a trademark of OCEG.

 

By: Sumner Blount
Sumner Blount has spent his 25-year career focused on the development and marketing of software products for a range of top-tier enterprise IT firms. Currently, he’s a Director in the Security business unit at CA. Previously he managed the large computer operating system development group at Digital...
Read More..

3 people have left comments:

Thanks to both of your for your comments. <br>Amol, you have summarized my point well, and I certainly agree with you that there is often significant resistance to change that must be faced. Improvements in business processes often generate resistance, but GRC (due to its breadth of impact) is particularly subject to this type of experience. This sounds like a good topic for a subsequent blog post. :-)<br>Kathy, I&amp;#39;m sorry that you found what you think are contradictions, because there are certainly none intended. As we know, GRC is a function of process, policy, people, culture, and technology. Improvements in any of these areas can have a beneficial effect on the entire GRC approach, and making people more efficient is certainly an example of this. So, I would disagree with your statement that &amp;quot;people adding value&amp;quot; is against the concepts of Lean GRC. Feel free to expand on your thoughts (either on the blog or directly to me) and we can discuss it further.<br>thanks for your readership

Posted by: Sumner Blount | October 1, 2009 12:03 PM

Great post indeed.<br><br>I think GRC is more about people, policy, process and progress. <br>Today, we are equipped with better GRC software, technology and proven frameworks and together we can add enormous value to the business, yet some people with influential positions do not want to change. No GRC solution can be effective unless it is adopted in the right spirit. The need of the hour is to keep the compliance and risk factors on the upfront and let the right person handle the right job.<br><br>Thanks &amp;amp; Regards,<br>Amol Bharti

Posted by: Amol Bharti | October 1, 2009 12:03 PM

This article does contain some contradictions in terms of who add value and how. It also indicate that GRC process is not understood or at least not clearly defined. <br><br>It starts off indicating the process add value and then converge to the point that &amp;quot;people&amp;quot; add value, which contradict the LeanGRC concept.

Posted by: Kathy Miller | October 1, 2009 12:03 PM

Leave a Comment

* An asterisk indicates a required field

* :  

:

* :  

 Submit