Who Was in ItChapter 7 of 125 min
Resistance Is Just Data
Core idea. Friction is not a personal failure or a cosmic punishment. It is surface feedback showing you where to adjust.
Takeaway. Stop spending most of your energy complaining about obstacles, and put that energy into clear problem-solving.
The pothole
You hit a pothole on the way to work. It jolts the car, you spill a little coffee, and for the next ten minutes you replay it: the council should have fixed that, you should have seen it, this is typical of your week.
Now look at what the pothole actually told you. There is a hole in the road at that spot. That is the whole message. Everything else, the ten minutes of replay, you added yourself.
And notice where those ten minutes were spent: not on the road, where the pothole was, but in the first ten minutes of whatever you did next. That is the only part of this that has a price, and chapter 12 is about how to read it.
This chapter is about the difference between the message and the replay. Most people spend ninety percent of their energy on the replay.
Friction is information
Engineers do not get angry at friction. They measure it. When a machine runs hot, that heat tells them exactly where two parts are rubbing. It is a signal, not an insult.
The obstacles in your day work the same way. A project changes scope. A colleague criticises your work in front of others. A plan falls apart. Each of these is feedback: something about your approach met something about the world, and there was resistance at that point. The resistance is the data. It shows you where to adjust.
The Raja Yoga tradition has a word for the way your actions shape your inner state: karma. In the full edition this is treated not as a ledger kept somewhere else but as immediate physics. In plain words: when you react with blame, defence, or resentment, you pay for it straight away, in the form of inner drag. Not next year. Now. The clenched jaw and the ten-minute replay are the bill.
| What happened | The message (data) | The replay (added by you) |
|---|---|---|
| A critical comment in a meeting | One person sees a weakness in the plan | "They never respected me. I should have prepared more. Everyone saw." |
| A project is cut | Priorities changed above you | "Three months wasted. This always happens to me." |
| A late train | You will arrive twenty minutes late | Twenty minutes of fury about the rail company |
How fast do you bounce back?
The most useful number in this book is not how often things go wrong. It is how long it takes you to return to calm after they do. The full edition calls this latency to zero. In plain words: recovery speed.
A brittle system rings like a struck bell for days. A well-damped system takes the hit, absorbs it, and is still again almost at once. Think of a wine glass versus a sandbag. Both get hit. Only one keeps vibrating.
The target the book sets is sixty seconds. Not never being knocked, but being back to baseline within a minute. That is a skill, and like any skill it improves with repetition.
brittle (low mass): /\/\/\/\/\/\/\/\/\/\ still ringing days later
steady (high mass): /\_ back to calm in seconds
The three-step reset
When something lands hard, here is the sequence. It is the same whether the shock is an angry email or a genuine crisis.
- Sever the reaction. Do not speak or act for five seconds. Force a physical pause. Remind yourself that the noise of the event is not the same as its content.
- Return to centre. Pull your attention back from the surface of the event to the place behind your forehead. Say, silently: "I am the one watching this. It cannot set my inner state unless I hand it over."
- Respond cleanly. Address the actual situation with no defence and no attack. Say what is true, say what you will do, and add nothing about how you feel about it.
Step three is where the energy goes. The ninety percent that used to fund the replay now funds the fix.
Try this: one recent obstacle
Think of the last thing that went wrong this week. Write two lines. First line: what was the actual message, in one sentence, with no adjectives. Second line: what did you add? Look at the two lines side by side. That gap is the energy you get back.
Key takeaways
| Friction | Feedback about where you and the world are rubbing | Read it, adjust, move on. Do not narrate it. |
| Karma as real-time drag | Reactive choices cost you inner peace immediately | The replay is the bill. Stop paying it. |
| Recovery speed | How fast you return to calm | Aim for sixty seconds. Track it. It is the best measure of progress. |
| The three-step reset | Pause, return to centre, respond cleanly | Use it for everything from a rude email to a real crisis. |
What changes after this chapter
A team lead reads a sharp message from a client at ten to two. Her next block starts at two and it holds perfectly: two hours, door shut, nobody interrupting, exactly as planned. The client's sentence is in the room for most of it. Nothing on her calendar records that, and by any measure she keeps, the afternoon was a success. After this chapter she writes the actual message down in one line, strips out the four sentences she added to it, and answers the real thing — and the block gets the two hours it was given.
- You start reading friction as information rather than insult.
- You stop paying for an interruption that never got as far as the door.
- You keep energy for the response instead of spending it on the replay.
Next. Friction you can read is manageable. The next chapter is about the two kinds that are not: the shock that takes the afternoon out, and the obstacle that will not move.