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.

We treat retreats as something you earn — a reward that shows up once you've worked hard enough, long enough. I don't think that's right, and I think it's the exact reason most people never actually take one. A retreat isn't a break from the work. It's part of it.

I had just wrapped a multi-day virtual retreat inside our TimeCrafting Trust community and was about to head into another one at a conference, so I was sitting right in the middle of two different kinds of retreat as I recorded this. That felt like the right moment to break down what a retreat actually is, the two forms it can take, and the five most common ways people sabotage their own attempt at one.

Six Discussion Points

• Treating a retreat as a reward for hard work puts it at the end of effort, contingent on having "done enough" — which means most people never feel like they qualify for one.
• The military root of "retreat" isn't surrender, it's a strategic withdrawal to regroup and reassess before moving forward again.
• There are two forms of retreat — retreat as place (the getaway, the conference, the cabin) and retreat as practice (a daily or weekly stepping back) — and the practice is what makes the place valuable, not the reverse.
• A retreat is not the same as rest; the deepest retreats can be genuinely challenging and often leave you needing an actual break afterward.
• Most retreats fail not in the stepping back, but in the reentry — without a plan to carry intentions forward, a retreat becomes a pause instead of a strategic reset.
• A retreat requires a balance of both time and space: too much space with too little time invites rushing, and too much time with too little space invites drift and procrastination.

Three Connection Points

• Get the free Retreat Map
• Join Time Crafting Trust
• Stop Managing Your Time, Start Crafting Your Time Instead

A retreat doesn't require a flight, a mountain, or a week away from your life. It requires a boundary and an intention — and permission you give yourself instead of waiting for. If you take nothing else from this episode, take this: the practice is what makes the place richer. Not the other way around.

Most of us don't drift into quitting a job. Something happens — a single, identifiable moment — and that's when the relationship with our work actually changes. Anthony Klotz calls these moments "jolts," and once you have the word for it, you start seeing them everywhere: in your own career, in the people around you, in decisions you made years ago that you never quite had language for until now.

Anthony is the organizational psychologist who coined the term "the Great Resignation," and his new book, Jolted: Why We Quit, When to Stay, and Why It Matters, is the deepest treatment I've read of why people actually leave jobs — and just as importantly, why they sometimes shouldn't. We got into direct jolts versus honeymoon jolts, why positive jolts are rarer and more powerful than negative ones, the "power surge" that hits right before someone quits, and why silence is usually the smartest exit strategy. I shared my own Costco story along the way — a demotion that turned out to be one of the clearest jolts of my working life.

Six Discussion Points

• A "jolt" is a single identifiable event that knocks you out of autopilot with your work — almost half of all quitting decisions trace back to one, rather than a slow, logical decline.
• The instinct after a jolt is to react immediately; the better move is almost always to reflect first, because doing nothing right away is often the strongest default option.
• Positive jolts exist but are rarer and less discussed than negative ones — our brains are wired to dwell longer on the bad, even though a compliment or a big win can just as easily be the moment that changes everything.
• The "honeymoon hangover effect" explains why job-change regret is so common: we see all the flaws in our current role and only the upside of the next one, until the new role reveals its own brown spots.
• "Leaning back" — quietly renegotiating your extra, unpaid job tasks — is an underused alternative to quitting that doesn't require dramatic action or public declaration.
• The "power surge" that hits right before someone resigns is real, and the discipline to sit with it quietly is usually worth more than any parting message ever could be.

Three Connection Points

• Jolted: Why We Quit, When to Stay, and Why It Matters
• Connect with Anthony on LinkedIn
• Stop Managing Your Time, Start Crafting Your Time Instead

If you're sitting in a job right now wondering whether what you're feeling is a real signal or just a bad week, this conversation is worth the full listen. And if you take one thing from it: remember what Anthony's colleague Kim Scott says — don't forget to quit. Not as a threat, but as a reminder that it's always been an option on the table.

This month's PM Talks starts with a confession: I've had an epiphany, and I don't use that word lightly. Somewhere between an "aha, I get it now" moment and what I can only describe as a holy moment is a distinction most of us never bother making — and once you start looking for the difference, you start noticing which of your own realizations actually deserved the weight you gave them.

Patrick Rhone and I use this month's conversation to pull that distinction apart: the difference between a dawning recognition and a genuine unlocking, why holding an idea loosely lets it unfold instead of unravel, and how something as small as what his daughter calls a credit card turned into a real look at the nature-versus-nurture question neither of us can fully answer. I don't give away the specifics of the epiphany I'm sitting with this month — some things need more than one episode to explain — but the shape of it, and what to do with a moment like that once it arrives, is exactly what we get into.

Six Discussion Points

• An "aha moment" is a small recognition — oh, I get it now — while a full epiphany carries a much heavier, more disorienting weight; treating every insight as the second kind burns you out.
• Real epiphanies tend to arrive with equal parts fear and fascination — the discomfort isn't a sign to back away, it's part of what makes the moment significant.
• Holding an idea loosely gives it room to unfold; gripping it tightly is what causes it to unravel instead — the difference between disassembling something on purpose and watching it fall apart.
• Genetic or predisposition information (like a cholesterol test result) doesn't eliminate the value of lifestyle choice — it just narrows the range you're actually choosing within.
• Big epiphanies rarely land once and disappear; they tend to keep resurfacing for days or weeks afterward, the way aftershocks follow an earthquake.
• The right response to a major realization is often reflection, not immediate action — sitting with it, journaling about it, letting it keep unfolding before trying to "do" anything with it.

Three Connection Points

• Read more from Patrick Rhone
• Catch up on past issues of The Lantern (and more)
• Productiveness

I'm not going to tell you what the epiphany was — not yet, anyway. What I will say is that if something's been quietly resurfacing in your own life for years without your noticing why, it might be worth sitting with it instead of trying to explain it away. Some things take six years to make sense. Give yours the same patience.

Logic is beautiful and it's also almost never enough. That's the tension running through this entire conversation — the idea that we want our decisions to be purely logical because it's simple and concrete, but almost no real situation in a human life actually has the structure logic requires. I've believed for a long time that reason lives somewhere in the nuanced middle between logic and emotion, and I wanted to sit down with someone who's spent a career studying exactly that boundary.

Tom Griffiths is a Princeton professor and the author of the new book The Laws of Thought: The Quest for a Mathematical Theory of the Mind. If you know his earlier book, Algorithms to Live By, this one is the foundation underneath it — the deeper, denser history of how mathematics has tried, and often failed, to fully capture how minds work. We covered logic's limits, David Hume's riddle about induction, why AI systems fail in strange and "jagged" ways humans don't, and how a 200-year-old idea from George Boole ended up, several generations later, inside modern neural networks through his own great-great-grandson.

Six Discussion Points

• Logic only works when you already have all the information you need and the conclusion is certain — which describes almost none of the decisions we actually make as humans.
• Amos Tversky's early work on similarity (a horse is more "like" a camel than a camel is "like" a horse) laid the groundwork for the heuristics-and-biases research he later did with Daniel Kahneman.
• "Productivity," in the cognitive science sense, means a system's ability to generate something genuinely new — which is closer to creativity than to output.
• David Hume's riddle of induction shows we can't logically justify assuming the future will resemble the past — we simply have a habit of expecting it to.
• AI systems demonstrate "jagged intelligence": strong on one problem, mysteriously weak on the problem right next to it, because they arrive at solutions through a completely different process than human brains do.
• Reading old, "outdated" books remains valuable specifically because they capture the right questions — not just today's most efficient answers.

Three Connection Points

• The Laws of Thought by Tom Griffiths
• Algorithms to Live By by Tom Griffiths and Brian Christian
• Stop Managing Your Time, Start Crafting Your Time Instead

If there's one thing to sit with after this conversation, it's that fuzziness isn't a flaw in how we think — it's often the most accurate description available. Tom's book gives you the historical throughline for why that's true, and honestly, it's a book you want to take your time with, not tear through. Give it the same patience the ideas in it deserve.

There's a two-word sentence that's been sitting with me since I finished this book, and I haven't been able to shake it: life is. Not life is hard, not life is good, not life is anything — just life is. Gary John Bishop makes the case that the moment you add a descriptor to that sentence, you're not describing life anymore, you're arguing with it.

Gary is the author of Unfuck Yourself and his newest book, Now What: You, Your Life, and the Truth You've Been Avoiding — a book I finished in one sitting and then immediately wanted to read again, which is about as strong an endorsement as I can give. We got into ontology, why "time management" is a phrase we cling to out of a need for false control, the difference between knowing something and knowing it "to the degree that it gets here," and yes, eventually, a fairly deep dive into vintage watches.

Six Discussion Points

• "Life is" isn't an incomplete sentence waiting for a descriptor — the descriptor is where the struggle and noise get added back in.
• Language isn't something that happens after you feel or see something; you speak from a distinct place, and that place shapes what becomes possible for you.
• "Time management" survives as a phrase because it offers the illusion of control over something — time itself — that was never actually manageable to begin with.
• Now isn't a moment in time; Gary frames it as a location — the one place where your memories, hopes, and worries are all actually happening.
• Real understanding isn't the same as having knowledge about something — you can know all about love, or now, or time, without it ever "landing" the way lived experience does.
• Setting concrete goals is fine, but postponing your sense of confidence, power, or satisfaction until you reach them is optional — those states are available to practice right now, not just after you arrive somewhere.

Three Connection Points

• Now What: You, Your Life, and the Truth You've Been Avoiding by Gary John Bishop
• Connect with Gary at garyjohnbishop.com, or his new podcast, Truth and Conversation
• Stop Managing Your Time, Start Crafting Your Time Instead

If there's one exercise to take from this conversation, it's this: try sitting with the sentence "life is" and stopping right there. No descriptor, no judgment, no story attached. See how long you can hold it before your mind wants to finish the sentence for you. That's the whole book, honestly — and it's worth spending more than one sitting with.

Inbox zero was never about the number. That's the part almost everybody forgets. When Merlin Mann coined the term in the early 2000s, "zero" wasn't a count of unread messages — it was the amount of mental space your inbox occupied. Somewhere along the way, we turned a philosophy about protecting attention into a scoreboard, and the guilt machine that followed is the reason so many of us feel like we're failing at something that was never actually the goal.

I want to walk you through where this idea went sideways, why even someone as rigorous as Cal Newport still aims at the same numeric target after correctly diagnosing the problem, and what I think the real goal should be instead. I'm calling it Inbox Today — not a number, a state. This one connects directly to the broader work I do around TimeCrafting and productiveness: the shift from chasing quantity to protecting quality of attention.

Six Discussion Points

• Merlin Mann's original "inbox zero" was never about the count in your inbox — it was about getting email out of your head.
• Cal Newport diagnoses the inbox problem correctly (it's a terrible place to store obligations) but still calls the win condition "empty," proving how deeply the numeric frame is baked in.
• Your inbox is a receiving dock, not a warehouse — it's meant to be passed through, not lived in.
• Batching email by context, instead of processing top-to-bottom in arrival order, protects you from the mental cost of constantly switching topics.
• "Inbox Today" swaps a universal number everyone interprets the same way for a personal, situational sense of calm that's different for every person, every day.
• Doing one task that's actually yours before you open email at all tilts the entire day back in your favor — no app, no system, just a 10-minute head start.

Three Connection Points

• Get the FREE inbox tips matched to where you're at right now → mikevardy.com/email
• Stop Managing Your Time, Start Crafting It Instead
• Subscribe to The Lantern for more on productiveness

Email isn't a solvable problem the way we've been taught to treat it — it's a relationship, and relationships need boundaries, not scoreboards. If today's conversation landed for you, the next step isn't a new app. It's deciding what "today" looks like for your inbox, not what "zero" does.