Every layer of the product-experience industry, the docs, the tours, the tooltips, the training videos, the help desks, exists to compensate for one assumption: software can't explain itself, so an explanation industry must surround it. The end state now visible is the assumption dissolving, software that greets, guides, answers, and teaches as a property of the product, not a department around it.
The explanation industry was scaffolding
Look at the stack we normalized: documentation describing interfaces at a distance, onboarding flows narrating fixed paths, training videos aging from render day, support queues staffed to interview confused users about screens nobody could see. Each layer is scaffolding around the same load-bearing gap, the product could not attend to its user. None of it was wasteful at the time; scaffolding never is until the building stands. But scaffolding has a tell: it grows in proportion to the gap it compensates, and this stack grew into entire industries, which measures how large the gap always was.
What self-explaining actually means
Not tooltips with better copy, presence. Software that explains itself meets the user the way a knowledgeable colleague would: it sees where you are and what you're doing; it answers the question you actually asked, in your language, in the moment you asked it; it shows by doing, on your own screen, with your permission; it remembers where you left off and carries an agenda for where you're going; and it knows when to bring in a human. The mechanism is the live agent, eyes, voice, hands, and a brain grounded in the product's living truth, but the end state is better described from the user's side: the product's expertise is ambient, and learning-the-software stops being a phase of using it.
What dissolves, and what remains
The artifact layers dissolve first: interface-showing content that rots per release, tours that break on redesign, the training that was really a queue for scarce human attention, all replaced by explanation that derives from the live product and so is never between versions. What remains, and grows, is the human judgment the scaffolding always obscured: deciding what's worth teaching, designing the journeys, handling the accounts and moments where empathy and stakes outrank efficiency. The explanation industry's people don't disappear; they move up a level, from producing the scaffolding to directing the attention.
The competitive endgame
When explanation is ambient, product experience stops being gated on user diligence, and the advantage shifts to whoever's software attends best: greets every visitor, activates every signup, resolves on-screen, trains in-flow, remembers everything. Products that still hand users homework will feel, quickly, like products that don't care. The end state of product experience is software that explains itself, and the companies that get there first will make everyone else's scaffolding visible as what it was. (Disclosure: building that end state is Skippr's whole premise, live AI employees as the product's ambient expertise, from first demo to renewal.)
See what a live agent actually does
The category is easier to watch than to define. Fifteen minutes is enough to see where the mechanism differs from everything it gets confused with.