_:n2f1b74048e8040a699b78b7a5c13e707xb0
<http://schema.org/articleBody>
"It might sound like something that lurks in damp soil, but process ROT is actually becoming a widespread problem for many organizations.\r\n\r\nProcess ROT occurs when established business processes become hampered by redundant, obsolete and trivial (ROT) information. It's something that's happening within large numbers of organizations, yet many are not aware that it is occurring, nor are they aware of the potential risk and <span style=\"color: #0000ff;\"><a style=\"color: #0000ff;\" href=\"https://www.corporatecomplianceinsights.com/category/compliance/\">compliance</a></span> implications.\r\n\r\nROT becomes a business problem because humans tend to be natural information-hoarders. Throughout organizations, people tend to collect and store large volumes of documents and other materials and are very reluctant to ever delete them.\r\n\r\nThis type of hoarding is a big problem when it comes to efficient process and risk management. Multiple documents, or multiple versions of the same documents, can quickly become overwhelming. Finding the latest details on a process and how it should be undertaken can be difficult, if not impossible.  And if teams aren't clear on which process they should be following, it is very difficult to effectively manage and track compliance.\r\n\r\nIn many cases, project and business teams are left to figure it out for themselves. They have to determine what information really needs to be retained and the best system to use for that task.\r\n\r\nThe result can be the introduction of a number of different systems that are impossible to manage and control. Different departments or groups adopt their own approach with little or no regard for what is happening in other parts of the organization. This results in the continuing spread of ROT.\r\n<h3>The telltale signs of ROT</h3>\r\nThere is one sign that's a clear indication that process ROT has started or is likely to become a problem within an organization.  If teams are storing process-related documentation on a server or intranet, then the problem exists and is likely to get worse.\r\n\r\nAnother telltale sign is when staff experience difficulties searching for information about particular processes as they have no clear \"place\" in which to look. Rather than getting on with the task of using or monitoring the process, their time is wasted hunting down the appropriate information.\r\n\r\nThis situation is exacerbated when there are duplicates of documents or different versions stored in different places. Work may begin on a process only for staff to find that the steps they are following are out-of-date or have been replaced.\r\n\r\nOverall, having poor control over storage and access to process-related information makes it less likely those processes will ever actually be put to use. When information is no longer used, it is simply left to ROT.\r\n<h3>The cost of ROT</h3>\r\nProcess ROT can hurt an organization in a variety of different ways. It makes finding required information difficult, reducing productivity and lowering the impact of the processes that have been designed to add business value.\r\n\r\nAs a result, an organization can face a hit to its reputation and, potentially, an increased exposure to litigation. Teams may waste time searching for information that turns out to be outdated or misleading. The result can be increased complaints from users, a lack of faith in the process, noncompliance with industry regulations and the gradual erosion of brand values.\r\n<h3>How do you fix it?</h3>\r\nIn the past, many organizations have simply left it up to individual staff members to deal with the challenge of process ROT. However, because they often helped to cause the problem in the first place, it can be difficult for them to be part of the solution.\r\n\r\nThe key to fixing the challenge is the creation of a centralized business process repository. This repository should provide an easy-to-comprehend and visual structure of all information about each process in a single, accessible location.\r\n\r\nHaving a central database for company policies is not only beneficial during audits, it helps with version control and means teams will always have access to and be able to follow the most current, agreed-upon process.  And integrating risk and process management can improve compliance and risk management by ensuring that there is awareness and consideration of risk impacts at the time of a process change – not later in the year during an audit, which could be too late.\r\n\r\nHowever, it must be remembered that it's not enough to clean up ROT only to have it creep into the organization all over again. Planning, creation, maintenance and governance processes need to be put in place and work as hard as they can to prevent ROT from returning.\r\n<h3>The bottom line</h3>\r\nProcess ROT can be a significant staff engagement killer that can stop a process improvement program in its tracks and create avoidable risks. If left to grow, the impact on an organization will only become more detrimental over time.\r\n\r\nThe good news is the problem is readily fixable. It's a matter of establishing a well-designed knowledge repository in which all detailed and up-to-date information about processes can be stored, searched and accessed. By taking a measured and methodical approach, the problem of process ROT can be banished forever."
<https://www.corporatecomplianceinsights.com/does-your-organization-suffer-from-process-rot/>