When Trauma Meets “That’s the Process”

There is a sentence we hear far too often in organisations:

“That’s the process.”

Sometimes it is said as an explanation. Sometimes as reassurance. And sometimes, if we are being truthful, it is simply used to close down the conversation.

I believe in processes. I believe in policies, boundaries and good governance. Organisations need them.

But I don’t believe we should become so attached to the systems we create that we stop asking whether they are actually working.

Because a process can be perfectly compliant on paper and still cause harm in practice.

It can ask someone to tell their story again and again.

It can duplicate information that already exists.

It can add another form, another handover, another person, another wait.

It can create so much administration that the people doing the actual work spend more time feeding the system than supporting the people the system was created for.

And eventually, people start finding ways around it just to get the job done.

That should tell us something.

Trauma-informed doesn’t mean process-free

This is something we talk about a lot through our work at Nova & Root.

Being trauma-informed doesn’t mean removing structure, boundaries or accountability.

Quite the opposite.

Good systems can create safety.

Clear processes reduce uncertainty. Good policies protect people. Clear roles help people understand what is expected of them.

But being trauma-informed also means being willing to look at the impact of those systems.

Not just:

Is everyone following the process?

But:

What is this process actually doing to the people experiencing it?

Is it helping?

Is it making someone repeat something they have already shared?

Is it creating unnecessary delays?

Is it adding pressure to an already stretched workforce?

Are we collecting information because we genuinely need it or because we have always collected it?

Does everyone involved even understand why each step exists?

And one of my favourite questions:

If we were designing this today, knowing what we know now, would we still design it this way?

If the answer is no, why are we still doing it?

A review date doesn’t mean “do not touch until then”

Most policies and procedures have a review date.

Of course they should.

But somewhere along the way, we can start treating that date as permission not to look at something until then.

A review date should be the latest point at which we formally review something. It shouldn’t stop us changing something sooner when practice is telling us it isn’t working.

If staff keep raising the same barrier, listen.

If people accessing services are telling us something is confusing, repetitive or difficult, listen.

If teams have created five unofficial workarounds just to make a process function, definitely listen.

We shouldn’t need a crisis before we give ourselves permission to change something.

And yet organisations do this all the time.

We wait until the backlog is unmanageable.

Until somebody makes a complaint.

Until staff are exhausted.

Until something goes wrong.

Then suddenly we review the process everyone has been saying wasn’t working for months.

Someone always carries the broken bits

This is the part I think we sometimes miss.

When a system doesn’t work, the work doesn’t disappear.

Someone carries it.

Usually people.

Staff stay later.

Managers pick things up.

Teams create spreadsheets.

Someone sends another email.

Someone makes another phone call.

Someone repeats their story.

Someone waits longer for support.

Someone absorbs the frustration.

And eventually we start talking about resilience, workload or wellbeing without asking whether some of that pressure is being created by the organisation itself.

That is why, at Nova & Root, we don’t see trauma-informed organisational work as simply training people to understand trauma.

It has to go further than that.

We look at the structures around people too.

Policies. Processes. Leadership. Culture. Decision-making. Communication. Where responsibility sits. And what happens when the written process meets the reality of the work.

Because you cannot ask people to work in a trauma-informed way while placing them inside systems that repeatedly create unnecessary pressure, uncertainty or harm.

Review before crisis

One of the simplest questions we can ask in an organisation is:

What no longer needs to be this difficult?

Not everything needs a transformation programme.

Sometimes the form just needs to be shorter.

Sometimes two processes need to become one.

Sometimes nobody knows who owns something and we need to decide.

Sometimes a policy written three years ago simply doesn’t fit the organisation we have today.

And sometimes leadership is simply having the courage to say:

“This isn’t working anymore. Let’s change it.”

For us at Nova & Root, that is part of what trauma-informed leadership looks like.

Not another framework sitting in a folder.

Not another set of values on a wall.

Not asking people to become more resilient so they can tolerate systems we already know aren’t working.

It is being willing to look at what we have created, listen to what people are experiencing and change things before the crisis forces us to.

Because “that’s the process” should never be the end of the conversation.