Meta's smart glasses, in their current form, don't have a display. No screen, nothing floating in front of your eyes. Just a camera, a microphone, headphones. Given how much more the underlying technology could plausibly do — Sutherland notes this is a deliberate choice, not a technical ceiling — the missing display is strange, until you realize it's the same move Sony made with the original Walkman decades earlier: strip a new product category down to almost nothing, on purpose, so that people can actually understand what it's for.1
A genuinely new product category has a specific adoption problem that has nothing to do with whether the underlying technology works: nobody yet has a mental model for what the thing is for. Give a first-generation product every capability the engineering allows, and you don't get a more impressive launch — you get a device nobody can describe in one sentence, because it does twelve unrelated things reasonably well instead of one thing unmistakably. The Walkman trick is to withhold capability deliberately, cutting the product down to the single, obvious affordance you want the market to understand first, and letting later generations add complexity only after the core use case has become intuitive.2 Constraint, in this reading, is not a compromise forced by cost or immaturity. It's a communication strategy — the product's limited feature set is itself the explanation of what it does.
This runs directly against the instinct that a new product should ship with maximum functionality to justify its price and maximize its addressable use cases. The Walkman trick's implicit argument is that maximum functionality at launch actually raises the adoption cost, because every additional capability is one more thing a first-time user has to parse before they can answer the basic question "what is this and why would I want it." A portable music player that also did nothing else was instantly legible: it plays music, and you can carry it. A smart-glasses product that has a camera, a display, a voice assistant, an AR overlay, and a dozen other capabilities from day one forces the buyer to do interpretive work most buyers won't do — they'll default to not buying rather than working out which of the twelve features matters to them.
The specific choice Sutherland highlights — voice, camera, and headphones, no display — is instructive because a display is exactly the feature most people would assume any modern wearable needs. Its deliberate absence forces the product to be understood entirely through what it does rather than what it shows, which narrows the interpretive question a first-time user has to answer down to something almost binary: do I want a device that listens and sees for me, hands-free? That's a question most people can answer quickly. "Do I want an augmented-reality interface layered onto my vision" is a question almost nobody can answer quickly, because almost nobody has a working mental model of what that would even feel like yet.
You're on a product team debating the feature list for a genuinely new category's first release, and engineering has built more than the launch plan calls for — capabilities are ready, and the instinct is to ship everything that works rather than "waste" finished engineering effort. You make the case for holding features back regardless of whether they're ready: readiness on the engineering side is not the same question as legibility on the adoption side, and shipping a feature before the market has a mental model for the category can actively slow adoption of the core use case you need to establish first.
Later, the same product succeeds at its narrow launch use case, and the roadmap conversation turns to which held-back features to add next. You point out this is where the Walkman trick's second half matters as much as the first: the sequence in which capability gets reintroduced should track how the market's mental model is actually expanding, not simply which features happen to be ready. Adding the wrong capability too early — however well-engineered — can re-blur the legibility the deliberate first-generation constraint bought you.
Much later, a competitor launches with everything your product deliberately withheld, marketed as "more complete." Leadership gets nervous. You walk through the comparison calmly: the competitor is optimizing for a feature checklist; your product optimized for a specific, well-understood use case that's already driving adoption. A feature-complete product that nobody can explain in one sentence is not automatically winning the category — it may simply be repeating the mistake the Walkman trick exists to avoid.
The strongest evidence for this pattern is that it recurs across genuinely different technology eras and companies — the original Walkman decades ago, Meta's current smart-glasses strategy — suggesting this isn't one company's idiosyncratic choice but a recognized, repeatable response to the same adoption problem every new category faces.
The open tension: the source doesn't specify how a team decides which capability to keep and which to withhold — the Walkman kept "play portable music," the glasses kept "listen and see hands-free," but the source offers no general method for identifying the single core affordance a new category should be legible around, only retrospective examples where the choice, in hindsight, looks obviously correct.
This connects to the same source's separate, more skeptical riff on the iPhone's lost physical keyboard (see Physical Keyboard Loss as Productivity Regression) in a way the source itself doesn't reconcile explicitly. Both cases involve a deliberate reduction in device capability or affordance — no keyboard, no display — but Sutherland treats one as a smart legibility strategy (the Walkman trick) and the other as a real loss masked by novelty. The distinction that resolves the apparent contradiction, though the source doesn't state it directly: the Walkman trick withholds features temporarily, as a deliberate adoption strategy meant to be revisited; the keyboard's disappearance was permanent and driven by aesthetic/display priorities rather than a legibility strategy with a planned next step. Constraint-for-legibility and constraint-as-genuine-regression can look identical at a glance and require checking the maker's actual intent and roadmap to distinguish.
Behavioral-Mechanics — The Screen-Size Status Reversal. Both pages document consumer technology moving toward less rather than more, but for different underlying reasons — screen size shrank because portability became more urgent than display quality; the Walkman trick withholds capability specifically to make a new category legible, independent of any portability constraint. The insight the pairing produces: "reduction" in consumer technology is not one phenomenon but at least two structurally distinct ones — externally-forced trade-offs (screen size, driven by a competing technology convergence) and internally-chosen strategy (the Walkman trick, driven by a deliberate adoption-legibility decision) — and conflating them risks either over-crediting an accidental trade-off as clever strategy, or under-crediting a genuinely deliberate constraint as a mere limitation.
Behavioral-Mechanics — Information Asymmetry Exploitation. Information asymmetry theory generally treats a seller's information advantage over a buyer as something to be closed (via branding, reputation) or exploited (via deception); the Walkman trick suggests a third option specific to genuinely novel products — deliberately reducing what the product itself communicates, so that the limited information the buyer does receive is unambiguous rather than overwhelming. The insight the pairing produces: for a new category, the problem is often not too little information reaching the buyer but too much undifferentiated information, and deliberately constraining what the product can do is itself a form of information-asymmetry management — simplifying the buyer's evaluation problem down to a size they can actually process, rather than either hiding information or flooding them with it.
Sharpest implication: for a genuinely new product category, shipping less capability than the engineering allows can be the more sophisticated choice, not the compromised one — because the real bottleneck to adoption is rarely what the device can do, it's whether a first-time buyer can explain to themselves, in one sentence, why they'd want it.
Generative questions: