Draft pattern
The Dashboard Changes the Behaviour
People learn what the display notices and adjust their work to be seen by it.
How it starts
A dashboard is introduced to improve visibility. It promises shared facts, fewer surprises and a calmer way to spot trouble before it becomes expensive.
How it drifts
Once people know what is visible, they start managing the display. Work is timed, labelled or split so the dashboard looks healthier. The display becomes part of the operating environment.
Why it survives
The dashboard is useful enough that nobody wants to remove it. The problem is subtler: it is treated as a mirror, when it has become a lever.
What to watch
Look for teams explaining their work in dashboard categories before they explain the work itself. The reporting surface has begun to shape the behaviour it claims to observe.
Questions worth asking
- What behaviour changed after the dashboard appeared?
- Which useful signals are still off-screen?
- Can people safely say the dashboard is misleading?
- Does the display help learning, or mainly help judgement?
Comment carefully
Send examples or corrections by email. Responses are private by default and manually reviewed before anything is quoted. Respond to this draft.