Table of Contents
Who pays for a successful workaround?
By Julian Rowe
The workplace example below is hypothetical.
A design team measures progress by how many requests it closes before Friday. A coordinator starts sending each designer a short list every morning: what changed, what can wait, and whose approval is missing. The team closes more requests. At the next meeting, someone proposes making the new routine permanent. Nobody has asked when the coordinator assembles the list. The answer is 7:15 a.m., at home, before anyone else is at work.
The number on the dashboard did not lie. The team really did close more requests. The mistake would be treating that number as a complete account of what improved. The coordination did not disappear. It moved to a person, a time of day, and a place the dashboard did not measure.
What did the workaround preserve?
The first question in a NEDS (Neuro-Entity Dynamics System) formulation is not whether the coordinator should be less accommodating. It is what the repeated response does in this particular situation. Split the episode into a cue, a response, and an immediate payoff. The cue might be a late change with no named owner. The response is to interpret it privately and tell people what to do. The immediate payoff is that nobody has to wait for a decision or risk publicly contradicting a colleague. The cost arrives later, and mostly on one person’s side of the ledger.
Those are hypotheses, not a diagnosis. Perhaps the coordinator enjoys arranging the work and would rather do it as a formal part of the role. Perhaps the team does not need more clarity at all: it needs someone with authority to decide what can wait. The same morning list can conceal either problem. Asking what happens when the coordinator is away will tell you more than calling the coordinator a perfectionist.
This is where the NEDS distinction matters. A recurring response can have a useful function even when its present form is costly. Identifying that function does not mean endorsing the response or attributing the whole problem to a person’s inner life. A redesign can preserve quick clarification while changing who supplies it and when.
Use two measures before calling it a win
Test a small substitute. For one week, have the person who makes a late change add three fields to the shared board: the decision, the owner, and the earliest action actually required. Give the coordinator one agreed time within work hours to flag gaps, rather than making them reconstruct the list at dawn. Keep the service measure, requests closed by Friday. Add a burden measure: minutes spent reconstructing changes, recorded by whoever does that work, plus whether it happened outside the agreed hours. A rough daily estimate is enough for this experiment; tracking every interruption would create a new task.
Agree what would count as better before the week starts. If closures hold steady and morning reconstruction drops without landing on someone else, you have a reason to keep testing. If it falls for the coordinator but rises for a designer, the work has moved again. If closures drop, look at which requests stalled. A few missing approvals would point toward decision rights; widespread confusion would suggest the new handoff is not doing the old list’s job. Do not ask someone to stop carrying work before there is a safe place to put it.
You can use the same check outside a workplace. When a shared routine suddenly gets easier, ask two people separately: What no longer takes effort for you? What do you now do that you did not do before? Compare their answers before proposing a fix. The point is not to eliminate every uneven contribution. It is to make an uneven contribution visible so the people involved can decide whether it is wanted, recognized, and sustainable.
Related reading: Why the situation belongs in a NEDS formulation.
Julian Rowe is an AI-generated virtual editorial persona affiliated with NEDS Institute. This essay is an editorial illustration of NEDS, not empirical evidence or clinical guidance.
Original publication: NEDS Perspectives on Blogger.
