Skip to content
C.W.K.
Stream
Lesson 03 of 05 · published

A Deliberately Unfriendly Channel Is a Permission

~11 min · audience, positioning, density, constraints

Level 0Cold Workshop
0 XP0/35 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete

Refusing to Chase

The channel this work ships to is deliberately unfriendly. It does not optimize for reach, does not lower its bar to widen its audience, and does not add explanation to keep viewers who were not going to stay. That sounds like an artistic indulgence, and the interesting part is that it functions as an engineering permission.

Because the audience is not being chased, the screen does not have to be self-explanatory. It may be dense. It may present something a viewer does not immediately parse. It may reward a second viewing, which means it may contain things a first viewing misses. Every one of those is forbidden by default when the goal is to retain the marginal viewer.

The Two Positions Are Genuinely Incompatible

You cannot half-take this. Optimizing for the marginal viewer means every frame must be legible immediately to someone with no context — which caps density at whatever the least-invested person can absorb on first pass, and that cap is low. Accepting that some viewers will not follow lifts the cap, and the work that becomes possible above it is a different kind of work.

Trying to have both produces the worst outcome: content dense enough to lose casual viewers and explained enough to bore the committed ones. That is not a compromise, it is a design that fails both audiences, and it is the most common shape because it is what you get by never deciding.

The Discipline the Permission Requires

The permission is not a licence for obscurity, and this is where it would be easy to abuse. Density has to be earned — the dense frame must reward the attention it demands, and a viewer who works at it must get something. Difficulty that pays nothing back is not an unfriendly channel; it is a badly made one wearing the same clothes.

The honest test is whether a second viewing yields more than the first. If it does, the density was carrying content. If a second viewing yields the same thing more slowly, the difficulty was decoration and the permission was spent on nothing.

Decide who you are not for, explicitly. Most work never makes this decision, and by default optimizes for the least-invested possible reader — which quietly caps how good it can be for everyone else. Naming the audience you are declining is what converts a vague ambition into an actual constraint you can design against.

Code

What each position permits and forbids·text
CHASING THE MARGINAL VIEWER          NOT CHASING
---------------------------          -----------
every frame legible on pass 1        frames may reward pass 2
density capped at lowest context     density capped at what pays back
explain before showing               show; explain only if it earns
no unexplained references            references may reward recognition
retention is the metric              the committed viewer is the metric

THE TRAP: doing both
  dense enough to lose the casual viewer
  + explained enough to bore the committed one
  = fails both, and is what you get by not deciding

External links

Exercise

Take something you maintain that has an audience — documentation, a newsletter, an internal dashboard, a talk. Write one sentence naming who it is explicitly not for. Then find the places where you have hedged against exactly that person: the extra explanation, the removed detail, the softened claim. Decide for each whether it stays, now that the decision is conscious.
Hint
The hedges are easiest to spot as sentences beginning "of course, if you are not familiar with..." Each one is a small payment to a reader you have not decided to serve, and collectively they set the ceiling on how useful the piece is to the reader you have.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.