Systems as Care
The best systems do not control people. They reduce uncertainty, protect attention and make good work easier to do.
Category:
Systems Thinking
Author:
Ana Andersen
Read:
4 mins
Location:
Norway
Date:
When people have to carry the system
There is something I keep noticing in organisations. A process works because one person remembers everything. Someone knows who needs to be asked. Where the latest file lives. Which decision was made three meetings ago. Who needs reminding. Which exception applies this time. From the outside, the system appears to work. But often, it is really a person holding it together. And the moment that person is unavailable, things become slower, less certain and more difficult than they need to be. I have become increasingly interested in this because I don't think structure is only an efficiency question. Good systems are an act of care. They reduce the amount of uncertainty people have to carry in their heads. They make expectations clearer. They protect attention for the work that actually requires judgment, creativity and expertise. A good structure should not make people feel more managed. It should make good work easier to do.
Structure should reduce friction, not create it
Structure often gets associated with control. More approvals. More templates. More rules. More reporting. But adding structure and designing a good system are not the same thing. For me, useful structure starts with a different question: Where is unnecessary effort being created? Sometimes the problem is unclear ownership. Sometimes different teams are working towards goals that make sense individually but pull the organisation in different directions. Sometimes knowledge lives almost entirely inside people's heads. And sometimes a strategy exists, but nobody has designed the path between the strategy and the hundreds of everyday decisions required to make it real. This is where I tend to zoom out. Not because every problem needs a complicated framework, but because the visible friction is often being created somewhere else in the system. One department can optimise its process perfectly while making the experience worse for everyone downstream. Every part can be working hard without the whole working particularly well. The goal, then, is not to design more process. It is to build just enough structure for people to understand the direction, make better decisions and keep moving without unnecessary dependence on one another.
A good system leaves room for people
The systems I find most interesting are not rigid. They provide enough consistency to create trust, but enough flexibility for people to use judgment. They help knowledge survive when someone leaves. They make decisions easier to understand. They reduce repeated conversations about things that have already been decided. And they create a shared foundation without assuming every situation should have exactly the same answer. That matters because organisations are human systems. People need clarity, but they also need autonomy. They need direction, but also room to question it. They need accountability, but not unnecessary layers of permission. I think hierarchy can be useful when it supports those things — when it helps information move, decisions happen and people understand where responsibility sits. It becomes less useful when the structure itself creates distance from the work. This is probably why I keep returning to systems thinking across seemingly different areas — brand, customer experience, strategy, sustainability, leadership and organisational design. Underneath them, I am often interested in the same question: How can we design the conditions that allow people to do better work? Not by removing complexity entirely. But by making sure people are not carrying complexity the system could have carried for them. "Good systems are an act of care. They reduce the mental burden people have to carry so they can focus on the work that actually needs them."
