top of page

Recognition Is Not Simplification

Writer: Andrew Mallaband
Andrew Mallaband
Jul 24
4 min read

Updated: Oct 19

Black background with white text: "More messaging adds detail. It doesn't add momentum." Curved lines on right. Button: "Why we started building Storylines."

Why complex ideas do not always need to be made smaller—just introduced in the right order

We were reviewing a conference banner for a technically complex business.

The company was introducing an architectural approach that differed materially from how most of its market currently thought about the problem. The banner included technical language, diagrams and supporting claims intended to show why the approach was genuinely different.

One view was that there was simply too much on it.

Visitors would only have a few seconds to look while walking past the stand. The terminology was unfamiliar, the diagrams required attention, and the architecture would be difficult to understand without a longer conversation.

From that perspective, the answer seemed obvious: reduce the information, simplify the language and make the message immediately accessible.

The other view was almost the opposite.

The architecture was the differentiation. Removing the terminology and technical detail risked making the company sound like every other vendor at the event. A simpler message might be easier to process, but it could also remove the substance required to understand why the approach mattered.

That argument seemed equally reasonable.

How much could we remove without weakening the idea?

Neither side was wrong. One was protecting accessibility. The other was protecting meaning.

The more I listened, however, the less convinced I became that the disagreement was really about the amount of information.

Perhaps they were not arguing about what the audience needed to know.

Perhaps they were arguing about what the audience needed first.

The Question We Were Missing

The question being asked was:

Can someone understand this in a few seconds?

That is perfectly reasonable for a conference banner.

But it may not be the most useful place to begin.

A different question started to emerge:

What has the visitor recognised before this explanation begins?

The banner opened by introducing the company’s architectural model, technical terminology and the mechanisms through which it worked.

All of that material mattered.

But it assumed the visitor had already recognised the operational condition that made the architecture relevant.

Without that recognition, the visitor had to decode unfamiliar language, interpret a technical diagram, work out which problem the architecture addressed and decide whether that problem mattered in their own environment.

The issue was not necessarily that the banner contained too much information.

The issue was that explanation had begun before relevance had been established.

That distinction changes the objective.

The idea does not necessarily need to become smaller.

The path into it needs to become more natural.

Complexity Wasn’t the Problem

Some ideas are complex because the reality they describe is complex.

An architectural change may depend on understanding why the current architecture creates limitations. A new operating model may require someone to see how decisions, ownership and dependencies interact across a business.

In those situations, simplification can become distortion.

The communication gets shorter, but the idea becomes less accurate. The language becomes easier to process, but the reason the organisation is different becomes harder to see.

Looking again at the banner, the technical material did not necessarily need to disappear.

The diagrams, architectural language and technical differentiation could all remain. They simply needed to appear after the visitor had encountered something they already recognised.

The communication could begin with a familiar operating reality.

From there, it could reveal a recurring pattern.

Then the deeper constraint.

Only after that would the architecture be introduced as the response.

At that point, the technical idea would no longer appear in isolation. It would become an explanation for a condition the visitor had already begun to understand.

Nothing about the underlying idea had been diluted.

The technology, diagrams and technical claims all remained.

What changed was the order in which the audience encountered them.

Sequence Changes Meaning

I have seen versions of the same problem across very different commercial and organisational conversations.

A website explains a sophisticated platform in detail while leaving visitors to work out which operating problem it exists to address.

A product demonstration begins with features and workflows before anyone has established which consequence the customer is trying to avoid.

In both cases, the explanation may be good. The logic may be sound. The evidence may be credible.

Yet the audience is being asked to begin from the organisation’s understanding rather than its own.

That creates an interpretation burden.

People must translate what they are being shown back into their environment before they can decide whether it matters.

This is often treated as a need for simpler communication.

Sometimes it is.

But sometimes the audience has simply entered the explanation too late in the reasoning.

They are being shown the answer before they have recognised the question.

Evidence Cannot Create Relevance

This also changes the role of evidence.

When engagement is weak, organisations often respond by adding more proof: more statistics, more case studies, more customer logos and more technical validation.

Evidence matters, particularly when a claim is unfamiliar or the perceived risk is high.

But evidence usually strengthens an understanding that has already begun to form.

It should not be expected to create relevance on its own.

A technical diagram can show how a system works. It cannot guarantee that someone understands why the system is needed.

A case study can demonstrate that a result occurred. It cannot ensure the reader recognises the same underlying condition in their own organisation.

Evidence can reinforce relevance.

It rarely creates it.

When it arrives before recognition, it can feel like assertion.

When it arrives after recognition, it has something to support.

A Better Question

A conference banner cannot complete a complex journey of understanding.

Nor should it try.

Its responsibility may only be to help the right person recognise enough of their own reality to stop and begin a conversation.

A banner may create recognition. A website may develop curiosity. A conversation can explore the underlying constraint and the capability required to address it.

Each surface has different limitations.

But each should prepare the audience for what comes next.

That leads to a more useful review question.

Not:

Is this simple enough?

And not:

Have we included enough technical detail?

But:

What does the audience need to recognise before this explanation can become meaningful?

Recognition-first communication does not mean reducing every complex idea to a slogan.

It does not mean audiences are incapable of understanding technical depth.

It means complexity becomes easier to engage with once people can see why it matters.

The idea does not become smaller.

The path towards it becomes clearer.

The medium changes.

The progression does not.

Comments


bottom of page