Care as Infrastructure
Care as infrastructure is the practice of building care into the conditions, processes, expectations, and structures of a system so that humane participation doesn’t depend entirely on the memory, energy, generosity, or intervention of individual people.
I’ve worked in plenty of places where care existed because a particular person kept making it exist.
Someone remembered to check in. Someone quietly explained the process nobody had documented.
Someone noticed who hadn’t spoken yet. Someone stayed late, made the exception, fixed the problem, absorbed the frustration, or knew exactly which rule could bend when a human being needed it to.
We tend to call those people caring.
I’ve started wondering what it says about the system that we needed them to compensate for it in the
first place.
That’s where care as infrastructure begins.
From individual care to structural care
Care matters between people. I don’t want to design that away, and I don’t think we could.
But some of what we routinely ask caring people to do isn’t unpredictable human need. It’s compensation for predictable structural failure.
If a program works because one exhausted person remembers everything, follows up with everyone, translates the confusing parts, catches every dropped ball, and makes the process humane through sheer force of care, I’m not sure we have a successful system.
We may have a person successfully compensating for an unsuccessful one.
Care as infrastructure asks what would happen if we stopped treating that labor as an unlimited resource and started examining what the structure itself could carry.
What care looks like when it’s built in
Care as infrastructure isn’t about making a system feel nicer. It’s about its actual mechanics.
It can show up in time, when pacing doesn’t require people to operate in permanent urgency.
It appears in support, when help is part of the process rather than hidden behind knowing the right person or asking exactly the right question.
It appears in accessibility, when human variation is anticipated instead of addressed only after someone struggles.
It can mean documentation that keeps essential knowledge from living in one person’s head, feedback loops that allow people’s experiences to change the system, and recognition that makes otherwise invisible labor visible.
And it requires shared responsibility, because a system isn’t caring if its apparent smoothness depends on someone quietly absorbing everything the structure failed to hold.
None of these things is particularly dramatic.
That’s part of the point.
Infrastructure is often easiest to notice when it fails.
Care as an Open Practice commitment
Care as infrastructure is one of the six commitments that guide Open Practice at The Open Practice Academy, alongside enterability, accessibility by design, clarity over cleverness, distributed ownership, and evidence-informed iteration.
Within Open Practice, care isn’t something added after a system has been designed. It changes the questions we ask while we’re designing it.
What are people being asked to carry here?
What happens when someone needs help?
Where does flexibility exist, and does using it come with a penalty?
Whose invisible labor is keeping this process functioning?
What predictable difficulty are we continuing to solve through individual generosity instead of better design?
Those questions make care something we can practice rather than simply something we say we value.
Care as a developing scholarly idea
I’m also interested in care as infrastructure beyond its use inside TOPA.
There is a long and substantial tradition of scholarship on care, including care ethics and work that understands care as practice, labor, responsibility, relationship, and something shaped by social and institutional arrangements. I’m still reading my way into that scholarship, and I don’t want to use it simply as a citation trail that makes my own idea look more established than it is.
I’m interested instead in the conversation between what I’ve learned through practice and what these traditions can help me see differently.
My own starting point was practical. I kept seeing organizations depend on individual people to humanize structures that weren’t particularly humane on their own.
Care as infrastructure is the language I’ve begun using for the alternative.
Infrastructure doesn’t replace relationship
There’s an important limit here.
I don’t think infrastructure can replace human care, and I wouldn’t want it to. No process can anticipate every person, relationship, circumstance, or need. There will always be moments when caring requires judgment, attention, flexibility, responsiveness, and another human being choosing to show up.
The goal isn’t to engineer our need for one another out of a system.
It’s to stop making human kindness responsible for repairing every predictable failure we could have designed differently.
A humane system doesn’t make caring people unnecessary.
It gives them somewhere sturdier to stand.