Leverage and fragility

Leverage increases the effect of a decision, resource or structure. It lets a company obtain a larger result from a smaller base. The same amplification can also increase fragility when the operating structure has little slack, weak visibility or too many hidden dependencies.

In brief

Leverage is not only financial. It appears whenever a small node has a large system effect: a key person, a major customer, one operating tool, one approval point, one supplier, one data source, one automated decision.

Leverage can create speed and growth. It can also make the company brittle. The question is whether the organisation has enough legibility, buffer and governance to absorb what leverage amplifies.

Operational definition

A structure is leveraged when a change in one point produces a larger effect across the system.

A structure is fragile when a disturbance produces disproportionate consequences because alternatives, buffers or visibility are weak.

Leverage becomes dangerous when it sits on an unclear base. A fast process with poor data spreads errors faster. A major customer with no capacity buffer absorbs the organisation. A delegated role without decision rights amplifies ambiguity.

Why it matters for SMEs

SMEs often use leverage because resources are scarce. One experienced person coordinates several flows. One customer funds growth. One spreadsheet connects the work. One system promises scale.

This can be efficient until the dependency is stressed. Then the same structure that created speed becomes a constraint.

For external evaluation, the key issue is whether leverage is controlled. Concentration, key person dependency, weak data ownership and single-point approvals all affect resilience.

Observable signals

Look for one person whose absence stops several flows.

Look for one customer, tool, role or approval point carrying disproportionate weight.

Look for growth that increases coordination faster than capacity.

Look for automation applied to unstable decisions.

Look for small disturbances creating large operating consequences.

Common mistakes

The first mistake is seeing leverage only as upside. Amplification works in both directions.

The second mistake is scaling before making the base legible. Scaling an unclear process scales confusion.

The third mistake is removing all buffers around high-impact dependencies.

The fourth mistake is assuming a profitable company cannot be fragile. Performance and resilience are different properties.

Operational example

A company grows around one large customer. The relationship improves utilisation and makes planning easier at first. Over time, purchasing, production and staffing adapt around that customer’s rhythm.

When the customer changes forecast, the impact spreads through the whole company. Other work waits, priorities are reopened and the founder becomes the live coordinator.

The issue is not that the customer is bad. The issue is unmanaged leverage. The company introduces concentration monitoring, capacity rules and a plan to reduce dependency before accepting another large commitment.

Diagnostic questions

Which person, customer, tool or decision point has disproportionate effect?

What happens if that node is unavailable for two weeks?

Which buffer protects the dependency?

Which process weakness would be amplified by scale?

Which leverage is intentional, and which accumulated by habit?

What would reduce fragility without destroying useful leverage?

Practical implications

Map the high-leverage nodes. For each, identify alternatives, buffers, owner and early warning signals.

Before increasing leverage, improve legibility: process clarity, data ownership, decision rights and stop rules.

Keep deliberate slack where amplification is high. Efficiency without buffer can look strong until the first disturbance.

MARTRO reading

In MARTRO’s reading, leverage and fragility explain why some companies look strong and still have exposed structures. The issue is not performance alone, but sensitivity to hidden dependencies.

This connects finance, operations and governance: customer concentration, key person risk, decision bottlenecks, system dependency and thin operating buffers are related forms of amplified fragility.

Frequently asked questions

Is leverage only financial? No. It can be operational, organisational, commercial, technological or cognitive.

Is fragility the same as poor performance? No. A high-performing company can still be fragile if performance depends on a few exposed nodes.

Can leverage be useful? Yes. It can create speed and scale. It becomes dangerous when unmanaged.

How do we reduce fragility? Increase legibility, diversify dependencies, create buffers and clarify decision rights.

Why does this matter to investors? Because exposed leverage increases the sensitivity of future performance to a small number of conditions.