Presence is the intersection where Hand meets Heart: work that does its job with precision and reads to the user as if someone made it specifically for them. The two qualities are easy to describe and rare to find together. Most products are precise without being personal (the well-engineered tool that feels anonymous) or personal without being precise (the warm, generous interface that is also confusing and slow).
The diagnostic question for Presence is: does this design make the user feel seen? Being seen is not the same as being entertained, delighted, or impressed. Entertainment plays to anyone who encounters it. Delight is an aesthetic reaction. Impression is general. Being seen requires the product to have read something specific about this person: their state, their context, or their intent, and to have responded to it. The empty state that says “You haven’t added anything yet, here’s the fastest way to start” is doing Presence work. The empty state that says “Welcome! 🎉” is doing decoration.
Presence shows up most visibly in three places.
Copy: The language the product uses with the user, where Presence first registers, or fails to, because language carries tone more directly than visual choice does. Compare “Sorry, that didn’t work” to “Error 422.” The first acknowledges the user’s situation. The second reports a system fact. Both might be technically equivalent. Only one is present.
Timing: The exactness of when something happens. A confirmation that arrives a beat too late reads as the system not noticing. One that arrives at the right beat reads as the system being with you.
Anticipation: The design’s choice about what to show before the user has to ask. A booking flow that pre-fills the user’s last-used address is anticipating. One that leaves the field empty is technically correct and not present.
