Not usually as anger. More often as a low-level irritation. A sense of heaviness. The feeling that something keeps repeating but is hard to name.

It’s often treated as noise.

Something to manage. Push through. Stay professional about.

But in complex systems, frustration is rarely random. It’s usually early data.

It appears when roles are misaligned. When expectations are unclear. When responsibility increases without a corresponding increase in authority or permission.

In those conditions, frustration isn’t a personal shortcoming. It’s a signal that the system is asking for something it hasn’t been designed to hold.

What tends to happen next is predictable.

Capable people look inward. They ask whether they’re managing well enough, communicating clearly enough, coping properly.

Meanwhile, the system stays the same.

Nothing about this is dramatic. That’s part of the problem. Systems don’t usually fail loudly. They drift. And frustration is often the first indication that judgement is being put under pressure.

If you’re in a role where you’re relied on, trusted, and carrying responsibility, it’s worth pausing here.

Not to fix the frustration. Not to override it.

Just to notice what it might be pointing to.

In the next few pieces, I want to explore what happens when we start treating frustration as information rather than interruption, and what becomes visible when we do.

For now, it’s enough to recognise this:

Frustration isn’t always the thing to get rid of. Sometimes it’s the first thing telling you the truth.