Insight
Stable Frame, Dynamic Contents
If the interface is different every time, how does anyone learn it or trust it? The answer isn't less adaptation. It's splitting the interface into a frame that stays and contents that move.
The objection: different every time
An interface that rearranges itself on every visit. Spatial memory is lost, and in a system handling coverage or money, exhausting shades into untrustworthy.
Frame versus contents
The room stays — shell, primary navigation, the persistent landmarks. Only the work on the table adapts to the situation you came in for.
Two failure modes and the target
Static (frame and contents both fixed) and chaotic (everything moving) versus the target: a stable frame with dynamic contents.
The obvious objection to situational interfaces is a good one: if the screen is different every time, how does anyone learn it or trust it? Spatial memory is real. People rely on "the thing is always in the top-right." An interface that rearranges itself on every visit is exhausting, and in a system handling coverage or money, exhausting shades into untrustworthy.
The resolution isn't to be less adaptive. It's to split the interface into two layers. The frame — the shell, the primary navigation, the persistent landmarks — stays put, always. It's the room. The contents — the payload assembled for the situation at hand — is what adapts. Same room every time; different work laid out on the table depending on why someone came in.
Get it wrong the other way and you're back in the old world: a stable frame and stable contents, identical for every situation — just a static screen. Get the split right and you get the best of both: a place people already know, and an interface that already knows why they're here.
Adaptive where it helps, fixed where it grounds. The frame is a promise; the contents are the work.