Edition

These pages don’t end in a lecture. They end with what to do next and, just as important, what not to decide yet. When the ground is still moving, knowing which decisions can wait is often worth more than any single answer.

Planned, and not built yet

Named here so the gap is visible where you would feel it, rather than only on the methodology page. Each of these is honestly missing: nothing below exists in any form, and none of it has a date.

  • PlannedCrisis and recovery as a system rather than page by page — seventh, because the guide has to serve the reader whose life has left the common route, and because recovery deserves to be described mechanically rather than moralised about.
  • PlannedArchetype comparison and resemblance — seeing which patterns a situation resembles, with resemblance, prevalence, confidence and viability kept firmly separate, and never used to assign anyone a destiny. Behind a research gate, because a resemblance read as a destiny is the failure mode.

If none of these is quite it, start from what happened and let two questions point you, or lay the whole situation out first. If you need a person rather than a page, here are numbers.

Waiting on a slow decider

An application in its ninth month. A result that takes three weeks. A hiring process that said “we’ll be in touch shortly” a month and a half ago. Someone who has said they need time to decide whether to stay. As subjects these have nothing to do with each other. As situations they are identical: something large about your life is being decided by somebody who is not you, on a timetable you do not control, with no reliable information about progress — and the whole interval is unspendable, because you cannot commit to anything that either answer would undo.

The first useful thing to know is that this costs something. Waiting is not free time; it is time with a background process running, which is why people come out of these stretches exhausted having apparently done nothing. Observers call it procrastination and so, often, does the person doing it. It is neither. Four moves work across the whole family:

  • Find the real timescale, from someone who knows. Not the published one. Institutions and people both routinely quote a default rather than an estimate, and a real answer converts an indefinite wait into a bounded one, which is an enormous psychological difference for no cost at all. This is the highest-value move here and almost nobody makes it.
  • Establish what is genuinely unaffected by either answer, and do that. There is nearly always more of it than it feels like. The freeze usually spreads far beyond what the decision actually touches.
  • Prepare the worse answer once, specifically, in writing — then stop. Not rumination: one concrete pass at what you would actually do. It converts an unbounded dread into a named set of steps. Doing it once helps; doing it nightly is the failure mode, and the difference between the two is whether anything is written down at the end.
  • Set a review trigger. A date on which you chase, escalate, or act as though the answer were no. Without one the wait extends indefinitely by default, and the default is somebody else’s convenience rather than yours.

And four things that reliably do not work, which is worth knowing because they are what the time goes into: chasing more often than the real timescale warrants; re-reading what you submitted; re-deciding every evening what you will do in each case; and narrating the whole thing to everybody, which converts a private wait into a public one you then also have to manage.

Not solvable, only navigable

Most practical writing treats every difficulty as an optimisation problem whose solution has not been found yet. Some difficulties are not that. Where two things you genuinely want are incompatible, or two obligations both bind, there is no arrangement that satisfies both — and presenting one as though there were is how people conclude they are failing at something everyone else has worked out.

Naming the category is the substantive content. It says: the thing you are looking for does not exist, you are not missing it, and what remains is choosing which loss to take deliberately rather than letting it be chosen by whichever demand is loudest. Two tests are worth running first, because both possible errors are expensive in different directions. Is one side a proxy? — often what looks like a want is standing in for something else, and the things underneath turn out not to conflict at all. Is the scarcity a total or a simultaneity? — two commitments needing more hours than exist is a hard conflict; two commitments that both need Tuesday frequently has moves that a hard conflict does not.

If it survives both tests, the honest output is a way through rather than an answer. The conflict step of the board is where a real case gets written out in its own words, and the guidance flow is willing to finish by saying that no ranking is available yet and naming what would change that. On this class of situation, that ending is not the instrument failing. It is the instrument being accurate.