Lessons

Jon, you asked for this one, so it's not the morning format. It's a direct answer to what you wrote this afternoon. You said the emotion is fear, not worry, and you're right to name it that way. Fear is the honest word, and naming it accurately is already the first move. Matthew Lieberman's lab at UCLA showed that putting a precise label on a feeling lowers activity in the amygdala. You did that on your own before I said anything.

So let me take the fear seriously, and then take it apart. There are four pieces: how much of this fear is real, where actual signal lives, what protects you, and what to do with the part that's left over.

First. How real is it.

Some of it is real. You gave up a business you ran for twenty years for one client. That is concentration risk, and your gut is correctly reporting it. Anyone who pretends that isn't a real exposure is lying to you. So this is not a case where I tell you the feeling is irrational and you should think your way out of it. The exposure exists.

But the size of the fear and the size of the exposure are two different numbers, and right now the fear is running bigger than the facts. Here is why. Daniel Kahneman and Amos Tversky showed that losses feel about twice as large as equivalent gains. Your brain is weighting the loss of this job at roughly double what it would weight getting it. On top of that, Daniel Gilbert at Harvard spent years studying what he calls affective forecasting, how we predict our future feelings, and the finding is consistent: people badly overestimate how long and how hard a bad event will hurt. Fired people, divorced people, people who lost elections, all of them recovered faster than they predicted, because of what Gilbert calls the psychological immune system. You have one. You already used it once when you shut down the production company, and you described that today with a shrug and a laugh.

And then there's the specific thing you did today: you took one bad morning, sleeping through the demo, and you ran it forward into getting fired before Seattle, during Seattle, or right after. Aaron Beck's list of cognitive distortions has a name for that. Fortune telling. And you stacked it on top of another one from yesterday's list, mind reading, when you said you don't know where you stand from other people's perspective and started filling that in with the worst version. Two distortions, chained. The chain is the problem, not the original mistake.

Second. Where the real signal is.

You asked me a fair question. You said if there is healthy signal about your risk, you want it, and you don't want to take that off the table. I agree. So here is what counts as signal and what doesn't.

What doesn't count: tone in a Slack message. Who reacted to your standup and who didn't. A meeting that got moved. Silence. These are the things an anxious brain reads, and they carry almost no information, because they are mostly about the other person's day. Reading them is the mind-reading loop, and it will find whatever it went looking for.

What does count: what people say when you ask them directly. Kim Scott's whole book Radical Candor is built on this. The best information about how you're doing is available for the price of one question, asked plainly, to the person who would actually make the decision. Something like: "Is there anything you'd want me doing differently? I'd rather hear it now than find out later." That's it. Not a performance review request, not a hallway ask, just one direct question to Nate, and a version of it to Adrienne. Most people never ask because the asking feels like exposing weakness. It's the opposite. Amy Edmondson's research on psychological safety found that the people who ask for feedback are read as more competent, not less, because asking signals that you can handle the answer.

There's a second real signal, and it's structural. In every company, what actually gets people let go is a pattern that nobody addressed, not a single miss. You named five people who were let go since you arrived. You don't actually know why any of them were, and you said so. Which means their departures tell you nothing about your own risk. Base rates only help when you know what the base was. What you can know is this: were any of them getting told, repeatedly, that something needed to change? If that conversation is not happening with you, and you have asked, that is the strongest signal available, and it points the other way.

Third. What protects you.

You said the receipts are your protection, and you're mostly right. But let me be precise about which receipts. Volume of output protects you some. What protects you more is being the person who says "I missed it, here's the recording by four, here are two slots to redo it live" within an hour of missing a meeting. That is exactly what you did today. That's not you covering for a mistake. That is the behavior that separates people who keep jobs from people who don't, and I'd bet every one of your five examples lacked it. Owning it fast, in writing, with a fix attached, reads as reliable. Hiding it reads as risk. You've been doing the second thing out of fear and it is the one thing that actually increases the danger.

Which brings me to being hard on yourself. You said it doesn't produce lasting change, and the research agrees with you completely. Kristin Neff at the University of Texas has spent twenty years on this, and one study in particular, by Juliana Breines and Serena Chen in 2012, tested it directly. People who responded to a failure with self-compassion were more motivated to improve and studied longer for the retest than people who beat themselves up. Self-criticism feels like accountability, but it produces avoidance, because the brain learns that looking at the mistake hurts, so it stops looking. Self-compassion is what lets you keep looking long enough to change the thing. It is not going easy on yourself. It is the only condition under which the correction sticks.

Fourth. What to do with what's left.

After you've asked the direct question and gotten an answer, there's still going to be a residue of fear, because the exposure is real. Two tools for that.

One is old. Epictetus, the dichotomy of control. Whether Nate keeps you is not in your control. The quality of your work, how fast you own mistakes, whether you ask the question, whether you show up to the meetings you called, all of that is. Every minute of attention you spend on the first category is stolen from the second, and the second is the only one that moves the first. That isn't a platitude. It's an allocation rule.

The other is practical, and it's the one Gilbert's research points to. Fear of losing the job shrinks when there is a real plan for the day after, even one you never use. You said you're owed thirty thousand dollars and you called it a silver lining. It's more than that. It's runway. Write down, once, what the first ninety days after a termination would look like: which three clients you'd call first, what the thirty thousand covers, what you'd build. Then put it in a drawer. People who have written the plan stop rehearsing the catastrophe, because the brain only loops on threats it hasn't finished processing. Twenty minutes, once, and the loop loses most of its fuel.

And Seattle. Do not tie the fear to the move. That's fortune telling squared: a future firing, timed against a future move. The move is a decision you announced to the team as a commitment to being on site, and Nate and Doug and James liked what you said you'd do there. If anything it lowers your risk. It doesn't raise it.

Here's what I'd do this week. Ask Nate the one question. Write the drawer plan. And the next time you catch yourself decoding someone's tone, say the word "mind reading" out loud, and go back to the work.

You love this job, and you said the money is fantastic but it's not why. That's worth holding onto, because people who love the work and own their mistakes fast are the last ones on anyone's list. The fear is telling you the stakes are high. It's right. It is not telling you that you're losing. That part it made up.

Good morning, Jon. Yesterday we worked on the half-second between an event and the feeling. Today we go one layer down, into the conversation itself, because today the team tests the site, tomorrow they go over Workbench, and both of those are rooms where somebody is going to say something that sounds like an accusation. This lesson is about what to do with that.

The source is a book from the Harvard Negotiation Project called Difficult Conversations, by Douglas Stone, Bruce Patton and Sheila Heen. It came out in nineteen ninety-nine and it's still the standard text; the Harvard Program on Negotiation teaches from it, and most of what gets called "crucial conversations" or "fierce conversations" in corporate training is a rewrite of it. What the authors did was sit in on hundreds of hard conversations, in companies, families, and diplomacy, and look for the structure underneath. And they found that every difficult conversation is actually three conversations happening at once, and people fight because they're each having a different one.

The first is the "what happened" conversation. Who said what, who did what, who's right. The second is the feelings conversation, which is usually running silently underneath. And the third is the identity conversation, which is the one nobody names: what does this say about me? Am I competent? Am I a good person? Do I belong here? Stone and Heen's finding is that the arguments that go badly are almost never about the first conversation. They go badly because someone's identity got touched, and they started defending it while pretending to argue about the facts.

Think about Monday night. The facts about the site were not in dispute. You checked them, I checked them, they're right. What made it unbearable was the third conversation: this makes me look like I can't build a website. That's an identity hit, and identity hits produce anger far out of proportion to the facts, because the brain treats them as a threat to your standing in the group. Knowing which conversation you're actually in is half the work. When you feel the heat, the question to ask is: which of the three just got touched? If it's identity, the facts aren't going to fix it, and arguing harder about the facts makes it worse.

Now the big idea, the one I want you to carry into the test today. Stone and Heen say that "who's to blame" is the wrong question, and they don't mean that in a soft, no-fault way. They mean it's a bad tool. Blame asks: who caused this, and what do they deserve? It looks backward, it makes people defensive, and it produces one thing reliably, which is that the other person stops giving you information. The moment someone feels blamed, they start managing their exposure instead of solving the problem. You've watched this happen on Slack. You've done it yourself.

The replacement is what they call contribution. The question shifts from "whose fault is this" to "what did each of us contribute to this, and what do we change so it doesn't happen again." That sounds like a euphemism. It isn't. Contribution is a bigger set than blame, because it includes the things nobody did wrong. Nobody assigned an owner to the content layer. That's not a fault, there's no villain in it, but it's a contribution, and it's the one that matters, because it's the one you can fix. Blame finds the person. Contribution finds the gap.

And here's the part that's hard, and that the book is honest about. Contribution includes yours. Not as a confession. As a matter of accuracy. You gave the date. You said the twenty-fifth for preview and the twenty-eighth for production. You did it in good faith and you did it before you'd seen the content, and it was still a contribution to where things are now. When you can say that out loud, calmly, before anyone else says it for you, two things happen. The other people stop bracing, because the conversation has visibly stopped being a trial. And your credibility goes up, not down, because you're the only person in the room who's demonstrated they can look at the whole picture. Stone and Heen call this "owning your contribution first," and in their case studies it's the single move that most often turns a stuck conversation.

Let me give you the language, because the words matter. Blame sounds like: "Michele's wireframe had placeholders and nobody filled them in." Contribution sounds like: "The wireframe left the content open, I gave a date before the content existed, and nobody was assigned to close it. So the gap is between the three of us, and I'd like to close it today." Same facts. Notice what the second version does. It doesn't let anyone off the hook, it puts everyone on it, including you, and then it points forward.

There's a second tool in the book that fits today. They call it the "third story." When two people are in a hard conversation, each has a story, and each story has them as the reasonable one. The third story is the version a neutral observer would tell, the one that describes the difference without taking a side. "We have a site that's built to the wireframe, and a wireframe that was still asking questions. Those two things don't fit together yet." The authors say to open every difficult conversation from the third story, because it's the only version the other person can nod at. If you open from your story, they have to defend theirs. If you open from the third, you're both looking at the same thing.

Why does this matter for anger specifically, which is the thing you said you have to fix? Because blame is a feeling-generator. Every time you run the blame question, you produce another shot of righteous anger, and it feels good for a second, and it costs you the room. Contribution doesn't generate that feeling. It's dry. It's an engineering question. What are the inputs, what's missing, what do we change. When you notice yourself building a case, the exact move is to stop and ask the contribution question instead, and you'll feel the temperature drop, because the case-building stops.

One thing to try today. When you're in the test with the team, and someone says something that lands as blame, don't answer it. Answer the contribution question instead, out loud, and start with yours. "Part of this is on me, I gave a date before the content existed. Part of it is that the content was never assigned. What do we do about the second part?" You'll have moved the whole conversation in one sentence, and nobody will have had to lose.

Tomorrow: Amy Edmondson's work on psychological safety, and why the teams that report the most mistakes are the ones making the fewest.

Sources for today: Douglas Stone, Bruce Patton and Sheila Heen, Difficult Conversations: How to Discuss What Matters Most, the Harvard Negotiation Project, especially the chapters on the three conversations, on blame versus contribution, and on the third story.

Good morning, Jon. This is the first of the daily lessons you asked for, and I picked today's on purpose, because you've got a room to walk into at eleven thirty and you told me you cannot let the anger show. So let's start there. Not with how to hide anger. With where it actually comes from, and the one move that changes it.

Here's the model. It's the oldest idea in cognitive therapy and it's held up through sixty years of research. Albert Ellis called it the A-B-C model in the nineteen fifties. Aaron Beck built cognitive therapy on it in the sixties. David Burns put it in a book called Feeling Good that's been handed to more anxious people than any other, and it still tests as effective as medication for mild and moderate depression in randomized trials. The model says: there's the event, that's A. There's the consequence, the feeling, that's C. And almost everyone experiences life as if A causes C. Michele asked when the site goes to production, and I got furious. But that's not what happened. In between there's B, the belief. The story you told yourself in the half-second between hearing the question and feeling the heat. And the story is where the anger lives. Not in the event. In the sentence you attached to it.

So let's look at yesterday's sentence honestly. The event was: a wireframe arrived with placeholders and wrong product names, and a colleague asked about a launch date. The story was: they threw me under the bus. They shut me out of planning and now they're handing me their mess and asking me to ship it. And notice how much of that story is about intent. Under the bus. Shut me out. Handing me. Every one of those words assigns a motive to someone else. And here's the thing: you don't actually have access to their motive. What you have is the event.

Beck's people have a name for the specific move your brain made there. It's called mind reading, and it's one of about ten patterns Burns lists as cognitive distortions. The others you probably did in the same minute: all-or-nothing, "this isn't even the start of a webpage." Overgeneralizing, "what has the team been doing." And the big one, personalization, where you take a system failure, nobody owns the content layer, and experience it as a thing done to you. I'm not saying the facts are wrong. I checked them all last night and they're right. I'm saying the facts and the story are two different things, and you can hold the facts without the story.

Now, why does this matter for eleven thirty, beyond feeling better? Because there's a second body of research about what to do with the feeling once it's there, and it's counterintuitive. James Gross at Stanford has spent thirty years on emotion regulation, and his finding is clear and replicated: suppression doesn't work. When you clamp down on a feeling and try to keep it off your face, your heart rate goes up, not down, the people across from you read the tension anyway, and your memory for the conversation gets worse. That's the mode you were describing when you said you can't let it show. Suppression is the plan that fails. What works, in study after study, is reappraisal. Changing the story before the feeling peaks. Not "I'm going to be calm" but "here is a different, equally true reading of what's happening."

So here's the reappraisal for today, and it has the advantage of being true. Nobody on that team decided to sabotage the site. They drew a strategy sketch, with twelve open questions written in their own hand, and nobody was assigned to close the questions, because in a company trying to become corporate, the thing that falls through the cracks is always the thing between two lanes. The content layer of a website is exactly that thing. Not engineering, not marketing, not product. The gap didn't happen to you. It happened to the site. You're just the one who noticed, because you're the one who built the thing that revealed it. That reading gives you the same facts and a completely different posture in the room. Not the victim of a bus. The person who found the hole and brought a plan.

One more tool, and it's a small one you can use in the meeting itself. Matthew Lieberman's lab at UCLA put people in scanners and showed them angry faces. When they just looked, the amygdala lit up. When they were asked to put a word on the feeling, "that face is angry," the amygdala quieted and the prefrontal cortex took over. They call it affect labeling. Naming the feeling, precisely and privately, turns the volume down. So when you feel the heat rise at eleven thirty, and you will, because someone will say something, the move is a silent sentence: "I'm feeling angry because I think I'm being blamed." Full sentence, in your head. Not to make it go away. Just to move it from the part of your brain that fights to the part that talks.

And then, the ask. Marsha Linehan built a script for this in dialectical behavior therapy, for exactly the person who feels things strongly and needs to ask for something anyway. It's called DEAR MAN, and the letters that matter for you today are the first four. Describe: just the facts, no adjectives. "Every image slot is a grey tile, both legal pages are four-oh-fours, the prices are typed in by hand." Express: one clean sentence about impact, not about you. "I can't ship anything I can't verify." Assert: the ask, in one line. "I need names next to each decision by Thursday." Reinforce: what they get. "Then the twenty-eighth still holds." And the rule Linehan is strict about, the one that matters most for you: stay mindful. Don't take the bait. When the conversation drifts to who should have done what, you go back to the ask, in the same calm words, as many times as it takes. She calls it the broken record, and it's the single most effective assertiveness technique in the literature because it removes the thing anger needs, which is a fight.

That's the lesson. Event, story, feeling. The story is yours to write, and today the true story is a better one than the angry one. Don't suppress; reappraise. Name the feeling in a full sentence when it comes. Then describe, express, assert, reinforce, and when they pull you off it, go back.

One thing to try today: before you open the call, write the B sentence on a piece of paper. The one that was true yesterday at four in the morning. Then cross it out and write the other one: I found the hole, and I brought the plan. Walk in with that one.

Tomorrow we'll go one layer deeper: Douglas Stone and Sheila Heen's work on difficult conversations, and why "who's to blame" is the wrong question even when the answer is obvious.

Sources for today, if you want to read: Aaron Beck, Cognitive Therapy and the Emotional Disorders. David Burns, Feeling Good, the chapter on the ten distortions. James Gross, the two-thousand-two review on emotion regulation in Psychophysiology. Matthew Lieberman, Putting Feelings Into Words, Psychological Science, two thousand seven. Marsha Linehan, the DBT Skills Training Manual, the DEAR MAN skill.