Serenita
←Back to all reflections
10/6/2026

Tools, Not Boxes

When frameworks help us understand and when they begin to limit what we see

Tools, Not Boxes

We like things to make sense.

When something feels complex, uncertain or difficult to understand, we naturally look for ways to organise it. We name things. We identify patterns. We create categories. We develop models and frameworks that help us make sense of what we are seeing and there is value in that.

A framework can give us language for something we have struggled to describe. It can help us notice patterns we might otherwise miss. It can guide our questions, inform our decisions and sometimes point us towards something that needs greater attention.

In counselling, we use theories and formulations to help us understand human experience.

In education and professional practice, we use frameworks to think about development, behaviour, learning, trauma, attachment and additional needs.

In organisations, we use models to explore leadership, culture, motivation, change and the systems within which people work.

Tools help us navigate complexity.

But there is a difference between using a framework to help us understand what is in front of us and using a framework to decide what is in front of us.

And that difference matters.

When a Lens Becomes a Label

The difficulty begins when the framework stops being something we look through and becomes something we put around a person, behaviour or organisation.

Once we believe we know which box something belongs in, curiosity can begin to disappear.

We stop asking:

What else might be happening here?

What am I not seeing?

Does this person's experience actually fit my assumption?

What is different about this context?

Instead, we begin looking for evidence that confirms what we have already decided.

A child becomes the difficult child.

A person becomes their diagnosis.

An employee becomes resistant to change.

A team becomes dysfunctional.

An organisation becomes a diagram of boxes, arrows and categories.

The language may help us describe something real but it can never describe everything that is real.

The Person Is More Than the Framework

This matters particularly when our frameworks concern people.

Two people with the same diagnosis may experience themselves and the world very differently.

Two children displaying similar behaviour may be communicating entirely different needs.

Two employees who appear disengaged may have very different reasons for withdrawing.

Two organisations facing apparently similar problems may have completely different histories, relationships, pressures and cultures beneath them.

The framework may tell us where to look. It cannot tell us everything we will find when we get there. That requires something else: curiosity.

Behaviour Is Communication But We Still Have to Listen

At Serenita, we often return to the idea that behaviour is communication. Yet, even that principle can become a box if we are not careful.

If a child becomes angry, we cannot automatically decide what the anger means.

If an employee stops contributing in meetings, we cannot know from the behaviour alone whether they are disengaged, exhausted, afraid of speaking, disagreeing silently, struggling personally or simply choosing to listen.

If somebody repeatedly avoids something difficult, the behaviour gives us information but it does not hand us the explanation.

Behaviour invites curiosity. It does not remove the need for it.

The same applies to the frameworks we use to understand behaviour. They can help us formulate possibilities. They should not give us permission to stop asking questions.

The Same Risk Exists in Organisations

Organisations are particularly tempting to reduce to models.

We map their cultures. Categorise leadership styles. Assess readiness for change. Identify resistance. Measure engagement. Analyse structures.

These tools can be enormously useful. They can help us step back from a complicated system and notice relationships or patterns that would otherwise be difficult to see. But an organisation is not the model we use to analyse it.

It is people.

It is relationships.

It is history.

It is formal structures and informal influence.

It is what leaders intend and what employees experience.

It is what gets said in meetings and what gets discussed afterward.

It is policies written on paper and the unwritten rules people learn through experience.

No single framework can hold all of that. So perhaps the purpose of an organisational model is not to give us the answer, but to help us ask better questions about the system in front of us.

Expertise Should Increase Curiosity, Not Replace It

There is an understandable comfort in certainty. Professionals develop knowledge and experience precisely so that we can recognise patterns and draw on what has been learned before but expertise carries its own risk.

The more familiar a pattern becomes, the easier it can be to believe we already understand what we are seeing. Sometimes professional maturity may involve being able to say:

This looks familiar but I don't yet know whether it means what I think it means.

That does not diminish expertise. It strengthens it. Good practice does not require us to abandon what we know. It requires us to remain open to what we do not yet know.

Tools, Not Boxes

Frameworks matter.

Theory matters.

Diagnosis can matter.

Models matter.

Assessment matters.

They give us shared language, accumulated knowledge and ways of approaching complexity that we would be foolish to discard. The question is not whether we should use them. The question is how we hold them.

Perhaps good practice means holding our frameworks firmly enough to benefit from what they can teach us but lightly enough that the person, behaviour or organisation in front of us is still allowed to surprise us.

A tool should help us notice. It should help us question. It should help us understand but it should never become more important than what we are trying to understand.

So perhaps, every now and then, there is one question worth asking ourselves:

Are we using our frameworks to understand what is in front of us or using what is in front of us to prove our frameworks?