The Redundant Screen Teaches People Not to Watch

The Complaint and the Cause

A familiar observation about video: most people do not really watch it. They put it on, look away, and listen. The usual response is to design for that — make the audio self-sufficient, treat the picture as a companion, and put a subtitle band over a slow zoom so nothing is lost by not looking.

That response was proposed here and rejected outright, because it has the causation backwards. People listen without watching because the screen was made meaningless. A picture that only repeats what the narration is already saying earns nothing, so ignoring it is the rational response — and a format that then concludes "viewers do not watch" and adds more redundancy is completing a loop it started itself.

Two Channels, One Rule

The rule that replaced it is short: never render what the narration already said. Two channels are running simultaneously, and using them to transmit the same content halves the bandwidth for no gain. Every moment the screen echoes the audio is a moment it could have carried something the audio cannot.

This immediately makes the screen harder to design, which is the honest cost. Redundancy is easy — you always know what to put up, because the narration just told you. Non-redundancy demands that you know what each channel is uniquely good at, and then that you have something worth putting in the second one. Some material genuinely does not, and the correct answer there is silence on that channel rather than filler.

Where This Generalizes

The pattern is not about video. It appears wherever a system offers two channels and the cheap move is to mirror one into the other.

Documentation that restates the function signature in prose. A chart whose caption reads out the values. Log lines that repeat the exception message the stack trace already contains. An interface where the icon, the label, and the tooltip all say the same word. In every case the second channel has been spent on a copy, and in every case the same fix applies: ask what this channel can do that the other structurally cannot, and either put that there or leave it empty.

Audiences respond rationally to what you have taught them. Before treating a behavior as a fact about your audience, check whether your own design produced it. People skip your changelog because it has never contained anything, ignore your alerts because most of them were noise, and look away from your screen because it never rewarded looking. That is learned behavior, and it can be unlearned by making the channel worth attending to.

Code

The loop the redundant default creates·text

        screen repeats the narration
                    │
                    ▼
        looking at it earns nothing
                    │
                    ▼
        viewers stop looking
                    │
                    ▼
        "our audience listens without watching"
                    │
                    ▼
        make the audio MORE self-sufficient  ──┐
                    │                          │
                    └──────────────────────────┘

# Each step follows reasonably from the last.
# The loop is only visible if you question step 1,
# which is the step that never gets questioned
# because it is the medium's default.

Exercise

Find a place in your own work where two channels carry the same content — a chart and its caption, a log message and its stack trace, a label and its tooltip, a diagram and the paragraph explaining it. Pick one and rewrite the second channel to carry something the first structurally cannot. If nothing qualifies, delete the second channel and notice whether anything was lost.

Hint

Documentation is the richest hunting ground. Any sentence that restates a signature in words is a channel spent on a copy — the prose could have carried why the function exists, what it costs, or when not to call it, none of which the signature can say.

The Complaint and the Cause

Two Channels, One Rule

Where This Generalizes

Code

External links

Exercise

Progress

Comments 0