Why payroll pressure rarely sits in isolation

The same ratio, three different stories

Consider an elevated payroll load alongside its neighbours:

• Payroll high, cash runway short. Now it's an execution and liquidity problem. The business is carrying a wage bill it may struggle to fund, and every payroll cycle draws down a buffer that's already thin. This is the combination that constrains decisions — you can't easily restructure a team you're mid-way through paying.
• Payroll high, margin compressing. Now it's a pricing or scope problem. Labour cost is rising faster than the value being captured, which usually means work is being underpriced, projects are overrunning, or the mix has drifted toward low-margin clients. The payroll figure is the symptom; the pricing model is the cause.
• Payroll growing, revenue flat or falling. Now it's a question of timing and intent. Payroll ahead of revenue is expected in a growth phase where you hire before the income lands — and worrying if there's no growth to justify it. Same number, opposite conclusions, entirely dependent on the trajectory beside it.

The lesson is simple: don't review payroll pressure as a line item. Review it as one corner of a picture that includes cash, margin and revenue direction.

Why connected risks need boundaries

Once you accept that signals combine, it's tempting to connect everything to everything. That's a mistake in the other direction. A connected-risk view is only useful if it's disciplined, and discipline means clear boundaries:

• A connection should be informational, not authoritative. Flagging that payroll load and liquidity pressure are compounding is useful context. It should not silently change the severity of either individual item or reorder your priorities on its own. The advisor still assesses each risk on its own terms; the connection informs that judgement rather than overriding it.
• The relationship should be real, not decorative. Two metrics moving at once isn't a connected risk. A connected risk is a specific, explainable interaction — liquidity pressure plus payroll load constrains workforce decisions; margin compression plus payroll pressure suggests delivery costs are misaligned with pricing. If you can't articulate why the combination matters, it isn't one.
• It should be transparent and repeatable. An advisor should be able to see exactly why a combination was surfaced — which signals, at what levels — and get the same result every time from the same inputs. A connected-risk view that can't be explained is just a black box with extra steps, and it erodes the trust the individual signals earned.

What this means in practice

When payroll pressure appears in a review, resist the urge to act on it directly. Instead, ask the three neighbouring questions. Is cash tight enough that this wage bill is a funding risk? Is margin holding, or is labour outrunning the value it produces? Is revenue moving in a direction that justifies the load? The answers turn a vague "payroll looks high" into a specific, actionable conclusion — and often into a very different recommendation than the ratio alone would suggest.

Payroll is a good example precisely because it's so often misread in isolation. But the principle generalises: the signals that matter most in a business are the ones that only make sense together. The advisor's job isn't to react to each metric — it's to read the combination, with enough discipline that the connections illuminate the picture rather than clutter it.