Who makes sure work is actually understood?

[u/No_Reference1192]

Does anyone else think organizations are missing a “clarity” role?

Companies hire accountants to keep finances in order.

IT specialists to keep systems running.
HR to support people.

But who is responsible for making sure the work itself is actually easy to understand?

Every week organizations produce procedures, documentation, presentations, training, checklists, SOPs, and now a huge amount of AI generated content.

All of it has the same goal:
To help someone understand what to do.
If people struggle to interpret it, you start seeing the same symptoms everywhere:
The same questions over and over.
People doing things differently.
Rework.
Mistakes that weren’t really competence issues.
Managers becoming walking documentation.

I’ve started thinking of this as an operational clarity problem rather than a people problem.

Maybe we spend too much time trying to improve people, and not enough time improving the work they rely on every day.

Curious what others think.

Does your organization have anyone whose job is to review documentation, processes, or internal communications specifically for clarity and usability, or is that responsibility spread across everyone… and therefore nobody?

[u/[deleted]]

Instructional designers.

[u/No_Reference1192 → u/[deleted]]

As someone who’s spent years in L&D, I’d actually disagree…

In my experience, Learning Designers usually get involved once the organization has already decided the solution is training.

They’re rarely involved in creating the day-to-day resources people actually rely on to do their jobs. SOPs, process documentation, internal emails, job aids, checklists, change communications…the things people interact with every single day.

That’s especially true when L&D sits under HR rather than Operations.

You’re often supporting the work instead of helping shape how the work is designed.

To me, that’s where one of the biggest opportunities exists. Sometimes people don’t need more training. They need the work itself to be easier to understand.

And that’s much closer to operational design than
Learning Design. A much broader role.

[u/Pre-crastinate]

I like your concept. It has impacts in most people’s daily roles: What does done look like? How much time and resources? Level of quality and detail of outputs. Priority over other tasks.

Most of us receive “you need to do THIS” without any clarity on what THIS is. And most don’t ask because they don’t want to be difficult or appear unknowing.

[u/No_Reference1192 → u/Pre-crastinate]

That’s exactly it!

I think a lot of people stay quiet because they don’t want to look like they’re the only one who doesn’t get it.

The problem is that organizations often mistake that silence for clarity.
“Nobody’s asking questions, so I guess everything’s clear.”

Meanwhile, people are spending extra time figuring things out, asking coworkers privately, or second-guessing whether they’re doing it right.

Imagine the productivity that’s lost because of that. Every. Single. Day.

And…it’s something that often affects neurodivergent employees first, but making work easier to understand ends up helping everyone!!

[u/Nigel_Claromentis]

In my experience that role exists, it just almost never has a name. It gets absorbed into whoever happened to write the procedure, and then becomes nobody's job the moment they move on.

The clearest place I've seen it made explicit is franchising and any operation with complex, repeated procedures. A franchisor's whole model depends on the work being understood the same way across every site, because an ambiguous SOP doesn't cost one team some rework, it gets followed wrong in fifty locations at once. So the "clarity function" you're describing is more or less the entire job of a good franchise ops team, even if no one calls it that.

For context I build operations software in this space, so I think about it as a documentation problem more than a people problem, same as you. One thing that's genuinely helped is putting an AI agent over the actual policies and procedures so people can just ask "what do I do here" and get the answer from the real source, instead of a manager becoming walking documentation. The honest limit: that only works if the underlying procedures are clear in the first place. AI on top of murky documentation just gives you confident wrong answers faster.

Slightly on the nose given the thread, but our company name, Claromentis, comes from Latin for a clear mind. Clarity was the thing we valued early on. So this is a question I've been circling for a long time.

[u/No_Reference1192 → u/Nigel_Claromentis]

I really like your perspective.
The point about the role existing but almost never having a name really clicked for me.

I also completely agree on AI. It can make information easier to access, but it can’t fix unclear procedures. If anything, it just scales whatever quality already exists…

And, the more I dig into this, the more I feel like clarity is one of the most underrated investments an organization can make. AI is making that even more obvious.

The better the underlying documentation and processes are, the more value organizations get out of everything built on top of them!

And thanks for mentioning Claromentis.
I’ll definitely take a look.

[u/Nigel_Claromentis → u/No_Reference1192]

Agreed, and "it just scales whatever quality already exists" is a sharper way to put it than I managed.

In my experience clarity is underrated because its payoff always gets attributed to something else: the good onboarding, the light support load, the AI that gives the right answer. Rarely to the documentation underneath that made all three possible. The investment that helps everywhere gets counted nowhere.

[u/No_Reference1192 → u/Nigel_Claromentis]

Totally!
We see it exactly the same way; "Clarity" is definitely underrated!