When Good People Are the Only Plan

Want people systems that actually hold up when things get hard? Want to stop reinventing the wheel every time a manager needs guidance or someone leaves unexpectedly?

Of course you do.

You may have even tried a few things already. A new handbook. A performance review template someone downloaded from the internet. A team meeting where you talked about "getting more consistent." And yet somehow, the same situations keep landing on your desk.

In this post I'll share four rookie mistakes small to mid-sized organizations make when it comes to managing their people — and what to do instead. Grab a coffee and let's get into it.

What does "people infrastructure" actually mean?

Before we talk about what goes wrong, it helps to be clear about what we're working toward.

People infrastructure is simply the set of structures that support how your organization manages its staff. Think of it as the organizational equivalent of a building's foundation — you do not notice it when it is working, and you absolutely notice it when it is not.

In plain terms, it is the collection of processes, expectations, and practices that answer questions like: How do we hire? How do we onboard someone? What do we expect from our managers? How do we handle a performance issue? What happens when someone leaves?

In other words, it is the difference between decisions being made consistently and decisions being made by whoever is available that day.

For your organization, that means:

• Staff have roughly the same experience regardless of which manager they report to

• Leaders spend time on things that require leadership, not on problems that should have a process

• The organization can function during transitions without everything depending on one person being present

With that out of the way, let's look at the mistakes.

The Number One Rookie Mistake: Assuming the informal system is the same as a system

Meet Sarah. She is the executive director of a 90-person nonprofit that has been around for fifteen years. The organization has good values, a committed team, and a culture people genuinely like. When I ask Sarah how they handle onboarding, she tells me about Marcus — a program director who has been there since the early days and who is great at bringing new people in. When I ask about performance conversations, she tells me about the way her senior team talks things through. When I ask what happens when a manager is struggling, she describes how she usually finds out through the grapevine and steps in.

Do you see it?

Every answer Sarah gives me is a person, not a process. Marcus is the onboarding system. The senior team's communication style is the performance system. Sarah herself is the escalation system.

This is the most common mistake I see, and it is completely understandable. Informal systems built around capable people often work beautifully — right up until Marcus takes another job, or the senior team dynamic shifts, or Sarah is stretched too thin to catch everything.

Informal systems feel like systems because they produce consistent results. The problem is they only produce consistent results when the right people are present, available, and paying attention.

This mistake persists because:

• It is invisible when things are going well — the process is working, so there appears to be a process

• The people holding it together are often excellent at what they do, which makes the dependency easy to miss

• Building actual systems takes time that never feels available when the informal ones are holding

Have you been relying on specific people for so long that you are not sure what the process even is without them?

That is not a failure of leadership. It is what happens when organizations grow faster than their infrastructure. It is extremely common in mission-driven organizations where relationships and trust have always been the currency.

What to do instead:

Start by naming your Marcuses. Identify two or three processes in your organization that depend heavily on a specific person's knowledge, availability, or judgment. Then ask: if that person were not here next week, what would actually happen? The answer tells you where to start building.

You do not need to document everything at once. Pick one process, write down how it actually works — not how it is supposed to work — and share it with one other person. That single act changes the conversation about what is at risk.

Mistake 2: Treating manager consistency as a personality issue

None of us is naive enough to think the first mistake is the only one. If it were, HR would be a much simpler field.

The next mistake I see regularly is assuming that inconsistency across managers is just a matter of different styles.

Here is what actually happens. One manager gives direct, timely feedback. Another avoids hard conversations for months. One holds their team to clear expectations. Another lets things slide until something escalates. Leaders observe this and think: they just have different approaches. Staff experience it as: the rules are different depending on who you work for.

That is not a style difference. That is a fairness problem.

This mistake happens because management style is a real thing, and respecting it feels like respecting autonomy. The trouble is that style governs how someone manages — their warmth, their communication preferences, their energy. It does not govern whether they have a performance conversation or give feedback at all. The latter is an expectation, not a style.

When organizations allow wide inconsistency across managers, staff lose trust in the institution itself, not just in individual managers.

What to do instead:

Get specific about what you expect from every manager, regardless of department or style. Not a lengthy competency framework — just three or four concrete expectations that apply across the board. Write them down. Share them explicitly. Check in on them. That is not micromanagement. That is clarity.

Mistake 3: Waiting until something breaks to build the process

This one is easy to make, and honestly, I have seen it happen even in organizations that knew better.

The mistake is treating people infrastructure as a reactive project. Something goes wrong — a messy exit, an employee complaint, a manager situation that escalates — and suddenly there is urgency to build a process. The process gets built for that situation. Then things calm down and the next gap does not get addressed until something else breaks.

The reason this happens is that building proactively requires spending time on something that does not yet feel urgent. In small to mid-sized organizations, there is almost always something that feels more urgent. The people infrastructure work gets pushed, not because it is unimportant, but because nothing is currently on fire.

The cost is that you are always building in response to a problem rather than ahead of one. That means the process is being built while someone is already hurt, already frustrated, or already on their way out the door.

What to do instead:

Set aside a small amount of time each quarter — even an hour — to ask: what people situation is most likely to catch us off guard in the next six months? Then take one concrete step toward that, before it becomes urgent. It does not have to be a big project. It just has to happen before the disruption that makes it obvious.

Mistake 4: Confusing a good culture with a functional HR system

This one is worth naming directly because it shows up most often in organizations that are genuinely doing good work and genuinely care about their people.

The mistake is believing that because your culture is strong, your people systems are too.

Culture and systems are related but they are not the same thing. A strong culture tells you what people value and how they treat each other. It does not tell a new manager what to do when a staff member is underperforming. It does not ensure that two people who file a complaint are handled with the same process and the same fairness. It does not protect an employee — or the organization — when something goes wrong.

Organizations with strong cultures sometimes have the hardest time building systems because the culture has been doing so much of the work. The relationships are good. People trust each other. The informal approaches have mostly worked. It can feel unnecessary, even vaguely corporate, to put more formal structures in place.

But culture is not scalable in the way that systems are. As organizations grow, change, or navigate difficulty, culture alone cannot hold everything together.

What to do instead:

Think of systems not as a replacement for culture but as the structure that lets your culture actually function at scale. A clear process for handling a difficult situation does not make your organization less human. It makes it more fair. And fairness is usually at the center of the values organizations like yours are trying to live out.

A personal note on getting here

When I first started working in HR at a small nonprofit, I thought good HR was mostly about relationships and good judgment. I was not wrong exactly, but I was missing half the picture.

What I learned over the years — slowly, and sometimes the hard way — is that good judgment without structure produces inconsistency. And inconsistency, even when it comes from a place of care, erodes trust over time.

The organizations I have seen navigate hard moments most gracefully were not the ones with the biggest HR budgets or the most sophisticated systems. They were the ones that had done the quiet, unglamorous work of writing things down, clarifying expectations, and building processes before they needed them.

That is the work I find most meaningful. Not the crisis response — the prevention.

Here are a few things I wish I had known earlier:

• Start smaller than you think you need to. One documented process is more valuable than a documentation project you never finish.

• Name the dependencies before they become vulnerabilities. Every organization has a Marcus. Know who yours are and what they are holding.

• Consistency is an act of care. When staff know what to expect and can trust they will be treated the same way as their colleagues, that is not bureaucracy. That is respect.

About People, Honestly.

In short: informal systems are not the problem. Staying dependent on them longer than makes sense is.

The good news is that building people infrastructure in a small to mid-sized organization does not require a large HR team, expensive software, or a complete overhaul. It requires starting somewhere specific and building steadily from there.

If any of this resonated, I write about exactly this kind of thing every Friday in People, Honestly. - a short newsletter for leaders at small to mid-sized organizations navigating the people side of running an organization.

Subscribe below to get it in your inbox every Friday.

And if you want to think through where your organization's gaps might be, I am always happy to connect.