People, Structure, Systems: the three layers we read.

When a company slows down, the explanations people reach for are almost always single-layer: “we need to hire,” “the tools are a mess,” “people aren't stepping up.” Sometimes that's right. More often it's a symptom in one layer caused by something in another — and acting on the symptom spends money without moving anything. Three layers, read together, is how you stop doing that.

People

The People layer reads how work is distributed across seats: where you're genuinely short-handed, where the load has quietly concentrated on a few shoulders, and what's exposed if a key seat empties tomorrow. That last one — key-person risk — is the quiet killer in a growing company, because it's invisible right up until the day it isn't. This layer works at the level of roles and load. It never judges named individuals; it looks at the shape of who carries what.

Structure

The Structure layer reads where decisions actually route — not where the org chart claims they do. Who really owns each call, how wide the spans run, how many layers a question crosses before it reaches someone who can say yes. This is where the founder bottleneck and the spans-and-layers problems live. The chart on the wall is fiction until you trace how a real decision moves; the gap between the two is usually the whole problem.

Systems

The Systems layer reads your tools and your documentation: whether the work is written down and tooled for the stage you're entering, or held together by memory and a few people who “just know how it's done.” Undocumented work is the thing that makes every other layer fragile — it concentrates risk on people, and it makes structure impossible to change without breaking something.

The problem you can name is usually a symptom. The real constraint is in the layer you didn't look at.

Why the seams matter more than the layers

Here's the core idea: the constraint usually lives between layers, not inside one.

A “hiring problem” is often a structure problem — you don't need another person, you need an existing seat to actually own the decision that keeps stalling. A “tooling problem” is often a systems-and-people problem — the tool is fine, but the work was never written down, so it lives in one person's head and no software can fix that. A “people aren't stepping up” problem is often a structure problem — they can't step up into a decision nobody gave them the right to make.

Read any one layer alone and you'll confidently solve the wrong thing. Read all three and the seams light up — and the seam is where the leverage is.

From three layers to five moves

Reading the three layers together is what produces the rest of a Staff Analysis: the scale-ready verdict on whether all three hold through your next 2×, and the Top 5 People Moves that fix the seams — ranked, role-level, with a 90-day sequence. Three layers in, five moves out, in five days.