Month: August 2021

Something that has made me alternately frustrated, depressed and extremely angry in the last few months is that there appears to be NO research about the impact of classification scheme design on records management system usage.

In the face of no research, I’ve had many arguments with long standing practitioners who tell me that the practices we use are “well proven” – while conveniently ignoring rates of systematic control of records between 10 and 20%, and the FACT that when you put people on a windows file server and let them organise their own information, they happily implement a classification scheme that makes sense to them and use it. Incidentally, the classification scheme they are using is very different to the one we try and implement for them.

The most infuriating piece of practice I keep running into concerns variable terms and non-variable terms. No one in records management seems to like the idea that there’s a variable term above a non-variable term.

This means that we try and implement a project classification scheme that makes many people go somewhere else. The example that keeps coming up is project management.

Project managers universally (in my experience) want –

Project name –> Project stages

This is how they think about their work.

What we seem to want them to deal with is

Project Stage –> Project Name.

This is apparently considered “best practice” and “proven.”

It makes project managers go somewhere else – where they inevitably create a file structure that goes Project name –> Project Stage.

This structure is also copied in EVERY SINGLE PIECE OF PROJECT MANAGEMENT SOFTWARE that I’ve ever seen. None of them start at stages and move down to projects. NONE.

To recap –

• Project managers organise their information in a certain way.
• Project management software vendors organise the information in the same way.
• Records managers do it differently.
• Records managers can’t get project managers to use their systems.
• The way records managers do it is “proven” and “best practice.”

We could argue about the virtue of a static number of stage files above a potentially unlimited number of project files, but that is an academic argument that still sees project managers not knowing how to deal with what we’ve created and going somewhere else.

We could also argue about the problems of variable terms above fixed ones – but it is something we do for our convenience and the convenience of system vendors, not the people that we actually need to use the system.

Lets move on to woolworths.

I am 100% comfortable saying that their classification scheme does not stand up to records best practice. Simply looking at their drinks shows you that they’re not interested in a “best practice” classification.

You’ve got Coke in the “drinks” section with 180kj/100ml of energy. Monster in the “energy drinks” section with 9kj/100ml of energy, milk (a drink) in the dairy section with 247kj of energy/100ml, orange juice (drink is broader than juice) in the “juice” section with 180kJ/100ml.

So why do they organise their stores like this?

Simple – they’re in it to make money, and they know that organising the stores like that is more effective.

And to me, that should be the iron rule of classification.

Do what is effective.

If you implement best practice and usage goes down, back it out. If you implement terrible classification practice and usage goes up – stick with it.

Records management is not struggling because we have a shortage of best practice.

Records management is struggling because we can’t get people to use our systems.

We should take a leaf out of woolworths book and organise the information we have in the way that gets us what we want.

And what about classification to ensure we have good archives and can classify according to disposition needs?

The problem we have at moment is getting people to put information in the systems. If it never gets into the systems, it’s never going to get to archive, and if we never get control of the information disposition and our profession become irrelevent. It has to get in the system first.

The only iron rule for classification scheme development should be “do what gets people using what you’ve built.”

User experience research.

I think it’s the core of what’s missing from records management.

We have a unique value proposition – which is the concept of business evidence and it is timeless and will be fit for purpose forever. But…

20 years ago a different group of people started doing records management.

Records management went from being done by professionals to being something that was done by people using what professionals had built.

Simply put, 20 years ago, we started to have to look after users.

But no one has ever trained us to look after users.

Universities don’t teach us how to look after users.

There’s no research into the the link between how we build systems, and the effectiveness of those systems.

And we can’t get them to use what we’ve built.

Because we have rules of thumb that worked when we didn’t have users but that I think now actively work against adoption by them.

Rules like “you can’t have a fixed term above a variable term” in a classification scheme – which are convenient for us, but which I think mean that people who would use our systems go somewhere else.

Don’t agree?

That’s the problem – there’s no agreement, no central pool of research that says “this works, this doesn’t.”

There’s no A/B testing.

No card sort.

We need user experience focused research to tell us why we can’t get the bar up.

We need it to save us from the practices that used to work.

If you’re already doing this, know someone who is, or would be interested in doing some research in the area, I’d love to talk to you about it – please reach out https://www.linkedin.com/in/karlmelrose/

Recently I’ve been discussing records practice with people and looking for the evidence that it is succeeding.

The thing that keeps happening, is that we reach a point on a discussion of a practice where whoever I’m discussing it with will say “it’s well proven” – or something to that effect.

What is interesting about this, is that the anecdotal feedback I get from the organisations I talk to is that records practice is currently gaining systematic control of between 10% and 30% of records.

To me, this doesn’t say that practice in its current form is succeeding.

Logically, this means that the proven practices that we have need to change.

I think that the records regulatory authorities know this.

In the last couple of years we’ve seen frameworks go from completely prescriptive with metadata standards that were very difficult to implement, to frameworks based on a handful of principles, and 3 – 5 pieces of metadata.

I also had an opportunity recently to pose a question about whether the model of sentencing and disposition we have is fit for purpose to a RIMPA panel of two directors of state records, and an assistant director from National Archives. One of the directors said that he didn’t think it was fit for purpose – but also that he didn’t currently have an alternative.

What this all points to for me, is that we have to re-examine what “proven” means.

The core of our profession is high quality evidence of business practice.

The practices that we have are supposed to produce this.

If they aren’t, they need to change.

The question is, how do we know what needs changing?

I think complexity theory has the answers for us here. When dealing with complex problems, complexity theory tells us that we should run multiple “safe to fail” experiments and when we find evidence that one is more effective – we do more of that.

Ultimately, the question that we need to answer for everyone is “how much of our practice is proven, and how much is effective?” The only way we’re going to know is by finding evidence that what we do is more effective than the alternatives, and the only way we can do that is to try the alternatives.

If you’re already doing this – I’d love to hear from you and I’d love to take an opportunity to share your story (good or bad) – so please leave a comment or find me on LinkedIn.

It means to use something built by a professional.

We have to rememebr this, because the vast majority of records best practice is developed by professionals for professionals.

We are a profession with 5000 years of being done by professionals, for professionals.

The problem though, is that the vast majority of records management is now done by users – and this has only been the case for about 20 years.

So we have a problem.

5000 years of professional records management.

20 years of users.

Our training and resources teach us how to think like professionals.

This means that if we build systems based on our training and resources, we’re going to build things that only professionals can easily use.

And I think that probably explains quite a lot of our problems.

The question we all need to ask every day is “have I built this system* to be easily understood by the users I have, at the maturity level they are at.”

*System in the general sense, including but not limited to the IT system sense.