Care Is Infrastructure

We talk about care as if it is something people either have or don't have. Institutions are described as caring or uncaring. Workers are described as compassionate or cold. Organizations are described as supportive or indifferent.

But care has a design. And when that design is absent, the absence is felt — not as a policy gap, but as a personal failure. The person who falls through the gap rarely blames the system. She blames herself.

This is one of the most consequential design failures in public and social systems. And it is entirely preventable.

Care is not a value that organizations hold. It is a quality that systems either produce or fail to produce — by design.

What care actually requires

Care, in a systems design sense, is not warmth. It is not the tone of voice of an intake worker, or the poster on the wall of a waiting room, or the word “support” in an organization’s mission statement.

Care is structural. It is present when a system has been designed to reduce the burden on the people navigating it. It is absent when a system transfers that burden onto individuals — expecting them to absorb the complexity, the waiting, the documentation, the emotional labour, the translation of their own lived experience into institutional language — in order to access what they are entitled to.

The difference between a care-producing system and a harm-producing system is not intention. Most systems were designed with good intentions. The difference is whether the design accounts for the full reality of the people it is meant to serve.

The invisible weight

Consider what it actually requires to navigate a basic social service in Manitoba. A woman arriving at an intake appointment may have arranged childcare, taken unpaid time off work, translated documents that exist only in a language she is still learning, prepared to explain her situation to a stranger for the third time this month, and managed the anxiety of not knowing whether she will be believed.

None of this burden appears in the system’s design documents. It is invisible to the institution. But it is entirely real to her. And it accumulates — appointment by appointment, form by form, denial by denial — until the cumulative weight becomes the reason she stops trying.

This is what we mean when we say that systems produce harm through their design rather than their intent. The harm is not malicious. It is architectural.

When we ask why women disengage from programs designed to help them, the answer is almost never that they don’t want help. The answer is that the cost of accessing the help — in time, in emotional exposure, in dignity — is too high.

Care as a design principle

At The Nia Initiative, we approach care not as a value to communicate but as a design principle to implement. It shows up in specific, technical decisions:

• Whether a program requires disclosure of trauma histories to access services — or whether it does not.

• Whether eligibility criteria account for the realities of women navigating multiple systems simultaneously — or whether they assume a linear, uncomplicated path.

• Whether the highest-risk transition periods are the most intensively supported — or whether support is front-loaded at intake and tapers precisely when it is most needed.

• Whether cultural and linguistic context is built into the program design — or added as an afterthought through a translator brought in on short notice.

These are not philosophical questions. They are engineering questions. They have answers. And the answers determine whether a system produces care or extracts it from the people who can least afford to give it.

Why this matters beyond individual programs

The argument for care as infrastructure is not only ethical. It is economic.

When employment programs fail to retain participants, the cost falls on income assistance, emergency services, mental health systems, child and family services. The cumulative cost of a poorly designed pathway — measured across all the systems that absorb its failures — is substantially higher than the cost of designing it well in the first place.

Care-centered design is not expensive. The absence of it is.

This is the case NIA makes to governments, funders, and institutions: that the infrastructure of care is not a soft add-on to serious systems work. It is the condition under which serious systems work actually produces results.

Systems that reduce harm do not cost more. They cost differently. The investment moves from crisis response to prevention, from remediation to design, from managing failure to building something that works.

The design question

The next time your organization prepares to launch a program, a service, a policy, or a process, we invite one additional question before you finalize the design:

What does this system require from the people navigating it — and have we designed it to minimize that requirement, or have we simply assumed they will absorb it?

The answer to that question determines whether your system produces care or consumes it.

At The Nia Initiative, we believe that care is infrastructure. That when systems are designed to reduce harm rather than transfer it, everything else becomes possible.

The Nia Initiative is a systems design organization working at the intersection of institutional transformation, African women’s leadership, gender-diverse African wellbeing, and care-centered practice. We design the structures behind access, dignity, and long-term opportunity.