Hebel

Systems archetypes

Attractiveness Principle

Growing systems hit several limits at once and cannot resource-fix them all — some aspects improve while others erode.

RGrowth engine (attractiveness → inflow)BLimit 1 (e.g. service capacity)BLimit 2 (e.g. infrastructure/sales)

Definition

The “Attractiveness Principle” is an advanced extension of Limits to Growth. Where that archetype pits a growth engine against a single limit, here it runs into several competing limits at once. Because resources are insufficient to fix every constraint, only some dimensions of attractiveness can be sustained — others inevitably degrade. The core lesson: you cannot be all things to all people.

Structure

At the centre sits a reinforcing loop (R) as the growth engine: attractiveness draws inflow, and inflow feeds further growth. But this engine runs into not one but several balancing loops (B) simultaneously — for example a service-capacity limit (B) and an infrastructure-or-sales limit (B). Each constraint alone would brake growth. Because resources are finite, you can only invest in some of the bottlenecks; the unaddressed limits activate and let their attractiveness dimension decay, even as others keep growing.

When it applies

Scaling tech companies trying to hold feature breadth, service quality and sales velocity at once. Urban development forced to choose between new attractions, traffic capacity and affordable housing. Whenever success draws on several scarce resources simultaneously and the budget cannot cover them all.

Leverage points

The reflexive mistake is to spread scarce resources thinly across every limit — then attractiveness erodes a little everywhere. The better move is a deliberate, proactive decision about which constraints you will permanently accept (and therefore which attractiveness dimensions you will let degrade), so that investment concentrates on the bottlenecks that matter most to your core strategy. Strategy here means explicitly refusing to be all things to all people.

Examples

A SaaS provider whose user base explodes: it cannot simultaneously ship new features, sustain support quality and grow sales — if it picks features and sales, support quality visibly collapses. A popular city that invests in culture and tourism while transit and rents spiral out of control.

Model it in Hebel

Build this pattern as a causal loop and simulate it.

Get invited

Related concepts

Sources: Kim & Senge (1994), Putting Systems Thinking into Practice · Senge (1990), The Fifth Discipline