Care is a system, not a sentiment

I stepped back from full-time design work for a while. It was a period of becoming a mother and of reading for a Master's at the same time, and I came back to the work with my attention rearranged rather than interrupted. I want to be precise about that, because there is a version of this note that apologises for a gap, and there is nothing here to apologise for. It was the most useful thing that has happened to my practice.

What changed is that I stopped thinking about care as a feeling.

Before, if you had asked me to design something caring, I would have reached for tone. Gentler copy. Softer corners. A slower transition. Warmth, essentially, applied at the surface. Which is the same instinct I have written about elsewhere and still catch myself having.

Care in practice turned out to be almost entirely logistics. It is remembering, on someone else's behalf, at a time that is not convenient, repeatedly, while tired. It is holding a schedule that only exists in your head. It is the invisible labour of tracking what another person needs before they can say it. Very little of that is warm. Most of it is administrative, and the administrative part is the part that is actually hard.

This is not a subtle distinction in practice. It changes what I flag in a critique.

I notice, now, how many interfaces assume an undistracted user with both hands free, full attention and an uninterrupted five minutes. I notice flows that can only be completed in one sitting and lose everything if you leave. I notice the ones that ask you to remember something the system already knows. I notice how often a product's answer to a difficult moment is a message, when the useful answer would have been to have kept the state.

And I notice that these are usually not accessibility failures in the formal sense. They pass the audit. They are simply designed for a person with more slack than most people have.

It also gave me the question that most of my work now turns on. When a system says nothing, when the status has not changed, when the reply has not come, when the notification stops arriving, the person on the other end concludes something anyway. Interfaces are careful about what they say and careless about what a silence means. That is the thread running through the capstone, and it is not a thread I would have been able to see clearly from a desk.

I am not romanticising the season. It was exhausting and a good deal of it had nothing to do with design. But I would not trade what it taught me about what people are actually carrying when they open something I made.