Turning ROT into ART: Why Humans and Governance Are Your AI Readiness Foundation

(This post was originally shared on my LinkedIn Profile.)

We talk obsessively about AI readiness. Plug in the right tools, train the model, scale the adoption. But I keep hearing the same quiet concern in rooms full of knowledge and learning leaders: What happens when we feed the beast garbage?

The garbage has a name: ROT. Redundant, obsolete, trivial content. And if you’re serious about AI readiness—or frankly, about knowledge management at all—you need to stop treating ROT disposal as a nice-to-have technical task. It’s a governance problem. It’s a people problem. And it’s non-negotiable.

The ROT Problem Is Your AI Problem

Here’s the uncomfortable truth: the organisations struggling most with AI implementation are the ones drowning in ROT.

Redundant documents that say the same thing three different ways. Obsolete processes locked in PDFs from 2015. Trivial information cluttering search results so badly that finding what you actually need takes longer than just asking a colleague. Add multiple systems, no single source of truth, and inconsistent version control, and you’ve created a perfect petri dish for training data that’s incomplete, contradictory, or simply wrong.

Now feed that into an AI system. The model doesn’t know intent. It doesn’t know that the 2015 process was replaced by something newer. It can’t distinguish between the authoritative procedure and the three near-duplicates authored by well-meaning teams in different divisions. It learns from what you give it. Garbage in, garbage out—but faster, at scale, and with the veneer of algorithmic confidence.

That’s not an AI problem. That’s a governance problem. Which is a people problem.

Enter ART: Accurate, Reliable, Trustworthy

The antidote to ROT is ART: content that is accurate, reliable, and trustworthy.

Accurate means it reflects reality as it currently stands. The process described is the process actually followed. The policy hasn’t shifted. The template is current. Accuracy requires human judgment—someone who understands the business has to say, “This is true today.”

Reliable means it’s consistent and findable. Identical information doesn’t exist in five formats. Metadata is correct. Version history is transparent. There’s a clear path to the current, authoritative version. Reliability requires governance: standards, ownership, maintenance schedules.

Trustworthy means people believe it enough to act on it. That only happens when they’ve seen it stay accurate and reliable over time. Trustworthiness is built through culture—through demonstrating that the knowledge function takes stewardship seriously.

None of these are technical properties. They’re human commitments, enforced through governance structures.

The Governance Gap

Here’s where most organisations trip. They treat quality as a technical project: cleansing tools, metadata standards, taxonomy implementation. These are important. But without governance, they’re cosmetic.

Governance asks the hard questions:

  • Who owns this content? (Not who wrote it. Who’s responsible for keeping it true?)
  • Who decides what’s redundant, and by what criteria? (Delete the 2015 process, but who makes that call, and what if someone was relying on it for context?)
  • When does content become obsolete, and who’s checking? (That vendor partnership doc from 2012—is it history or a hidden liability?)
  • What happens when we find contradictions? (Two teams think they own the same process. Now what?)
  • Who’s accountable for trustworthiness? (Not a system. A person or team.)

Governance without people is theatre. But people without governance quickly become overwhelmed, inconsistent, or burnt out. You need both.

Keeping Humans in the Loop

This is where AI readiness becomes interesting. The temptation is to assume AI can automate the governance problem away—classifiers that identify ROT automatically, algorithms that spot inconsistencies, systems that flag obsolete content.

Some of that is useful. But it’s not sufficient. And if you try to make it sufficient, you’re back where you started: garbage in, garbage out.

Humans stay in the loop at the critical junctures:

Defining what matters. What counts as redundant rather than useful context? What’s a necessary variant rather than an inconsistency? These are judgement calls. Tools can flag; humans decide.

Ownership and accountability. An algorithm can tell you content needs updating. A human has to take responsibility for updating it, and for saying “I’ve reviewed this and it’s true.”

Interpretive consistency. Policies that sound the same might apply differently in different contexts. Humans who understand the business catch that. Algorithms amplify the confusion.

Escalation and exceptions. ROT-clearing sometimes reveals gaps or conflicts in your business logic, not just your documentation. Those need human attention, not automated resolution.

The goal isn’t to remove humans from governance. It’s to remove humans from the repetitive, low-judgment parts so they can focus on the parts that require discretion, accountability, and real understanding.

The Real ROI

Organisations that have tackled ROT properly—through committed governance, clear ownership, and sustained human attention—report something interesting: it’s not just cleaner data. They report faster decision-making, fewer duplicated efforts, lower training time for new staff, and better cross-team collaboration.

And when they do deploy AI, it works. Not because the tool is magic, but because the foundation is solid.

The quiet concern I keep hearing? It’s legitimate. You can’t automate your way out of a governance problem. But you can solve it. It just requires treating knowledge stewardship as seriously as you treat technology adoption.

That’s the difference between readiness and recklessness.

Knowledge vs. Learning vs. Information vs. transfer

I just recently received an email about disaster preparedness, it contained a scan of a document that the person who sent it to me had received. What does this have to do with KM?

Nothing and everything.

The point the person who sent me the scanned document was making was that he had received this document in the middle of summer, while people were away on vacation, it was poorly produced, there didn’t seem to be an electronic version available, and he believed that if any of these floods, fires, earthquakes etc. ever happened (or maybe that should be when they happen), he wouldn’t be able to remember the information in the document (which was about 10 pages long), and if he remembered that he had received this document, he wouldn’t be able to find it again.

Again, so what you say? What does this have to do with KM or learning or information or anything at all?

Well, if we are doing knowledge management, or learning management or information management we need to be concerned about how knowledge/information gets transferred and shared. How do the users want to receive it? What is their environment like? What circumstances will they be using this information/knowledge in? Who is going to be using this knowledge/information.

If we don’t design our systems and processes with the users in mind, all of the users, not just some of the users, they won’t use the knowledge/information and then what good is all the effort we put into implementing our KM/Learning/Information program?

Notes from KM Legal Europe January 2015

I attended KM Legal Europe last week in Amsterdam; I enjoyed the conference very much. I got to talk with many of the speakers and attendees and learn more about what the law firms and corporate legal departments in Europe are doing in the KM space. I was impressed by their thoughtfulness and recognition of the fact that KM can bring them efficiencies and effectiveness as well as innovations and competitive advantage. They were a passionate group of practitioners.

While KM in law tends to focus on documented knowledge because of the nature of the sector and the need to track matters and precedents, there were discussions of lessons learned and sharing tacit knowledge too.

One of the things that (pleasantly) surprised me, was the discussion of automated document creation, when I have spoken with other organizations (not just law firms) about this technology they haven’t even known what it was, so to sit in a room where many were enthusiastic users was refreshing.

Other things that I found refreshing were the discussion of continuous improvement, six sigma, and process re-engineering. Again, all things that utilize an organization’s knowledge and especially, at least in my mind, the use of lessons learned processes and activities. This probably deserves its own blog post, as the participants were quite interested in this area and unfortunately we ran out of time.

One final thing that I found gratifying was the group’s willingness to not only share and learn from each other, but the interest in my experience working in other industries and sectors. They seemed to recognize that KM is KM and that they were behind many other sectors, so there were many things that they could learn from those who have gone before them.

All-in-all a wonderful few days with wonderful people, so glad I was able to take part.

KM in Law Firms: compare and contrast

(this is a slightly longer version of an article that I published in the Knoco March 2013 newsletter, one of 5 flavours of KM that were discussed)

In many law firms knowledge management starts in the IT department, and in a few cases, the library and like in many other organizations is focused on document management and technology. Also in common with other organizations law firms are dealing with pressure to reduce costs, be more efficient and effective for their clients, address issues of an aging workforce, and the technology demands of freshly minted lawyers who expect near instant access to knowledge.

There are also differences in KM inside a law firm. While in many organizations KM focuses on not just access to information/knowledge but on learning from mistakes, e.g. after action reviews and lessons learned processes and databases, this seems almost totally absent in law firms.

As I prepared to write this article, I wondered if I had just been missing something because of my limited exposure to KM in law firms. Maybe there really was a learning focus that I was missing out on; but in the research scan I did to supplement my experience, I didn’t find what I was looking for.

Now, don’t get me wrong, there is KM being done in law firms, but it focuses on documented knowledge. A fine activity, and definitely about connecting people to the knowledge they need to do their jobs, but not specifically learning focused and not focused on innovation as is often the case in other organizations.

It seems lawyers see knowledge management as a way to:

  • Give the firm a competitive advantage since the firm’s know-how becomes more easily accessible
  • Increase productivity: lawyers don’t waste time searching for information
  • Improve practice support by fostering collaboration
  • Speed response time to client requests
  • Provide an on-ramp for junior lawyers to get up to (billable) speed more quickly
  • Help integrate the “practice of law” and the “business of law”[1]

Now, I have done work with Steven Lastres, the author of this work I’ve just cited, and have the highest regard for what he is doing in his firm, which is leading the way for KM in law firms, but by not including the learning aspect of KM it seems to me that law firms are missing something.

One of the presentations that I attended at KM World 2012 was Eric Hunter’s, “Innovation, Change Management, & Business Optimization.” Eric Hunter is another leader in the law firm KM sector. What they are doing at his firm is moving towards that learning objective through collaboration and social technologies[2].

If law firms are lagging behind other organizations, the question that comes to my mind is why? In my experience law firms are conservative and risk adverse. They believe that only a lawyer understands their business, which has resulted in people with a CKO (Chief Knowledge Officer) type title at law firms being lawyers, and the main people on their teams are other lawyers and librarians. This lack of diversity on their teams and lack KM specialists specifically, I believe, has led to the focus on documented knowledge.

There is a shift happening, however. Law firms are starting to look outside their industry to see what lessons they can learn from other industries and from KM specialists. I have been doing a series of workshops and webinars for law librarians. The participants in these sessions have been engaged and interested to learn the lessons that I have to share from my experience in other industries. And I have been glad to share my experience and let them know that they are not alone, that the challenges they face are the same challenges that any KM leader faces; somehow there’s comfort in that knowledge.

Note: Connie Crosby and I have also just launched a KM Strategy assessment service for law firms, feel free to get in touch if you’re interested in learning more.



[1] Lastres, Steven, “Knowledge Management in Law Libraries: The Role for Legal Information Professionals” presentation at CALL ACBD Conference, from https://www.callacbd.ca/en/webfm_send/1274, February 28, 2013.

[2] Hunter, Eric, “Law Firms of the Future: Driving Intranet Evolution with Google+”  from https://www.bradfordbarthel.com/Eric/LM-JulyAug2012-ForwardThinking.pdf on February 28, 2013.

LawTech Camp, KM Technology discussion

A few weeks ago, I participated in LawTech Camp in Toronto. Connie Crosby and I were launching our beta-test for our Law Firm KM assessment tool, so we had an opportunity to do a demo presentation and talk about KM, I’ve posted the slides on SlideShare, click on the <demo presentation> or <about KM> links to see the slides.

There was a lot of discussion both during and after the presentation about one of the slides, so Connie wrote a blog post about it, which you can see here: https://www.slaw.ca/2012/06/11/km-101-more-on-technology-complexity/#top.

 

KM helps you be lazy!*

Imagine this scenario: you’re working hard on a project or task, you’ve got a deadline you’ve got to meet, but you’re stuck, you don’t know how to finish.

What do you do?

Well, if you are experienced in the ways of knowledge management you:

  • ask your colleagues,
  • ask the Community of Practice you’re a member of,
  • search in your expertise location system or yellow pages at peoples profiles,
  • post something on your internal Q&A or social media application,
  • you search your corporate document management system, ECM system, or other such repository/repositories to find the answer.

And you find the answer, doing considerably less work than creating the solution yourself and you meet your deadline. With all that time you saved you take a couple of minutes to post the solution, so that someone in your shoes days/weeks/months/years from now can find your solution and be lazy too!

*Thanks to Kathleen Wilson for the idea for this post.

The Difference Between KM and IM

Check out this exchange about the difference between KM and IM https://www.nickmilton.com/2011/10/question-or-short-rant.html?utm_term=knowledge+management&utm_source=twitterfeed&utm_medium=facebook