Context Design and Experience
I want to put a name to something I keep running into.
When we build software, we design what people see (the interface) and what they go through (the experience). There is a third thing that now decides most of how a product feels, and we rarely design it on purpose: the context.
By context I mean everything a system has in hand at the moment it acts. Who you are. What you just did. What you asked for last week. What it was told to ignore. What it has forgotten. For AI products this is literal: a model can only work with what is put in front of it. Two products built on the same model can feel completely different, and most of that difference is context.
I'm calling the practice of shaping this Context Design and Experience.
Context Design and Experience is the practice of deciding what a system knows, when it knows it, and how that knowledge feels to the person on the other side.
It has two halves.
Context design is the structure. What gets collected, what gets kept, what gets thrown away. What is pulled in for this moment, in what order, and who is allowed to change it.
Context experience is how that structure feels from the outside. Not having to explain yourself twice. Not being caught off guard by something the system remembered that you never meant to tell it. Being able to see what it thinks it knows about you, and fix it when it's wrong.
Why it needs its own name
Pieces of this already live under other names. Engineers talk about context windows, retrieval and memory. Designers talk about personalization. Legal teams talk about data and consent. Each group holds one piece, and the person using the product feels all of them at once.
"It forgot what I told it." "How does it know that?" Neither complaint is really about the model or the interface. Both are about context, and right now no one's job is to own that.
Where I'd start
- Know only what helps, and collect it in ways a person would expect.
- Let people see what the system believes about them.
- Let them correct it.
- Forget on purpose. Decide what expires and when.
- Never make someone explain themselves twice.
These will change. This is the first post here, and I expect to come back to this idea many times.
If you work on what a system knows and how that feels, you are already doing context design and experience. Now it has a name.