Meadows' ladder, M12 to M1

Where you push decides what changes

A launch has buried your support team in tickets. You have one afternoon of effort to spend. Here are five places to spend it, each on a different rung of the ladder. Pick one and watch the next three years.

Rent a buffer

M11 · Buffers
M12 · weakestM1 · strongest

Team, this pushTeam, hiring as usualBacklog
0Peak team
0Let go after the spike
0Weeks of month-long waits
0Team in year three

What the ladder is telling you

Three reaches, one direction

Numbers move numbers


M12 to M10 · parameters, buffers, structure

Hire faster, rent capacity, add a queue. Real relief, and the system you have afterwards is the system you had before. The next launch finds it unchanged.

Loops move behaviour


M9 to M5 · delays, loops, information, rules

Change how the system answers itself. Order matters here: cut the loop that feeds on the gap before you slow the correction, or the slower correction feeds it.

Purpose moves everything


M4 to M1 · self-organization, goals, paradigm

Ask what the support team is for: closing tickets, or fewer reasons to open one. The answer rewrites every rung below it, and it is resisted hardest.

The Motus Ladder

Where you push, who can reach it, and when you may say it held

Meadows' twelve rungs, kept whole. Davara adds who can pull each one, the proof a push needs, and the clock it keeps. Pick a rung.

A lever is placed by her, witnessed by someone else, and held when its falsifier is read on the rung's clock and does not fire. Only held is leverage.

What would prove this wrong. Turn on an honest auto-reply that names the real wait. If re-filed tickets per new ticket have not fallen by half within two months, re-filing is not what feeds this backlog, and the M7 result above is fiction.

The math, in full
An illustrative model · 36 months · built by Davara