# Progressive Disclosure and the Blank Box **The old job:** Progressive disclosure was the politest idea in UX. Show people what they need right now, tuck the rest behind an "Advanced" tab, and let complexity reveal itself as competence grows. The whole discipline assumed the interface had too much to show. Menus were maps: you could read a menu bar like a table of contents and know roughly what the software could do. Disclosure was rationing. **The inversion:** Then the all-purpose prompt arrived. A blank text box is the least disclosive interface we've ever shipped. It can do nearly anything and shows you nearly nothing, territory with the map torn off. The empty rectangle quietly outsources the interface to the user's imagination, and imaginations are calibrated by past software. People ask an AI for what the search bar taught them to ask for. They request the sortable column when the whole dashboard was on the table, because nothing in the frame suggested the bigger ask was legal. The old problem was users drowning in features they could see. The new problem is users starving next to capabilities they can't. **Intent is dredged, not captured:** My working theory is that intent doesn't sit in a user's head as a finished spec, waiting for a good enough form field. It forms on contact with output. Show a fast, imperfect draft and the user discovers what they actually wanted by reacting to what they didn't. The first artifact isn't the deliverable, it's the probe. I keep relearning this on my own projects ([[Pausr Product Ideation|the product diary]] is mostly a record of it): the vision refines through prototypes, not before them. The prompt box on its own is another [[Thesis - Current tools are lossy membranes|lossy membrane]], intent leaking out between what a person means and what they manage to type. **What disclosure looks like now:** A few mechanisms seem to carry the weight the menu bar used to: - *Chips as vocabulary lessons.* Suggestion chips aren't shortcuts, they're a syllabus. Each one teaches a legal move. - *The well-timed question.* An interview, not an interrogation. Asking "who's this for?" after seeing the request beats a ten-field intake form before it. - *The fast draft.* The artifact is the disclosure. Every capability the draft demonstrates is a feature the user just discovered. - *The counter-offer.* Here's the sortable table you asked for, and here's the dashboard you maybe meant. Surfacing the outcome a user didn't know to grasp for is the new feature discovery. **The restraint clause:** Same warning as every powerful pattern (the [[UX - Glass|glass piece]] ends the same way): guidance curdles into steering fast. A suggestion chip is one business-model meeting away from becoming an ad slot, and an assistant that guesses intent too aggressively stops dredging and starts railroading. The goal is to widen what the user can see, then let them choose. Disclose the possible; don't prescribe it. **Takeaways:** * **The job inverted:** progressive disclosure used to protect users from complexity. Now its job is rescuing them from possibility. * **Ship the probe:** the fastest path to real intent is a draft the user can react to. Artifacts are the new menus. * **Guide, don't steer:** outcome suggestions are the most valuable and most corruptible surface in the prompt era. Restraint, again.