A Productive Conversation

This isn't a book about getting more done. It's a book about what it takes to keep going when the conditions around you make that difficult — and once I read it that way, I couldn't stop seeing the overlap with the work I do. We don't talk about care when we talk about productivity. We talk about systems and output and capacity. We almost never talk about what's actually required to sustain any of it. Dr. Tiffany G. Townsend is a psychologist and former professor, and her book Weathering the Storm: Navigating the Antisocial Justice Wave argues that self-care isn't a luxury you get to once there's time — it's the precondition, and without it burnout stops being a risk and becomes arithmetic. We got into why microaggressions land as surprises you can't prepare for, why you don't owe anyone a response in the moment, what separates tokenism from actual change, and what she means by radical hope: holding a clear-eyed view of how hard something is at exactly the same time as believing it can change. Six Discussion Points Self-care isn't the reward for doing the work, it's the condition that makes continuing to do it possible — which makes protecting it a practical decision rather than an indulgent one. AI was supposed to reduce intensity; inside most organisations it's raised the expectation instead, because an assistant doesn't lighten a workload so much as expand what's assumed possible. Joy is protective infrastructure, and it's most at risk exactly when the work you care about is under attack — which is when protecting it matters most. Microaggressions arrive as surprises, which means you won't be prepared, and that's fine — therapeutic moments don't disappear, so you can protect yourself now and respond when you've decided how. Tokenism is representation without resources or power: it produces the appearance of change while quietly eroding the sense of efficacy of the person placed in the role. Working collectively isn't only more effective — it's where the healing happens, which is why doing meaningful work alone has a time limit on it regardless of how capable you are. Three Connection Points Weathering the Storm by Dr. Tiffany G. Townsend AI Doesn’t Reduce Work—It Intensifies It (HBR) Productiveness Tiffany used the word efficacy in this conversation, which almost nobody does — it's one of the nine principles in my own book, and hearing someone arrive at it from a completely different direction was one of those moments where you realise the thing you've been circling isn't yours alone. Her practical starting point is smaller than you'd expect: find thirty minutes a week that nobody gets access to, and find people who share the thing you care about. Not a system. Just protected time, and company.

I spoke at Podcast Movement in New York last month, and the whole conference ran on headphones — every attendee wearing a set, switching channels to pick which stage they were listening to. Which meant that partway through my talk, I watched at least one person in front of me switch to somebody else. It was a bold format. I'm still not sure it worked. But it was a real experiment, and I came away thinking about how rarely we name the experiments we're already running. Patrick Rhone and I spent this month's PM Talks on that — including a distinction I think matters more than it sounds like it should. Experiments have an end in mind. Tinkering doesn't. One of them produces a decision; the other produces the feeling of progress without ever asking you to make one. We also got into Patrick's unrecorded podcast, which got him mocked by some fairly prominent people at the time and then quietly became the thing everybody does now. Six Discussion Points Most of the choices you make in a day are experiments you never labelled as such — you're acting without knowing the outcome, which is the definition, whether or not you framed it that way. The difference between experimentation and tinkering is an endpoint: an experiment asks a question you intend to answer and then stop, while tinkering is perpetual adjustment that feels productive precisely because it never resolves. Parameters make an experiment possible rather than constraining it — knowing what you can't control is what tells you what's actually worth testing. You cannot predict which thing will land; after thirty years of writing online, the most-linked post of Patrick's career came from a car conversation with his wife and took twenty seconds to write. Coming home from a conference with pages of notes almost guarantees nothing happens — picking exactly three (one thing to act on, one person to connect with, one thing to think about) lets the rest fall away without festering. Stopping is itself an experiment: quitting something at its peak asks a real question about what you'd do with the time and how you'd fill the gap, and you genuinely don't know the answer going in. Three(ish) Connection Points Between us we promised rather more than three of these on air, so here they all are. Consider the overrun an experiment. Patrick Rhone — and his NOW page, which he swears he updates every couple of weeks Tiny Experiments by Anne-Laure Le Cunff Fish: a tap essay by Robin Sloan — the one he lost the source code to and rebuilt from scratch Microsoft's Biggest Miss — Patrick's most-linked post, written in about twenty seconds, based on something his wife said in the car What You Bring Home — my piece on the three picks, which is where this conversation started My NOW page The poem Matt wrote about my talk — handed to me on orange card stock when I went back for my laptop The three-picks idea came out of my own notebook after New York, and I wrote about it thinking it was a minor observation. It got more response than most things I publish, which rather proves the other half of this conversation — you don't get to choose what resonates. You only get to choose what you try. So: what have you been tinkering with that you could turn into an actual experiment, with an end date and a decision attached?

We're at a forty-year low for trust across nearly every institution, and the reflex is to reach for something faster — a better funnel, a tighter system, an optimization. Nick Richtsmeier's argument is that the reflex is the problem. The things that actually rebuild trust are slow, uncomfortable, and resistant to being made efficient, which is exactly why so few people do them. Nick is the author of The Damn Rules: How Vulnerability, Inefficiency, and Love Liberate Leaders from the Trustbroken Economy, and he's clear that none of the seven rules in it are surprising. You don't read them and think he's a genius. You read them and think: that's true, and I wish it weren't, because my life would be easier. We got into why impatience is a symptom rather than the disease, why being a "category of one" works against you, why the customer is wrong without meaning to be, and why efficiency is a fine tool for managing waste and a terrible one for building anything people care about. Six Discussion Points Impatience is downstream of the real problem — going after it directly just produces resistance, because what's actually driving it is exhausted nervous systems, anxiety and isolation. We're all playing in an attention casino: miserable most of the time, with occasional payouts just large enough to keep us pulling the arm. People move through resistance on a cocktail of three things — better information, more support, or more pain — and better information is the least important of the three, because we can talk ourselves out of information all day. "Who am I being in this situation?" does more than any personality framework, because identity is largely repeatable behaviour, and change starts when someone sees their own pattern rather than the problem. The customer is wrong, and not maliciously — humans are poor predictors of their own behaviour under changed circumstances, which makes customer will a moving target rather than a North Star. Being a category of one is trust-breaking rather than advantageous; competition supplies the contrast that makes a decision easy, and without it you carry the entire burden of proving the category should exist. Three Connection Points The Damn Rules by Nick Richtsmeier Damns Given — Nick's ongoing work Stop Managing Your Time, Start Crafting Your Time Instead The line I keep turning over is Nick's: inefficiency is load-bearing. We've spent a couple of decades treating every inefficiency as a defect to be engineered out, and what we've engineered out along with it is most of what made people trust each other. If your strategy is to do as much as possible, as fast as possible, as cheaply as possible, it's worth asking what that strategy is actually building — and whether anyone will care about it when it's built.

Normally I'm the one asking the questions. This time I wasn't. I was in New York for Podcast Movement, my daughter Grace came down from Montreal to meet me — partly for a concert, let's be honest — and since we were both sitting in a studio anyway, we turned the tables. She'd written her own questions. She hadn't read the book. I had no idea where any of it was going. What came out of it is the most personal conversation I've put on this feed in a long time: why productiveness is a state and not a rate, and why that distinction matters more than it sounds like it should; which of the nine principles I actually struggle with, and the reframe a therapist gave me years ago that changed how I measured a decade of my working life; why I've cut interviews on this show from fifty-two a year to twelve; and why, after eighteen years of doing this, I've never once described myself as a podcaster. It felt right to put this one out on International Podcast Day. Eighteen years, no breaks, and the thing I keep coming back to is that the show was never the point — it's the connective tissue between everything else. Six Discussion Points Productiveness predates productivity as a word, and the substitution quietly swapped a state for a rate — which matters because a state is tethered to identity in a way a rate never is. Data can change your rate. It can't change your state — which is why measurement alone has never made anyone feel less behind. "Is this the right app?" is almost never the first question; whether the work is aligned with your energy is, and most systems will never stop to ask it. A therapist's reframe — that you're a stay-at-home parent who happens to run a business, rather than a business owner who happens to be at home — leaves every fact unchanged and completely alters what success was ever supposed to look like. Cadence is the hardest principle to hold because the seasons of a life keep invalidating the rhythm that was working, and grace is what makes that survivable rather than damning. Legacy is built by the ride rather than designed at the end of it, and you don't get a vote in how it turns out — which is an argument for being more interested in the ride than the result. Three Connection Points Productiveness The Front Nine-era photo of Grace and Colton Grace's ask: She's a psychology student looking for lab experience. If you're a teacher, psychologist or sociologist with room in your lab, get in touch and I'll pass it along. Grace has been around for this work her entire life — she wrote show notes for this show as a teenager for twenty dollars an episode, which she brought up on air and which I had genuinely forgotten. Getting to have this conversation with her, in a studio, in a city we were both in for completely different reasons, is about as good an illustration of the ride-over-the-result argument as I could have staged on purpose. I didn't stage it. That's rather the point.

I missed two Wednesday livestreams this month, and I spent more time than I'd like to admit trying to decide whether that meant I'd fallen behind. Somewhere in there I realized I was asking the wrong question. Falling behind and stopping are not the same thing — they just feel the same and they get called the same name. Falling behind requires somebody waiting. There's a pace that was set, an agreement, a real person on the other side of it. Stopping is just the absence of motion. That's the whole definition. In this one I get into why confusing the two costs people entire summers, the three predictable ways re-entry breaks, and the distinction between consistency and cadence that finally made all of this click for me. I use my own two missed Wednesdays as the worked example throughout, because it would be a bit strange if I didn't. Six Discussion Points Falling behind requires that someone was actually waiting; if you can't name them in four seconds, you didn't fall behind — you stopped, and nobody sends a bill for stopping. A guilty conscience quietly converts a neutral fact ("I stopped") into a moral one ("I failed"), and once it's moral you feel you have to atone before you're allowed to simply resume. The Full Restore assumes two weeks away had zero effect on your capacity — an expectation nobody would apply to running or to a language, but that we apply to our work constantly. The debt story treats rest as a withdrawal to be repaid, which quietly means rest was never rest at all; it was borrowing, and every day off becomes a loan against a future day of overwork. The clean slate delay is the most expensive of the three because it feels like planning when it's actually stalling with a calendar in your hand — a two-week stop becomes a six-week one. Consistency is mechanical and treats any gap as a broken chain; cadence is musical, and a rhythm can absorb a rest because rests are written into the score. Three Connection Points Subscribe to The Lantern The 10-Second Inbox Listen to the Gary John Bishop conversation (APC668) A system you can return to is worth more than a system you never leave — because the one you never leave is going to get left eventually. Something always happens. When it does, the only thing that matters is whether you built something you can walk back into. If you stopped something in the last six weeks, the question isn't how you let it happen. It's whether this is a rest or a drift, and the only difference between those two is whether you come back.