Two Ways to Communicate the Same Thing

Signal and backup

A fire alarm that only rings assumes everyone can hear it. A departure board that only displays text assumes everyone can read standard print at a distance. A booking confirmation sent only by email assumes everyone has consistent inbox access and can parse a dense PDF. Each assumption quietly excludes a portion of the people the system is meant to serve — not through hostility, but through the logic of designing once, for a single channel.

Redundant communication design starts from the opposite premise: that information delivered through more than one format or sensory channel simultaneously is not wasteful, it is structurally sound. The word "redundant" carries baggage in management culture — it suggests surplus, inefficiency, things to cut. In systems engineering and in inclusive design, it means the opposite: a backup that makes the primary channel more reliable, not less necessary.

The practical question for anyone specifying a building, a service, or a digital environment is not "can we afford to communicate this twice?" It is "which single channel are we prepared to have fail?"

What redundancy looks like in practice

Consider wayfinding in a hospital. A department signage system that uses text alone is readable to most sighted visitors with adequate literacy in that language. Adding colour-coding — consistent across every floor, every junction — means a visitor who missed the text, or couldn't read it quickly enough while moving, still has a signal to follow. Adding pictograms extends the system again, to people reading in a second language, or under cognitive load, or with certain print-reading difficulties. None of these additions removes the text. Each layer serves the same function by a different route.

That is redundant design: the same information, multiple channels, simultaneously present. It differs from sequential design — where a visitor who can't use the primary route is redirected to a secondary one — and it differs from segregated design, where a separate system is built for disabled users while the main system remains unchanged. Redundancy is structural; the alternatives are accommodations.

The same principle applies in digital environments. A video without captions forces a deaf viewer to request an alternative. A video with burned-in captions provides the same content simultaneously to a hearing viewer, a deaf viewer, a viewer in a loud space without headphones, and a viewer for whom the spoken language is not their first. The captions do not degrade the experience for anyone who doesn't need them — and this is the test of whether redundant design is genuinely embedded or still being treated as an afterthought.

Contrast ratios, audio descriptions, tactile indicators alongside visual ones, SMS confirmation alongside email, large-print alongside standard — in each case, the question is whether the second channel is present by default or available only on request. Built in, not requested, is the principle that separates the two.

Where it breaks down

The failure mode is almost always framing. When a communications team treats an accessible format as a special version — produced separately, published later, formatted differently — it has not implemented redundant design, it has created a two-tier system. The standard version ships; the accessible version follows when someone asks, or when resource allows, or never. At that point, the second channel is not redundancy: it is a workaround that depends on a disabled person identifying themselves, requesting something, and waiting.

Procurement is one of the leverage points. Specifying that all public-facing communications must simultaneously provide information in at least two modalities — visual and auditory, text and graphical, digital and non-digital — sets a baseline that contractors must meet before launch, not after complaints. Without that specification in the contract, the delivery team will default to one channel and treat the rest as optional extras.

The built environment needs the same thinking. A tactile paving route that leads to a door, combined with an audible signal at that door, combined with clear sightlines and legible signage — these are not four systems. They are one system using four channels. Each is doing the same job by a different means. Remove any one of them and the system becomes less reliable for everyone — because no single channel works in all conditions, for all users, all the time.

That is the argument for redundancy: not inclusion as charity, but engineering as discipline.