Insight

Why proximity alone isn't enough

Why proximity alone isn't enough

Someone who only gets a brief sees a summary of reality. Someone fully absorbed into the internal workings no longer notices some of the assumptions. Good external work takes enough context to understand what's going on, and enough independence to keep questioning it.

A printed page whose layers gradually drift out of register while a fixed registration mark makes the shift visible.

A brief is useful. It reduces a question to what can be named at that moment. But it is also always a selection: what an organisation has noticed, found relevant and managed to put into words — not what remains unclear underneath. A client asks for more content, for example, while the offer itself isn't sharp yet. That the most interesting work therefore often starts before there is a brief is something I've written about before. This piece is about the question that comes after: what it takes to keep seeing that, even after years of working together.

To notice that the question being asked isn't always the real question, an external partner needs to see enough of how things actually work. That can mean being present at the office, on a construction site, at a trade fair or during a production. But proximity doesn't come only from physically sitting somewhere. It also grows by staying involved long enough in decisions, documents, recurring questions, production and follow-up — and by still being around later to see what an earlier choice has caused in practice.

That is more than getting a better brief. It makes visible what hasn't yet been formulated as a question.

At the same time, there is a risk in it.

Anyone who works alongside an organisation long enough gets to know its language, priorities and exceptions. That is necessary to deliver good work. But the same familiarity can make something start to look normal simply because everyone sees it that way every day. A temporary fix becomes a standard way of working. A term that sounds clear internally gets used outside the company without further checking. A process survives because nobody asks anymore why it was ever set up that way.

So proximity produces context, but not automatically better judgement.

For me, the value of remaining external is not in keeping my distance. It is in the room to treat an assumption as an assumption again. To ask why a choice is made the way it is. Not to simply paper over a gap between what a company says and how it works with better communication. And to put a question back with the person who actually has to decide on it.

That takes involvement without taking over the organisation's role.

In practice, none of this looks spectacular. In an ongoing content operation, the strongest story sometimes only becomes visible once you're on site; strategy then has to keep working during production, not just before it. In other work, writing, editing and publishing the content first-hand made visible that the agreements, information and follow-up behind the communication didn't hold together well enough. And in a project where software was allowed to prepare almost everything, every decision stayed with a person who had the actual authority.

Different kinds of work, but the useful position is roughly the same each time: close enough to the work to see what is really happening, and independent enough to name what should happen with it — or who needs to decide on that first.

That doesn't mean all the work has to be done by one person. Within Simply Dom, we divide preparation, production and specialist parts of the work when that is faster or better. I safeguard the business, strategic and editorial line throughout, so it doesn't get lost between the people or steps contributing to it.

A strategic sprint doesn't always need that long-term proximity; sometimes a well-defined question really is a well-defined question. In an ongoing collaboration, though, the value isn't only in availability. It is also in the memory that builds up: knowing why something was decided earlier, which exception sits behind it, what has already been tried and where practice no longer matches the story.

That doesn't turn Simply Dom into an internal department. The involvement has to be large enough to understand the context and help carry the execution. The position stays external enough to ask the questions that easily disappear inside an organisation.

So proximity alone isn't enough. It produces context, but what that context is worth depends on the freedom to keep questioning it. That freedom rarely disappears through distance. It disappears through habit. That is what I keep an eye on.