Chapter 6 of 6 / it already went wrong
It already went wrong
The one chapter where hurrying is correct, and it is correct because something has already happened rather than because somebody is offering you something. That distinction covers most of what this site is about.
What happened
- I typed my password on a copyMessages first, balance second. That order is deliberate.
- I sent a payment to the wrong placeFinal. The useful work is on the machine, not the payment.
- I gave somebody a code or a phraseThe one thing on this site measured in minutes.
- I have lost my recovery materialUsually final, and the fix belongs to the next account.
The order that applies to all of them
- Stop using the thing that went wrong. The address, the machine, the channel, whichever it was.
- Get in through something you checked yourself, not through the route that caused it.
- Read the message log before the balance. This one is counterintuitive and it is right.
- Change what can be changed, everywhere it was reused, not only here.
- Then stop and write down what actually happened, while it is fresh, because the next decision is better made from notes than from memory.
Why messages before balance
An emptied account is not the worst outcome of a taken account. An account with a real history and somebody else reading it is, because the productive use of one is not draining it, it is writing to the people who already trust it. Checking the log tells you whether you have become the source of somebody else problem, and that is time sensitive in a way a balance is not.
What genuine urgency looks like
| Situation | How fast | Is hurrying right |
|---|---|---|
| A code or a phrase given away | Minutes | Yes, act now |
| A session you think is live right now | Minutes | Yes, act now |
| A password typed on a copy | Within the hour | Yes, but calmly |
| A payment already sent to the wrong place | Not urgent | It is final. Nothing gets better by rushing |
| Anything asking you to act before you can check | Not urgent | That is the opposite pattern |
The last row is the whole distinction. Real urgency follows a mistake. Anything urgent that asks you to do something new is the shape of the problem rather than the response to it.
What is worth doing once it is over
- Write down what actually happened, in order, while it is fresh. Not for anybody else, for the version of you deciding what to change.
- Find the channel rather than the incident. The address, the message, the install. That part repeats and the incident does not.
- Change one habit, not five. The person who resolves to do everything differently goes back to normal in a fortnight.
- Leave an accurate review if an order was involved, after the process finishes rather than during it.
The instinct after something goes wrong is to tighten everything at once, and it does not survive contact with the next busy week. One durable change beats five that lapse.