Skip to content

PAN Lab pressures

Pressure

Monitoring goes stale

The dashboards still run, but nobody has to act on what they show. Nobody revises the alert levels set at launch, nobody holds the scheduled reviews, and nobody reads the alerts. Drift builds while the controls stay the same.

What it is

A team sets up monitoring when a system launches, when attention is highest. Months later the people who set it up have moved to other work, and the monthly review has become an occasional one. The screens still show numbers, so everyone assumes that someone is watching.

What it pushes on in the Lab

In the Lab, this pressure lowers the engagement of deployment authority, which is whether someone with real power to change or halt the deployment watches it on a regular schedule. It also amplifies the failure regime, pushing the network toward failures that cascade rather than correct themselves.

decreasedDeployment authority engaged
amplifiedFailure regime

Who feels it

Nobody feels it at first, and that is what makes it dangerous. The clients feel it when a worker acts on an error that a working review would have caught.

What answers it

An answer has to restore a real review schedule, stop the system when its alarms fire, or correct drift before it compounds. Each lever below does at least one of these.

Levers in the Lab that push the other way on something this pressure pushes on:

The list leaves out levers the Lab has retired, levers it keeps as counter-examples, and any lever no network offers.

Where it starts switched on

The evidence behind its effects

The Lab cites no claim from the evidence registry for this pressure's effects. The Lab's authors set the direction and size of each effect.

Switch this pressure on in the PAN Lab and watch which way it pushes the network.

Open the PAN Lab