The Reason Your People Fixes Don't Stick

clare2635
Apr 20
4 min read

Most founders who recognise a people operating system problem do one of two things: they try to fix everything at once, or they reach for the most visible symptom. That usually means a new project management tool, a team offsite, or a clearer job description. None of these are bad ideas. But starting there almost never works, because the sequence matters as much as the fix.

Why the order matters

A broken structure cannot be patched from the top. If you build a project management tool on top of unclear ownership, you get a well-organised record of confusion. If you run training before people have clear authority over their work, you give them skills they cannot apply. If you try to install a management cadence before anyone knows what they are accountable for, you end up with a meeting schedule attached to nothing.

The most effective repairs to a people operating system follow a specific order: role clarity and decision rights first, then workflow standardisation for the processes that touch clients or revenue, then a management cadence, and tools and training last.

Fix role clarity and decision rights first in your people operating system

Role clarity and decision rights reduce more friction faster than almost anything else. Most of the operational problems in a growing business (errors, escalations, rework, slow decisions) trace back to unclear ownership. When people do not know what they are responsible for, they either overstep or they wait. Both cause problems.

Decision rights are the part most businesses miss. It is not enough to assign someone ownership of a process if they do not also know what they are authorised to decide when something goes wrong. The account manager who "owns" client onboarding still escalates to the founder if they do not know whether they can approve a scope change. The operations lead who "manages" the delivery team still defers upward if they are unsure whether they can shift a deadline without sign-off.

Getting this right does not require a restructure. It requires a clear answer to two questions for every significant role: what does this person own, and what are they authorised to decide without asking? When people have those answers, a significant amount of daily noise clears without any other intervention.

Identify which workflows to standardise next

Once people know what they own, you can see which processes actually need documentation. Not all of them. Start with the highest-volume or highest-risk: the processes that touch clients or revenue most often, and the ones where errors or inconsistency are already visible. A client onboarding process that runs differently every time is a better starting point than an internal approval checklist that runs once a quarter.

Document those first. Keep it practical. A clear, short process that people actually follow is worth far more than a thorough one that nobody reads.

What a management cadence should look like

A management cadence is a predictable rhythm: daily visibility on work in progress, weekly accountability conversations, monthly performance discussions. It replaces ad hoc escalation with a structure where issues surface early, rather than landing on the founder's desk fully formed.

This is not about more meetings. A well-designed cadence often means fewer conversations overall, because the routine ones happen at the right time and the right level. The goal is a business where the founder is not the first point of contact for every problem the team should be resolving themselves.

Why tools and training come last

The instinct to start with tools is understandable. They feel concrete, they have a visible price tag, and they give the impression of progress. But a tool built on top of a broken process does not fix the process. It gives the confusion somewhere to live.

The same applies to training. Skills development works when people have clear ownership of their work and the authority to apply what they learn. Without that foundation, it is expensive and easy to dismiss as something that "doesn't work here."

Get the structure right first. Then ask which tools support it.

Q: What is the difference between a job description and role clarity?

A: A job description lists responsibilities. Role clarity goes further: it defines what someone owns end-to-end, what they are authorised to decide without escalating, and where their authority stops. Most businesses have job descriptions. Very few have genuine role clarity.

Q: How do I know if role clarity is actually the problem?

A: Two questions are worth asking. Can a capable new person do this work without repeatedly asking the founder? Can the team make routine decisions without escalation? If the answer to either is no, role clarity and decision rights are almost certainly the issue, not a gap in tools or training.

If you haven't yet identified where the biggest gaps are in your people operating system, the Is Your Business Scale-Ready? diagnostic is the right place to start. It takes about ten minutes and gives you a clear picture of where to focus first.

If you would prefer to talk through what this looks like in your firm, book a scale-readiness call.