People chronically work the wrong row — money moves when the problem is exhaustion, effort when the problem is a goal they no longer hold. Walk the check below: every answer is a choice from a list, nothing is typed, nothing is scored, and the reading names the one constraint doing the most work — which row, never how bad.
These stay in this browser. Nothing is sent anywhere, put in the address bar, or scored. This walks one check — which pressure is actually binding — and names the row, never a number.
Which pressure is binding
Answer at least the first two rows — your state and your buffer — and the reading appears here. It names the one constraint doing the most work, so you don’t spend effort on the wrong row.
Reading the board: which pressure is binding
When you look at it, the useful question is not “what should I fix?” but “which row is actually binding right now?” Most people misidentify this and then work the wrong problem, with great diligence, for a long time. The reason is simple: you work the thing you can see. Money is legible, so people work money; effort is always available, so people apply more effort. But the binding constraint is disproportionately one of the three things you cannot see from inside — your own condition, whether a wall is really a wall, and whether you still want the thing you are aiming at.
So it is worth checking in an order, because skipping a step quietly invalidates the ones below it:
Is a condition active? Burnout, depression, acute grief, exhaustion, danger. If so, stabilise before optimising — resource work done inside an unaddressed condition gets undone. If it is danger, stop here and get to the help-now page.
Is there any slack? Not money — margin. Would one unexpected demand break something? If there is none, the buffer is the binding constraint, because almost every improvement move needs some slack to execute.
Is it a wall or a door? If it is genuinely a wall, more effort is not a strategy — adapt, redesign around it, or accept it, which frees everything you were spending on it. If you are not sure, finding out is usually a cheap move.
Do you still hold the aim? Before optimising a route, confirm the destination. People improve their execution of a goal they would no longer choose, and experience the result as meaninglessness.
Is the aim in conflict with another you also hold? If so, that conflict is the problem, and it will have been presenting itself as a time-management complaint. No calendar resolves a conflict between two things you both want.
Only now: resources and moves. Which is where nearly everyone starts, and it is the sixth thing to check, not the first.
One honest limit, because it changes how to use all of this: a board filled in while burnt out is a board filled in by burnout. It will reliably under-report the condition row and over-report the stuck row — and then hand the reading back to you with the borrowed authority of something written down. The only real correction is external. If you can, show it to one person who knows you well and is standing outside the situation, and let their reading of your condition outvote your own.
One last thing about whatever you decide to do next. Asking, waiting, and accepting are moves too — they are on the list of things you can do here, not what is left when the list runs out. Waiting deliberately, while a slow decision is made somewhere else, is not the same as doing nothing, and it is often the correct move. Asking is not a confession that you could not manage alone; it is the cheapest way there is to move something. And accepting a thing that will not move frees everything you were spending on it, which is a gain and not a surrender.