Culture Is Infrastructure
What can a system outsource, and what does it still have to own?
For several years, I served on the Board of a small condominium association, including as president.
During that time, we worked with three different professional property management companies.
All three were reputable. All three had capable people. And each time, at least initially, there were reasons to believe the experience might be different.
But over time, many of the same problems tended to reappear.
Longstanding conflicts remained longstanding. Building issues that had survived previous Boards and managers continued to resist resolution. Responsibilities sometimes became less clear rather than more clear.
An owner would approach the property manager and discover that something required a Board decision. They would approach the Board and hear that management was supposed to handle it.
The property manager might reasonably operate within its scope. The Board might reasonably believe it had delegated the work. And a difficult problem could remain unresolved while everyone involved sincerely believed someone else was responsible for moving it forward.
Eventually, I began to suspect that the strongest variable was not the property management company.
It was the culture and leadership of the association itself.
The Natural Instinct to Add a Layer
When a system becomes difficult to manage, one of our most natural responses is to add something.
A manager. A consultant. A process. A platform. A methodology. A committee. Another layer of expertise.
Sometimes that is exactly the right thing to do.
But adding capability and transferring responsibility are not the same thing.
A professional property manager can administer a system. It cannot substitute for a functioning system of governance.
That distinction took me a while to understand.
A management company has many clients. It needs defined scopes, standardized processes, repeatable ways of working, and enough consistency across accounts to operate economically.
That is not a criticism. It is the structure of the model.
But every organization is also particular.
It has history. Relationships. Unwritten expectations. Previous decisions. Old conflicts. People who remember why something was done one way and others who only experience how it works now.
A management company inevitably has to apply some degree of standardization to something that is not entirely standard.
When the underlying organization is healthy, that can work extremely well.
When it is not, another layer does not necessarily repair it.
Sometimes it simply gives the dysfunction somewhere else to travel.
What the System Can Delegate
Eventually, we tried a different approach.
Instead of asking one intermediary to hold everything together, we built direct relationships with the professionals whose expertise we actually needed.
A bookkeeper. Attorneys who understood condominium governance. Insurance professionals. Tradespeople. Landscaping and snow-removal vendors. People with specific expertise doing specific work.
We also became more intentional about matching people within the building to roles where their skills and interests could contribute.
That experience changed the way I think about delegation.
A lot can be purchased.
Bookkeeping can be purchased. Legal expertise can be purchased. Insurance expertise can be purchased. Administrative support can be purchased. Specialized work can be purchased. A property manager can be useful augmentation for many of those things.
But some things remain difficult to outsource.
Leadership. Accountability. Transparency. Ownership. Culture.
The objective should not be for unpaid volunteers to do everything themselves. That is not sustainable either.
The challenge is to distinguish between what the system can intelligently delegate and what the system itself still has to own.
Culture Is Infrastructure
For a long time, I probably thought of culture as something adjacent to governance.
The relationships were important. The social events were nice. Trust helped. But the real work was budgets, contracts, insurance, maintenance, rules, and decisions.
I no longer see those things as separate.
The social fabric was part of the infrastructure through which governance happened.
I have learned that the environment itself teaches.
A system continually teaches people what participation means, where responsibility lives, whether disagreement is safe, whether reasoning will be visible, and whether speaking up is likely to lead to understanding or escalation.
None of those lessons need to be written into a policy.
People learn them by participating in the system.
Knowing one another mattered. It helped us understand who had relevant expertise. Who cared about particular issues. Who might enjoy contributing. Where old tensions existed. Where misunderstandings were forming. Who could help. Who needed help.
It gave us ways to distribute responsibility rather than continually asking the same few people to carry everything.
And when disagreements arose, relationships created pathways through which people could speak directly rather than allowing every difficulty to disappear behind email, enforcement, or institutional intermediaries.
Those conversations were not always comfortable.
But some problems that had survived for years finally began to move.
That experience left me with a principle I believe much more strongly now:
Culture is infrastructure.
It is not the soft material surrounding the operating system.
It is part of the operating system.
A sophisticated strategy operating inside an unhealthy culture will eventually be shaped by that culture.
A relatively simple system operating inside a culture of openness, responsibility, trust, and collaboration can accomplish an extraordinary amount.
When Responsibility Disappears
One of the more interesting things about systems is that they can contain many responsible people and still produce irresponsibility.
That can happen without anyone intending it.
It happens when ownership is unclear. When the edges between roles are ambiguous. When decisions travel through too many intermediaries. When everyone has enough responsibility to participate but no one has enough responsibility to move.
From inside each role, the behavior can make perfect sense.
The manager protects scope. The Board assumes administration is being handled. The owner assumes someone with authority is addressing the problem. The vendor waits for instruction.
Everyone may be behaving rationally.
And still nothing happens.
The failure belongs less to an individual than to the architecture through which responsibility is moving.
That is why governance cannot simply mean assigning tasks.
Someone has to know:
Who owns this? Who decides? Who advises? Who executes? Who needs to understand why?
Without that clarity, accountability has nowhere reliable to land.
Make the Reasoning Visible
Transparency became another part of the lesson.
People do not only need to know what was decided.
They need enough visibility into how the decision was made.
What information was available? What constraints existed? Where did judgment enter? What was uncertain? What alternatives were considered? Why was one path chosen over another?
When that reasoning remains invisible, people fill in the gaps.
Usually with whatever explanation makes sense from where they are standing.
Different people can observe the same decision from different histories, assumptions, and positions within the system and construct very different explanations for what occurred.
Transparency does not guarantee agreement.
It gives disagreement something real to organize around.
Instead of:
I don’t trust what they are doing.
The conversation can become:
I understand how they reached the decision, and I disagree with this part of their reasoning.
That is a very different kind of conflict.
The goal is not to eliminate disagreement.
It is to make disagreement more workable.
A Different Informational Environment
There is another reason this matters now.
The informational environment has changed.
AI has dramatically reduced the amount of time and specialized skill required to begin understanding complex systems.
A person can take governing documents, correspondence, timelines, policies, competing arguments, and years of institutional material and organize them in ways that once required far more time and expertise.
That does not make every conclusion correct. It does not replace professional judgment. It does not replace legal advice where legal advice is needed.
But it changes participation.
Complexity is becoming less effective as a barrier to understanding.
That matters for organizations.
A governance model that depends, intentionally or unintentionally, on people becoming exhausted, confused, or intimidated by institutional complexity is going to work less and less well.
The healthier response is not to become more defensive.
It is to become more legible.
Make the information available. Make the reasoning visible. Acknowledge where judgment exists. Explain how discretion is being exercised. Allow people to inspect the system.
Trust that clarity can withstand scrutiny.
In that environment, legitimacy comes less from informational advantage and more from the quality and visibility of the reasoning itself.
Augmentation, Not Substitution
This is also how I have come to think about outside expertise more broadly.
The best outside support increases the capacity of the people inside the system.
It augments agency.
It helps people understand more. See more. Decide more clearly. Execute more effectively.
It does not quietly become the place where ownership goes to disappear.
Consultants can help. Technology can help. AI can help. Managers can help. Frameworks can help.
But the system still has to know what it is trying to do.
It still has to make decisions. It still has to live with those decisions. It still has to maintain relationships with the people affected by them. It still has to carry disagreement.
That part cannot be outsourced.
Enough Healthy Participation
Healthy systems do not require everyone to become equally enthusiastic about governance.
A few people working well together can change the trajectory of a system.
Two people create movement. Three create more resilience. Four or five people with complementary strengths can distribute work enough that participation stops consuming anyone’s life.
The goal is not maximum involvement.
It is enough healthy participation that responsibility does not collapse onto one person or disappear entirely.
From there, participation can grow.
People are more likely to contribute when the system is understandable. When their role is clear. When they can see where their effort matters. When joining does not mean inheriting everything.
Healthy participation tends to make more participation possible.
What the System Has to Carry
I have been thinking recently about a related principle:
A principle has to survive disagreement.
It is not much of a principle if it applies only when everyone is aligned.
But organizations face a parallel challenge.
For a principle to survive disagreement repeatedly, the culture itself has to be capable of carrying disagreement.
Without hiding from it. Without automatically escalating it. Without outsourcing what the system itself still has to own. Without reducing the people involved to the problem.
That requires more than procedures.
It requires enough trust to remain in contact with one another. Enough transparency to understand what is happening. Enough clarity that responsibility does not disappear. Enough distance for people to recover their center when conflict becomes intense. And enough agency that disagreement does not automatically collapse into force.
Perhaps that is what healthy governance is ultimately trying to create.
Not a system in which conflict disappears.
A system resilient enough to metabolize conflict without losing itself.
The Things We Still Have to Own
I no longer believe the question is whether professional management is good or bad.
That is too simple.
The better question is:
What problem are we asking management to solve?
If the problem is bookkeeping, administration, vendor coordination, expertise, or workload, outside support may be exactly what the system needs.
If the problem is that nobody owns decisions, nobody trusts the process, reasoning is hidden, disagreement cannot be carried, and participation has collapsed, adding another intermediary may not touch the real problem at all.
Because some things remain ours.
We can outsource work. We can outsource expertise. We can outsource administration. We can use technology to amplify what people are capable of doing.
But eventually, human beings still have to decide how they are going to participate with one another.
They have to tolerate some disagreement. Own decisions. Make reasoning visible. Create enough trust for other people to participate. Establish a culture capable of carrying the weight placed upon it.
That is infrastructure too.
Perhaps the most important kind.