The Level You Engage At Decides What You Get

There are multiple ways to solve our problems.

There are also multiple levels at which our problems are solved.

We tend to notice the first and overlook the second. When something needs fixing, we look for someone who can fix it. A vendor, a service provider, a partner, a contractor. We compare their price, their experience, their availability. What we rarely ask is at which level they will engage with us. Yet that question decides more about the outcome than almost anything else.

The three levels

Think of it as a stack.

At the bottom: fixing problems. A problem comes in, a fix goes out. The relationship is transactional. Nothing more is expected and nothing more is offered. Once the fix is delivered, the relationship is complete until the next problem arrives.

In the middle: understanding what you want, and providing it to you. This is a step up. Someone listens, works out what you are asking for, and delivers it. They are responsive and agreeable, and they are often very good at it. This is the pleaser, the entertainer, the manager. You ask, and you receive.

At the top: understanding what you need, influencing you to get it, and helping you get it. This is the leader, the advisor, the consultant, the mentor, the parent. They start with your need, not your request. When the two differ, they tell you, and they work to move you towards what you need even when it is not what you came in asking for. Then they stay and help you get there.

The difference between the middle and the top is the one that matters most, and it is the easiest to miss. Both levels listen. Both are helpful. But one serves your wants, and the other serves your needs.

Wants and needs are not the same

A child wants sweets before dinner. A pleaser hands them over, and the child is happy. A parent understands that the child needs a proper meal, says no, explains why, and sits at the table until the plate is finished. In that moment, the parent is far less popular than the pleaser.

The same pattern runs through every relationship where one party relies on another to solve a problem.

What we want is shaped by what we can already see. What we need is often outside our view, which is exactly why we need someone else to help us see it. A provider who only gives us what we want can never give us more than we already understood when we asked.

A familiar example

Consider a council eighteen months into the replacement of its finance system.

The software vendor works at the bottom of the stack. Issues are logged, tickets are resolved, patches are applied. Each ticket is closed on time. Each fix works.

The implementation partner works in the middle. When the finance team asks for the new system to produce the same reports as the old one, the partner builds them. When the payroll team asks for a customisation to match the old process, the partner builds that too. Every request is met. The client is satisfied, and the partner is easy to work with.

Everyone is busy. The ticket queue moves. The change requests move. The status reports are green.

And yet the council is quietly rebuilding its old system on a new platform, at great expense, because nobody in the room is working at the top of the stack. Nobody has asked what the organisation actually needs from the change, or pointed out that each reasonable request is pulling the program further from the reason it was funded.

Nobody is failing. Each party is doing exactly what its level asks of it. The problem is that no one is engaging at the level the situation requires.

Busy is a signal

This is the part worth paying attention to.

Our condition improves dramatically if and when we move higher up the stack. When we are stuck with partners lower down the hierarchy, we keep busy doing work.

Busyness feels like progress. Tickets closed, requests delivered, meetings held. But at the lower levels, activity is what the relationship produces. Problems get fixed, and similar problems return. Wants get met, and new wants take their place. The work keeps coming because the underlying need was never touched.

When we engage at the top of the stack, the shape of the work changes. Fewer things get done, but they are the right things. Some requests get declined. Some problems stop recurring, because the reason they kept appearing has finally been addressed.

So the amount of work in a relationship tells us something. If we are constantly busy with a provider and the situation is not getting better, it may not be a question of effort. It may be a question of level.

It is a choice, on both sides

None of this means the lower levels are wrong. Some problems genuinely need a fix and nothing more. Some situations genuinely need someone to deliver exactly what was asked. A transactional relationship is the right one for a transactional problem.

The mistake is engaging at a lower level than the problem requires, and then wondering why it does not go away.

That choice sits with us as much as with them. We often keep providers at the lower levels ourselves, because it is more comfortable. A pleaser does not challenge us. A transactional supplier does not ask awkward questions. Being influenced towards what we need, rather than given what we want, is uncomfortable. It asks us to admit that our request might have been wrong.

Moving up the stack means inviting that discomfort in.

The questions that remain

Here are some questions to ponder.

Think of the vendors, service providers and partners you rely on most. At which level is each of them engaging with you, and at which level does the problem actually need?

When did one of them last tell you that what you asked for was not what you needed?

And if you are busy with them all the time while nothing fundamentally improves, is that a problem with their effort, or with the level at which you have allowed the relationship to sit?