What the Tube Map Gets Right About CGI

In 1933, Harry Beck produced something that looks, at first glance, like a simple diagram.

The London Underground map replaced a geographically accurate representation of the network with something deliberately abstracted: straightened lines, simplified routes, consistent spacing, and no real attempt to show where stations sat in relation to each other on the ground.

It was immediately understood.

It still is.

Beck’s insight was not simply to make the network simpler. It was to make it useful. He understood what passengers actually needed to know, stripped out what did not serve that need, and designed around the rest.

The map is not incomplete.

It is purposeful.

And that purposefulness is exactly what makes it work.

The same principle sits at the heart of good architectural visualisation.

The Complexity Behind a Scheme

A proposed development does not arrive as a neat, single idea.

It arrives as layers of information: architectural intent, structural constraints, landscape strategy, planning requirements, access, servicing, interior specification, commercial objectives, sustainability targets, occupier needs and budget realities.

All of it matters.

But very little of it is immediately accessible to the people who need to understand the scheme quickly.

• A planning officer may need to understand scale, context and impact.

• An investor may need to understand value, risk and market positioning.

• A prospective occupier may need to understand operation, access and suitability.

• A member of the public may simply need to understand what is changing and why.

The visualisation does not replace the complexity behind the project.

It translates it.

Into something a specific audience can understand, respond to and use.

Why the Brief Is Where It Goes Right or Wrong

This is where the Tube map analogy becomes useful in a practical sense.

Beck did not set out to draw every piece of information about the Underground network. He set out to help people navigate it.

The destination came first.

Everything else followed from that.

The same logic applies when commissioning visualisation, and it is where briefs most often fall short.

“We need some CGIs of the building” is a starting point, not a brief.

It describes the output, but not the purpose.

The important questions come next.

• Who is it for?

• What do they need to understand?

• What decision is this helping them make?

The answer should shape every decision that follows: the viewpoint, lighting, time of day, level of context, people in the scene, what sits in the foreground, and what is left out entirely.

A planning image and a marketing image of the same building can look very different from each other.

Not because the building has changed.

Because the audience has.

And therefore the job the image needs to do has changed too.

Treating them as interchangeable is the visual equivalent of handing a passenger the engineer’s schematic instead of the Tube map.

Technically full of information.

Not especially useful for the person trying to get somewhere.

The Brief Question Worth Asking

Before briefing any piece of visualisation work - an image, animation, film or interactive model - it is worth pausing on one question:

What does this need to make someone understand, feel, or decide?

That answer should shape the rest.

• Which views to commission.

• What format to use.

• How much detail is needed.

• How much detail becomes a distraction.

It is a conversation we have with clients at the start of most projects, and it consistently produces better outcomes than working backwards from a shot list.

Because a shot list tells you what to make.

A good brief tells you why it needs to exist.

Choosing the Right Tool for the Level of Complexity

The same principle applies at every scale.

A single CGI can translate one carefully chosen idea: how a building sits in context, how a landscape strategy softens an edge, how a space might feel once occupied.

An animation can do more. It can move through a scheme, connect inside and outside, explain arrival sequences, show multiple buildings, and reveal relationships that a single still image cannot.

A film can go further again, shaping a clearer narrative around the project - who it is for, how it works, and why it matters.

And when the complexity increases again - multiple buildings, multiple phases, multiple sites, or a national portfolio - the challenge becomes something else entirely.

It is no longer just about producing an image or a film.

It is about making complex information navigable.

That is where we are currently doing a lot of thinking with Interact3D: a way of bringing project information, locations, visuals and data together in a format people can explore more intuitively.

But the underlying question is the same, whatever the tool.

• Who is the audience?

• What are they trying to understand?

• What complexity are we trying to remove?

Whether the answer is a CGI, an animation, a film, or something more interactive, the point is not to show everything.

It is to show the right things clearly.

We are now at the stage where we can demonstrate Interact3D properly, and we are setting up meetings with clients and project teams who may find it useful.

If that sounds relevant - or if you are working on a scheme where the information is becoming difficult to communicate clearly - get in touch and we will show you where we have got to.

That's where my head was at this week!
Rich

[email protected]
07777 146 495