Care is made of resources

Parenthood has made it impossible for me to believe that care is primarily a feeling.

Love matters enormously. Love also does not pack the lunch, remember the appointment, notice the shoes no longer fit, coordinate the schedule, sit through the hard conversation, refill the prescription, find the missing form, or create enough time for a child to tell you the thing they did not know how to say quickly.

Care is expressed through resources.

An hour at 2 p.m. is not the same resource as an hour at 2 a.m. Six fragmented blocks of ten minutes are not always equivalent to one uninterrupted hour. Being physically present can matter differently than being reachable.

Organizations flatten time because calendars and capacity models need units. Human systems experience time contextually.

A family can look functional because someone is continually coordinating it. The same is true of a team. Schedules align, supplies appear, forms are completed, transitions happen, information travels.

Coordination is labor. And when that labor is invisible, the system can mistake the outcome for something that occurs naturally. Then it is surprised when the coordinator stops carrying it.

Care needs margin

If every minute is allocated before the day begins, another person’s unexpected need becomes a threat to the plan. The response is not necessarily less love. It is insufficient capacity.

Margin is what allows care to become responsive rather than merely scheduled.

A system cannot claim to value care while treating the resources required to provide it as waste.

Years ago, I underlined a fragment in one of my journals: duty = commitment = privilege = joy. I'm not entirely sure I could have explained what I meant then. I think I can now. By privilege, I didn't mean advantage or entitlement. I meant the privilege of being entrusted with something and the strange fact that responsibility can be both a weight and an honor.

Parenthood has made that especially obvious to me. There are obligations that are exhausting precisely because I care so much about what happens. I don't always enjoy the work of them. But there can still be joy in the responsibility itself: I get to be responsible for this. I get to care for this. This matters enough to ask something of me.

Duty can become commitment. Commitment can become privilege. And sometimes, somewhere inside all of that, there is joy.

But joy does not make the labor weightless. Love does not eliminate logistics. Commitment does not create infinite capacity. One of the easiest ways to exploit care is to assume that because someone chooses it, the resources required to provide it no longer count.

Care can be freely given and still have a carrying cost.

Care has to take form somewhere

Near the end of one role, I reached a point where I could not in good conscience keep hiring people onto my team.

The work mattered. I believed in the product. I cared deeply about the people already there. But the organization had not put enough capacity underneath what it was asking the team to carry. Recruiting another talented person would have solved a headcount problem while asking that person to enter conditions I no longer believed were sustainable.

That decision clarified something for me: care is not what we say about people. Care is partly what the system makes possible for them.

Good intentions still operate inside constraints

A manager can care deeply and still have no room in the budget. A teammate can want to help and have no time. A company can value inclusion while requiring people to navigate systems that assume everyone has the same capacity, schedule, body, language, or access.

Intent matters. It is not sufficient architecture.

Care has material requirements: time, information, attention, capacity, choice, redundancy, and somewhere for exceptions to go.

A second person who knows the process can look inefficient until the first person needs a week off. A little slack in a schedule can look underutilized until a child is sick, a customer has an emergency, or an implementation goes sideways.

When systems have no spare capacity, ordinary human variability becomes an operational threat. People are then asked to make themselves more predictable so the architecture does not have to become more resilient.

Accessibility reveals architecture

Accessibility is useful because it makes design assumptions visible. Who has to ask for an exception? Who can use the default path? Who must disclose something personal before the system becomes usable? How many additional steps does support require?

The answer tells us whether care is embedded in the structure or supplied afterward by a helpful person.

Sometimes care is framed as softness: a concession we make when performance permits it. I think that gets the relationship backward.

A system that continually consumes the people required to operate it is not rigorous. It is externalizing an operating cost. Designing for recovery, clarity, sustainable capacity, and human variation is not lowering the standard. It is taking the whole system seriously.

Care is not decoration added after the architecture is finished. It is one of the things the architecture decides.

The architecture of care

What happened to my sister taught me something I cannot unlearn: life—human, ecological, creative—is sacred and deserves to be supported. Every system that touches life has some responsibility for what its design makes possible.

I have written that education, healthcare, and the conditions we live in are not luxuries; they are the architecture of care. I mean architecture literally. Care has to take form somewhere. It appears in staffing, schedules, accessibility, information, redundancy, budgets, physical space, decision rights, and the amount of recovery a system permits after something goes wrong.

A value that has no mechanism for expression is mostly aspiration. If we say care matters, then we should be able to find it in the structure.