In order
Why a list is not a plan
A list of thirty-six things looks like a plan and is not one. The difference is forty-two dependencies, and no amount of ticking will reveal them.
Everybody in this situation ends up with a list. Thirty-six things, or some number near it, written down in the order they were heard about.
A list of this kind is not a plan, and the way it fails is specific enough to be worth setting out. A team turning this diagram into a limited operational pilot can explore the current functionality before choosing which time and project signals are genuinely necessary.
What a list implies and the map denies
A list implies three things. That the items are independent. That progress is the number ticked. And that any order will do, so the sensible one is whatever is convenient. For broader institutional research related to mobility, work and administrative systems, consult CEPR.
All three are false here.
| the list assumes | the map says |
|---|---|
| items are independent | 94 dependencies between 36 items |
| progress is items ticked | 6 items can be ticked, and they open nothing |
| any order will do | 42 dependencies admit no order at all |
The ticking problem
Six of the thirty-six steps can be completed while the map is genuinely stuck, and they are exactly the six papers brought from home. Nothing else in the record can be reached without first getting into a ring.
A person working a list would finish those six, see a sixth of the list crossed off, and reasonably conclude that the thing had begun.
It has not begun. Those six between them unlock nothing at all: every step that waits on them also waits on something inside a ring. Seven further steps stand outside every ring themselves, and all seven are held up by a predecessor that is inside one.
On a list, a sixth ticked means a sixth finished. On this map, a sixth ticked means the only part that could be done has been done, and nothing has opened as a result.
The order problem
The list's other assumption is that an order exists and that finding it is a matter of thinking about it for long enough.
For fifty-two of the ninety-four dependencies, that is right. Six layers, a clear bottom, a clear top.
For the other forty-two there is no order to find. A person who keeps rearranging a list, convinced that one more attempt will produce a sequence that works, is doing arithmetic on an object that has no solution. The failure feels like incompetence and is not.
What a plan would have to contain
Three things a list does not.
Which items are blocked by a circle rather than a queue. Those are twenty-three of the thirty-six, and nothing about them improves with time.
Where each circle can be entered. Eight soft dependencies open twenty-nine of the forty-six rings. The other seventeen have no opening at all, which means they are entered — in practice, by everybody — by some route the map does not contain: an exception, a sympathetic clerk, a document accepted that should not have been.
What is expiring while the circle is being walked. Nineteen of the forty-six rings take longer to go round than the shortest-lived paper inside them keeps. For those nineteen, going round once is not progress; it is a loop that consumes its own input.
The honest shape of a plan here
It would not be a sequence. It would be a small number of simultaneous bets: several provisional versions of things, several documents deliberately obtained late so they do not go stale, and an acceptance that two or three items will be done twice.
That is what people in this situation actually do, and it is why their accounts of it sound chaotic. The chaos is an adaptation to a map with forty-six circles in it, not a failure to be organised.
Doing something twice on purpose is the correct response to a ring. It looks like disorganisation and it is the only available technique.
What a list does to a person
It converts a structural problem into a personal one.
Thirty-six items, six crossed off, thirty remaining and none of them possible. There is no column on a list for blocked by a circle, so the thirty look like thirty things not yet done, and the person holding the list looks — to themselves most of all — like somebody who has not got on with it.
That is the practical harm of the wrong instrument. The list is not merely unhelpful; it is actively misleading about whose fault the situation is.
| what the person sees | what the map says |
|---|---|
| thirty things undone | twenty-three of them have no order |
| a sixth of the work finished | the only orderable part is finished |
| no progress in a month | the maximum possible progress |
A person who has done the six brought papers in a month has done everything the rules permit. There is no faster version.
The most useful thing a map like this can do for anybody is to say that the stuck part is not the list-keeper.
What this page is not
It is not advice. This record names no country, office or kind of permission, states no requirement, and has no view about what anybody should do.
What it offers is a distinction that a list cannot represent: between being behind and being blocked. Twelve of the thirty-six steps can be finished by effort. Twenty-three cannot be touched by effort at all, and telling one group from the other is the only part of this that planning can actually help with.
Next along the row
- After the file, a straight line
Once the file is lodged the map stops being a knot. Five steps remain and they run in sequence, ninety of thei - The dependencies most likely to be wrong
Three judgements in this drawing carry more of its conclusion than the rest put together. Here they are, named - The fifty-two that behave
Most of the map is not tangled at all. Fifty-two of the ninety-four dependencies sort into a plain order, and - Six layers, and what sits in each
With the circular dependencies set aside, the map sorts into six layers. Thirteen steps sit at the bottom and