A Productive Conversation

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.

The appeal of a hard challenge is that nobody's pretending it's easy. Most of what gets sold to us leads with how simple it'll be; programs like 75 Hard do the opposite, and that honesty is a large part of why they work. But the failure mode is predictable, and it's not laziness — it's taking on so many challenges at once that none of them survive contact with an ordinary week. Zakhar Azatian — Zach — is a founder building Be Hard, a platform for structured personal challenges, and he's failed at more of these than he's completed, which makes him a more useful guide than someone with a perfect record. We got into why one challenge with one focus beats ten, how longer challenges force you across seasons and schedule changes in a way 30-day sprints don't, why "I forgot" is a more common failure cause than any lack of discipline, and why a challenge that looks indulgent from the outside can still be doing real work. Six Discussion Points Programs like 75 Hard succeed partly because they're honest about being hard, in a market that mostly competes on how easy something will be. Doing multiple challenges simultaneously is the most common way people fail — one challenge with one clear focus, even if it combines physical, social, and mental elements, is far more sustainable. Longer challenges force you across month boundaries, season changes, and disrupted schedules, which is exactly what reveals whether something actually fits your life. Most failures aren't about discipline — they're about a rescheduled task falling out of routine and simply being forgotten. A challenge should be designed around a specific problem you're trying to solve, which means the same activity can be a real challenge for one person and meaningless for another. Fitting a challenge into a full life usually requires removing something rather than finding time — but that removal has to be honest about what's actually optional. Three Connection Points Be Hard — Zakhar's challenge platform Connect with Zakhar Azatian on LinkedIn Check out Mike's books If you've been circling a challenge you keep not starting, the useful question isn't whether you have the discipline. It's whether you've picked one thing instead of five, and whether you know what problem it's actually meant to solve. Get those right and the difficulty stops being the obstacle.

Patrick's wife has an iPad mini she uses for exactly one thing: reading. She's never called it an iPad mini in her life. She calls it her Kindle — and she isn't confused, she's being precise. The name follows the job, not the packaging. That's the second time in two months we've stumbled into how the words people choose quietly reveal what a thing is actually for. This month's PM Talks opens there and lands on a question Patrick puts plainly about twenty minutes in: what problem does this solve? We get into Clayton Christensen's milkshake, why a tool that does everything usually does nothing especially well, why the unused device in the corner is a capital-P project you've been sitting on rather than a small privileged annoyance, and — less comfortably — what happens when you point that same question at a friendship, a marriage, or a default nobody ever asked you to agree to. Six Discussion Points What people call a thing reveals what it's actually for; a device used only for reading becomes "her Kindle" regardless of what's printed on the box or which app is open. The jobs-to-be-done question cuts in both directions — it explains what you should buy, and it exposes what you're still holding onto that stopped doing its job a while ago. Deliberately refusing to install certain apps on a device is a forcing function, not a limitation; knowing what each device is for is what makes any of them work well. An unused device sitting in the corner isn't clutter, it's an open loop — and in David Allen's terms it's a full project with multiple tasks underneath it, not a single thing you can dash off. Capturing an open loop doesn't close it; what actually relieves the weight is having a plan and knowing the boundaries of the thing you captured. Asking what problem a relationship or a social default solves sounds cold, but it's really a prompt to notice when something has stopped doing the job you originally needed it to do — and to stop treating inherited arrangements as settled. Three Connection Points Read more from Patrick Rhone at patrickrhone.com Growth in Reverse Get Productiveness The move worth stealing from this one is Patrick's double-take in the Costco aisle: the walk past, the stop, the walk back. Most of us keep walking. Whether it's a device you've stopped using, a phone you pull out without deciding to, or an arrangement you've never actually questioned, the pause is the whole thing. What in your life is still there mostly because you never stopped to ask what it was for?

Most people describe work stress as one undifferentiated thing: I'm stressed at work. Amy Leneker's research says there are actually five distinct kinds, and the one doing the most damage to working people isn't the one that shows up most often. It's the sudden kind — the unexpected thing that yanks you off whatever you'd planned to do — and it has a nasty habit of multiplying into all the others. Amy is the author of Cheers to Monday: The Surprisingly Simple Method to Lead and Live with Less Stress and More Joy, and her book is built around a sequence — see, sort, solve, and then celebrate — that has to be done in that order, though almost nobody does. We got into why writing a stressor down doesn't make it bigger, why "just forget about it, it's not important" is terrible advice your brain physically can't follow, the research on how you ask for help mattering far more than who you ask, and why the shortest section of the book might be the one people skip most. Six Discussion Points A ten-word question — what are your hobbies, what do you do for fun — can expose how completely you've lost track of yourself, which is exactly how Amy's own unraveling started. There are five distinct types of work stress: schedule, suspense, social, sudden, and system — and sorting your stressors into the right one is what makes them solvable rather than just heavy. Sudden stress does the most damage despite occurring least often, largely because it snowballs — one person's missed deadline instantly becomes another person's social stress. Writing a stressor down doesn't make it more real or bigger than it is; those stressors are already running in the background like open browser tabs whether you name them or not. Telling yourself something unimportant isn't worth thinking about doesn't work — your brain hates open loops, and simple acknowledgment is what actually lets it move on. New research shows that how you ask for help determines whether it builds trust or damages it — framing it as learning and problem-solving reads as credible, while framing it as handing off your problem does the opposite. Three Connection Points Cheers to Monday by Amy Leneker Find Amy and her work at amyleneker.com Stop Managing Your Time, Start Crafting Your Time Instead The average person works roughly 2,109 Mondays in a lifetime. Deciding in advance that you're going to dislike all of them is a big thing to sign up for without thinking about it. If this conversation gets you to sort even one stressor into the right category this week, that's a start — and the book will take you the rest of the way.