The people who look thick-skinned may just recover faster
Resilience is how quickly you return to normal after a setback.
Welcome. For the next thirty days you will get one short reading, one question and one thing to try each day. The question matters most. Each answer is a specific commitment in your own words, and the last day of each of the six parts shows your answers back and asks you to write one section of a document. By day 30 you will have written your own digital roadmap.
We start with resilience because every later day assumes you are still standing. Things go wrong: a build fails in front of the team, the platform you standardized on is discontinued in a Tuesday email, or critical feedback arrives in writing late at night. You do not control how many setbacks you get. You do control how long each one takes to recover from.
A common mistake is to think resilience means being hit less hard, so people try to care less and admire colleagues who look unbothered. Those colleagues may be feeling the setback just as much and recovering faster, or they may be better at hiding it. What you can measure is the recovery time. Two hours knocked off balance is a bad afternoon. Two months knocked off balance is most of a quarter.
The method has two steps. When something goes wrong, write two lines: what happened, and what you told yourself about it. “The migration failed” and “I am not up to this” are two different stories, and only the first one is information. Then follow a fixed recovery routine, the same one every time, such as a walk, a coffee or ten minutes outside. Choose the routine in advance, because on a bad day you are in no state to choose one.
Picture a build failing at four o’clock. One person stares at the same stack trace for three hours. Another person closes the laptop, walks around the block, and comes back to read the error properly. Both had the same failure, and the second person was back at work in twenty minutes.
Today's question
This question has two parts. First, who is this roadmap for: you, your team or your company? Describe the situation in two or three sentences: what is changing around you, and what you are trying to do about it. Second, what is your recovery routine? Name the one thing you will do every time, in the first hour after something goes wrong at work.
A good answer names a real situation with a project or a date in it. The routine is specific enough that a colleague could tell whether you did it: a walk around the block, twenty minutes away from the screen, or two lines in a notebook.
Try today
The next time something goes wrong today, however small, write two lines before you do anything else: what happened, and what you told yourself about it.