how vurr works
three moves. sharpen the thinking, lock the decision, execute the move. here is what each one actually involves.
most tools in this space pick one end of the problem. a chat tool helps you think and then forgets. a task tool holds what you decided but had no part in deciding it. vurr covers the span between the two, which is where decisions actually go to die.
01 — sharpen
you arrive with something unformed. "i think i need to change pricing." "something is wrong with how the client work is going."
sharpening turns that into a decision that can actually be taken. it pressure-tests the reasoning, separates the two decisions you have tangled into one, and names the thing you are avoiding if there is one.
this is the step most people skip, and it is why so many decisions sit. you cannot commit to "sort out pricing". you can commit to "move new client pricing to 4,500 from 1 september".
02 — decide
the call gets locked. not written in a note, locked as a structured object with fields:
- confidence, one to five. how sure you are, recorded at the time, before hindsight rewrites it.
- impact, one to five. so the important calls can be told apart from the noise later.
- a deadline. the date you decide by, not the date you are certain by.
- a review date. when you come back and log what actually happened.
the fields are the whole trick. they are what turns a year of decisions into something you can actually query, instead of a folder of notes you will never reread.
03 — execute
a locked decision produces tasks. progress, completion, and then the outcome logged on the review date.
this is the part that closes the loop. a decision recorded but never executed teaches you nothing, because there is no result to compare your confidence against. vurr is built around movement for that reason. it is not a journal.
then it repeats, and that is where it gets interesting
one locked decision is admin. fifty, with outcomes attached, are a record of how you operate that no chat interface can hand back to you.
after a few months the pattern layer has something to work with: where you stall, when you move fastest, what conditions make you commit, whether your confidence runs high or low and in which direction. those readings are made against the self force framework rather than assembled from nothing, which is why they get specific faster than a generic tool can.
what it is not
- not a mood journal. it tracks what you decided and whether you moved, not how you felt.
- not an oracle. it sharpens your thinking, it does not hand you the answer. the call stays yours.
- not a task manager. tasks exist to close decisions, not to be a second inbox.
if you want to see the cost side of this before committing to anything, the decision fatigue calculator is free and takes about a minute.