How to Redesign Your Life and Work So Progress Takes Less Force
If something slows you down more than once, fix it.
There’s a joke that runs through all eleven seasons of Modern Family. Phil Dunphy heads up the stairs, and one particular step, the loose one, catches his foot. He stumbles, grabs the rail, recovers, and mutters the same line every time: Gotta fix that step. The actor, Ty Burrell, improvised it once, it got a laugh, and it stuck around for a decade.
And then he never does it. Not that episode, not the next season, not ever. Same step, same stumble, same line – for more than ten years. It’s funny because it’s a joke, and it’s funnier – if you sit with it a second – because it isn’t. You have a step like that. I know you do, because I have several, and I’ve never met anyone who doesn’t.
Let me tell you about two of mine, and notice how dumb they are, because the dumbness is the point. A few months ago, the toilet in our master bathroom started running. The flapper had gone bad and it was leaking, leaking enough that the water company actually emailed me to say they’d detected “continuously running water” and I might have a leak. So I had a confirmed, documented problem, flagged by a third party. Our solution? We shut off the water to that toilet and started using the hall bathroom. (To be fair, that was my solution, not my wife’s.) For weeks. A flapper costs a few dollars and takes ten minutes to swap, but the fix meant a trip to Home Depot and the long walk back to the plumbing aisle, and somehow that was the thing I couldn’t get myself to do. So we just moved bathrooms.
Here’s the other one. The battery died in my garage door remote. Rather than pop it open, figure out what kind of battery it takes, and grab one the next time I was at the store, here’s what I did instead – every single day. I’d back the car out of the garage, hit the wall button to start the door closing, then hop out and step over the safety sensor so it wouldn’t bounce back up, and drive off. When I got home, I’d park on the driveway, go in through the front door, walk through the house to the garage, hit the button from the inside, and pull the car in.
Read that again. That routine takes longer than fixing the remote would take. Not longer over a month, longer on the first day. And I did it anyway, over and over, because at no point in that little performance was I ever in what I’ve come to call “fix-it mode.”
You could look at those two stories and conclude I’m lazy, or disorganized, or a bit of an idiot. I’ve considered all three. But that’s not what’s going on, and figuring out what is going on is the whole reason I wrote this book. In neither situation was I short on motivation to have a working toilet or a working garage door. I wanted both of those things very much. And in neither one was the task itself hard. A flapper and a battery are about as easy as home repair gets. What stopped me wasn’t the size of the job. It was a small, specific point of resistance sitting right in front of it: the trip, the unfamiliar battery, the little bit of figuring-out I’d have to do before I could even start.
That resistance has a name, and once you have the name, you start seeing it everywhere. The name is friction. Friction is anything that makes something harder than it needs to be. It’s the gap between how hard a thing actually is and how hard it feels to start. It shows up as searching, waiting, deciding, remembering, switching, redoing, and figuring out, all the little bits of drag that surround a task without being the task itself. The toilet repair wasn’t hard. The friction around it was just barely high enough that, day after day, walking to the other bathroom was easier. And the path of least resistance always wins. That’s not a character flaw, it’s physics.
Here’s the way I’ve come to picture it. Imagine a road you drive every day, and right in the middle of it there’s a pothole. Every morning you slow down, swerve, brace, and recover. It costs you a few seconds and a little jolt of irritation. A few seconds is nothing. You’d feel silly making a project out of a few seconds. But you don’t pay it once. You pay it every day, both directions, for as long as you live on that road. And you pay more than the seconds. You pay the bracing, the little flare of annoyance, the attention it steals from whatever you were thinking about before you had to swerve. That’s friction. It’s a tax you pay every time you travel a badly built road, and you’ve basically got two choices. You can keep paying the tax with patience and willpower, forever, or you can fix the road once.
Most of us invent a third option, though, one that feels like escaping the choice entirely. We build a detour. We put together an elaborate little route around the pothole and call it a solution, because a detour feels free in a way that filling the hole never does. My garage remote routine was a detour. So was moving to the other bathroom for a month. The trouble is that a detour is just the tax again, paid in a different currency. It never makes you stop and do the work, so it wins every time, and it quietly costs more than the repair it saved you from.
Almost all of us, almost all the time, keep paying the tax. Not because we’re foolish, but because each individual payment is too small to bother with, and stopping to fix the road feels like a project we don’t have time for. So the tax just goes on getting collected, quietly, for years. And that’s the trap, because friction compounds. One annoyance you can shrug off. The same annoyance, paid every day, becomes one of the most expensive things in your life, and you never even see the bill.
Which brings me back to Phil and his stair. Here’s the part of that joke I find almost profound, and I don’t think the writers planned it, though since Burrell made it up on the spot, maybe he sensed it. Phil notices. Every time. He says the line, gotta fix that step, out loud. He is not oblivious. He has diagnosed the problem correctly, repeatedly, for eleven years, and it changes nothing, because noticing a thing and fixing a thing turn out to be two completely different acts. He has all the awareness in the world and none of the repair. That’s most of us. We know exactly where our loose boards are, and we could list them right now. The knowing was never the problem.
So this book is built on one simple rule, the rule I wish I’d had taped to my bathroom mirror years ago:
If something slows you down more than once, fix it.
That’s the whole thing. Not “if something is a disaster,” not “if something finally becomes unbearable.” If it slows you down more than once, if you’ve hit that step twice, it is no longer a random inconvenience. It’s a recurring one, and recurring friction deserves a completely different kind of attention than we usually give it. The first time might be bad luck. The second time is information. The third time is a system quietly asking to be fixed.
And here’s what the rule is really for. It isn’t mainly about saving time, though it will save you plenty. It’s about turning that little flash of irritation, the ugh, this again, into a signal instead of just a feeling. Right now, when you hit your loose board, the annoyance flares and then fades and you keep moving, because you’re busy, because you’re in the middle of something, because you’re never in fix-it mode at the exact moment the friction hits. The rule takes that flash and puts it to work. This again becomes the cue to stop, just for a second, and ask a different question than the one you usually ask. Most of the time, standing in front of an annoying task, we ask how to get through it. The rule asks something else entirely: how do I make this stop happening? That one shift, from getting through it to making it stop, is the difference between finishing a task and improving your life. And it works at every scale. It works on a garage remote, and it also works, as you’ll see, on the things you’ve been meaning to do for years.
Because I’ll be honest with you, the loose boards that really cost me weren’t the toilet and the remote. Those are just easy to laugh at. The expensive ones were the projects I genuinely believed in and still couldn’t seem to start, or couldn’t seem to finish. I had one, a real one, that sat parked for two years. Not because I didn’t want it, and not because I didn’t have the time. It stalled on a single piece I didn’t know how to build, and that one unfamiliar piece was enough to freeze the entire thing. I’ll tell you that whole story a few chapters from now, because it taught me more about friction than anything else ever has. For now I just want you to know that this is not a book about tidying your junk drawer. The junk drawer is where we’ll warm up. Where we’re going is the stuff that has actually been weighing on you.
Here’s the thing, though: this idea has a dark version, and I don’t want you to mistake one for the other. This is not a book about making your life frictionless, and it is definitely not a book about making your life empty. Some friction is the entire point. Cooking dinner for someone you love takes effort, and the effort is the gift. A hard conversation is uncomfortable precisely because it matters. A slow walk with no destination is “inefficient,” and that’s exactly what it’s for. If you strip all the effort out of a life, you don’t get a better life. You get a thinner one. So the goal was never to remove effort. The goal is to remove the unnecessary effort, the drag that adds nothing, so that your time and attention and energy are free for the things that actually deserve them. There’s a line I’m going to come back to more than any other, because it’s as close as I can get to the whole idea in five words:
Automate the drag. Protect the meaning.
That’s the deal this book is offering. Not a life with less in it, but a life with less resistance in it, so there’s more room for what you actually care about.
So here’s where we start. Sometime today, you’re going to hit one of your loose boards. Maybe it’s small and stupid, like my toilet. Maybe it’s big and quiet, like a project you’ve been carrying around unfinished for so long you’ve stopped noticing the weight of it. When it happens, you’ll probably do what you always do, mutter something under your breath and keep walking. I just want you to catch yourself in that moment. That’s all, for now. Don’t fix anything yet. Just notice the flash, and hear it for what it is: not a comment on your character, but a loose board on the stair you’ve been stepping over for years.
We’re going to fix that.
Here is a list I could have written about myself at almost any point in my adult life. I was going to start exercising again. I had a stack of papers on the kitchen counter that I meant to file, and instead I moved it, from the counter to the desk to the top of the dresser and back to the counter, for the better part of a year. There was a task at work I dreaded so much that every week I found a reason to push it to the following week, and every following week I did it again. None of these were hard. None of them were mysterious. I knew exactly what needed to happen in each case. And still, week after week, month after month, nothing happened.
For a long time I had a single explanation for all of it, and I suspect you have the same one, because it’s the one everybody reaches for. I told myself I was lazy. Or if not lazy, then scattered, or undisciplined, or bad at follow-through, or just not the kind of person who has their act together. When the same problem shows up over and over, the most natural thing in the world is to conclude that the problem is you. The papers keep piling up, so you must be a messy person. The exercise never happens, so you must lack willpower. The dreaded task keeps sliding, so you must be a procrastinator. It’s a tidy story. It has one character, and that character is the villain, and the villain is always you.
I want to take that story away from you, because it’s wrong, and it’s been costing you far more than any of the tasks it’s supposedly about. Most of the recurring problems in your life are not discipline problems. They are friction problems. And those two things are not just different. They are opposites, and they need opposite solutions.
A discipline problem is when you know the thing is worth doing, the path to doing it is clear and unobstructed, and you simply don’t push yourself to do it. The fix for that really is more willpower, more resolve, more gritting of teeth. A friction problem looks almost identical from the outside, but underneath it’s the reverse. It isn’t that you won’t push. It’s that there’s something in the way, some small point of resistance sitting between you and the thing, and every time you approach it you hit that resistance and peel off. The fix for that is not more force. It’s less resistance. You don’t need to push harder against the obstacle. You need to remove the obstacle so there’s nothing to push against.
Now here’s why this matters so much, and why getting it wrong is so quietly destructive. When you treat a friction problem as a discipline problem, you reach for the one tool that was never going to work. You apply willpower to a resistance problem, and willpower doesn’t clear resistance – it just spends itself against it. So you try harder, and it doesn’t work, and you try harder again, and it doesn’t work again, and after enough rounds of this you draw the only conclusion that seems available: the tool is fine, so the failure must be in me. You’ve been swinging a hammer at a screw and concluding you’re weak because the screw won’t go in. The hammer was never the problem, and neither were you. It was just the wrong tool for the job, aimed at the wrong diagnosis.
Take the exercise I kept not starting. For years I read that as a willpower deficit, a thing about my character. When I finally looked at it honestly, the resistance wasn’t the workout. I actually like how I feel afterward. The resistance was everything crowded in front of the workout: finding the clothes, deciding what I was even going to do that day, the sense that I needed a solid hour or it didn’t count. Every morning I ran into that little wall of deciding and preparing, and every morning I peeled off. More willpower would have meant forcing myself over that wall by brute effort, every single day, forever. It would have worked some days and failed most, and each failure would have gone straight into the ledger as more evidence that something was wrong with me. The actual fix had nothing to do with willpower. It was laying the clothes out the night before and deciding, once, that ten minutes counted. Remove the deciding and the preparing, and the thing I supposedly lacked the discipline for started happening on its own.
The papers on the counter were the same shape. I don’t have a moral failing that makes me leave paper lying around. What I had was no easy place to put it. Filing meant deciding which folder, and half the time there wasn’t a folder, so I’d have to make one. That was just enough of a hitch that moving the stack to the dresser was always the easier move. The pile wasn’t a verdict on my character. It was a missing folder. But you cannot fix a missing folder by feeling worse about yourself, and feeling worse about myself was the only strategy I’d been running for years.
This is the reframe the whole rest of this book stands on, so I want to say it as plainly as I can. When the same problem keeps happening, the useful question is not what’s wrong with me? The useful question is where’s the friction? That’s it. That’s the entire shift. One question sends you looking inward for a flaw to fix, a search that rarely finds anything but more guilt. The other sends you looking at the road for an obstacle to remove, and obstacles, unlike character flaws, can actually be removed.
I know how that can sound at first, like I’m handing you a way off the hook. Let yourself off, blame the road, call it a friction problem and go take a nap. But that is not what this is, and I want to be careful here, because the reframe only works if it’s honest. Asking where’s the friction? is not an excuse. It doesn’t say the thing doesn’t need doing. It fully expects you to do the thing. It just refuses to blame you for not having done it yet, because blame was never going to get it done. Self-blame feels like taking responsibility. It has the texture of accountability, the sting, the seriousness. But it’s actually the opposite of responsibility, because it keeps you staring at the wrong thing. Every hour I spent deciding I was lazy was an hour I wasn’t spending finding the missing folder. The kind version and the effective version turn out to be the same version. Stop asking what’s wrong with you, and you free up all the energy you were spending on that question to go find the actual obstacle and take it out.
There’s a deeper layer to this, and it took me a long time to see it, so let me try to say it carefully. For years I thought the bad feeling around all these undone things was guilt about being lazy. It wasn’t. When I finally sat with it, what I found underneath was something different and more tender. The guilt was never that I was lazy. It was that I knew I could, and hadn’t. That’s a very specific ache, and it’s not the ache of a lazy person. A truly lazy person doesn’t feel it at all. The ache lives precisely in the gap between what you know you’re capable of and what you’ve actually gotten done. It’s the distance between the person you know you could be and the pile of paper on the counter that says otherwise. You feel it because you believe in your own capability. The guilt is the evidence that you were never the problem, because you can’t feel that particular gap unless you already know the ability is in there.
Which is why finishing feels the way it does. When you finally clear one of these things, the relief is almost always bigger than the task deserves. File the papers, and you feel lighter than a stack of paper could possibly account for. That’s because you weren’t just carrying the task. You were carrying the gap. And closing it does something more than complete an item on a list. It restores a kind of integrity with yourself. Every one of these undone things is a small promise you made to yourself and then quietly broke, over and over, every time you walked past it. Finishing is how you keep the promise. That’s the real reason it feels like relief and not just accomplishment. You’re not celebrating a filed stack of paper. You’re rejoining the person you told yourself you were.
So if you take one thing from this chapter, let it be this. The recurring problems you’ve been treating as proof of some flaw in you are, almost every one of them, just badly built roads. You’ve been paying a tax and blaming yourself for the size of the bill, when the road was the thing that needed fixing all along. It’s not you. It’s the road. And the beautiful part, the part that makes everything after this possible, is that roads can be fixed, and you were never broken to begin with. You were just trying to drive over a pothole with more willpower, which is the one thing that never fills a pothole.
We’re going to go find those roads now, starting with the ones that cost the most. But you don’t need to fix anything yet. For now I just want the question changed. The next time you catch yourself sighing at the same old thing and reaching for the old verdict – that you’re lazy, scattered, not the type who has it together – I want you to notice you’ve grabbed the hammer again, set it down, and ask the other question instead. Not what’s wrong with me? Just where’s the friction? You’ll be surprised how often the answer is small, and fixable, and standing right there in front of you where the guilt used to be.
A few chapters ago I promised you a story. I told you the loose boards that really cost me weren’t the running toilet or the dead garage remote – the ones that are easy to laugh at – but a project I believed in that sat parked for two years over a single piece I didn’t know how to build. This is that story. But before I tell it, I want to name the thing it taught me, because once you see it you will not be able to stop seeing it in your own life.
Here it is. I can get eighty, maybe ninety percent of the way through almost anything. I’m guessing you can too. That first big stretch is the part you already know how to do, the part that plays to what you’re good at, and honestly the part you enjoy. So you fly through it. You build momentum, you feel capable, you can practically see the finished thing. And then you arrive at the last slice, the final ten or twenty percent, and you stop. Not because you got lazy, and not because you ran out of belief in the project. You stop because that last slice is made of something different. It’s the part that requires learning something you’re not confident about, or doing something you’re pretty sure you won’t enjoy. And that is exactly where the resistance lives.
This is the thing I got wrong about myself for years. I used to think a stalled project meant I didn’t want it badly enough, or that I was the kind of person who starts things and doesn’t finish them. That story is popular and it feels true and it is almost always wrong. The projects I stalled on were projects I wanted. I had proven I wanted them, because I’d already done the hard, sustained, eighty-percent work of building them. Nobody grinds through eighty percent of something they don’t care about. The belief was real. The wall was real too, and the wall was never the whole project. It was one specific slice near the finish – the slice where my competence ran out or my enthusiasm did – and that slice was enough to freeze everything behind it.
That’s the pattern I want to hand you in this chapter, because it’s the bridge between the small stuff and the big stuff. In Chapter 1 I told you about six pill lids and a garage remote, and you might have thought, fine, cute, but my real problem isn’t a remote, it’s the business I never started or the book I never wrote. Same lens. Same diagnosis. The friction on the pill bottles was six lids, a hidden micro-step that wasn’t the task itself. The friction on the big project is the exact same shape, just larger: one unfamiliar slice sitting between you and the finish line, doing all the stopping. The scale changes. The move doesn’t.
Let me show you what it looked like in my life.
I run an insurance and benefits business, and a while back I wanted to build a website called ComplyDIY. The idea was a self-serve compliance tool, a place where a small employer could work through what they actually needed to do to stay compliant without hiring somebody like me to hold their hand through all of it. I knew this material cold. Compliance is my world. I could write every checklist, every notice, every explanation, every piece of guidance on that site in my sleep. I could design how it should flow. I could build the pages. All of that – the whole body of the thing, the part that made it valuable – was squarely inside my eighty to ninety percent. I knew it and I enjoyed it.
And there was one piece I didn’t know how to build: the paywall. The payment processing, the user registration, the membership access, the whole machinery that lets a person sign up, pay, and log in to see the stuff they paid for. That’s it. That was the slice. Everything a customer would actually value, I could make. The turnstile at the front door, I could not.
So the project stalled. Not for a week. For about two years.
Now watch what I did during those two years, because this is the part that matters. I did not sit around lacking willpower. I threw real resources at that wall. I tried to outsource it. I found people to build just that one piece, the payment and membership setup, and I paid them actual money to do it. And they didn’t deliver. I spent the money and I did not get the thing. So then I figured I’d have to learn it and build it myself. Every time I looked at that prospect I knew it would be a pain – unfamiliar and tedious and not even slightly fun – and so, in my own words, I just procrastinated forever on it. The whole site, finished in every way that counted, sat there waiting on a login screen I couldn’t bring myself to build.
I want you to sit with how absurd that is, because I’ve had to. A complete, valuable thing, parked for two years, over a piece that was a tiny fraction of the total work and none of the total value. If you’d asked me in that stretch why ComplyDIY wasn’t live, I’d have told you I was busy, which was true. And I’d have believed that was the reason, which was not. I had time to build the entire rest of the site. I did not have whatever it takes to start the one part I dreaded. The wall wasn’t time. The wall was one unfamiliar slice, and I’d organized two years of my life around walking past it.
Here’s how it finally broke. I sat down and described what I needed to a piece of AI software, one of the tools I now use for exactly this kind of thing. I typed in, more or less: here’s what I’m trying to do, the payment and the registration and the membership access – can you explain how to build it? And it laid the steps out for me, clearly, the way it does. And then it added one more line, almost as an aside. It said, in effect, or I can just do it for you.
I remember my exact reaction. What? Yes. Do it for me.
And it did. The slice I’d dreaded for two years, the one I’d paid strangers to handle and gotten nothing, got built. The turnstile went up. And ComplyDIY, a thing I’d carried around unfinished for so long it had become part of the background noise of my life, went live. I’ll be honest about how that felt, because I skipped over it in Chapter 1 and it’s the part that actually matters. It was relief, out of all proportion to the size of the task. I wasn’t relieved that a login page existed. I was relieved that I’d stopped breaking a promise I’d made to myself two years earlier.
So let me pull out the lessons, because I don’t want you to just enjoy the story and miss the point. There are three, and they’re the whole reason this chapter exists.
The first lesson is where the friction actually was. It was never the compliance content. That was the eighty to ninety percent, and it was the valuable part, and I never once struggled with it. The resistance lived entirely in one unfamiliar technical slice near the finish. If you’d asked me for two years what was hard about ComplyDIY, I might have gestured vaguely at “getting it launched,” as if the difficulty were spread across the whole thing. It wasn’t spread across anything. It was concentrated in one spot, and I hadn’t named the spot. Naming where the friction lives is half of removing it, and I’d skipped the naming for two years.
The second lesson is the one that cost me money to learn, so let me save you the tuition. Throwing willpower at the wall didn’t work, and neither did throwing money at it. I outsourced the exact slice that was stopping me, I paid for it, and it failed. That’s worth pausing on, because our two default answers to a stalled project are “try harder” and “hire it out,” and I ran both experiments in full. Discipline wasn’t the answer. Spending wasn’t the answer. The thing that finally worked wasn’t a bigger push or a bigger check. It was removing the friction, aiming a tool at that one specific slice and letting it do the part I couldn’t. That’s the whole thesis of this book playing out in a single project: you don’t get over the wall by wanting it more. You get over it by attacking the exact slice that is the wall.
The third lesson is about AI, and I want to be careful and honest here, because it would be easy to turn this into a commercial and that’s not what this is. AI mattered in this story for one specific reason: it happens to be very good at exactly the kind of thing that last ten to twenty percent is usually made of. The unfamiliar technical build. The tedious setup. The part you don’t know how to do or don’t want to do. It didn’t replace the eighty to ninety percent I already had, the knowledge and the content and the judgment. That was still mine, and it always will be. What it did was clear the one segment where my projects reliably died. That’s the honest, modest role for these tools in this book. Not magic. A friction remover that’s pointed right at the spot where things stall.
But here’s the part I most want you to hear, because it’s the part that keeps this from being a book about software. AI is one way over that wall. It is not the only way. That same slice can be cleared without any AI at all. Sometimes the move is a better approach, a simpler path to the same end that sidesteps the hard part entirely. Sometimes it’s delegating for real, finding the right person instead of the wrong one and actually getting the thing. And sometimes the move is lowering the bar on the part you don’t enjoy – deciding that the dreaded slice can be good enough instead of perfect, which is often all it ever needed to be. The tool I reached for was AI. The lesson underneath it is older than any tool: find the slice that’s stopping you, and aim your effort at that slice only.
Which brings me to the move I want you to take out of this chapter. When a project stalls, the first thing most of us do is reach for a verdict about ourselves. I never finish anything. I lost interest. I’m not disciplined enough. Put that down. It’s not only unkind, it’s inaccurate. And worse than inaccurate, it’s useless, because it doesn’t tell you what to do next. Do this instead. Ask where the project actually stopped, and get specific about it. Not “the whole thing feels stuck,” but the one slice. What is the exact piece you keep walking past? It’s almost always the part you don’t know how to do, or the part you’re dreading. That’s not a coincidence. That’s the wall announcing itself. Name that slice out loud, and then aim everything you’ve got at it and nothing else. Your effort, a tool, a better approach, the right person, a lower bar. You don’t have to re-motivate yourself for the whole project. You already did the eighty percent, remember. You just have to get over the one wall that’s left.
Because that’s the quiet good news buried in all of this. If you’ve stalled on something you care about, the finish line is a lot closer than the stuck feeling makes it look. You already did the hard, valuable part. What’s left is one slice. Go find it, name it, and take it down. The thing you’ve been carrying for two years can be done by the weekend. Mine was.
Here is a thing I did for the better part of a month, and I want you to know I am aware of how it sounds. Every evening I would go to write in the little journal I keep by the bed, and the pen would be dead. Not out of ink, just one of those pens that needs a good scribble to get going, and half the time the scribble didn’t work either. So I’d sigh, get up, walk to the kitchen drawer, dig for a pen that worked, bring it back, write my two lines, and set it down somewhere that was not next to the journal. And the next night the whole thing would happen again, because the working pen had wandered off during the day and the dead one was right back where it always was, waiting for me.
I told myself, most of those nights, some version of “ugh, this again.” And then I walked to the kitchen. That little phrase – that flash of irritation – is the most useful thing your brain gives you all day, and almost all of us throw it straight in the trash.
I want to spend this chapter on that flash. In the last chapter we talked about where projects die, at the last unfamiliar slice; before that, about the road and the tax. But none of that helps you if you can’t catch friction in the act. And the way you catch it is not by scheduling a friction audit for some tidy Sunday. It’s by learning to hear a bell that is already ringing, several times a day, in a language you’ve been taught to ignore.
Let me start with the thing that took me longest to believe. Avoidance is information, not a verdict.
When you keep sliding a task to tomorrow, the story we’re all handed is that this says something about you. You’re undisciplined, you’re a procrastinator, you lack follow-through. I spent a lot of years quietly agreeing with that story about myself, and it never once helped me do the thing. Here’s what’s actually true most of the time. If you keep avoiding something, that avoidance is pointing at a real thing – a specific point of resistance sitting between you and the task – and your reluctance is a reasonable response to it. You’re not avoiding the task. You’re avoiding the friction wrapped around the task, and you can’t tell the two apart because nobody ever taught you to look.
So instead of judging the avoidance, inspect it. When you notice you’ve dodged something three days running, don’t ask what’s wrong with you. Ask two smaller, colder questions. What is the actual first physical action here, the very first thing my hands would do? And what is standing in the way of that first action? Those two questions turn a character flaw back into an engineering problem, which is a much friendlier thing to have.
When you start inspecting instead of judging, you find the stall almost always has a recognizable shape. It’s rarely the task itself. It’s one of a handful of usual suspects, and once you can name them you stop taking them personally. You don’t know where to start, so the whole thing sits there as one undifferentiated lump. The tool you’d need isn’t ready or isn’t charged or isn’t where it should be. The workspace is buried, so before you can begin the real thing you have to do a whole invisible pre-task of clearing space. You don’t know where the information lives, so step one is a search you’re dreading. You’re a little afraid of doing it wrong, so not starting feels safer than starting badly. Or there are simply too many decisions crammed in front of the first move. Before you can act you have to make six choices, and that pile of tiny choices is heavy enough to send you to your phone instead.
Look at that list and notice what’s missing from it. Laziness isn’t on there. None of those are moral failures. Every one of them is a design problem, which means every one of them has a fix that has nothing to do with trying harder. My dead pen was the second one, the tool that’s never ready. It was never about discipline. It was about a pen.
Now, here is the piece I most want you to take from this chapter, because it’s the hinge the whole book turns on. The flash of “ugh, this again” is an alarm bell. It is your system telling you, in the only language it has, that you have just hit recurring friction. And the tragedy of it, the reason we walk to the kitchen for the pen night after night, is that the bell rings at the worst possible moment: right when you’re busy doing the thing. You’re mid-flow, head down, trying to get to bed, and that is precisely when you are least able to stop and redesign anything. So the insight, the “oh, I should fix this,” either never arrives or arrives at random – weeks later, in the shower, when there’s no pen to fix and nothing to act on. You are almost never in fix-it mode at the exact instant the friction hits, because the friction hits while you’re in doing mode. Those are two different gears.
That’s why the rule matters. Not because the rule is clever, but because it does a specific job: it installs the bell so you can’t sleep through it anymore. If something slows you down more than once, fix it. What that rule is really doing is converting a rare, lucky, out-of-nowhere realization into a standing trigger you can actually run. It says: the next time you feel “this again,” treat that feeling as a cue, the way a smoke detector treats smoke. And I want to be careful here, because “fix it” can sound like a command to drop everything and repair the road at midnight in your pajamas. It isn’t. Hearing the bell doesn’t mean you have to fix the thing this second. It means you stop, for one honest second, and register what’s happening: this is not a fresh problem, this is recurring friction, and recurring friction has earned a different kind of attention than I’ve been giving it. Sometimes you fix it right then. Often you just note it deliberately, so that later, when you’re back in that gear, it’s on the short list instead of lost. The point is to stop letting the bell ring into an empty room.
Back in the first chapter I put two questions side by side, and I want to sharpen them now, because this is where they earn their keep. Standing in front of an annoying task, a normal person asks the normal question: how do I get through this? How do I power through, grind it out, survive it one more time. That’s the doing-mode question, and it’s not wrong. Plenty of things just need doing. But a friction-reduction task asks a different question entirely: how do I make this stop happening? Not how do I get past the pothole today, but how do I fill the pothole so I never swerve here again. The first question ends when the task ends. The second question ends the task forever. And here’s the quiet part: you are allowed to ask the second question about almost anything, but you almost never do. The first question is the only one that fits inside doing mode. The bell is what reminds you the second question exists.
So how do you actually act on this without turning your evenings into a home-improvement project? The move that has done more for me than any other is embarrassingly simple. Once you’ve found the true first step, lower its cost until starting is nearly free. Not the whole task. Just the first physical action. Make the beginning so cheap that not-starting takes more effort than starting.
Here’s the personal version, and yes, it’s the pen. The fix was not “be more disciplined about journaling.” The fix was to buy a box of pens that actually work, put one in the journal as a bookmark, and stash three more in the drawer next to it so the supply never runs dry. That’s it. Now the first physical action, pick up the pen, is already done before I sit down. The friction didn’t get managed or muscled through. It got deleted, for a couple of dollars, one time. My grandmother did the grown-up version of this her whole life and called it “setting things out.” She’d lay her clothes out the night before, put the pills by the coffee maker, set the checkbook on top of the bills. She wasn’t being quaint. She was pre-paying the friction the night before, when she had a spare minute, so that morning-her, who didn’t, could just move.
Here’s the work version, and it cost me more years than I’d like to admit. For a long time, every time I needed to send a client a certain kind of letter, I started from a blank screen. Blank screen is the worst tool-not-ready problem there is, because a blank screen is where all six of those stalls live at once: where do I start, what’s the format, where’s the client’s info, what if I word it wrong. So I’d put it off, and the letters that should’ve gone out Monday went out Thursday every week, for no good reason. The fix was to build a template once, with the standard language already written and little bracketed slots for the parts that actually change. Now the first step isn’t “compose a letter.” It’s “open the template and fill three blanks.” I lowered the cost of starting from a cliff to a curb, and the letters started going out on time – not because I found new willpower, but because I stopped requiring any.
Which brings me to the one thing that can undo all of this, and I need to name it plainly because it’s so easy to do without noticing. The enemy here is not failing to fix the friction. The enemy is re-deferral. It’s the specific act of hearing the bell, actually noticing “this again,” feeling that flicker of recognition, and then walking around the pothole one more time anyway. That’s worse than not noticing at all, because now you’ve spent the awareness and gotten nothing for it. And it doesn’t just leave the loop open. It recharges it. Every time you notice and route around it again, you’re teaching yourself that the bell means nothing, that “this again” is just the sound your life makes, background noise, no action required. You’re training yourself back into deafness, one small walk-around at a time.
So I’m not going to ask you to fix anything yet in this chapter either. I’m just asking you to stop letting the bell ring for free. The next time you feel that little flash, the “ugh, this again,” catch it. Don’t scold yourself, and don’t necessarily grab a wrench. Just stop for one second and say, out loud if you have to, “okay, that’s the bell.” Look at what your hands were about to do the hard way. Ask what the true first step is and what’s blocking it. You may fix it on the spot, or you may just write it down. Either one is a win. The only losing move is the one we’ve all made a thousand times, which is to hear it clearly, know exactly what it means, and keep walking to the kitchen for a pen.
You’ve been hearing that bell your whole life. This is just the chapter where you finally answer it.
Let me do some arithmetic that nobody ever does, because doing it is the whole trick.
Say there’s a small annoyance in your day that costs you two minutes. Not a catastrophe, not even something you’d complain about. Two minutes. Opening the six pill bottles I keep telling myself I’ll take. Hunting for the charging cable that never lives where I left it. Logging into the same system that logs me out every time. Two minutes is nothing. You’d feel ridiculous calling a family meeting over two minutes.
But you don’t pay it once. You pay it every day. Two minutes a day is a little over twelve hours a year. So that small thing, the one too minor to mention, is quietly eating a day and a half of your waking life every year – for as long as you let it run. And that’s just the part you can put on a stopwatch. The stopwatch misses the expensive part. Because every time you hit that little snag, you also pay a flicker of dread on the way in and a jolt of context-switch on the way out. You were thinking about something, then you weren’t, then you had to find your way back. That switch has a cost that never shows up on the clock, and you pay it twice a day too.
Here’s why we let it happen. We misprice recurring friction because we price it one instance at a time. Standing at the kitchen counter with the pill bottles, the annoyance is small. Two minutes really is nothing. So at no single moment does it ever feel worth solving. The cost only becomes real in aggregate, and aggregate is exactly the thing you can’t see while you’re standing there. You experience the two minutes. You never experience the twelve hours. The smallness is a disguise, and it works every time.
I found the disguise on my own vitamins. Six different bottles, six lids, every morning. The resistance was never swallowing the vitamins, and it was never doubting that I needed them. It was the six lids. Six little acts of opening and closing before I’d even had coffee. So most mornings I just skipped it, and then felt vaguely guilty about skipping it, which is its own small tax on top of the first one. The fix, when I finally got around to it, was almost insultingly small. Once every couple of weeks I load a pill box instead of closing the lids. Twelve or thirteen fills a year, five minutes each. Call it an hour, total, for the whole year. One hour of setup to make the resistance disappear for all three hundred and sixty-five mornings. And taking my vitamins went from the thing I avoided to the first easy thing I do all day.
Now hold those two numbers next to each other, because this is the part that should stop you. The annoyance, left alone, costs me hours and hours a year plus the guilt. The permanent fix costs about an hour. I let the expensive one run for a long time to avoid the cheap one. On paper that’s insane. In the moment it was completely reasonable, every single morning. Because every single morning the choice in front of me was “open six lids” versus “stop everything and redesign my mornings,” and open six lids always won.
That’s the compounding, and it’s worth saying plainly: a small annoyance repeated daily becomes a life tax. But there’s a second cost hiding underneath the compounding, and it’s the one this chapter is really about, because it’s the one almost nobody counts.
The full cost of a task you keep putting off is not just the eventual fix. It’s the fix plus everything you pay to carry it while it stays undone.
Think about what “undone” actually does to you. The task itself is finite. Whenever you finally do it, it takes however long it takes, and then it’s over. But the weight of it not being done isn’t finite. It runs the whole time. Every day that thing stays open, it hums in the background as one more item on the list of things you’re supposed to get to. It taxes your attention even when you’re not touching it. You can be doing something completely unrelated, and somewhere underneath, quietly, a little part of you is still holding “I really need to deal with that.” That’s the carrying tax. It’s the rent you pay on an open loop, and it comes due every day whether you make progress or not.
This is why deferring is so close to pure loss. Waiting doesn’t shrink the fix. The pill box takes the same hour whether I build it today or next March. Waiting doesn’t make the task easier or cheaper. All waiting does is keep the meter running on the carrying tax while you postpone the relief. You pay more to carry it than you’d ever pay to finish it, and at the end you still have to finish it.
And it explains something that used to puzzle me. Every so often I’d finally knock out some tiny thing I’d been avoiding for months, something small, and the relief would be enormous. Wildly out of proportion to the task. I’d think, that took nine minutes, why do I feel like I just set down a backpack full of bricks? For a long time I assumed I was just being dramatic. I wasn’t. The relief wasn’t about the nine minutes of work. It was about the months of carrying. Closing that loop didn’t just finish a task. It turned off a hum that had been running the entire time, so quietly I’d stopped hearing it, until it stopped and the silence told me how loud it had been. You weren’t carrying the task. You were carrying the fact that it stayed open. Finish it, and you don’t just cross off a line. You turn off the hum.
Once you see the carrying tax, the way we handle deferral starts to look strange. We will put off for months a project that would take an afternoon. We will tolerate for years a daily annoyance whose permanent fix costs about an hour a year. Read those two sentences again, because they describe the same person, and that person is all of us. We overpay wildly to avoid small one-time costs, and we do it precisely on the things where the math is most lopsided in favor of just fixing it. It’s obvious on paper and invisible in the moment, and the reason it’s invisible is that the bill never arrives as a bill. Nobody hands you an invoice for twelve hours and a year of low-grade dread. It’s collected in installments so tiny you never notice a single one, which is exactly why you never move to stop it.
So here’s the question I want you to carry out of Part One, the one that sits underneath this whole book. When you catch yourself walking around the pothole for the tenth time, the hundredth time, stop and ask it:
How many times will I pay this tax before I fix the road?
That question does something the annoyance alone never does. The annoyance is a feeling, and feelings fade in about four seconds and then you keep moving. The question turns the feeling into arithmetic. It drags the invisible aggregate cost into the one moment where you could actually do something about it. It’s the same move as the rule from Chapter One, aimed now at the compounding: not just is this annoying, but how many more times am I going to let it be annoying before I make it stop.
This is the part that runs against every instinct we have about small things. Our whole reflex is to give small things small attention. It seems reasonable. It seems mature, even, to not sweat the little stuff. But recurring friction is the exact case where that instinct betrays you, because a small thing that repeats is not a small thing. It’s a large thing wearing a small thing’s clothes. So recurring friction deserves the opposite of what we give it. It deserves disproportionate attention. It deserves you stopping, on a Tuesday, over something that seems far too trivial to stop for, precisely because it isn’t trivial once you multiply it by the next hundred times you’ll hit it.
I’ll give you the work version, because this isn’t just a home thing. For a while, there was a particular question I’d get from agents, the same question, over and over, phrased a dozen different ways but always the same underneath. And every time, I’d write it out again from scratch. A few minutes, a real answer, actually helpful. Then the next person would ask, and I’d write it again. Each individual reply felt like the job. Of course I answer the question, that’s what I’m here for. What I couldn’t see, one reply at a time, was that I wasn’t answering a question. I was re-answering an answer I already had, indefinitely, because I’d never once stopped to write it down somewhere they could find it themselves. The fix was an afternoon. The carrying cost had been running for years, a few minutes at a time, plus the small background hum of knowing that email was always coming again. Every repeated question really is a broken system, and the tax on that broken system had been collected from me in installments so small I’d filed them all under “just doing my job.”
I’m not going to fully unpack what to do about the next hundred times here. That’s where the whole back half of this book is headed, and it’s where it ends. But I want to plant it now, because it’s the reframe that makes fixing the road feel worth it. You are not fixing a thing once. When you fix recurring friction, you’re reaching forward and making the next hundred times easier than the last ten. The fix is one payment. The return arrives every single time you’d otherwise have hit that pothole, for years, and it keeps arriving whether you’re paying attention or not. That’s the best deal in your whole day, and we walk past it constantly because it’s disguised as something too small to bother with.
You have heard a bigger version of this logic your whole life, and you probably believe it. Live below your means. Invest a little now so your future self has more later. Do the work today so you get to enjoy the thing tomorrow. It is good advice, and it is also a little exhausting, because the sacrifice is always now and the reward is always off in the distance, with years in between. Friction reduction is that same wisdom shrunk down to the size of a Tuesday. It is delayed gratification, but the small, fast, repeatable kind. Nobody is asking you to suffer for a decade so life is better later. You are just accepting one small inconvenience now so you stop paying the same tiny tax over and over. Fix the drawer once so it stops fighting you every morning. Write the template once so you stop rewriting the same message. Clear the folder once so you stop hunting for the same file. Schedule the appointment now so it stops living in your head. Spend twenty minutes fixing the thing that has already stolen five minutes from you ten separate times.
Once you see it as a trade, it is hard to unsee. Every time you tolerate recurring friction, you are letting the present borrow from the future. You take the easy option now and quietly bill every later version of you who has to hit that same pothole tomorrow, and the day after, and next year. Every time you fix the road, you do the opposite. You make one small deposit now, and it pays out to all of them. So make today a little harder on purpose, just this once, and every future version of this moment gets easier. That is what friction reduction really is. Not a grand sacrifice for a distant payoff, but a small, quiet investment in your own near future, paid back to you a few minutes at a time for years.
And there’s a timing piece, which is really the door into Part Two. Since the fix costs about the same no matter when you do it, and the carrying tax keeps running every day you wait, the math points in one direction. Do it sooner. Not do everything, not do it frantically – just close the loops you’ve already decided you’ll close, sooner rather than later, because the only thing delay buys you is more days of paying rent on the dread. You’re going to feel the relief eventually. The task will get done, the hum will go quiet, and you’ll wonder why you waited. So why not feel that sooner, and spend more of your life on the light side of it?
That’s what I want you to take from Part One. You have loose boards. They’re not a verdict on your character. They’re just roads that were never fixed, quietly collecting a tax you never agreed to pay. You can see them now, which is most of the battle, and you know the question to ask when you hit one. So let’s go fix some roads. We’ll start small, in the ordinary corners of a life, and I promise the first few will feel far better than they have any right to.
We’ve spent the first part of this book learning to see the loose boards and stop blaming ourselves for stepping on them. Now we get practical. This part is about the everyday roads, the ordinary stuff of a life, and we’re going to start with one of the most expensive and least noticed taxes of all: searching for things you already own.
Think about how much of an ordinary day is spent looking for something. You pat your pockets for the keys. You dig through the junk drawer for the one charger that fits. You scroll back through your texts trying to find the address somebody sent you last week. At work you open four folders and a search bar hunting for the version of the document that’s actually the final one. None of these searches takes long by itself. Ten seconds here, two minutes there. But you do them constantly, and they don’t just cost the seconds. They cost the little spike of low-grade stress every time, the break in your train of thought, the moment where you were about to walk out the door on time and now you’re not. Searching is a small cost you pay dozens of times a day, and because each hit is small, you’ve never once considered that you could simply stop paying it.
Here’s the thing I want to convince you of in this chapter, and it’s going to sound backward at first. The goal is not to get organized. I know that’s what everyone says. Get organized, they tell you, as if organization were a personality trait you either have or lack, and if you’d just try harder you’d become one of those people with the labeled bins and the color-coded calendar. I’ve bought the bins. The bins don’t fix it. The goal isn’t perfect organization. The goal is reliable retrieval. Those are not the same thing, and confusing them is why so many organizing projects collapse.
Organization is about how things look when you’re done. Retrieval is about whether you can lay your hands on the thing later, when you actually need it, without thinking. A system works when two things are true: you know where a thing goes when you’re done with it, and you know where to find it when you want it again. That’s the whole test. Not whether it’s pretty. Not whether it would survive an inspection. Whether the thing comes back to you when you reach for it. A slightly messy drawer where the scissors are always in the same corner beats a beautiful drawer where you’re never quite sure. Reliable beats tidy every single time.
And here’s the move that follows from that, the one I’d tape to the wall if I could only keep one line from this chapter: build the shelves before you collect more stuff. Most of us do it the other way around. We accumulate first, in a pile, on the counter, in a folder called “Downloads” that has four thousand items in it, and we tell ourselves we’ll sort it later. Later never comes, because sorting a giant pile is miserable, and every day the pile grows and the sort gets worse. If you build the shelf first, the home for the thing, then every new item has somewhere to land the moment it arrives, and the pile never forms. The shelf is cheap. The pile is expensive. Build the shelf first.
Let me tell you how I learned this the hard way, because I earned this one over about twenty years.
I am, and I’ll just admit it, a digital pack rat. I keep things. And nowhere did that show up worse than my photos. Over the years I’d switched computers, swapped hard drives, backed things up to a new drive and then backed the backup up somewhere else. And every time I did, the whole photo library came along for the ride and quietly duplicated itself. By the time I finally looked at the situation honestly, I had something like a hundred and thirty folders of pictures scattered across drives – thousands upon thousands of images, and a staggering number of them were exact duplicates of each other. Same photos, sometimes with the same filename, sometimes renamed by whatever camera or phone or import tool had touched them last. It was two decades of my life, trips and holidays and birthdays, all of it, and it was completely unusable. If you asked me to find a specific picture from a specific year, I couldn’t do it. The pictures existed, technically, but I couldn’t retrieve them. And a photo you can’t find is almost the same as a photo you never took.
I’d “meant to” deal with it for years. It’s a perfect example of the last chapter’s wall: I knew exactly what needed to happen, and the piece that stopped me was that no human being could actually do it by hand. You cannot eyeball thousands of near-identical files and reliably tell the true duplicates from the ones that just share a name. It wasn’t hard in the way that’s satisfying to push through. It was hard in the way that’s simply impossible at that scale, so it sat.
What finally broke it loose was handing the sorting to a tool that could do the part I couldn’t. I had software go through the whole mess, rename the files into something sensible, and group them by year and by event. Instead of a hundred and thirty random folders, I had a structure that actually mapped to my life. For the duplicates, it did something smarter than I’d have trusted myself to do: it compared the files by their actual byte size to find the ones that were genuinely identical, and rather than deleting them outright, it moved them into a separate review folder. That last part matters, and we’ll come back to it. It didn’t destroy anything. It set the suspected duplicates aside so I could confirm before anything was gone for good.
I’ll be honest that it’s still a work in progress. I’m still going through and adding descriptions, still checking corners of it. It is not finished and it is not perfect. But that was never the point. The point is that for the first time in twenty years, when I want a photo, I know where to look, and it’s there. The retrieval works. The library went from a thing that quietly nagged at me every time I thought about it to a thing I can actually use, and the relief of that was much larger than “sorted photos” has any right to be. I hadn’t been carrying the photos. I’d been carrying the fact that they were lost.
The rest of my digital life told the same story. Gigabytes of duplicate files, old documents copied and recopied across drives, the accumulated sediment of a pack rat who never once threw anything away. When I finally cleaned it up, I used the same approach on purpose: the duplicates didn’t get deleted, they got quarantined, moved into a holding folder where I could verify them before committing. I want to flag that instinct now because it turns into something important later in the book. There’s a third option between keeping something forever and deleting it, and it’s the one that dissolves most of the fear that keeps our stuff stuck in place. For now just notice the shape of it: I didn’t have to choose between hoarding and loss. I got to set things aside and stay in retrieval, not regret.
So that’s the principle and that’s my confession. Let me give you the concrete moves, because this is a practical book and you should be able to close this chapter and go build a shelf today.
Start with the physical world, because it’s the easiest win and the fastest relief. Pick a permanent home for the things you touch every day and lose constantly: keys, wallet, phone, chargers. A hook by the door, a bowl on the counter, a specific drawer. It does not matter where. It matters that it’s the same place every time, and that the rule is absolute: the keys live there, full stop. The first few days you’ll have to consciously put them back. After that your hand does it without you, and you will never search for your keys again. That one takes an afternoon to install and pays you back every morning for the rest of your life.
Next, give yourself one inbox for capture. Not five places where things might be written down, one place where new things land. A single notebook, a single notes app, one spot where the thought, the reminder, the thing-I-can’t-forget goes the instant it appears. The failure mode is scattering: a sticky note here, a text to yourself there, a scrap in your pocket. Scattering guarantees you’ll lose things, because there’s no one place to look. One inbox means capture is frictionless and retrieval is guaranteed.
Then pick a single trusted place for the things you want to keep and refer back to, your notes, your lists, your reference material. For me that’s an outliner, a tool built for nesting and structuring information so I can find it later. There are plenty that do the job well; I happen to use one called Workflowy, but the tool is not the point and you should use whatever you’ll actually open. The point is that there’s one trusted home, so you never have to remember which of four apps you put something in. When there’s one place, “where did I write that down” stops being a question you ever ask.
A couple of smaller shelves worth building. Adopt a naming convention for your files and use it every time, something plain like the date first, then a clear description. Things sort themselves, and you can guess a name before you even search. And set up a home for the paperwork of a life – receipts, statements, warranties, the documents you need exactly once a year and can never find under pressure. One folder, physical or digital, where those go the moment they arrive. Build it before tax season, not during.
None of these is a heroic project. Every one of them is a shelf you build once so the pile never forms. And the payoff is the quietest luxury I know of, which is the relief of never searching for the same thing twice. You find a home for a thing one time, and from then on it simply comes back to you when you reach for it. The tax you’d been paying dozens of times a day just stops getting collected. You stop patting your pockets. You stop opening four folders. You reach, and it’s there.
That’s what one place for everything really buys you. Not a tidier life for its own sake, but a life with a little less friction humming underneath it, a little more of your attention freed up for whatever you actually walked into the room to do.
You have already met my pill box. A couple of chapters back it was my example of the carrying tax, an hour of setup across a year to kill a daily drag that had been quietly costing me far more than that. But that little plastic box did a second thing, and it is the thing this chapter is about. The morning I first loaded it, I didn’t only remove some friction. I made a decision once and then never had to make it again. In one calm moment, with the six bottles open in front of me, I decided what every future morning would look like. After that there was nothing left to decide. I flip open a lid, tip the pills into my hand, and I’m done.
What I’d done, without having a name for it yet, was make a pre-decision. And that word, deciding, is the one I want you to sit with, because a decision you make every single day is one of the most expensive things you can own, and almost nobody counts it.
Here is the thing I most want you to hear in this chapter, before anything else, because the whole idea gets misread without it. A pre-decision does not take your freedom away. It protects it. I know it sounds backwards. Committing in advance feels like putting yourself in a box, like you’re trading away your options and locking the door. But run the honest math on where your options actually go. Your attention is finite. Every morning starts you with a certain amount of it, and every choice you make, no matter how trivial, spends a little. When you burn that budget deciding which vitamins in what order, or where the receipt goes, or what to eat for lunch you eat most days anyway, you have that much less left for the choices that carry real weight. The low-value decisions do not politely wait their turn. They crowd to the front and eat the attention you needed for something that mattered. A pre-decision is how you stop the small stuff from feeding on the big stuff. You are not giving up the choice. You already made it once, on purpose, and now it runs without charging you again.
Most people already accept one version of this and don’t think twice about it: automatic bill pay. Nobody experiences a monthly electric bill as a rich exercise of personal freedom. It is predictable, it recurs, it takes almost no judgment. The only thing that changes month to month is a number you’re going to pay regardless. So we let it run. We decided once that the bill gets paid, and then we got out of the way. Nobody feels imprisoned by autopay. They feel relieved. That relief is the whole thesis of this chapter. The only real question is why we stop there – why we hand off the electric bill and then go right back to hand-deciding a dozen other things that are every bit as predictable.
Let me give you my other favorite example, because it taught me the rule of thumb I now use for all of this. Every Saturday I pay the guy who cuts our lawn, and every week we give at church, and both of those happen in cash. I don’t carry much cash, so for a long time each week included a trip to the ATM. Not a hard trip. Not a long one. But a standing weekly errand whose only job was to feed two payments I already knew, to the dollar, weeks in advance. Completely predictable, and completely un-set-up. It repeated only because I’d never sat down and arranged for it not to. So now I pull a month at once. I load the church envelopes ahead, I fill the little ziploc bags I leave under the doormat for the lawn guy, and then I don’t think about any of it for weeks. The payments still happen. The errand doesn’t.
That is where the rule comes from, and it’s short enough to keep in your head:
Predictable equals batchable.
If you can see a task coming, if it recurs on a schedule and doesn’t ask much of your judgment when it arrives, then you are almost certainly handling it one exhausting slice at a time when you could handle it all at once, in advance, and be done. The cash run wasn’t hard. It was just repeated, because nobody had ever set it up to run. Predictable things are the easiest of all to pre-decide, because the future is already sitting there in plain view, asking you to make the call now instead of fifty more times later.
Once you have the eye for it, candidates turn up everywhere, and none of them are dramatic. That’s the point. A default outfit, so the first decision of your day isn’t standing in front of a closet. One place the receipts go, decided once, so you never again stand holding a slip of paper wondering where it belongs. A fixed first action for the morning, the same small thing every day, so you begin in motion instead of negotiating with yourself about where to begin. A standard answer to the question people keep asking you, written down and reused, so you stop composing a fresh reply to a question you’ve now answered forty times. A default order at the restaurant you go to every week, a standard grocery list you start from instead of building fresh each time, a set process for the work task that comes back around every month. Every one of those is a decision you are currently paying for on the installment plan, over and over, when you could pay it once and own it outright.
Notice what these have in common, and what they do not. They are all decisions that don’t get better for being remade. That is the test. Some choices genuinely deserve fresh attention every time, and you should protect those fiercely, which we’ll come back to near the end of the book. But most of the choices eating your day are not like that. The receipts do not go somewhere more inspired because you deliberated about it this morning. Your Tuesday lunch is not richer for having agonized over it. When a decision produces the same answer nearly every time, remaking it isn’t freedom, it’s just tax, dressed up as choice.
I do want to draw one line carefully, because a pre-decision is easy to confuse with a rule, and they are not the same animal. A rule constrains you: it says you may not, it stands over you, and part of you spends energy resenting it or looking for the exception. A default is different. A default just says here’s what happens unless you decide otherwise. It sets the path you’ll take when you’re not paying attention, which is most of the time, but it leaves the door open. I take the vitamins from the box, unless I don’t. I eat the usual lunch, unless today I want something else. The default is doing the quiet work of removing the friction on every ordinary day, and it steps aside without complaint on the day you actually have a reason to choose differently. A rule takes the choice away. A default hands you back the attention the choice was costing and lets you spend it where you like. That difference is the entire reason a pre-decision frees you instead of fencing you in.
There’s a plain reason this matters more than it looks like it should. Deciding is tiring in a way we don’t credit, and the tiredness is cumulative. It isn’t the big calls that wear you down over a day so much as the steady drip of small ones, each too minor to notice, adding up to a fatigue you feel by evening without being able to say where it came from. I won’t lean on the science of it, because you don’t need a study to recognize the feeling. You already know that some days you get to the important thing with nothing left in the tank, and it wasn’t the important thing that emptied it. It was the hundred little forks in the road you took on the way there. Pre-decisions close off the forks that never deserved your attention in the first place, so you arrive at the choices that matter with something still in reserve.
So here is the move, and it’s the same one every time. Find a decision you are making again and again that keeps landing on the same answer. Make it once, deliberately, while you’re calm and have the pieces in front of you. Then set it up to run, and stop deciding. Load the box. Pull the month of cash. Write the standard answer down. You are not shrinking your life or handing your freedom to a system. You are clearing the small, repeating choices out of the way so the big, meaningful ones have room to breathe. Automate the drag; protect the meaning. The vitamins were never really about the vitamins. They were about whether I wanted to keep spending myself, one lid at a time, on a decision I’d already made. I didn’t. Once I saw that, I couldn’t unsee it, and I don’t think you will either.
A routine sounds like a fancy thing, like something a disciplined person has and you don’t. It isn’t. A routine is just a path you’ve walked enough times that it stopped costing you much. The first time you drive to a new office, it takes all of your attention: the turns, the exits, the parking, the which-door-do-I-use. A month later you get out of the car and realize you don’t remember the drive at all. The road didn’t change. You did. The path got worn smooth, and once a path is smooth, walking it is nearly free.
That’s all a routine is, and it’s worth saying plainly, because we tend to give routines a kind of moral weight they don’t deserve. We talk about them like they’re proof of character, like the people who have good ones are simply better at being alive than the rest of us. They’re not. They just paid the cost of learning the path a few times, up front, so they wouldn’t have to pay the cost of deciding every single day after that. A routine is friction reduction that happens to run on repetition. You do the deciding once. Then the path carries you.
So if a routine is a worn path, the interesting question isn’t “do you have discipline?” It’s “how well is the path built?” And here’s where most of us go wrong, because we build the wrong kind.
There are two kinds of routines, and they look almost identical on the first day. One requires perfect conditions to work. The other survives imperfect ones. The first kind is fragile. The second kind is useful. And the difference between them is the whole game.
A fragile routine goes like this. I’m going to get up at five, meditate for twenty minutes, journal, work out for an hour, make a real breakfast, and read before I touch my phone. It’s beautiful on paper. It works great for four days. Then I sleep badly and miss the alarm, or I wake up sick, or I travel – and the whole chain breaks at link one. Because it was built as a chain, breaking one link breaks all of it. Miss the five o’clock and the meditation’s gone, and once the meditation’s gone the rest feels pointless. By day nine the entire thing is in the ground. Not because I lacked willpower. Because I built something that could only stand in perfect weather, and weather is never perfect.
A useful routine assumes the weather will be bad. It’s built low to the ground and simple, so that a bad day dents it instead of destroying it. And the real test of a useful routine, the thing almost nobody tells you, is not whether you can keep a perfect streak. It’s whether you can restart after you break one. Because you will break it. Everyone breaks it. The streak is going to end no matter who you are, so a routine that depends on the streak never breaking is a routine designed to fail.
Let me say this as plainly and as kindly as I can, because I spent years getting it wrong: missing a day is not the failure. Being unable to restart is. The skill was never the streak. The skill is the restart. If you work out three days, miss five, and come back on the sixth, you did not fail and start over. You have a useful routine, and you just used the only part of it that actually matters. The people who look consistent from the outside are not people who never miss. They’re people who got very good, and very unbothered, at beginning again.
Once you believe that, a whole layer of guilt falls off. The broken streak stops being evidence that you’re not the kind of person who does this. It becomes what it always was, a Tuesday that didn’t go your way. And the question stops being “how do I never miss?” and becomes the far better question: “how do I make restarting cheap?”
The answer to that question is the most useful routine idea I know, and I call it the standard start.
Most of the cost of a hard block of work is not the work. It’s the beginning of it. Starting is where the friction lives, because starting is where you have to decide: what do I do first, where’s the thing I need, am I really doing this right now or checking my phone one more time. Every one of those little decisions is a place the whole thing can stall. So the move is to make the first step of a hard block almost free, and fixed, so that beginning takes no negotiation at all.
You do this by building a standard opening move, the same one every time, so easy it’s beneath your ability to refuse it. Not the whole task. Just the first step, pre-decided and pre-loaded, so that when it’s time to start you don’t have to think. You just do the move you always do, and the move you always do drops you straight into the work.
Two things make the opening move nearly free. The first is preparing the night before, so the version of you that has to start isn’t also the version that has to set up. The second is putting things where they’ll be used, so the environment does the remembering for you. We spend a whole chapter on that next, because your surroundings are quietly training you all day, but the short version is: friction hates a thing that’s already in your hand.
Here’s mine on the personal side. I want to work out in the mornings, and for a long time I didn’t, and I told myself it was about motivation. It wasn’t. It was that the morning had a dozen tiny decisions stacked in front of the actual exercise, and any one of them was enough to sink it. So I moved the decisions to the night before. Clothes and shoes laid out where I’ll literally trip over them. Water bottle filled and by the door. The first thing I’ll do written down so I’m not standing there planning at six in the morning. Now the morning has no decisions in it. My opening move is: put on the clothes that are already sitting there. That’s the whole start. And once the clothes are on, I’ve never once taken them back off and gone to the couch. The clothes weren’t the workout. They were the standard start, and the standard start is the part that used to break.
The work version is the same shape. For years the beginning of my workday was a slow, leaky thing. I’d sit down, open email, get pulled into whatever the loudest message was, and look up at eleven having done nothing I’d actually chosen. So I built a fixed opening move, and I do the same one every morning before I let email exist. I open the one document where I keep the day’s three real priorities, the ones I decided on the day before, and I start the first one for ten minutes before anything else is allowed in. That’s it. It sounds almost too small to matter. But it means I never start my day by negotiating with my day. The negotiation happened yesterday, when I was calm. This morning there’s just the move, and the move carries me past the exact spot where the day used to get away from me.
Notice what both of these have in common. The setup happened at a different time than the start, done by a version of me with room to think. And the start itself asks nothing of me except to do the one small thing that’s already sitting there waiting. That’s the trick. You don’t need more resolve at the hard moment. You need to have removed the decisions from the hard moment in advance, so that beginning costs almost nothing, so that even a bad-weather day still clears the bar.
Which brings me to the warning, because there’s a way to hear all of this and immediately overbuild.
We love a heroic routine. We love the version with the five o’clock wake-up and the color-coded morning and the eleven interlocking habits, because designing it feels like progress and it flatters us to imagine being the person who runs it. I’ve built that routine more than once. It photographs beautifully and it collapses in a week, every time, for the reason we already covered: it’s a chain, and it needs perfect weather, and there’s no such thing.
The routine that actually changes your life is embarrassingly modest by comparison. It’s simple, so there’s almost nothing to break. It’s visible, so the environment reminds you instead of relying on your memory: the clothes on the floor, the one document open on the screen. And it’s easy to restart, so a missed day is a missed day and not the end of the experiment. Simple, visible, easy to restart beats ambitious and brittle every single time, and it isn’t close. The impressive routine is built to be admired. The useful one is built to be missed and picked back up, over and over, for years – because that is what actually happens to routines, and the honest ones plan for it.
So don’t build the cathedral. Pick one hard block that matters to you, and give it a standard start: one opening move, prepared the night before, sitting where you’ll use it, so easy you’d feel silly skipping it. Then let yourself miss. You will, and it’s fine. And the day you come back you’ll find the move still sitting there exactly where you left it, waiting, asking almost nothing of you. That’s not a broken streak. That’s a path built well enough to walk again. And walking it again is the only skill you ever needed.
I used to think I made my choices. I stood at the counter, weighed my options like a reasonable adult, and picked. Then one night I caught myself doing something that made me reconsider the whole arrangement. I’d sat down to read a book I actually wanted to read, and within about ninety seconds my hand had found my phone, unlocked it, and opened an app – all before any part of me that I’d call “me” had decided anything. I didn’t choose that. My hand just went where my hand had been trained to go. The phone was face-up on the arm of the couch, and a face-up phone is a small machine for producing exactly that reach.
That’s the thing I want to hand you in this chapter, because once you see it you can’t stop seeing it. Your environment is always training you. Not sometimes, not when you’re weak, always. Every room you spend time in is quietly teaching your hands and your attention where to go, and it teaches by layout more than by willpower. The phone is visible, so you reach for it. The running shoes are by the door, so lacing up is a little easier. The desk is buried under yesterday’s mess, so starting anything today costs you a cleanup first. The right document is already open on the screen when you sit down, so the next step is just there, waiting, and you take it without a fight. We like to believe behavior comes from intention. A lot more of it comes from what’s in reach.
This is the same road-and-pothole idea from the front of the book, just pointed at the space around you instead of at a task. Friction is the drag between you and the thing you meant to do. And the space you live and work in is full of it, most of it invisible because you built it yourself and stopped noticing. The good news is that if the environment is training you either way, you might as well be the one writing the lesson plan.
There are two levers here, and they’re a matched pair. The first is the obvious one: reduce the friction for the behavior you want. Make the good thing the easy thing, the near thing, the already-set-up thing. The second is the one people forget, and it’s just as powerful: add friction to the behavior you don’t want. Put distance between yourself and it. Add a step. Get it out of sight. Log out. You spend the whole rest of this book learning to remove friction, so it feels strange to deliberately add some. But friction is a tool, not an enemy. A little bit of it, placed on purpose in front of the thing that keeps hijacking you, does more for your behavior than a month of resolutions.
Let me make both levers homely, because they only matter in the specifics.
Reducing friction for the good thing looks like this. If you want to take your vitamins, don’t leave them in the cabinet behind the glasses; the pill box on the counter, next to the coffee maker you already touch every morning, does more than any reminder. If you want to floss, hang the floss on the mirror where your hand lands anyway. If you want to drink water, fill the bottle the night before and set it where you’ll trip over it. If you want to play the guitar more, take it off the wall hook in the closet and put it on a stand in the middle of the living room, where it’s a little in the way. An instrument you have to go get is an instrument you play on special occasions. An instrument that’s already out is an instrument you pick up while you’re waiting for the pasta water to boil. None of this is about wanting it more. It’s about shortening the distance between the wanting and the doing until the distance stops mattering.
Adding friction to the bad thing is the same move run backward. The phone is the obvious battlefield, so start there. Face-down instead of face-up. In a drawer instead of on the desk. In another room instead of in the drawer. Charging overnight in the kitchen instead of on the nightstand, so that reaching for it at midnight means actually getting up. Every one of those is a small wall, and small walls work, because the reach was never a deep decision in the first place; it was a trained reflex riding on how easy it was. Make it a little harder and a lot of it just stops. Log out of the sites that eat your evenings, so that every visit costs you a password instead of a tap. Delete the app off the phone and keep it only on the laptop, so the thing you were doing in line at the store now requires sitting down at a desk. If there’s a snack you keep eating not because you want it but because it’s at eye level in the pantry, move it to the top shelf, or don’t buy it – which is the top shelf of top shelves. You are not fighting your own character here. You’re just regrading the ground so the easy roll is toward the thing you actually want.
There’s a special case of the good lever that I care about more than any single tip, and it’s this: build a workspace you don’t have to rebuild every time you use it. Most of us pay a setup tax we’ve stopped counting. You sit down to work on the thing, and before you can start you have to find the files, reopen the tabs, remember where you left off, clear the coffee cup and the mail and the receipt off the desk, and dig out the one notebook you need. By the time you’re ready to begin, some of the wanting has leaked out, and beginning was always the hard part. The fix is to leave it set up. When you finish for the day, don’t tear the workspace down. Leave the document open to the spot you’ll start on tomorrow. Leave the tools out. Leave a one-line note to yourself about the very next step, so that tomorrow’s you doesn’t have to reconstruct today’s train of thought from a cold start. Starting should cost as close to nothing as you can make it, because starting is where projects go to die.
Here’s the personal version. For years my home office desk was a landing strip. Mail, packages, the thing I kept meaning to return, whatever I set down “for a second.” So every time I wanted to do focused work at home, step one was clearing a runway, and step one is exactly the step that sends you to the couch instead. What finally fixed it wasn’t discipline. It was giving all that other stuff its own home, a tray by the door for mail, a bin for the stuff that used to pile up, so that the desk stopped being the default dumping ground. Now the desk is boring. It has the monitor, the keyboard, and nothing else. And a boring, empty desk turns out to be an invitation, because sitting down at it doesn’t cost a cleanup first. I didn’t get more disciplined. I removed the thing I’d been walking around every single day.
Here’s the work version, and this one runs my business. In my office we quote insurance plans, and a quote used to mean assembling the same scaffolding from scratch every time: pull the templates, find last year’s numbers, hunt down the carrier documents, open the tools in the right order. The work that mattered, the judgment, the actual advice to the client, was maybe the last twenty percent. The rest was setup, paid fresh on every quote, times every quote, times every person in the office doing it. So we built the standard start. Now the workspace for a quote comes preloaded. The templates are already there. The tools open where they should. The next step is staring you in the face when you sit down. We didn’t make anyone work harder or care more. We took the runway-clearing out of the job, and the work that survives is the work that was worth doing. That’s the same “leave it set up” move I made with my desk at home, just scaled up to a team and repeated a few thousand times a year. If it slows you down more than once, fix it, and setup is the thing that slows you down every single time.
I want to be honest about the limit of this, because it would be easy to hear all of it as a trick for manipulating yourself into being productive, and that’s not quite the point. Some of what you arrange this way isn’t about output at all. Leaving the guitar out isn’t productivity. Putting the phone in another room at dinner isn’t a hack, it’s protecting the meaning of the dinner. The two levers serve whatever you point them at. If you want to read more at night, put the book on the nightstand and the phone in the kitchen, and you’ve stacked the deck toward the thing you actually value. Automate the drag, protect the meaning. Sometimes that just means making the meaningful thing the path of least resistance, and burying the cheap thing under one more step.
So here’s what I’d have you do with this. Look at the space where you keep failing to do the thing you meant to do, and stop asking what’s wrong with you. Ask what the room is teaching. What’s in reach that shouldn’t be? What’s hidden that you wish were in front of you? What do you have to rebuild every time before you can even start? Then move three things. Just three. Move the phone, move the shoes, move the snack. Leave the desk clear, leave the document open, leave the note for tomorrow. You are not trying to become a more disciplined person. You are regrading the ground so the good path runs downhill, and then letting gravity do the work you were trying to do with willpower.
You’ve been training yourself this whole time, in every room, without meaning to. Might as well teach yourself something kind.
Somewhere along the way, “get organized” turned into a threat. You picture the weekend. The one where you finally do it, where you empty every closet onto the bed, pull every file out of every drawer, and reduce your whole life to sortable piles before dinner. It’s the makeover-show version of a fixed life, and it has convinced a lot of good people to do nothing at all, because the price of admission looks like two days you don’t have and an energy level you can’t fake. I’ve stood at the mouth of that weekend more times than I can count. I know exactly how it goes. You clear one shelf, you feel great, you get tired around noon. By three o’clock the piles are bigger than the mess you started with and you’ve decided you’ll finish next Saturday. You will not finish next Saturday.
So let me take the whole heroic weekend off the table. You don’t need it. Reducing friction is not a renovation you complete once and stand back to admire. It’s maintenance, the same way brushing your teeth is maintenance. Nobody schedules a heroic dental weekend. You do a small thing daily, and it takes almost no time. It works precisely because it’s small enough to actually happen. The loose boards in your life did not all appear on the same day, and they are not going to get fixed on the same day either. They got installed one at a time, quietly, over years. That’s the good news, because it means they can come out the same way.
Here is the whole practice, and it fits on an index card. Fix one thing a day. One. A junk drawer that fights you every time you open it. A cabinet where the lids and the containers have stopped being on speaking terms. A file folder named “Misc” that has quietly become the place documents go to disappear. One repeated annoyance, one broken little workflow, one loose board. You are not trying to fix your life today. You are trying to fix one thing today, and then get on with your life. The instruction I keep coming back to is this: do not just get through the day. Improve the path by one small notch. Get through the day and leave it slightly better built than you found it. That’s the whole ask.
I want to be honest about why the small size is doing so much of the work here, because it’s easy to hear “just do one small thing” as a cute motivational trick, and it isn’t. It’s the opposite of a trick. Remember what actually stops us. It was never the size of the job. It was the little wall of resistance sitting in front of it, the trip to the store, the unfamiliar step, the gear-change into fix-it mode. A heroic weekend piles all of that resistance into one enormous slab and asks you to clear it in a single leap. Of course you defer it. Deferring it is the sane response to a slab that big. But one small thing a day is a wall you can step over without thinking. You lower the bar until the resistance is smaller than the annoyance, and the moment that’s true, the fix finally happens on its own.
There’s a mindset that makes this easier, and it’s one I lean on constantly, in the little things and the big ones both. Assume the answer is yes. Try the thing before you decide it’s too complicated or too much of a hassle to bother with. Most of the time what you were dreading turns out to be a ten-minute job you’d built up in your head into an afternoon. I can’t tell you how many items I avoided for months on the theory that they’d be miserable, only to sit down, start, and be done before I’d finished being annoyed about having to do it. So you try the thing, and you get a win. Then, because you got one win, the next one feels a little more possible, so you get another. And they stack. That’s not a motivational poster, it’s just how momentum actually behaves. The wins compound the same way the friction did, except now they’re compounding in your favor. Small is not the whole highway. Small is the on-ramp, and the on-ramp is the part people keep skipping, which is exactly why they never get moving.
Now I want to teach you the one distinction that will make your daily fix count for more than it looks like it should. Not all of these small jobs are the same kind of job, and learning to tell them apart is most of the skill. Some tasks just clear an item. Others improve the system that generates the items. Those are two very different acts, even though they can look identical on a to-do list.
Here’s the cleanest way I know to see it. Say the dentist is due. You call, you book the appointment, you cross it off. That’s a task. You cleared one item, and it felt good, and in six months the exact same item comes back and you’ll clear it again, and again after that, for the rest of your teeth-having life. Now say that instead, before you walk out of the office, you schedule the next appointment on your way out the door, or you set a standing reminder that surfaces on its own every six months. That’s not clearing an item. That’s building the thing that clears the item for you, from now on. The first move asks how do I get this done? The second asks how do I make this stop landing on my list? One finishes a task. The other retires a category. Both are worth doing, and on any given day either one is a perfectly good “one thing.” But the second kind is worth more, often far more, because you only pay for it once and it keeps paying you back. So when you’re standing in front of your list picking today’s fix, give the edge to the ones that eliminate a whole recurring category over the ones that just close a single door. Spot the high-leverage ones and let them jump the line.
Let me show you what this looks like when it’s real, because I’ve been living inside this exact practice, and it started with a slightly embarrassing discovery. I’d been keeping to-do lists for years. Several of them, actually, which was the first problem. There was a list in one app and a list in another and notes scattered around and things I was just carrying in my head. At some point I decided to pull all of it into one place and actually look at the whole thing at once, and when I did, the number was more than three hundred. Three hundred open items. Some of them were years old. Things I had truly meant to do, believed I would do, and had simply been carrying, unfinished, quietly humming in the background the entire time.
You can react to a number like that two ways. You can feel buried by it, which was my first instinct, or you can recognize it for what it actually is, which is a to-do list finally telling you the truth. It had been three hundred items the whole time. I just hadn’t been able to see it, because it was scattered across enough places to stay comfortably invisible. So I didn’t book the heroic weekend. I have never once successfully executed the heroic weekend. Instead I started clearing them a few at a time, in the evenings, while watching TV. That’s it. That’s the whole grand strategy. An hour on the couch, half paying attention to a show, knocking out a handful of items that had been sitting there for years. It’s almost aggressively unimpressive, and it’s working, and it’s working precisely because it’s small enough that I actually do it instead of dreading it.
And here’s where the distinction earns its keep. As I go, I don’t just clear from the top. I look for the items that eliminate a whole category rather than close a single task. Anytime I spot one that isn’t really a task but a broken system, a thing that will keep regenerating itself onto the list forever if I only clear this one instance, I move it up. I’d rather spend tonight’s hour building the recurring reminder than scheduling the one appointment, because building the reminder means that appointment stops being my job to remember, permanently. Clearing a task removes one item from the list. Fixing the system removes an item that was going to keep coming back. When you’ve got three hundred of them, the difference between those two moves is the difference between bailing water and fixing the leak, and I would very much like to stop bailing.
I want to leave you gentle about all of this, because the whole point of the daily fix is that it’s kind to you, and I don’t want to accidentally hand it back to you as one more thing to feel behind on. You are not going to fix everything, and you don’t have to. Some days your one thing will be tiny, a drawer, a rename, a two-minute annoyance you finally kill off, and that counts. That counts completely. This is the on-ramp chapter on purpose. Everything harder in this book, the projects that stalled for years, the piles you’re afraid to open, all of it gets easier once you’ve felt a few of these small wins land, because you’ll have proof, in your own hands, that the wall in front of a thing is almost always smaller than it looks from across the room.
So tonight, or tomorrow, pick one. Just one. Try it, and let yourself feel the little click when it’s done. Then, tomorrow, one more. You are not organizing your life this week. You’re just leaving the path a single notch better than you found it, every day, and trusting that a notch a day, stacked up over a year, gets you somewhere no heroic weekend ever could. Don’t just get through the day. Improve the path by one small notch.
Ask almost anyone why they haven’t done the thing they keep saying they want to do, and you’ll get the same three words. I don’t have time. I’ve said it. You’ve said it. It’s the most reasonable-sounding sentence in the language, and it ends every conversation instantly, because who’s going to argue with it? Time is finite. There are only so many hours. Case closed.
Except I’ve started to think it’s usually not true. Or not true in the way we mean it. When I actually sit down and do the arithmetic on where my hours go, the story falls apart pretty fast, and what’s left underneath isn’t a shortage of time at all. It’s something else, something I’d rather not look at, which is exactly why “I don’t have time” is such a comfortable place to stop looking.
Let me back up, because I want to be fair to the feeling. The feeling is real. Most of us really do feel busy, buried, behind. That feeling isn’t a lie. But here’s the thing I’ve come to believe, and it took me a while to say it out loud: the busyness itself is a form of friction. Not the tasks. The sense of being too busy to do anything about the tasks. It’s a drag all its own, a background pressure that talks you out of every fix before you’ve even priced it. And like most friction, it may not reflect reality. Or at least not the reality that’s actually available to you if you looked.
Think about what a single ordinary week is really made of. It isn’t one big block of important work with your dreams stacked neatly behind it. It’s a hundred small obligations, most of them barely worth naming on their own. The groceries. The pharmacy. The dry cleaning you keep driving past. The bills. The email that needs a two-line reply you’ve now been avoiding long enough that it needs a paragraph of apology first. The oil change. The appointment you keep rescheduling. The dishes, again. The lawn guy, the trash cans, the little recurring nothing-tasks that don’t register as work because none of them is big enough to. Each one has its own small friction, its own little step you don’t love. And no single one of them is the reason you never started the book, or the business, or the trip, or whatever it is you’ve been carrying around unstarted for years.
But together they are. That’s the part that took me a long time to see. Not any one obligation, but the collective mountain of them. All the small drags, big and little, piled into one mass that sits between you and the things you actually want to do. You don’t lose your evenings to one villain. You lose them to the crowd. And a crowd is much harder to fight than a villain, because there’s nothing to point at. You can’t defeat “everything.” You just feel it as a general heaviness and call it being busy.
So let’s do the arithmetic, because the arithmetic is where this gets interesting, and a little uncomfortable.
Take the errands. I used to run them the way most people do, one at a time, as they came up, whenever I noticed I was out of something or a deadline got close. A trip for this on Tuesday. A trip for that on Thursday. Swing by the other place on Saturday because I forgot it Thursday. None of those trips felt like much. Twenty minutes here, half an hour there. But a trip is never just the trip. It’s the deciding to go, the stopping what I was doing, the drive, the parking, the store, the drive back, and the several minutes on either end where my brain is spun up on logistics instead of anything I care about. Call it forty-five real minutes for a twenty-minute errand, once you count the whole tail. Do that four or five separate times in a week, spread across the week, each one interrupting a different afternoon – and you’ve spent the better part of an evening’s worth of hours, plus you’ve fragmented five days instead of one. That’s the tax, collected in installments so small each looks free.
Now run it the other way. One trip. A list built during the week so nothing gets forgotten. A single loop that hits the pharmacy, the store, and the place I keep driving past, in one drive, on one afternoon I’ve already decided is the errand afternoon. The stops themselves take exactly as long as they always did. But the deciding happens once. The spinning-up happens once. The other four afternoons stay whole. I didn’t find more hours. I stopped leaking the ones I had.
That’s the whole move, and it scales past errands. The standing weekly obligations are the richest vein of it, because they’re the most predictable, and predictable is the magic word. A few chapters back I talked about the Saturday cash run, pulling a month of cash at once and pre-loading the church envelopes and the lawn guy’s bags instead of hitting the ATM every single week. Same shape here. Anything that shows up on a schedule, that you already know is coming, is a candidate to be batched, defaulted, or set to run without you. The bills that recur can autopay. The appointments you’ll need again can be booked before you walk out of the current one. The groceries you buy every week don’t need to be reconsidered every week. Most of what fills a life is not a series of fresh decisions. It’s the same decisions, made over and over as if they were new, and remaking a decision you’ve already made is one of the purest forms of friction there is.
When I added it all up, and I mean really added it up, the honest number of hours locked inside my routine maintenance was much bigger than I’d have guessed and much bigger than I’d ever admit while standing in the middle of a busy week feeling like I had no time. The hours were there. They were just distributed into pieces too small to see, spent on tasks too dull to count, in a pattern too familiar to question. That is what “I don’t have time” is usually covering for. Not an empty calendar with no room in it, but a full one leaking in a hundred places nobody bothered to plug.
I want to go one layer deeper, though, because I don’t think “just batch your errands” is the real lesson, and I don’t want to leave you there. If it were only about arithmetic, we’d all have fixed this long ago. The math isn’t hard. So why don’t we?
Here’s the most honest answer I’ve found, and it’s the one that finally let me stop feeling like a failure about it. Go back to any of my dumb stories, the running toilet, the dead garage remote. In every one, the detour costs more than the fix. I proved that already. So if it isn’t really about time, what is it about? It’s about where the cost sits. The workaround rides along inside something I’m already doing. I’m already backing the car out, so stepping over the sensor borrows momentum I’ve already spent. It feels free because it’s tucked inside motion that was happening anyway. But the fix doesn’t ride along inside anything. The fix has to be started from a stop. It’s a standalone act, begun cold, that interrupts whatever I was in the middle of. And it turns out humans will almost always choose a cost that comes bundled with something we’re already doing over a cost we have to initiate on our own, even when the bundled cost is objectively larger.
Which means the true sentence isn’t the one we say. We say “I don’t have time to fix it.” The honest version is quieter and a little harder to admit: I don’t want to stop to fix it. Stopping is the price. Not the time, the stopping.
I say that with total sympathy, because I do it constantly, and because saying it that way is what finally made it fixable for me. As long as the reason was “no time,” there was nothing to do about it. Time is scarce, end of story – I’m off the hook and also stuck forever. But once the real reason is “I didn’t want to stop,” that’s something I can actually work with. I can decide, on purpose, to stop. I can put one errand afternoon on the calendar so the stopping is pre-scheduled and doesn’t have to be summoned fresh every time. I can spend one hour designing the batch so I never have to initiate the five separate trips again. The fix still has to be started from a stop. But I only have to start it once, and then it keeps paying me back on every trip I don’t take, every decision I don’t remake, every afternoon that stays whole.
And here’s the part I didn’t expect, the part that turned this from a time-management trick into something I actually care about. What you get back isn’t only the hours. When you clear even a piece of the collective mountain, when you plug even a few of the leaks, the thing that lifts is bigger than the time it freed. It’s the mental air. That low background hum of everything undone, all the small obligations murmuring at once that you can never quite silence because there are too many of them to hold – it gets quieter. There’s suddenly room in your head that used to be occupied by the ambient weight of maintenance. You feel it as calm, or as space, or just as the surprising sense that you’re not behind for once. That room is where the deferred things finally get to live. You don’t need more hours in the day to chase what you’ve been putting off. You need to stop leaking the ones you have, and you need to stop carrying the constant low static of tasks you’ve never designed to run without you.
So the next time you catch yourself saying you don’t have time, I’d gently ask you to do two things. First, actually do the math. I suspect, like me, you’ll find the hours are hiding in the maintenance, distributed into installments too small to notice. And second, ask yourself the more honest question underneath the busy one. Is it really that there’s no time? Or is it that the fix would mean stopping, and stopping is the one thing the busyness is very good at talking you out of?
The mountain doesn’t have to come down all at once. It never does. But every small drag you design away is a little more air to breathe, and a little more of your own life handed back to you, to spend on the things you’d actually choose.
I own two of a small kitchen gadget that chops onions. I don’t know how I ended up with two. One is slightly better than the other, and I could not tell you which one, which is exactly the problem. So every time I go to chop an onion, there’s a tiny hesitation, a half-second of “which one” – and then I grab one at random and get on with it. It is the most trivial thing in the world. It is also, if I’m honest, a little pothole I’ve been swerving around in my own kitchen drawer for about three years.
I’ve read the decluttering books. Most of them tell me the answer is to own less. Get rid of the extra chopper, they’d say, and while you’re at it get rid of half of everything else, because stuff is the enemy and less is peace. And I understand the appeal, I do. But I’ve never quite believed the premise, because the number of things I own has never been what bothered me. What bothers me is the half-second of “which one.” What bothers me is the drawer that fights me a little every time I open it. The count was never the issue. The drag was the issue.
So I want to reframe this whole thing before we go a step further, because Part Three of this book is about keeping, and I don’t want you walking in braced for a lecture about how you have too much. That’s not the conversation. Here’s the conversation.
Decluttering is not about having less stuff. It’s about having less drag.
Everything you own carries a maintenance cost. Not just the big obvious things, the boat you have to winterize or the second home you have to worry about. The little things too, and mostly the little things. Every object you keep is something you have to store, dust around, move when you move, look past to find the thing behind it, and decide about, over and over, for as long as you keep it. And it isn’t only objects. The files on your computer have a maintenance cost: they clutter the search results, they make you scroll. The subscriptions on your credit card have a maintenance cost: a little charge, and a little “should I still be paying for this” every time you see the line. The half-finished projects on the shelf have a maintenance cost, and it’s steeper than you think, because an unfinished thing doesn’t just sit there. It hums. It’s one more open loop, one more “I really should,” one more small withdrawal from your attention every time you walk past it.
That’s the thing nobody puts on the price tag. You paid for the object once. You pay for the maintenance forever. And the maintenance isn’t measured in dollars – it’s measured in attention, which is the one budget you can’t refill.
Now here’s the part that makes this a friction book and not a tidying book. The point was never to get the maintenance cost down to zero. Some things are worth what they cost you. My grandfather’s watch costs me a drawer it sits in and a little care when I move, and it is worth every bit of that, because it does something for me that has nothing to do with efficiency. That’s meaning, and we don’t automate meaning, we protect it. But a great many of the things I keep are not my grandfather’s watch. A great many of them are the second onion chopper. They cost me attention every day and they give me nothing back. And I’ve kept them anyway, out of habit, or inertia, or a vague sense that getting rid of them would be more trouble than keeping them.
So the whole exercise comes down to one honest question, asked object by object, file by file, subscription by subscription.
Does this earn its maintenance cost?
Notice that this is a different question than the famous one. The famous one asks whether a thing sparks joy, and I think that’s a lovely question for a certain kind of decision and a useless one for most of mine. A phone charger does not spark joy. Neither does the folder of tax documents, or the good stepladder, or the box of spare cables I will absolutely need the week after I throw it out. Joy is the wrong meter for most of what fills a life. The right meter is quieter: is this thing costing me more attention than it’s worth? Is it earning its keep, or is it just charging me rent and giving me nothing? That question works on the watch and the onion chopper both, and it doesn’t require me to feel anything in particular about a phone charger. It just requires me to be honest about the drag.
Ask it, though, and you run straight into a wall I hit every single time. Because once I’ve decided a thing isn’t quite earning its keep, the standard advice hands me exactly two options: keep it, or throw it away. And that binary is too harsh, so I freeze. Keeping it feels wrong, because I just admitted it’s costing me more than it gives. But throwing it away feels wrong too, because what if I need it, what if it matters, what if the version of me a year from now is furious at the version of me holding the trash bag today. And so, caught between two options that both feel bad, I do the third thing, which is nothing. I put it back. The friction survives, in limbo, because the decision was framed as a fight I didn’t want to have.
I did this for years before I noticed I was doing it, and once I noticed, the fix was almost embarrassingly simple. The problem was never the stuff. The problem was that I only had two doors, and I needed a third.
Here’s the third door. Between “delete” and “keep it active,” there’s a middle path, and I’ve come to call it retiring. Retiring a thing means you don’t throw it away and you don’t leave it charging rent in the middle of your life either. You move it out of the active workspace. You archive it, you label it, you zip up the folder, you put the box on the high shelf instead of the counter, and if it needs a note so future you knows what it is and why it’s there, you write the note. Two sentences. Then you let it go quiet.
The old software project I couldn’t quite bring myself to delete: I didn’t delete it. I zipped it, named the file so I’d know exactly what it was, dropped it in an “archive” folder, and got it out of my working directory where it had been cluttering every search for a year. The subscription I wasn’t using but felt weird about canceling outright: I paused it, or downgraded it, and put a reminder on the calendar to revisit. The pile of old versions of a document, seven of them, each named some frightened variation of “final_v3_ACTUAL_final”: I kept the real one where I could reach it and zipped the rest into a folder called “old versions” that I never have to look at again but is right there if the day ever comes that I need it. Nothing was destroyed. But nothing is charging rent in the present anymore either.
That’s the whole trick of retiring, and it’s why it works when the harsh binary doesn’t. It separates two things we usually tangle together: preserving the thing, and paying the ongoing cost of the thing. You can have the first without the second. You can keep it and still stop carrying it. The onion chopper, by the way, did not get retired. It got given away, because it turns out that once I’d named the actual cost – the half-second of “which one” every day – the decision made itself. But most of what I go through doesn’t end that cleanly, and for all of that, retiring is the release valve. It takes a decision that felt like a loss and turns it into a filing job. Filing jobs I can do.
There’s a line I keep coming back to in this book, and it belongs here more than almost anywhere: the past should not charge rent forever. Retiring is how you stop paying the rent without having to burn the building down. You’re not pretending the thing never mattered. You’re just declining to let it bill you, every day, for space in a life that’s happening now.
And here I have to be careful, because I can feel the easy version of this chapter trying to write itself, the version where “retire it, don’t decide” becomes a permission slip to never decide anything, to just shove every hard call up onto the high shelf and call it handled. That’s not what I’m offering, and if you’re the kind of person who keeps things, and I very much am, you already feel the danger in it. Because there’s a category of stuff that doesn’t fit any of this neatly. The stuff you’re keeping not because it’s useful and not because it’s junk, but because someday. The box you’ve moved three times without opening. The thing that isn’t earning its keep by any honest accounting, and that you still cannot let go of, because letting go would mean admitting that someday is never coming.
I know that box. I have more than one. And I’ve come to believe the “someday” pile is the truest, hardest, most human case in this whole book, because it’s not really about drag at all. It’s about a promise you made to yourself, and whether you’re ever going to keep it.
That’s the next chapter. For now, I’ll only say this: keeping a thing for someday was never as irrational as the tidying books make it sound. Not if the intention behind it was real. So before you go throwing out the box, let’s give it the honest hearing it deserves.
Set the drawer straight first, though. Start with the second onion chopper. The small, clear, unhaunted stuff is where you build the muscle, and you’re going to want the muscle for what comes next.
I am a keeper. I should just say that plainly, up front, because everything in this chapter comes out of it. My closet is too full. There is a storage space with my grandparents’ things in it, boxes I have never fully gone through, and next to those, my own school papers going back to elementary school. Report cards. Spelling tests. A construction-paper thing I made for some holiday I no longer remember. And that is only the physical side. On my computers and drives there are gigabytes of files I have carried from machine to machine for twenty years, the way you carry a box from one apartment to the next without ever opening it.
I want to be careful about how I describe this, because it is easy to turn it into a joke, and it isn’t quite a joke. This is not a hoarder situation. It is not piles of newspaper and a path worn between them. Nothing is rotting. It is closer to the opposite of chaos: it is held. Labeled, in some cases. Boxed up with a kind of care. I kept it all on purpose, and if you had asked me at any point why, I would have had an answer ready – and the answer was always the same one.
Someday.
Someday I’ll scan those photos. Someday I’ll go through Grandpa’s papers and figure out what’s worth keeping. Someday I’ll turn those old files into something. I wasn’t keeping it to hoard it. I was keeping it because I believed, honestly believed, that it would have a use one day. That there was a version of me, further down the road, who would sit down with all of it and finally do the thing I’d been saving it for. The keeping wasn’t the point. The keeping was storage. I was holding the raw material for a project I fully intended to get to.
And here is the quiet problem with someday. It never puts a date on the calendar. It is the most patient word in the language. It asks nothing of you today, which is exactly why today, and every today after it, you do nothing – and the box moves to the next shelf, the next house, the next unit.
I have literally paid for that. For years I paid a storage company to hold things I was not using, so that I could preserve the option of using them later. I moved boxes from one unit to another when I switched providers, lifting them, loading them, driving them across town, and setting them down again – without opening a single one. If you had filmed it and shown it to me with no context, I would have thought I was watching someone protect something precious. And in a way I was. I just never got to the part where the protecting paid off.
The standard advice about all of this is well known, and you have heard it. Let it go. If you haven’t used it in a year, you never will. Minimalism as a kind of moral cleanse: the clutter is weight, the weight is the past, and freedom is the empty shelf. I have read that advice, and some of it is true, and I have even said versions of it in this book. The past should not charge rent forever. I believe that.
But I want to add something to it, because the pure version of that advice has always felt a little cruel to me, and I think it is missing something true about why we keep things in the first place. It treats every kept box as a mistake. It assumes the keeping was irrational, a failure of nerve, and that the healthy move is simply to admit the sunk cost and dump it. And I don’t think that’s right. Keeping is not irrational if the intention behind it was real. My grandparents’ things are not clutter. My own grade-school handwriting on a spelling test is not clutter. Those old files were not clutter. They were promises. The problem was never that I made the promise. The problem was that I never kept it.
So here is the reframe, and it is the whole chapter. The kept thing is not the problem. The limbo is the problem. A box you are saving for a real purpose is a fine thing to have. A box you will move from unit to unit for the rest of your life, and then hand off to someone else to deal with after you’re gone, is not saved. It’s abandoned in place. The difference between those two boxes is not what’s inside them. It’s whether someday ever actually arrives.
Let me tell you what it felt like when it did.
Take those photos. Earlier in the book I walked through the mess itself, the hundred and thirty folders, the thousands of near-duplicates, the whole library scattered across old drives and completely unsearchable, and how a tool finally sorted it when I never could. What I didn’t tell you there was the part that actually mattered to me. Sorting those photos had been the definition of someday. I’d meant to do it for years, and on my own it wasn’t just hard, it was impossible, the kind of task whose hours I was never going to find. It was one of the boxes I’d been moving from machine to machine for the better part of two decades. And then it got done.
And I want to tell you the feeling, because the feeling is the reason this chapter exists and the reason this whole book exists. It was not the tidy satisfaction of a cleared task. It was bigger than that, and it was strange, and it took me a while to name it. What I felt was that the keeping had finally been worth it. All those years of carrying it, all the copying and moving and not-throwing-away, all of it retroactively made sense. I hadn’t been a pack rat. I had been in storage for this exact moment. Someday was finally here, and its arrival reached backward and paid for every year I’d spent holding the box.
That is the thing minimalism can’t see. When you actually do something with a kept thing, you don’t just gain the thing. You redeem all the time you spent keeping it. The years of moving boxes stop being wasted years and become what they always claimed to be: storage for a purpose that finally came true.
But I promised to be honest in this book, and I’m not going to hand you a permission slip to keep everything forever. Because I know what “someday” does when you leave it unsupervised. It rationalizes. “I might use it” can justify holding onto literally anything, and if that’s where this chapter stopped, I’d just be a keeper telling other keepers that keeping is fine. It isn’t always fine. So here is the honest resolution, and I’ve come to think it’s the kindest one too.
A kept thing has exactly two honorable exits. You convert it, or you release it. You turn it into the asset, the keepsake, the story, the finished project you were always saving it for. Or you let it go, cleanly, without guilt. Both of those are honorable. Both of those are done. The only thing that is not honorable, the only actual waste, is the third state – the one almost all of us actually live in: the limbo of carrying it forever, doing neither, paying to store a decision you refuse to make.
For most of my life, the reason I stayed in limbo was simple. Someday wasn’t really achievable. Sorting a hundred and thirty photo folders by hand was not going to happen, and some part of me knew it, so “someday” was safe. It cost me nothing to promise, because I was never going to be called on it. The promise and the box just sat there together, and I got to feel like I was going to get to it without ever having to.
What changed, and this is the honest role of the tools in this story, is that finishing became possible. When the thing you’ve been deferring goes from “realistically never” to “actually this afternoon,” someday collapses. And when someday collapses, the box has nowhere left to hide. It splits into one of two answers, and both of them set you free. Either you finally do the thing, and the keeping is redeemed. Or you sit down, look at it honestly, and realize that even now, with the finishing right there in front of you, you still won’t. And that is not a failure. That is information you never had before. It means you can let it go, this time without the guilt, because the guilt was always “I could still use this” – and now you know that you won’t. The excuse is gone, and so is the weight.
I’ve started thinking about it in terms I understand from my own line of work. A kept box is a house you’re still paying on. You have three options. You can pay off the mortgage by turning the house into something that produces value, an asset that finally earns its keep. You can sell the house and walk away with the equity. Or you can do what most of us do, which is pay rent, month after month, on a place you don’t live in and never use. Pay off the mortgage or sell the house. Either one. Just stop paying rent on limbo.
There is one more layer to this, and it’s the one that stays with me the longest, so I’ll only touch it lightly here and come back to it later in the book. Underneath all my keeping, underneath the grandparents’ boxes and the school papers and the drives full of files, is a wish I didn’t have words for until recently. I think what I really wanted, the whole time, was for the stuff to outlast me. For someone, someday, to be able to know who I was, in my own voice, with my own stories, after I’m gone. That’s what the school papers are, if I’m honest. That’s what the photos are. Not clutter. Not even keepsakes, exactly. They’re an attempt, a clumsy one, to leave something of myself behind that a future generation could actually reach out and touch.
And that turns out to be the same instinct as everything else in this chapter, just at the highest possible stakes. A life’s worth of stories and photos and voice, kept and carried and never assembled, is the biggest someday box there is. It has the same two honorable exits as all the others. You can convert it into something living, something a person years from now could sit with and ask questions of one day, or you can let it fade. What you cannot do, not honestly, is keep promising yourself you’ll get to it while the years keep moving the box from shelf to shelf.
I kept all of it because I believed it mattered. It turns out I was right. It did matter. I just had the timing wrong, because I thought someday was a place further down the road, when the whole time it was a door I could open now. Reducing the friction didn’t just clear a pile off my drive. It let me keep a promise I’d made to myself a very long time ago, back when I first decided this was worth saving.
Someday is finally here. It was always going to be. The only question was whether I’d show up for it while I still could.
Watch someone good at their job build something from scratch, and then watch them do it again a month later, and you’ll notice something strange. They start over. Not entirely, but more than they need to. They open a blank document, or a blank email, or a blank spreadsheet, and they begin building the thing they already built from memory, a little worse than last time. Last time’s version is buried in a folder somewhere, and it’s faster to just retype it than to go find it.
I’ve done this more times than I’d like to count. A client asks a question I’ve answered before – in almost exactly these words, for another client, three weeks ago – and I sit down and compose a fresh answer anyway. A proposal needs a paragraph explaining how a certain kind of plan works, and I write that paragraph like I’ve never explained it in my life, when in fact I’ve explained it a hundred times, in emails and meetings and phone calls. Every one of those explanations is gone the second I hit send. The work felt custom every time. It wasn’t. It was the same work wearing a slightly different hat, and I kept paying full price for it.
Before you decide this is a work problem, notice that you do the same thing at home. You write the note for the house sitter from scratch every trip. You rebuild the same mental packing list every time, and forget the same item every time. You re-explain the same directions to every visitor who gets lost on the same turn. It is the identical move: recreating from memory something you already worked out once. The reason this part of the book is about work is not that work is the only place it happens. It is that work is where it gets expensive fastest, because there the same recreation repeats across every client, every week, and often across every person in the building at the same time. Same friction, bigger multiplier. Everything in these chapters is the everyday principle you already know, scaled up to where the numbers start to hurt.
This is one of the most expensive kinds of friction there is, and it’s nearly invisible, because it doesn’t feel like friction. It feels like doing your job. Nobody sits at their desk thinking “I am recreating work I have already done.” They think “I am writing a proposal,” or “I am answering a client,” and the fact that they built something nearly identical last time simply doesn’t come up, because last time is out of sight. So the drag hides inside the ordinary. You don’t notice you’re repeating yourself, because each repetition arrives dressed as a brand new task.
Here’s the thing I had to see before I could fix any of it. A huge amount of what we call custom professional work is repeated work in disguise. Not all of it. Some of what I do genuinely is one of a kind, shaped to a particular client’s particular situation, and no template on earth would help. But that’s the smaller slice. When I actually looked at the work I do over and over, I found that most of it, call it eighty percent, was the same underneath. The same structure, the same explanations, the same steps in the same order. Only the last slice, the remaining twenty or so, was truly custom, truly specific to the person in front of me. And I had been treating the whole hundred percent as if it were custom, rebuilding the eighty every single time to get to the twenty that actually needed me.
That’s the reframe. The move is not to make everything generic. If you try to turn every job into a fill in the blank form, you’ll flatten the real judgment right out of your work, and clients feel that, and it’s bad work. The move is subtler and kinder to your own skill: find the reusable core, and separate it from the genuinely custom part. Build the core once, carefully, so it’s good. Then reuse it, so you never build it again. And spend the energy you save on the twenty percent that’s actually the point, the part where your judgment earns its keep.
Do it once carefully, then reuse it intelligently.
Let me tell you where this really landed for me, because it turned into something bigger than I expected. Years ago, I built a spreadsheet I named Stella.
The job Stella did was quoting. In my world, when a small business wants to offer health insurance to its employees, somebody has to take the details of that group, the ages, the sizes, who’s covering a family and who’s just covering themselves, and turn all of that into actual prices across a whole menu of plans. It’s math, and it’s fussy math with a lot of moving pieces. The usual way to do it was to go online, to the carriers’ systems, and grind through it plan by plan. I had done that quoting by hand more times than I could count, and every time it was the same shape of work with different numbers poured into it. Which, if you’ve been reading along, is exactly the sound a piece of repeated work makes when it’s asking to be turned into a tool.
So I built the tool. I put the rates right into the spreadsheet, so I didn’t have to go online at all, and I built in all the logic I’d been carrying around in my head – the way the ages map to prices, the way you compose a group rate, the way you lay plans side by side so a business owner can actually compare them. That last part matters more than it sounds. A lot of what I’d learned over the years wasn’t the arithmetic itself, it was judgment: which comparisons are useful, how to present them so they clarify instead of confuse, what a decent quote is supposed to look like when it lands on someone’s desk. All of that hard won judgment, the stuff that lived only in my experience, I poured into Stella, once, carefully.
And then something happened that I didn’t plan. Stella got good enough that other agents wanted it. It stopped being my personal shortcut and became its own small product, with agents around the state using it to quote their own groups. A spreadsheet I’d built to save myself from redoing the same math turned into a thing that saved a lot of people from redoing it. That’s the whole principle standing up and walking around. I didn’t do anything heroic. I just did the quoting work once, on purpose, in a form I could keep, instead of doing it from scratch every time and throwing the effort away when I was done.
I want to be careful here, because Stella has a longer story, and most of it belongs to later chapters. It didn’t stay a spreadsheet forever, and what happened when I finally tried to turn it into something more is a story worth its own space. For now, the part that matters is the plain part: I took a job I was doing over and over, found the core that never changed, and captured it into something reusable, so the next hundred quotes were built on top of the last one instead of starting from zero.
Now, most of us aren’t going to build a Stella, and we don’t need to. The reusable core hides in much humbler places, and once you start looking, you find it everywhere in your work. Think about the emails you write. If you handle anything more than once, there’s a version of it you’ve typed before, the welcome note, the here’s what happens next, the gentle nudge when someone hasn’t gotten back to you. Every one of those can be written once, well, and kept, so that next time you’re starting from something good instead of a blank screen. Think about the language in your proposals, the paragraphs that explain how a thing works, which are the same paragraphs no matter who’s reading them. Think about the questions clients ask you again and again, the ones you could recite in your sleep, and how each one you answer thoughtfully once could become an answer you never have to write cold again. There are checklists hiding in the sequences you run from memory and get slightly wrong when you’re tired. There’s a renewal workflow you rebuild each year that could simply exist, waiting, the same steps in the same order. There are intake forms, and the standard explanations you give, and the structure you use to compare options, which is the same structure every time even when the options change. All of it is core. All of it is buildable once and reusable forever, and almost none of it is.
And this isn’t an insurance thing, or a business thing. It’s a human thing, and I think everyone reading this has felt it. It’s the email you rewrite from scratch that you basically already wrote last month. It’s the document you rebuild because you can’t find, or can’t quite trust, the last one. It’s the same directions you give a new person every time someone new arrives, the same recipe you look up as if you’ve never made it, the same little report you assemble by hand each week from the same sources in the same way. None of it feels like waste while you’re doing it. It just feels like the task. But add it up across a year, across a career, and you’ve spent an enormous amount of your one finite supply of attention rebuilding things you already built and then quietly discarded.
The reason we don’t fix this is the same reason we don’t fix any friction: no single instance is bad enough to bother with. Writing one more version of an email you’ve sent before takes two minutes, and stopping to save a reusable version feels like more trouble than it’s worth in that moment. But you’re not doing it once. You’re doing it a hundred times, and the arithmetic only shows up if you’re willing to look at the hundred instead of the one. This is where the rule earns its place. If something slows you down more than once, fix it. The second time you write an answer you’ve written before, that’s a system asking to be built, not a coincidence.
So the practical move is small, and you can start it this week. The next time you finish a piece of work that felt at all familiar, before you close it and move on, ask one question: will I need something like this again? If the answer is yes, don’t throw it away. Save it somewhere you’ll actually find it, and save it in a form you can reuse, with the custom parts marked so you know what to swap. That’s it. You’re not building a product. You’re just refusing, once, to discard something you’ll only have to rebuild. Do that a handful of times and you’ll notice your work starting to compound instead of reset, each job standing on the shoulders of the last one instead of starting over on the ground.
That’s really the whole shift. Stop treating every task as a first draft of something you’ve never done. Most of your work has a spine that doesn’t change, and every time you rebuild that spine from memory you’re paying full price for something you already own. Build the core once, and build it well, so it’s worth keeping. Then let it carry you, and pour your real attention into the small custom slice that’s the actual reason someone came to you. You’ll do better work on the part that matters, and you’ll stop bleeding hours on the part that never did. Do it once carefully, then reuse it intelligently, and the next hundred times get easier than the last ten. That’s not a shortcut. That’s just refusing to keep paying twice.
Somewhere in my business there is a question I have answered a few hundred times. It’s a good question. It comes from clients, from the agents who use our tools, from the employers whose benefits we manage, and every so often from a student in one of my continuing-education classes. Each person who asks it is asking it for the first time. That’s the part that took me years to see. To me it feels like the same question echoing back over and over, so it starts to feel like a nuisance. To them it’s a brand new problem they don’t know how to solve, and they’ve done the reasonable thing, which is to ask the person most likely to know.
For a long time I was proud of being that person. If you needed to know how a composite rate worked, or whether a certain plan counted as minimum essential coverage, or what happened to a dependent when they aged off, you asked me, and I’d tell you. I was helpful. I was fast. I was, without realizing it, building a machine with exactly one moving part, and that part was me.
Here is the sentence that finally reframed the whole thing for me, and it’s the one I want you to carry out of this chapter.
Every repeated question is a broken system.
Not a broken person. The people asking are doing everything right. They have a real need, they can’t find the answer on their own, so they go find someone who has it. That’s smart. The break isn’t in them. The break is in a system that has quietly decided the only place a certain piece of knowledge is allowed to live is inside one human head. When the same question keeps arriving, it isn’t telling you that people are lazy or that they didn’t read the email. It’s telling you that the answer is too hard to find, too hard to understand, or too hard to use. Those are the three ways an answer fails, and a repeated question is the signal that one of them is failing right now.
That reframe matters because of what we usually do instead. Usually we treat the tenth time we’re asked something exactly like the first time. We sigh, maybe, and then we answer it, because answering is faster in the moment than fixing. And it is faster, that one time. It’s the same small tax as the pothole: each individual answer is cheap, two minutes, no big deal, and so no single instance is ever bad enough to make you stop and build something better. The cost only shows up in the aggregate, and the aggregate is invisible while you’re standing there typing the reply. Two minutes at a time, for years, and you never see the bill.
There’s a cost hiding in “just ask me” that’s worse than the minutes, though, and it took me longer to admit. When the answer lives only in your head, you become the bottleneck. Picture one clogged merge point on a busy road, every lane funneling down to a single spot: that’s you, and everything behind you slows to a crawl. Nothing moves until you’re available. Your team waits on you, your clients wait on you, and the work backs up behind the one door everyone has to walk through. Worse than slow, it’s fragile. If I’m on vacation, or out sick, or just heads-down on something that actually needs me, that question doesn’t get answered well by anyone else – the answer was never anywhere they could reach it. I had made myself important, but I had done it by making everything depend on me, and those are not the same thing. A system that depends on one person doesn’t scale, and it doesn’t rest. It just waits for that person, and that person gets tired.
So what do you do instead. You capture the answer once, and you put it somewhere the next person can find it without you. That’s the whole move, and it goes by a lot of names depending on where you are. At work it’s a knowledge base, an internal FAQ, a client portal, a searchable library of the things people keep needing to know. The specific tool matters less than the principle underneath all of them, which is that the answer stops being a performance you have to give live and becomes a thing that exists on its own, waiting to be found. You do the work of answering well one time, and then that answer keeps working while you sleep.
Let me tell you about the version of this I actually built, because it’s the clearest example I have. There’s a whole category of questions in my world that are technically simple but deeply confusing to a normal person: what a deductible really is, how a special enrollment period works, whether a certain kind of coverage counts for a certain requirement. People ask these constantly, and they ask them anxiously, because there’s usually money or a deadline attached. So I built a free site called HealthInsuranceFAQs, and the whole design of it is aimed at those three ways an answer fails.
The find problem, I solved by making it a question-and-answer site, organized around the actual questions people ask, in the words they’d use, so you can search the thing you’re worried about and land on it. The understand problem, I solved by giving each question a short, plain answer first – a few sentences a real human can read in the parking lot before a meeting, with no jargon standing guard in front of the meaning. And the use problem, which is the one most FAQs ignore, I solved with what I think of as deep links. Under the plain answer, I link straight to the exact passage in the source document the answer comes from, not the hundred-page PDF and good luck, but the specific paragraph. Because the short answer is what you need most of the time, and the source is what you need when the stakes are high and somebody’s going to want to see it in writing. One gives you speed, the other gives you certainty, and the deep link is what keeps the short answer honest.
I’ll say a word about how a site like that gets built now, without turning this into a chapter about tools, because the tool isn’t the point and it changes every year anyway. The useful part is not that some system can generate an answer. The useful part is retrievability: that a question, asked in messy human language, can reliably reach the right answer and the right source. Whether that’s a search box, a set of tags, or something smarter sitting on top of your own documents, the job is the same one it has always been. Make the knowledge findable, understandable, and usable. Knowledge that can’t be found behaves almost exactly like knowledge that doesn’t exist, and for years a lot of what I knew was technically written down somewhere and functionally lost.
Now, I want to pull this out of the office, because the pattern isn’t about business at all. It shows up hardest in families, and it wears a disguise there that keeps us from seeing it. Think of the household where one person knows how everything works. Where the wifi password is, when the mortgage draws, which pharmacy has the prescriptions, how the sprinkler timer is set, what the alarm code is, who the accountant is and what the login is to see the account. Everyone else in that house asks that one person, every time, and that one person answers, every time, and often feels good about it, because being the one who knows feels like being needed. I’ve been that person. It feels like love, and sometimes it is. But a family where all the important knowledge lives in one head is not a household with a hero in it. It’s a broken system with a single point of failure, and the failure is not hypothetical. It’s the day that person is in the hospital, or traveling, or simply gone – and everyone else is standing in the kitchen realizing they don’t know how their own life runs. The kindest thing you can do for the people you love is not to be the only one who knows. It’s to write it down where they can find it.
That reframe is the gift, honestly, because it takes the sting out of the fix. It’s easy to feel like building the FAQ, the shared document, the family binder is one more chore on a list that’s already too long. But you’re not adding a chore. You’re paying off a debt you’ve been servicing in installments for years. Every time you answer that question live, you pay a little. When you capture it once and put it somewhere findable, you stop paying, and so does everyone downstream of you. The math is the same lopsided math as the vitamins and the garage remote: one visible lump of effort now, against a hundred invisible little payments stretching out ahead of you. The lump is almost always the better deal. We just don’t see it, because the installments never feel big enough to add up, right up until you notice you’ve been the bottleneck for a decade.
Here’s the test, and it’s a comfortable one to run because you don’t have to fix anything today. Just start listening for the repeats. The next time you answer a question, notice whether it’s the first time you’ve ever answered it or the fortieth. The first time is a conversation. The fortieth is a system asking to be fixed, and it has been asking for a while. You don’t have to build a portal. You can write one clear email and save it. You can start a shared note. You can put the wifi password on the fridge. The scale of the fix should match the scale of the repeat, and most of the time it’s smaller than you fear.
Because the goal was never to stop being helpful. I still love answering the hard, strange, truly new question, the one that needs a person, the one where somebody’s real situation doesn’t fit the general answer. That’s the good part of the work, and it’s exactly the part I never have time for when I’m buried under the fortieth round of a question I answered clearly the first time. Capturing the repeatable answer isn’t a way of caring less about people. It’s how I get my attention back for the moments that actually need me. Answer it once, put it where they can find it, and let the answer do the repeating so you don’t have to. That’s not a smaller version of being helpful. It’s a bigger one.
Every family has a holiday that runs on someone’s memory. In mine, for years, that someone was doing the whole thing from scratch each time. What food, how much, who’s bringing what, which relative can’t have gluten, what time the turkey has to go in so it’s ready when people actually show up. All of it lived in one person’s head, reconstructed every November like it had never happened before. And every year the same two things got forgotten, because a head is a bad place to store a checklist that only runs once a year.
Then one year somebody wrote it down. Not fancy. A list on the fridge: the menu, the quantities, the oven timeline, the “call Aunt Susan about the pie” reminder. And the next year, the holiday got easier, not because anyone worked harder, but because the thinking had already been done. The list wasn’t a shortcut in the cheap sense. It was last year’s judgment, the good decisions and the hard-won corrections, saved so nobody had to earn them again.
That’s a template. And once you see it that way, you start to notice how much of your life you’re rebuilding from scratch that you already figured out once.
Here is the thing we get wrong about templates. We think of them as a convenience, a way to skip typing. And they are that. But the typing was never the expensive part. The expensive part is the deciding. When you sit down to write a proposal, or an explanation, or a difficult email, most of the effort isn’t in the words. It’s in the choices underneath the words. What do I lead with. What do they actually need to know. What question are they going to ask next. What did I forget last time that made me look sloppy. That’s the work. That’s the part that makes your head hurt.
A blank page makes you do all of that again, every single time, from nothing. And a blank page is intimidating precisely because it hands you the whole job at once, the structure and the reasoning and the wording, with no foothold anywhere. So you stall. You reread the last one you sent. You copy it, you hack it apart, you hope you didn’t leave someone else’s name in it. We’ve all sent the email that still says “Dear Robert” to somebody named Karen.
A good template removes the blank page. But that’s only half of what it does, and it’s the smaller half. The bigger thing is this: a template raises the floor. When your best thinking is written down, every version you produce afterward starts from your best, not from whatever you can scrape together on a tired Tuesday afternoon. Without a template, your quality is a function of your energy that day. With one, your worst day still ships something close to your best. That is what I mean when I say the line I want you to take out of this chapter:
A good template is not just a shortcut. It is stored judgment.
It’s the best version of how you explain a thing, how you ask for a thing, how you compare two options, how you decide. Captured once, so it doesn’t evaporate the moment you close the document.
Now I have to be careful here, because this idea has a bad twin, and the bad twin is everywhere. A template can go wrong in exactly one way, and it’s worth naming so you can avoid it: it can get so rigid that it does your thinking for you, which sounds great until you realize that some of the thinking still needed doing.
You’ve received the robotic version. The letter that clearly poured your name into a blank and changed nothing else. The proposal that answers questions you didn’t ask and ignores the one thing you actually cared about. It’s worse than a from-scratch effort, because it signals that nobody was really home. The template didn’t carry the sender’s judgment. It replaced it.
The fix is to build templates with slots for judgment, on purpose. A good template guides; it does not straitjacket. It carries the structure and the reasoning that are the same every time, and it leaves open, clearly marked, the places where you have to look up and think about this specific person, this specific situation, this specific number. The boilerplate is fixed so you can spend your attention where attention actually matters. It tells you where to go, but it still lets you steer.
So the test of a template is not “how much did it let me skip.” It’s “did it free my judgment for the part that needed it, and did it keep me from forgetting the part I always forget.” A template is a starting point that carries your best thinking. It is not a cage.
Here’s the part people overcomplicate. You don’t build a good template by sitting down to design the perfect one in the abstract. You build it by mining what you’ve already done well.
Go find your best recent example of the thing. The clearest client explanation you wrote, the proposal that landed, the email that actually got the response you wanted. You already made all the good decisions in that one. You’re not going to improve on your own best work by starting over; you’re going to lose it if you don’t capture it. So take that document and do two moves. First, strip out the specifics: the names, the dates, the dollar figures, the details that belonged only to that one case. Second, and this is the part that matters, keep the structure and keep the reasoning. Keep the order you put things in, because you put them in that order for a reason. Keep the transitions, keep the question you anticipated and answered before they had to ask it. Where a specific used to be, leave a marked slot that reminds you what kind of thinking goes there.
What you’re left with is the skeleton of your own good judgment. Do it once, on a calm afternoon, and you’ve turned a one-time performance into a repeatable standard. That’s the whole trick. You’re not inventing a template. You’re refusing to throw away the one you already accidentally made.
Let me get concrete, because in insurance this stuff isn’t theoretical. It’s most of the job.
Take an AOR letter. AOR stands for Agent of Record, and it’s a short letter a client signs to name us as their agent on a policy. It is not complicated. But I need one more than once, which is the whole signal right there: anything I need more than once should have a template, a place it lives, and a process for producing it. For a long time we didn’t have that, and so every AOR letter was a small archaeological dig. Someone would search their sent folder for the last one, copy it, and rebuild it – and every so often one would go out with the wrong carrier name, cannibalized from a different client’s letter. That’s the from-scratch tax, paid over and over on a document that never actually changes except for the slots. Once it became a real template, with the fixed language locked and the client name, carrier, and policy number as clearly marked fields, the letter stopped being a task and became a fill-in. The judgment about what an AOR letter should say got made one time and then just kept paying off.
The same logic runs straight up the ladder. A proposal is a template with bigger slots. The way I compare two plans, the order I walk a client through cost and coverage and tradeoffs, the way I frame the recommendation so it’s a decision and not a data dump. That structure is judgment I’ve refined over years, and there is no reason to rediscover it each time I quote a new group. What changes are the numbers and the client’s particular situation. Those are the slots. The reasoning is the template.
A clear client explanation is the same. When someone asks how a deductible works, or why their premium moved at renewal, I’ve explained it hundreds of times, and somewhere in there is my best version of that explanation, the one that actually lands. That best version should not live only in my mouth on the days I happen to explain it well. It should be written down, so the answer is that good every time, and so it doesn’t depend on me being the one in the room.
And a compliance notice is almost pure template, because the law wrote most of it. The content has to be exact, the deadlines are fixed, the audience is defined. The last thing you want there is fresh creativity. You want the stored, checked, correct version, produced the same way every time, with only the client-specific details as slots. That’s a case where the template isn’t just convenience. It’s how you keep from getting something important wrong.
Here’s the compounding view, and it’s the reason this matters more than it looks like it does. Without a template, your best thinking about a recurring thing has a lifespan of about one use. You do it brilliantly on Monday and by the following month it’s gone, and you’re back to your average effort, which means the quality of your work is sawtoothing up and down with your energy and your memory. A template flatlines that in the good direction. It takes your best and makes it the baseline. Every version afterward starts from the peak instead of the average.
That’s true whether the template is an AOR letter or a holiday menu or a packing list you rebuild the night before every trip, forgetting the phone charger every single time until the list finally remembers it for you. All of these are the same move: judgment, remembered, so you don’t have to re-derive it under pressure. The packing list is not smarter than you. It’s just you, from a calmer moment, doing your thinking in advance and handing it forward.
So when something you produce more than once still feels like starting over, that’s your cue. Somewhere in your sent folder is your best version of it, waiting to be turned into your standard version. Strip the specifics, keep the reasoning, leave the slots for the parts that still need you. You did the hard thinking once. The kindest thing you can do for the next hundred versions of yourself is to refuse to let it disappear.
Ask a good cook how they make dinner and you’ll almost never get a recipe read off a card. What you get is a base and a set of moves. There’s a way they start almost everything – the same pan, the same fat, onion and garlic going in while the rest of the plan catches up. That part doesn’t change much from Tuesday to Tuesday, and they’re not even thinking about it while they do it. The thinking goes somewhere else: what’s in season, what the person across the table is in the mood for, how to stretch one good tomato into something worth sitting down for. The base is fixed so the cook is free. Nobody calls that dinner impersonal. We call it skill.
I think about that a lot, because in my business the temptation runs the other way. Insurance work looks custom. Every client is a different company with a different budget and a different mix of people and a different set of worries, so it feels like every case should be built new – from a blank page, with fresh judgment poured into every corner. That feeling is flattering. It’s also mostly wrong, and it’s expensive. Because when everything is custom, you spend your best attention re-deciding things you already decided months ago, and you have nothing left for the handful of decisions that actually needed you.
So here’s the move this chapter is about. Standardize the parts that repeat, so you have energy for the parts that truly require judgment. Not “standardize everything.” Not “make it all a template and go home.” Standardize the base, on purpose, so the improvising lands where it counts.
Sit down with almost any recurring piece of your work and look at it honestly, and you’ll find something close to an eighty-twenty split. Roughly eighty percent of a given case is the same as the last one. The structure repeats. The order of operations repeats. The questions you ask, the documents you gather, the way you lay it all out, the boring middle of it. Then there’s the other twenty percent, the part that really needs fresh thinking, where this client’s situation actually diverges from every client before them and your experience has to earn its keep.
The mistake is treating all hundred percent as if it were the twenty. When you do that, the eighty percent doesn’t get better for being handmade. It gets worse. You reinvent the layout and forget a section you always include. You reword the same explanation for the ninth time and this time you say it slightly wrong. You do the arithmetic by hand and transpose two numbers. Custom work, applied to the part that didn’t need it, is just a longer road to a shakier result.
Standardizing that eighty percent does the opposite of cheapening it. It makes it more consistent, because it comes out the same reliable way every time. It makes it more accurate, because the errors that creep in when you rebuild from scratch stop creeping in. It makes it faster, so the client isn’t waiting on you to hand-assemble something you’ve assembled two hundred times. And here’s the part people miss: it makes the custom twenty percent better too, because you finally have the attention to spend on it. The judgment you were spreading in a thin layer over the whole job now gets concentrated where judgment actually changes the outcome. Standardizing the base is not a compromise on quality. It is how you raise it.
I know the objection, because I felt it for years and I still feel a twinge of it. Doesn’t this make the work impersonal? If I standardize, am I not just turning a craft into a commodity – handing people a form letter with their name pasted in, treating a person like a case number?
No. And it’s worth being clear about why, because the fear is pointing at something real – it’s just pointing at it backwards.
What makes work feel personal is not that every inch of it was built by hand. Nobody on the receiving end can see how much of your process was custom. What they feel is whether the parts that mattered to them got real attention. A client doesn’t experience your quoting template. They experience whether you understood their situation, whether you caught the thing their last broker missed, whether you explained it in a way that actually landed. That’s the twenty percent. And the whole reason to standardize the eighty is to protect exactly that. Every minute you’re not spending rebuilding a layout is a minute you can spend on the person. The rote part was never the personal part. It was the thing standing between you and the personal part.
So the standardizing doesn’t commoditize the work. It clears the rote out of the way so your judgment lands where it matters, and where someone can feel it. That’s the same deal the whole book keeps offering, just wearing a work suit. The meaning here is your attention on the client’s real problem. The drag is everything you were doing by hand that a base could have carried for you.
Let me get specific, because a principle with no example is just a nice feeling.
Quoting is the clearest case I have. Behind every quote is a mountain of the same: pull the census, structure the rates, build the side by side, produce a clean one-pager the client can actually read. For years I treated each one as a fresh build, and each one took the energy of a fresh build. When I finally standardized that base – upload the renewal, extract the numbers, generate the comparison in a fixed, reliable shape – the quote stopped being a project. What I noticed almost immediately was that I was thinking better about the client, because I wasn’t spending my thinking on formatting. The standard base didn’t make the advice generic. It gave the advice room.
Renewals are the same shape. A renewal season is dozens of the same motion repeated on different names: gather, compare, flag what changed, reach out. The eighty percent there is almost aggressively repetitive, which means it’s almost begging to be standardized. And when it is, the twenty percent that’s left is the good part – the client whose usage spiked, the group where the obvious plan is the wrong plan, the conversation that needs you and not a form.
Client education is one people don’t expect on this list, but it belongs. The questions come in over and over: how does a deductible work, what’s the difference between these two plans, why did my premium move. The answer to each of those does not need to be re-thought from zero every time somebody asks. It needs to be thought through once, carefully, and then delivered consistently and well. Standardizing your explanations isn’t lazy. It means every client gets the clear version, the one you’d give on your best day, instead of whatever you happened to have energy for that afternoon. Every repeated question is a broken system, and the fix is a standard answer good enough to reuse.
Compliance is where standardizing stops being nice and becomes the whole point. Compliance work is defined by its sameness: the same requirements, the same notices, the same deadlines, applied across everyone. There is almost no honorable place for improvisation in a compliance step, because “creative” and “compliant” are usually opposites. So you build the checklist once, you build it right, and it runs the same way every time. The standardization is the quality. The room it frees up goes to the truly unusual situation, the client whose case doesn’t fit the checklist, which is exactly where an expert should be spending their worry.
Service workflows tie it together. How a request comes in, who touches it, what happens next, what the client hears back and when. Standardize that path and two things happen at once. The client gets a reliable experience instead of one that depends on how swamped you were that day, and your team stops burning energy on deciding how to handle each request and can spend it on handling the request. A standard workflow is not a colder service. Ask anyone who’s been bounced around by a company with no standard workflow. Consistency is a kindness.
The real skill in all of this is not standardizing. Standardizing is easy once you decide to. The skill is drawing the line in the right place: knowing which parts are the eighty and which are the twenty, and being honest about it.
Draw the line too tight and you standardize things that actually needed judgment, and you get the cold, form-letter result everyone’s afraid of – the thing the objection was warning about. Draw it too loose and you’re back to building everything by hand and running out of yourself before you reach the part that mattered. So you have to look at each recurring piece of work and ask, plainly, which of this really varies with the client and which of this only feels like it does because I’ve always done it fresh.
A good test: if you’d do it the same way for the next ten clients, it’s base. Standardize it. If the answer really depends on who’s sitting across from you, that’s where your judgment lives, so guard it and pour yourself into it. Most of the friction in expert work comes from getting this backwards, spending the judgment on the base and the leftover scraps on the parts that needed the judgment.
And notice this compounds. The first time you standardize your quoting base, you save one afternoon. But you don’t do one quote. You do the next hundred, and every one of them is now faster, cleaner, and freer for the part that counts. Make the next hundred times easier than the last ten, and the standard you build once keeps paying you every time the work repeats, which in this business is always.
The base doesn’t make you smaller. It’s what lets you show up as the expert you actually are, instead of a tired person reassembling the same scaffolding for the tenth time this week. Standardize so the machine handles what a machine should handle. Then customize, with everything you’ve got left, right where your judgment is the whole reason they came to you.
Get the base right, and the good part is finally yours to give.
In most offices I’ve ever walked into, there’s a right way to do things, and it’s written down somewhere. There’s a process. There’s a folder where the file is supposed to go, a form the request is supposed to come in on, a checklist the compliance step is supposed to follow. The correct way exists. It is documented, approved, and, in a real sense, available to everyone. And it is quietly, consistently ignored.
Not by bad people. By good people, in a hurry, taking the easy path, which is almost never the documented one. The documented path lives in a binder, or a shared drive nobody remembers the layout of, or in the head of the one person who set it up. Following it means stopping, remembering it exists, going and finding it, and doing three extra steps that the fast-and-wrong way skips. So the fast-and-wrong way wins, over and over. Then everyone acts surprised that the results are inconsistent. They shouldn’t be surprised. The inconsistency was designed in the moment somebody decided the correct process could be inconvenient and still expect to get followed.
That’s the claim I want to plant at the front of this chapter, because it’s the one that changes how you build things. If the right way is the hard way, people will drift off it. Every time. And that drift is not a discipline problem or a caring problem. It’s a design problem. You built a road where the correct route goes uphill and the shortcut goes down, and then you asked people to climb, all day, on their own willpower – while a smooth downhill path sat right there next to them. Some will climb for a while. Nobody climbs forever. When the process only works if everyone is heroic about it, you don’t have a process. You have a hope.
Go back to the very front of this book, to the loose stair you kept stepping over. The engine under all of it was one plain fact: the path of least resistance always wins. Up to now I’ve pointed that fact at you, at your own habits and your own desk. This chapter points it at everything you build for other people, because the same law that sends your hand to the face-up phone sends your team to the shortcut. And the same fix applies. You don’t lecture the water about where it ought to flow. You regrade the ground.
So here is the whole design goal, and it’s short enough to tape above your monitor. Make the easiest thing to do also the correct thing to do. Put the right path downhill. When those two things line up – when the low-resistance move and the right move are the same – you stop needing to enforce anything, because there’s nothing left to enforce. People aren’t fighting the process anymore. They’re rolling down it. That’s the shift from getting compliance by pressure to getting it by design, and it’s the difference between a system that needs a person standing over it and a system that just runs.
I’ve come to say it this way, and I believe it more the longer I do this work. Compliance and consistency are downstream of convenience. You will not get either one by wanting it harder, or by writing a sterner policy, or by retraining everyone for the third time. You get them by making the correct action the low-friction default, so that doing it right is simply the least effort available. When you find a place where the right way keeps getting skipped, don’t start with a reminder. Start with the question: what makes the right way harder than the wrong way right now, and how do I flip that?
Let me make this concrete, because it only means anything in the specifics.
Take a request that comes into your team a hundred times a year, a quote, a change, an intake of some kind. If the correct way to submit it lives in someone’s memory, half of those requests will show up as a hurried email missing the three things you actually need. Every one of those turns into a back-and-forth that costs everyone a day. Now put a real intake form in front of it. Not a suggestion, a form, the easy front door, the thing that’s less work to fill out than composing that vague email would have been. The required fields are just there. You can’t submit it half-baked because the form won’t let you. The form isn’t a rule you’re imposing. It’s a downhill path. Because it’s downhill, people take it, and the requests start arriving complete without anyone being nagged into it. You made the right way the easy way, and the consistency showed up on its own.
Same shape, over and over, across a whole working life. A client portal, when it’s built right, is not extra work you’ve handed the client. It’s the path that’s easier than calling you, so they use it, and now the information lives in one findable place instead of scattered across voicemails. A shared knowledge base earns its keep the day answering a question there becomes faster than walking over to ask the one person who knows, because at that moment the correct behavior – look it up – becomes the lazy behavior too, and the answer stops living in one fragile head. A checklist engine that walks you step by step through a process beats a checklist printed in a manual, every time, because the printed one requires you to remember it exists and go dig it out. The built-in one meets you right where the work is and makes skipping a step take more effort than doing it. Notice the pattern under all of them. In each case the win isn’t that you added a rule. It’s that you moved the correct path from uphill to down.
My own clearest example is a compliance tool I built for exactly this reason. Employer compliance is not hard because the requirements are exotic. It’s hard because it’s confusing, it’s spread across a dozen deadlines and notices, and every single piece of it is easy to skip in a busy week when nothing’s on fire and no one’s asking. The correct path was available. It was also miserable, so people drifted. Then a deadline would arrive and the scramble would start. What ComplyDIY does, at bottom, is take that confusing, skippable mess and turn it into an organized default path. A checklist that tells you what’s actually required and in what order. Answers you gave once, saved, so you’re never hunting for the same information twice. The notices, ready to go instead of built from scratch under pressure. A calendar so the deadlines come find you instead of the other way around. None of that is magic, and honestly none of it is even about compliance in the deep sense. It’s about resistance. It took the right way, which used to be the hard way people avoided, and made it the easy way, the obvious way, the way that’s now less work than doing it wrong. The consistency that follows isn’t willpower. It’s the shape of the thing.
That’s the tell, by the way, for whether you’ve actually built the right way the easy way or just added a step and called it a system. Ask whether the correct action is now less effort than the alternatives, or more. A prebuilt open enrollment page that an employee can complete in five minutes on their phone is the easy path, so they walk it, and your enrollment data comes back clean. A standard folder structure, set up once and used by default, means the file goes where it belongs because that’s the first place your hand lands, not because anyone remembered a policy. A required naming convention only sticks if the correct name is easier to produce than a random one, which is why the ones that survive are the simple, obvious formats and the clever elaborate ones quietly die. If the “system” is more work than the mess it replaced, it will lose to the mess, and it should. The best system is not the most complete system. It is the system people will actually use, and people use what’s easy.
You don’t need to run an office to have lived this. Every household knows it. Somewhere in your home there is a Correct Filing System, a proper set of labeled hanging folders in a drawer, that nobody in the family has filed a single thing in since the day it was set up. And somewhere near the door there is a bowl, or a hook, or a beat-up labeled bin, that catches the keys and the mail and the permission slips every single day, without fail. It sits exactly where hands already pass and costs nothing to use. The filing system is the right way that’s the hard way. The bin is the right way made easy. Guess which one holds the family together. Every “why does nobody put things back where they go” fight in history is really a friction complaint wearing a discipline costume. The stuff doesn’t go back because back is too far. Move “back” to where the hands already are, and the fight just ends. Nobody got more responsible. The path got shorter.
I want to be honest about the shape of the effort here, because it isn’t free. Building the form, the portal, the checklist, the folder structure, the bin by the door – all of it costs you something once, up front, in fix-it mode, on purpose. That’s the lump of work most teams never spend, which is exactly why most teams are still climbing uphill. But this is the same trade the whole book keeps coming back to. You spend the fix once so you stop paying the tax forever, and here the tax isn’t just yours. It’s every skipped step, every incomplete request, every inconsistent result, every “who was supposed to do that,” multiplied across everyone who touches the process, across all the years it runs. Make the next hundred times easier than the last ten, and do it for the whole team at once. The return isn’t linear. It’s enormous, and it’s quiet, because a well-graded road doesn’t announce itself. It just stops generating problems.
So here is the move, and it closes out this whole part of the book, this section on the work that repeats across clients and years. Find one place, just one, where the right way is currently the hard way. You already know where it is. It’s the process people keep skipping, the step that keeps getting done wrong, the thing you find yourself re-explaining and re-fixing and privately resenting people for not doing correctly. Stop resenting the people. They’re just water, finding the low ground, the way we all do. Look instead at the ground. Then go regrade it, once, so that the correct path becomes the path of least resistance, the easy front door, the thing that’s simply less work than doing it wrong.
Do that, and you’ll notice something that still surprises me every time. The nagging stops. The exceptions dry up. The results get consistent, not because anyone tried harder, but because you finally stopped asking them to. You made the right way the easy way, and easy, it turns out, is a thing people are wonderfully reliable about. Put what’s right downhill, and watch how willingly everyone walks it home.
There are two ways people talk about AI right now, and they are both a little unhinged. One group says it’s about to think for us, replace us, and make most of what we do pointless. The other group says it’s a toy, a glorified autocomplete, a hype cycle we’ll all be embarrassed about in a few years. One camp is scared and one camp is dismissive, and I’ve spent enough time actually using the stuff to tell you that both are missing what’s in front of them.
Here is the calmer, more useful way to see it. AI is not a mind. It’s a friction remover. It happens to be the best one I’ve ever found, but it belongs on the same shelf as a pill box and a template and a shut-off valve you finally replaced. Its practical value in your life is not that it does your thinking. It’s that it clears the resistance sitting around the thing you already wanted to do. Once I started treating it that way, it stopped being either a threat or a miracle and became something much more valuable: a tool I actually knew how to use.
I want to make that concrete before we go one sentence further, because the whole rest of this book has been about staying concrete. Think back to the loose boards on your stair. The projects that stalled. Almost none of them stalled at the beginning, and almost none of them stalled because you didn’t care. They stalled at the wall.
Remember the wall from earlier in the book, the 80 or 90 percent wall. The project dies at the last slice – the piece you don’t know how to build, or the piece you know how to build and can’t stand. That’s where the belief was real and the finish never came. My compliance tool sat parked for two years on exactly that kind of slice, one segment I didn’t know how to build, and it wasn’t parked because I doubted it or lacked the time. One unfamiliar piece froze the whole thing.
Now here is why AI matters in a book about friction, and why I put it in this book at all. AI is uniquely, almost suspiciously good at exactly that last slice. The unfamiliar technical build. The tedious cleanup nobody wants to touch. The formatting. The reformatting. The thing you don’t know how to do or don’t want to do. It is not especially good at replacing the 80 percent you already had and were glad to do. It is very good at the 10 or 20 percent where your projects reliably went to die. When I finally described what I needed to a chatbot and it walked me through the steps and then added, almost as an afterthought, “or I can just do it for you,” that was the whole thing in one sentence. The resistance broke. The tool got built. The site went live. Two years of “someday” collapsed into an afternoon, and the feeling was not amazement at the technology. It was relief. The weight I’d been carrying just switched off.
I want to be honest about something, because the hype machine won’t be. AI is not the only way over that wall. It’s one way. You can clear the same slice by finding a better approach, by handing it to someone who does that thing easily, or by lowering the bar on the part you were dreading until it’s small enough to just get done. The wall is the real subject. AI is one very good ladder. If it vanished tomorrow, the principle underneath this book would not move an inch: find the resistance, and design it out. So don’t hear me saying AI is the answer. Hear me saying it’s an unusually capable friction remover, and friction removal is the point.
So what does it actually remove? Let me keep this plain, because this is where people get lost in the abstractions. It removes the blank page, the worst friction there is, by giving you a rough first draft to react to instead of a void to fill. It summarizes the forty-page document you were never going to read. It formats the thing you formatted wrong. It organizes the pile, the folder, the photos, the years of files with the same name from three different computers. It compares your options side by side when you’ve been circling a decision for a week. It extracts the numbers buried in a PDF that you would otherwise retype by hand. It searches your own material, the notes and posts and documents you wrote and then could never find again. Notice what every one of those has in common. None of them is the meaningful heart of the work. Every one of them is drag. Every one is a step you’d have skipped if you could, and now you can.
That changes the question you ask, and the question is where all the leverage is. For most of my life, standing in front of something big, the question was “how do I do all of this?” That question is exhausting, and it’s usually the reason the project never starts. The new question is quieter and much better: “what part of this should I still do myself?” You stop staring at the whole mountain and start looking for the one stretch that’s actually yours. The judgment. The taste. The relationship. The decision only you can make. Everything else is a candidate for removal. That flip – from “how do I do all this” to “what part is really mine” – is the single most freeing shift AI has handed me, and it has almost nothing to do with the technology and almost everything to do with friction.
Once you’re using it that way, a pattern shows up. I’ve come to think of it as four stages, and I only noticed them looking backward at what I’d actually done. The first stage is clearing the backlog. You take the deferred pile, the 300 open items, the photos, the cleanup you meant to do for years, and you finally get through it. The part that made it feel impossible was the tedium, and the tedium is exactly what AI eats. The second stage sneaks up on you. Clearing the pile reveals that the pile was never junk. It was hidden assets. I fed years of scattered article ideas into a tool expecting a cleanup and got back the raw material for several books I’d always meant to write. The backlog wasn’t a mess to survive. It was a mine I’d been standing on. The third stage is connecting those assets into something bigger than any one of them, taking the notes and the files and the records and turning them into a single thing you can actually use and ask questions of. And the fourth stage is the big one: eliminating whole categories of work by building systems, so the friction doesn’t come back next month, because the thing that generated it is gone. The next few chapters walk these four stages one at a time, with the real stories attached, so I won’t spend them here. For now I just want you to see the shape: clear the backlog, reveal the assets, connect them, then build the systems that retire the work for good.
I’ll add one more habit, and it’s one I unpack elsewhere, so I’ll keep it short here: assume the answer is yes. Before you decide AI can’t do the thing, just try it. You don’t lose much by asking and being wrong. You lose a great deal by assuming no and never checking, because that assumption is just friction wearing the costume of realism. And the wins stack, the same way a fixed drawer or a loaded pill box builds momentum. Small wins are the on-ramp here too.
Let me kill one myth on the way out, because it trips up more people than anything else. AI can build a tool that is not itself AI. This confused me at first, so I’ll say it plainly. That compliance tool I finally shipped runs on a checklist engine and saved answers. There’s no intelligence in it at runtime, no model thinking things over. It’s rules, plain and boring and reliable, the same logic every time. The renewal tool I’ve been building does the same thing: it reads a document and pulls the numbers out in about thirty seconds, and that extraction is rule-based, not some clever guess. The AI did the hard, unfamiliar part of building it, the exact slice I’d been stuck on for years. What it left behind is an ordinary tool that just works. So when you worry “is this all AI magic that’ll break or drift,” often the honest answer is no. You used a friction remover once, to build something plain and dependable, and then you own that plain dependable thing outright.
I’ll close with the smallest example I’ve got, because it’s the one that made the point land for me. After surgery on my thumb, I was tangled up in the usual medical confusion – half-understood terms, conflicting advice, no clear picture of my own recovery. I asked for a plain-English one-pager: causes, options, the pros and cons of each. A few minutes later I had it, and the fog was just gone. That’s not a company. That’s not a product I shipped. That’s a Tuesday, and a small pile of dread that didn’t need to exist. The tool didn’t do my deciding for me. It cleared the mess between me and the deciding, which is all I ever actually needed cleared.
That’s the whole reframe, and it’s the door into this last stretch of the book. AI is not a mind coming for your work, and it’s not a toy you can safely ignore. It’s the best friction remover I’ve ever put my hands on, aimed at the exact last slice where your projects have been dying for years. It doesn’t replace the part you already had. It clears the part that stalled you. Set down the awe and set down the fear, both. Pick it up like a tool, ask the better question, try the thing before you decide it can’t, and let’s go clear some walls.
Early in my working life, before insurance, before any of the tools I’ve been describing, I managed a department at Target. And I had an assistant named Vernon. Vernon had been a store manager at Walmart, which meant that on paper he outranked the job he was doing, and in practice he was better at almost every part of it than I was. He was faster. He knew the floor cold. He’d seen more, fixed more, and handled more than I had – and it wasn’t close. By any honest measure of the actual work, Vernon should have had my job.
But Vernon didn’t want my job. He’d done the managing, and he was finished with it. He didn’t want the meetings or the paperwork or the standing around deciding things. He wanted to work. He wanted to see a thing that needed doing and go do it, and be left alone while he did. And that, it turned out, made us a very good pair, because I was happy to decide what needed doing, and he was happy to make it happen.
Here’s how a day actually went. I’d look at what was in front of us and figure out what mattered, in what order, and Vernon would already be halfway to handling the first thing before I finished saying it. Often he’d have spotted it before I did. He didn’t wait to be told. He read the situation, understood what the day required, and moved. I directed, and I got the credit, and for a while that arrangement made me a little uneasy. From the outside, it looked like I was the one coasting while Vernon did the heavy lifting.
I’ve thought about that a lot since, and here’s where I landed. I want to be honest about it, because the honesty is the whole point of this chapter. I wasn’t lazy. I was doing a different job. My job was deciding what should happen. Vernon’s job was making it happen. Those are two real jobs, not one real job and one fake one. Somebody has to look at the whole thing and choose. Somebody has to say this matters and that can wait and that over there is a mistake we’re about to make, let’s not. That was mine. And somebody has to take the choice and turn it into finished work, quickly and well. That was his. Neither of us could have run the department alone.
I hadn’t thought about Vernon in years. Then I started using good AI tools in earnest, and one afternoon it hit me, almost embarrassingly clearly: this feels exactly like having Vernon back. Two of him, actually. The tools do an enormous amount of the doing. They handle the parts I used to grind through myself, and my job has quietly shifted into the one I had at Target. I direct. I judge. I decide what matters and what doesn’t. The work still happens, more of it than before, but I’m not the one moving every box anymore.
That’s the reframe I want to hand you, and it’s bigger than it first sounds. AI doesn’t just do some of your tasks for you. It changes what your work is worth. It changes the value of different kinds of effort, and it moves that value around in a way that’s worth understanding, because if you understand it you’ll spend your time very differently.
Think about the things a lot of us do all day. Copying something from one place to another. Pasting it. Reformatting it so it looks right. Searching for the file we know exists somewhere. Summarizing a long thing into a short thing. Recreating a document we’ve basically built before. For most of my working life, being good at those was useful. Being fast at them was a real skill, and I was proud of mine. But the value of all of that is dropping, and dropping fast, because those are exactly the things the tools are good at. The market rate on copying and pasting and formatting and searching and summarizing is heading toward zero, and no amount of being excellent at them is going to hold that price up.
Now think about a different set of things. Defining what you’re actually trying to accomplish. Looking at a piece of finished work and knowing whether it’s right or wrong, good or off. Catching the flaw in the logic that looks fine on the surface. Deciding, out of ten things you could do, which one actually matters. Those are going up in value, and for the same reason the others are going down. The more the doing gets handled, the more the deciding and the judging are what’s left, and what’s left is the expensive part.
So the honest headline is not that you’re being replaced. It’s that you’re being promoted. You’ve been moved off the floor and into the job Vernon didn’t want and I happened to have: you are not doing every task anymore, you are directing the work. And a promotion is good news, but it comes with the thing every promotion comes with, which is that the skills that got you here are not the skills the new job needs. Being the fastest doer in the room mattered a lot right up until the moment it stopped mattering, and now the room needs a good decider instead.
Which brings me to the part I’m least comfortable skipping, because it’s the real risk and I’d be doing you a disservice to sell you the upside without it. When you hand off your execution, it is very easy to hand off your judgment along with it. That’s the trap. The tool does the work and hands it back. It looks polished, it’s fast, and there’s a strong pull to just accept it and move on. But accepting output you can’t actually evaluate isn’t delegating. It’s abdicating. If I’d let Vernon run the whole department while I stopped paying attention, I wouldn’t have been a manager, I’d have been a bystander with a title.
So here’s the guardrail, and it’s the same one that makes any good supervisor good. First, you still have to be able to tell when the output is wrong. Not most of the time. Every time it matters. The moment you can’t judge the work, you’ve stopped being the manager and started being a customer who has to trust the salesman. Keep enough of your own competence to check. Second, do what a good supervisor does when they hand off a task. Give real context, so the work is aimed at the actual goal and not a guess at it. Give an example of what good looks like, because “make it good” means nothing and “make it like this one” means everything. And then check the work before it goes anywhere. Context, example, check. That’s not bureaucracy, that’s the job. That’s what directing actually is.
I’ll give you a small, slightly sheepish illustration of how far the manager mindset can go, and then I’ll get off it, because I don’t want to oversell it. Sometimes now I’ll set a tool going on a real task at night, right before bed. I’ll give it the context and the example and turn it loose, and I’ll go to sleep. In the morning I make coffee and I review what it did, the way I used to walk the floor first thing and see what the overnight crew had gotten done. Some mornings it’s most of the way there and I just clean it up. Some mornings it went sideways and I have to redirect it, which is exactly what mornings with any crew are like. I’m not claiming this is magic and I’m not claiming it always works. I’m telling you that the shape of my day has changed, and the change is that I’ve become the person who reviews the work in the morning instead of the person who was up all night doing it.
Let me put one more example on the table, a personal one, because I think the shift from executor to editor is easiest to feel in something close to home. For years I told myself I’d write. I had ideas constantly, and I’d talk them out, and they’d evaporate, because sitting down to turn a rough idea into finished pages was the part I never got to. The doing was the wall. What changed wasn’t that I suddenly found the discipline to grind out drafts. What changed is that the grinding got handled, and my job moved to the part I was always actually good at and always actually enjoyed: knowing what I wanted to say, reading a draft and feeling exactly where it went false, cutting the line that didn’t belong, deciding this chapter matters and that one is filler. I stopped being the executor who couldn’t get started and became the editor who could finally work. The book you’re reading exists because of that shift. I didn’t write every sentence by hand. I decided every sentence was right, or made it right, which is a different job, and it’s the one I could actually do.
That’s the move, all the way down. You are not doing every task. You are directing the work, judging the work, and owning the call on whether it’s good. The doing got cheap. The deciding got precious. Vernon and I made a good department because we each did the job we were suited for, and he never resented the directing and I never pretended I could do the floor faster than he could. You’ve just been handed a couple of Vernons of your own. They’re fast, they’re tireless, and they’ll do an astonishing amount of the work you used to carry yourself. Your job is to be the manager they deserve: clear about the goal, honest about the standard, and awake enough to catch it when the work is wrong. Do that, and you don’t lose anything in the trade. You get promoted into the work that was always the most yours.
For about three years, I did most of my thinking in the car. I’d be driving to a meeting or heading home, and an idea for an article would show up, the kind of thing I actually cared about, and I’d talk it into a tool on my phone. It would clean up my rambling and drop it onto a website I’d set up for exactly that purpose. I called it Read Eric’s Mind. And that’s where those ideas went to sit. A thousand of them, give or take. A thousand pieces of my own thinking, captured, saved, and going absolutely nowhere.
I had no firm plan for them. If you’d asked me, I’d have said something vague about maybe writing a book someday. I’d been saying “someday” about books for years. It was one of those aspirations I fully believed in and never touched, because the writing itself I could do, but turning a thousand scattered posts into actual books felt like a mountain I was never going to have a free week to climb. So the pile just grew. Every drive added to it. And every so often I’d think about it and feel that little pull of guilt, the one you feel about a thing you keep meaning to make something of and never do.
Then one day I pointed a tool at the site. It pulled all thousand articles. It read them, grouped them by theme, found the threads running through them, and in about twenty-four hours it helped me produce eight full-length book drafts. Eight. Plus a finished trilogy on top of that, three books that actually held together, start to finish. The deferred dream – the one I’d been carrying around for years with no idea how I’d ever get to it – turned out to be sitting right there the whole time, already written in pieces. I just hadn’t been able to assemble it.
I remember the feeling clearly, because it wasn’t really excitement. It was closer to relief mixed with a kind of embarrassment. All that thinking had been an asset the entire time. I’d been standing on a gold mine and calling it a pile.
That’s the idea I want to give you in this chapter, and it’s the payoff of the stage I called revealing hidden assets. Clearing the backlog is the obvious first win. But revealing hidden assets is the one that surprised me most, because it changes how you see everything you’ve kept. A pile of old material is not clutter. A pile of old material is a hidden asset, if you can finally do something with it. The difference between the two isn’t the pile. It’s whether you have a way to reach into it.
Let me give you a few more, because once I saw it in one place I started seeing it everywhere.
For sixteen years I’ve taught continuing-education classes for insurance agents. Sixteen years of classes means sixteen years of certificates, one for every person in every room, and if you’ve ever run anything like that you know those certificates pile up into folders and drives and email attachments until they’re just a sediment layer of your career. Technically saved, functionally lost. I’d meant to organize them for years. I’d even tried a couple of times and given up. It was too big and too tedious, exactly the kind of last-slice work I never had the appetite for.
So I handed the whole mess over. The tool grouped the certificates by person, read the license numbers right off the documents, matched people across years, and built me an all-time roster. About 5,200 unique attendees. Names, emails, when they last attended, how many of my classes they’d taken, their ratings, their comments, links to their records. Sixteen years of goodwill that had been sitting in folders as dead weight turned into a living roster I could actually use. That’s 5,200 people who chose to spend a day learning from me, and until that moment I had no clean way to reach a single one of them as a group. Now it’s a prospecting list and a testimonial archive and a record of relationships, all at once. The classes were never the asset. The classes were fine. The asset was the trail they left, and the trail had been invisible because I couldn’t assemble it.
Here’s one where I got even closer to throwing the gold away. Years ago I worked with an agency, and I had a folder of old notes from those days – onboarding notes, first-five-days-on-the-job stuff, ugly and half-formed. I was cleaning up files and I very nearly deleted them, because what are you going to do with rough notes from a job you don’t have anymore. But instead of deleting them, I ran them through and asked what was actually in there. What came back was a blueprint, a real one, on how to run a service-first insurance agency. The judgment was all in those notes. I’d written down hard-won lessons and then filed them under “old” and nearly hit delete. Trash, one keystroke from the bin, turned into a teaching asset I’m actually a little proud of.
And then there’s the one I laugh about, though it was a real question I carried for a long time. Years ago I got obsessed with betting systems – blackjack and roulette – the kind of thing where you’re sure there’s a pattern if you just track enough hands. I logged hundreds of hands into spreadsheets, chasing the system that beats the house. Then life moved on and those spreadsheets sat there for years. One day, cleaning up, I had my finger over the delete key. Old obsession, no use for it, why keep it. Instead I fed the spreadsheets in and asked the question I’d never been able to answer myself. The tool ran four thousand hands per system and came back with a clean verdict: nothing beats the house edge. Nothing. Which, honestly, I mostly knew. But there’s a difference between mostly knowing and finally knowing, and I got to close that loop after all those years. Closure on a question I’d carried around, from a pile I almost erased. Glad I didn’t just delete it.
Do you see the pattern across those four? The books, the roster, the agency blueprint, the betting spreadsheets. In every case the material already existed. I’d already done the work of creating it. What was missing was never the content. What was missing was a way in. And that’s worth naming plainly, because it’s the quiet reason so much of what we save turns to dead weight.
There’s a line I keep coming back to in this book: knowledge that cannot be found is almost the same as knowledge that does not exist. Sit with that for a second, because it’s the whole game. Those thousand articles existed. The 5,200 attendees existed. The blueprint existed. But existing isn’t the same as being reachable, and if you can’t reach a thing when you need it, it might as well not be there. A saved file you can’t find is a file you don’t have. A lesson you wrote down and can’t locate is a lesson you didn’t keep. All those years I thought my problem was that I hadn’t done enough. My real problem was that I couldn’t get to what I’d already done.
Now let me put two words in front of you, and I promise to keep them plain, because the plumbing matters less than what it does for you. The first is knowledge base. A knowledge base is just a place where your prior thinking is stored so it can be retrieved. That’s it. Not stored so it’s safe, stored so it’s findable. The whole value is in the getting-it-back-out, which is exactly the part we usually neglect. Most of us are good at saving and terrible at retrieving, and so we build enormous private libraries that we can never actually read.
The second is a piece of jargon you may have heard, RAG, and I only mention it so it doesn’t intimidate you when you run into it. Here’s all it means in practice: you can point a smart assistant at your own documents, and it answers from your material instead of from the open internet. That’s the whole idea. Not the world’s knowledge, your knowledge. Your notes, your files, your years of work, made answerable. Ask a question and get back what you wrote, what you decided, what you learned, rather than a generic reply from everywhere and no one. When people worry that these tools just make things up out of the ether, this is the honest answer to that worry: you can ground them in your own pile. You can make the pile talk back.
And that’s the shift I want you to feel. For most of my life, the stuff I kept was passive. It sat. Keeping it was an act of faith that someday it would matter, and someday kept not coming, and the boxes just got heavier. What changed is that the pile stopped being something I stored and started being something I could ask questions of. The roster answers “who should I be reaching out to.” The blueprint answers “how do I train someone new.” The thousand articles answered “what have I actually been trying to say all these years.” The material didn’t change. My ability to reach into it did, and that turned storage into supply.
So here’s your version of this, because you have one, I’m sure of it. It might be a physical box of notes in a closet. It might be an old hard drive you keep meaning to go through. It might be a folder of half-ideas, or years of photos, or a document where you’ve dumped things you didn’t want to lose. Whatever it is, you’ve probably been carrying it with a faint sense of guilt, telling yourself you’ll deal with it someday, treating it as clutter you haven’t gotten around to clearing. I want you to try seeing it the other way. That pile is not evidence of your disorganization. It’s inventory. It’s raw material you already paid for, with your time and your attention and your care. And it’s sitting there waiting for the one thing it never had: a way in.
The move is not to keep saving, and it’s not to finally feel bad enough to throw it out. The move is to open it and ask it something. Point an assistant at it and see what’s actually in there. You will almost certainly find that some of what you kept really was clutter, and you can let that go now with a clear conscience, because you looked. But you’ll also find, I’d bet on it, that some of it was gold, and you just never had the pickaxe.
The pile isn’t clutter if it becomes an asset. That’s the whole difference, and it was never about the pile. It was about whether you could finally reach in. You’ve been standing on a gold mine and calling it a mess. Go find out which one it is.
When I cleared out that pile of 300 open items I told you about, most of them cleared the way you’d expect. I did the thing, checked it off, and moved to the next one. One at a time, an evening at a time, in front of the TV. That’s ordinary work, and there’s nothing wrong with ordinary work. But somewhere in the middle of that pile I noticed something. A few of the items didn’t clear one thing. They cleared a whole class of things I’d never have to do again. And those few felt completely different from the rest.
That’s the distinction this chapter is about, and it’s the one I most want you to carry out of this whole section. Most tools save you minutes. A few tools change what work feels worth doing. The first kind makes a task faster. The second kind makes an entire category of recurring work disappear, and when a category disappears, something strange and good happens on the other side of it, which I’ll get to. First let me show you the difference, because it’s easy to say and easy to miss.
Think of the vitamins from early in the book. The pill box didn’t make opening six bottles faster. It removed the opening of six bottles from my mornings entirely, for two weeks at a stretch. That’s a tiny, humble version of the move, but it’s exactly the move. The friction wasn’t reduced. The friction was deleted, and a category of daily fumbling stopped existing. Now scale that same shape all the way up, into the work I do for a living, and you’ll see what a category-removing tool actually looks like.
Take quoting. In my business, a big recurring chunk of the work is comparing insurance plans for a group: pulling numbers off a renewal, building a census, laying out the current plan against the alternatives, and turning all of it into something a human can actually read and decide from. For years that meant a person sitting down and typing. Reading a renewal, keying the rates in, checking them, arranging the comparison, formatting the one-pager. It was skilled work, and it was slow, and we did it over and over and over – group after group, year after year. I’d taken some of the sting out with a spreadsheet along the way, but that was still, at bottom, faster typing.
The online version of that tool, Stella, does something the spreadsheet never did. You upload a renewal, and in about thirty seconds it extracts everything, builds the census, lays out the composite and age rates, produces the side-by-sides and the one-pagers. I’m not describing a faster way to enter the data. I’m describing the end of entering the data. The whole category of “read the renewal and type it in” is just gone. That’s the line I keep coming back to when I think about what that tool did for me: it took something that used to be a grind we absorbed as the cost of doing business and made the grind not exist. And I want to be careful here, because this book is not a sales pitch for any tool, including my own. I’m using it because I know exactly what it removed, and I lived on both sides of the removal.
ComplyDIY is the same shape pointed at a different category. Compliance, for a small employer, is a fog of “am I supposed to be doing something, and if so, what, and by when.” The recurring work was answering that fog, over and over, one confused employer at a time. The tool turned the fog into a checklist that knows the rules, remembers the answers, generates the notices, and puts it all behind a portal the employer can actually use. It didn’t make explaining compliance faster. It removed the need to explain compliance from scratch every single time. A whole category of repeated confusion, handled once, structurally.
And here’s a smaller, gentler one that maybe more of you will recognize from the receiving end: the open enrollment portal. Every year, for every group, employees ask the same questions about their benefits. What’s the deductible, how does the HSA work, is my doctor in network, what changed from last year. For a long time the answer to that lived in people’s heads and got repeated out loud, individually, hundreds of times each season. A good portal removes the category of “explain the same benefits information to the same kinds of questions over and over.” The information is laid out once, well, where people can find it, and the repeated explaining stops being a thing anyone has to do. Every repeated question is a broken system, and a portal is what fixing that system looks like when you finally build it.
So how do you spot a category worth removing, in your own life or work, before you’ve built anything? You don’t need my examples for this. You need a test, and the test is short. Look for work that is recurring, rule-bound, high-volume, and low-judgment. Recurring, meaning it comes back, it isn’t a one-off. Rule-bound, meaning the same inputs reliably lead to the same right answer, and you could almost write the steps down. High-volume, meaning you do it a lot, so removing it pays off many times. And low-judgment, meaning the value you add isn’t in the doing, it’s somewhere else. When a task scores high on all four, you’re not looking at a task to speed up. You’re looking at a category to remove. Reading a renewal and typing the numbers is recurring, rule-bound, high-volume, and takes almost no real judgment. That’s exactly why it was the right thing to delete rather than accelerate. The judgment was never in the typing. It was in what the person does with the comparison once it exists.
Notice what that test screens out, too, because that matters just as much. The parts of my work that are full of judgment – the read on a client’s actual situation, the call about which plan really fits a particular business and the people in it – those don’t score high on the test, and I don’t want a tool to remove them. Those are the parts worth having my hands on. The four-part test is really just a way of finding the drag with confidence, so you can leave the meaning alone.
Now for the thing on the other side of removal, the part I still find surprising even after watching it happen several times. When a tool removes a whole category of work, it doesn’t just give you back the hours you were spending. It changes the math of what you’re willing to take on at all. There were things I never attempted, not because I couldn’t, but because the recurring cost was too high to justify. When quoting meant hours of typing per group, I quoted the groups I had to. I wasn’t about to run detailed comparisons for prospects who might not sign, or re-run last year’s groups just to see if something better had come along, because each one carried that typing tax. The moment the typing tax went to roughly zero, all of those “not worth it” projects quietly flipped to “sure, why not.” I could quote broadly, revisit freely, explore. Work that had been sitting just on the wrong side of the line was suddenly on the right side of it, and I hadn’t gotten any more disciplined. The line had moved.
That’s the deeper effect, and it’s the reason I think category-removing tools deserve their own chapter instead of a footnote in a chapter about efficiency. A tool that saves you minutes helps you do the things you were already doing. A tool that removes a category lets you do things you had ruled out. It expands the set of what’s worth attempting. Projects that were parked forever with “someday, when I have the bandwidth” are the ones that come back to life, because the bandwidth was never really the issue. The recurring cost was. Remove the recurring cost and “someday” turns into “this week.”
You don’t need my business to feel this. The household version is everywhere, and it’s the same shape exactly. Most of us have paid for things that make a chore faster. The category-removers are the ones that make a chore stop being yours. Automatic bill pay doesn’t make paying bills quicker. It removes the recurring act of paying bills from your life, and it scores perfectly on the test: recurring, rule-bound, high-volume, low-judgment. A standing grocery order for the staples you buy every week isn’t a faster shopping trip, it’s the deletion of the “we’re out of the thing again” category. A housekeeper every other week isn’t a more efficient way for you to clean, it’s the removal of cleaning from your list entirely. And the same downstream magic shows up at home that shows up at work. When the recurring chore is gone, you take on things you’d been avoiding, because the ambient weight that made everything feel like too much has lifted a little.
Let me name one thing plainly so nobody gets the wrong idea about all this. These tools are often built with AI now, mine included, and it’s tempting to think that means the tools themselves are some kind of magic that thinks. They mostly aren’t. The renewal extractor follows rules. The compliance checklist follows rules. AI helped me build them, and it was the thing that finally got me over the walls I’d been stuck at for years. But the tools that came out the other side are ordinary, rule-based, and boring in the best way. That’s actually the point. A category worth removing is a category that runs on rules, and a thing that runs on rules can be handed to a system, however you build it. You don’t need magic to remove a category. You need to notice that the work is recurring, rule-bound, high-volume, and low in judgment. Then decide, once, to build the road instead of paying the tax down it forever.
So the next time you’re grinding through something, ask which kind of grind it is. If it’s truly yours – the judgment, the call, the part where you actually matter – keep it and do it well. But if it’s recurring and rule-bound and high-volume and low-judgment, don’t reach for a way to do it faster. Reach for a way to not do it at all. Because the best tools were never really about the minutes. They’re about what becomes possible on the far side of a whole category of work you’ll never have to touch again, and that’s a much bigger room than it looks from in here.
I have spent this whole book trying to talk you out of paying for things twice. The pothole, the loose board, the six pill lids, the walk to the other bathroom. Find the drag, name it, design it out, and get on with your life. So I want to be careful here, at the top of the last part of the book. Because if you take everything I’ve said and run it all the way to the wall, you end up somewhere I never meant to send you. You end up trying to remove the friction from your own life, all of it, down to the studs. And that would be a mistake, and it would be my fault for not saying this plainly, so I’m going to say it plainly now.
Some friction is the entire point. It is not drag. It is not a tax. It is not a badly built road you’re supposed to fix. It is the thing itself, and if you smooth it away, you don’t get a better version of the thing. You get nothing, dressed up to look like the thing.
Let me show you what I mean, because I’ve never trusted a principle I couldn’t put a picture next to.
Cooking a meal for someone you love is a lot of steps. You shop, you chop, you stand at the stove, you time it so everything’s ready at once, which never quite works, and you clean up after. You could skip nearly all of that. You could order the same food, better food probably, and have it at the door in half an hour with none of the effort. And on a Tuesday when you’re wrecked, you should, and I do. But the meal you cooked and the meal you ordered are not the same object, even if the calories match. The effort is not in the way of the gift. The effort is the gift. The person you cooked for knows you spent your evening on them, and that knowledge is most of what they’re actually eating. Automate that and you’ve automated it into a transaction.
Writing a note by hand is the same shape. It takes longer, your handwriting is worse than a font, you can’t undo a mistake without it showing. Every one of those is friction by the definition I’ve been using all book. And every one of them is why the handwritten note lands the way it does. The recipient can see that you sat down, that you couldn’t copy and paste, that the minutes were spent and can’t be gotten back. The inefficiency is the message. It says you were worth the slow way.
A slow walk with nowhere to be is pure friction if you look at it wrong. It’s the least optimized transportation possible. You’re not getting anywhere, that’s the whole design. Strip the “waste” out of it and you’ve got a treadmill, or a commute, and you’ve thrown away the one thing the walk was for, which was the not-getting-anywhere.
Then there are the hard ones, the ones that actually cost. A necessary conversation, the kind you’ve been circling for a week, is uncomfortable all the way through, and the discomfort is not a bug in the conversation. It’s the tax you pay for the relationship being real. You could dodge it, soften it into a text, let it go unsaid. That’s the frictionless path, and it leaves the thing rotting quietly underneath. The friction of saying it to someone’s face, watching it land, sitting in the silence after – that friction is what makes it count and what makes it work.
And the one that got me thinking about all of this in the first place: teaching someone something you could just do faster yourself. Walking a person through a knot, or a stick shift, or the recipe you make without thinking. Every atom of your operator brain – the brain this whole book has been sharpening – is screaming that this is wildly inefficient, that you could do it in a third of the time and everyone could move on. And you should ignore that brain completely, because the slowness is not overhead on the lesson. The slowness is the lesson. The point was never the finished task. The point was the person learning it, and the patience, and the time spent standing there together while they got it wrong and then, finally, didn’t. Optimize that away and you’ve saved a few minutes and skipped the entire reason you were there.
So here is the line, and it’s the one I’ll come back to more than any other in these last chapters, because it’s the whole ethic of the book in five words:
Automate the drag. Protect the meaning.
Two verbs, and they point in opposite directions on purpose. One says remove, the other says defend. The entire skill is knowing which is which, and the trouble is that drag and meaning can look identical from the outside. Both take time. Both take effort. Both slow you down. A stranger watching you cook dinner and watching you walk six times to the other bathroom would see the same thing: a person spending effort they could have avoided. The difference isn’t in how much it costs. It’s in what the cost buys.
Which gives us the test, and I want you to actually use it, because a principle you can’t apply is just a nice feeling. When you’re standing in front of some effort and your instinct is to design it away, ask one question. Would removing the effort remove the point?
Run it on the pill lids. Would removing the effort of opening six bottles remove the point of taking my vitamins? No. The point is having the vitamins in me. The lids are pure drag, nothing is lost by killing them, so kill them. That’s a fix, and I’d fix it again tomorrow. Now run it on the handwritten note. Would removing the effort of writing it by hand remove the point? Yes, completely, because the effort was the point. It was the part that said you mattered enough for the slow way. So you protect it. Same question, opposite answers, and the question sorted them cleanly.
Here’s a cleaner way to hold it. Ask what the effort produces. If it produces connection, or presence, or craft, it’s meaning, and you guard it with your life. If it just produces cost, if you spend it and get nothing back but a done task and a little less of your day, it’s drag, and you’re allowed to be ruthless. The pill lids produce cost and only cost. The dinner produces connection. The conversation produces presence, the awful, necessary kind. Teaching someone a skill produces both connection and craft at once, which is why it’s worth protecting and why you’d be a fool to speed it up. If removing the effort would cheapen the thing, the effort stays. Full stop.
I’m laboring this because there’s a failure mode here that’s easy to walk into, and it’s the exact failure mode of a person who read a book about friction and took it too seriously. You get good at this. You start seeing drag everywhere, because it is everywhere, and the seeing feels great. And if you’re not careful, the lens quietly widens until you’re optimizing the texture right out of your own life. You batch the meals until no meal is ever cooked for anyone. You template the birthday message. You rush the goodbye because there’s a faster way to say it. You get so good at removing effort that you start removing the effort that was the whole reason you’re alive. And the terrible part is it’ll feel like progress the entire time, because every individual cut looks like a win. You’ll have a beautifully frictionless life and you’ll wonder why it feels like nothing.
A perfectly frictionless life would be a thin one. I believe that as much as I believe anything in this book. The friction I’ve been teaching you to hunt is the friction that stands between you and your life. It was never the friction that is your life. A day with every rough edge sanded off isn’t a rich day. It’s a smooth, empty one, and smooth and empty is not what any of us actually wants when we’re honest about it. We don’t want a life with less in it. We want a life with less junk in it, which is a completely different request.
And that, finally, is why we bothered with all the rest of it. Go back and count what this book has spent its pages on. The pill box, the cash run, the templates, the knowledge bases, the tools that erase whole categories of work, the two Vernons, the pile turned into assets. Every bit of it was drag removal, and drag removal was never the goal. It was clearing. You don’t clear a field because you love bare dirt. You clear it because you want to plant something, and the weeds were in the way. Every hour I’ve helped you claw back from the undone list and the workaround tax and the background hum was an hour meant for something. Not for doing more errands faster. For the dinner. The walk. The conversation you keep not having. The thing worth teaching slowly. The work that’s actually yours to do and no one else’s.
That’s the deal, and I want it clear before we go on to the last few chapters, because the rest of Part Six is about what the friction was stealing and how to get it back. All that ruthless, joyful, slightly obsessive fixing was in service of one thing, and it wasn’t efficiency. It was room. You reduce the friction that costs you nothing to keep, so that you can afford the friction that’s worth everything. You automate the drag so you have the time and the attention and the plain human energy to protect the meaning. That was the whole point of the whole thing. I just needed you to have it in your hands before we finished.
For a long time I thought my problem was that I had too much to do. I had lists everywhere, on my phone, in notebooks, in my head at two in the morning. And the more I looked at all of it, the heavier the present felt. Not because I was working on any one of those things right that second, but because all of them were sitting there at once, humming, reminding me they existed. That is the strange thing about a backlog. It taxes you the whole time you don’t get to it, not just when you finally do. The task is finite. The weight of not doing it isn’t.
I want to give that feeling a target, and the target is a strange-sounding one. I call it getting to zero.
Let me say immediately what zero does not mean, because if you hear it wrong it sounds insane. Getting to zero does not mean finishing everything in your life. You are never going to finish everything in your life. There is no version of a full, engaged, ambitious life where the list is empty and stays empty, and if someone is selling you that, they are selling you a fantasy that will only make you feel worse. Zero is not about completing every task that could ever exist. Zero is about something much more reachable, and much more useful. It’s about deciding what actually belongs in your active system, and getting everything else out of it.
Here is the distinction that changed how I think about all of this. Most of our lists feel infinite. And they feel infinite because we never defined what “done” was. Think about the difference between two piles. One pile is “everything I could conceivably ever want to accomplish.” That pile has no bottom. You will never reach the end of it, because the moment you clear an item, life hands you two more, and the pile was never designed to be finished in the first place. The other pile is “the specific, named things I have actually committed to doing right now.” That pile has a bottom. You can see the edge of it. You can, in principle, reach it. Those two piles produce completely different feelings even if they contain some of the same items, because one is an open-ended obligation with no exit and the other is a defined amount of work with a visible finish line. A list you can actually reach the bottom of is a different psychological object than one you can’t. The infinite list is a source of dread. The finite list is just a to-do list.
So most of the relief people are looking for isn’t in doing more. It’s in drawing an edge. It’s in taking that formless, bottomless “everything” and turning it into a bounded “this.” And drawing the edge is a design move, not an effort move. You don’t work your way to zero by grinding harder. You get there by deciding what counts.
Which brings me to the actual work, and it’s simpler than you’d think. Getting to zero is mostly a sorting job. You go through your open loops, all the half-things and meant-tos and someday-maybes, and for each one you make a single decision. There are only a handful of choices, and once you see them laid out, you realize you’ve been avoiding making the choice at all. That avoidance is exactly why the pile never shrinks.
For each open loop, you decide one of these. You do it, if it’s small enough that finishing it is cheaper than tracking it. You define the next action, if it’s real and it’s staying but it’s been sitting there as a vague noun like “the garage” instead of an actual verb like “buy a battery for the remote” – because a vague item can’t be finished, only carried. You delegate it, if someone or something else should be holding it, because sometimes reducing the friction means handing the task off entirely rather than doing it or automating it. You delete it, if you’re honest that it’s never happening and it was never that important, and letting it go costs you nothing but the small sting of admitting it. Or you archive it, which is the one most people skip, and it’s the most freeing of the five.
Retiring things instead of deleting them, which I’ve leaned on before, belongs here just as much. A lot of what clogs an active system isn’t garbage and isn’t urgent. It’s fine, it’s maybe-someday, and the reason it never leaves your list is that deleting it feels like a small betrayal and doing it isn’t realistic right now. So it just sits in the active pile forever, taking up psychic space, making the present feel more crowded than it is. Archiving solves that. You move it somewhere out of the active system, a “someday/maybe” list, a folder, a labeled box, wherever, and you tell yourself the truth, which is that it’s parked, not abandoned. You haven’t decided never. You’ve decided not now, and you’ve moved it out of the way so it stops taxing you every time you look at your list. The past should not charge rent forever, and neither should the maybe-future. Retiring an item is how you stop paying the rent without having to burn the house down.
Let me make this concrete with two of mine, one at home and one at work.
The home one is my email inbox, which for years was less a place I read messages and more a monument to everything I’d half-dealt-with. Thousands of messages, all “active,” in the sense that they were all sitting in the same undifferentiated pile with no edge to it. And every time I opened it, I paid a little tax, because the inbox was silently telling me it contained things I owed people, and I couldn’t tell which. When I finally sorted it, I wasn’t trying to answer every email ever sent to me. That’s the infinite list, and it has no bottom. I was doing the five decisions. The ones that needed a real reply, I replied to or turned into an actual task with a next action. The ones that were reference, receipts, confirmations, things I might want later, I archived, out of the active view and searchable if I ever need them. The ones that were nothing, newsletters I’ll never read, threads long dead, I deleted without ceremony. And a handful I delegated, forwarded to the person who should actually own them. What was left, the true active set, turned out to be small. Not zero messages. Zero unsorted ones. Every remaining thing was there on purpose, and I knew what each one was. That’s the real definition of inbox zero, and it has almost nothing to do with the number in the corner. It’s knowing that what’s in front of you is everything that’s actually in front of you.
The work one is a folder of “someday” projects, ideas I’d started and parked, business things I meant to build, a couple of tools I’d talked about for years. For a long time that folder functioned as a low-grade guilt machine. Every project in it was an open loop, humming, and because they all lived together in one undifferentiated “stuff I should do” pile, they all felt equally alive and equally unfinished, which meant the whole set weighed on me all the time. Sorting it was the same five decisions. A few I defined the next real action for and pulled into the active system on purpose, because I’d actually decided to do them. Most I archived honestly, wrote down what the idea was so I wouldn’t lose it, and moved it out of the active pile with a clear conscience. And a couple I finally admitted I was never going to do, so I deleted them, and the world did not end. The pile didn’t get finished. It got sorted. And the difference in how the folder felt afterward was not proportional to how much I’d actually done, because I hadn’t done much. It was proportional to how much clearer the edge had become.
That’s the thing I most want you to take from this. The relief of zero is not the relief of an empty life. It’s the relief of a defined one. Zero isn’t emptiness, and it was never supposed to be. Zero is knowing that what’s in front of you is everything that’s actually in front of you, that there is no shadow list, no vague hum of forgotten obligations lurking behind the one you can see. When your active system contains only the things you’ve decided are active, and everything else has been done, delegated, deleted, or honestly retired, the background noise turns off. You stop carrying the open-ness of a hundred things at once. You’re left holding a finite, visible, reachable set, and a finite set is something a person can actually face.
You will not get there once and be done, and I don’t want you thinking of this as a heroic cleanout you do a single time. Things drift back into the pile. Life keeps handing you loops. The move isn’t to reach zero and freeze it. The move is to make the sorting a habit, so the active system stays honest and the edge stays drawn. Every so often you pass back through, and for each new open loop you make the one decision you were avoiding. Do it, define it, delegate it, delete it, or retire it. Five choices, one per loop, and the pile stops being infinite the moment you start deciding.
Getting to zero was never about having nothing left to do. It’s about knowing exactly what you’ve chosen to carry, and setting down everything you haven’t. And it turns out that’s most of what peace of mind actually is. Not an empty desk. A clear one.
When you fix a pothole, you get the drive back. That much is obvious. The few seconds you used to spend swerving are yours again, every trip. If that were the whole story, this would be a book about saving time, and there are already plenty of those.
But something else happens on that road, something quieter and much bigger, and it took me a while to notice it. Once the pothole is gone, you stop bracing for it. You stop scanning the asphalt a hundred feet out. You stop holding, in the back of your mind, the small standing instruction to slow down right about here. The seconds were never the expensive part. The expensive part was the attention the pothole occupied even when you weren’t driving. It sat there in your head, taking up a slot. The day you fixed it, that slot came back too.
That returned slot is what I want to talk about, because it has a name, and the name is capacity. Reducing friction gives you capacity, and if you think capacity just means free time on the calendar, you will miss almost everything that matters about it. It is more than minutes. It is mental space, the room to think a thought all the way through without something tugging at your sleeve. It is emotional space, the relief of not carrying a dozen half-open loops that hum in the background. It is decision space, the fresh energy you have when you are not spending it re-deciding things you already settled. It is creative space, the room a new idea needs to show up, which it will not do in a crowded room. And it is strategic space, the altitude to look at the whole map instead of the next three feet of road. Removing the drag frees all of that. It frees your attention, and your attention is the thing everything else is made of.
Here is why that distinction is not just a nice way to put it. If capacity were only time, then a friction fix that saves you five minutes a day would be worth exactly five minutes a day, and no more. But that is not how it feels when you actually clear one. Clearing a small, long-carried thing feels wildly out of proportion to its size. You fix the garage remote, a five-minute job, and you feel lighter for a week. That is not because you got five minutes back. It is because you got the slot back, the little bit of you that had been quietly assigned to working around a dead battery. Friction does not just cost you the seconds at the pothole. It rents space in your head the whole time in between. When you fix the road, you get the room back, not just the time.
Now, what is the room for. This is the question the whole book has been circling, and it deserves a real answer, because it is easy to give a small one.
The small answer is that you use the capacity to do less. Fewer errands, a lighter list, a calmer week. That is real, and on a tired day it is enough, and I am not going to talk anyone out of it. But it is not the point, and if it is all you take from this book, you have taken the least interesting part. The point of clearing the drag was never to do less. It was to become able to attempt what was out of reach before.
Because here is what I have watched happen, in my own life and in the businesses I have built. When you reduce the friction under a thing, you do not just make that thing easier. You change the math on a whole category of other things you had quietly filed under “not worth it.” A project that would have taken forty hours of grinding drudgery is an easy no. The same project, once the drudgery is automated down to four hours of the part only you can do, is suddenly a yes. Nothing about your ambition changed. What changed is the price. Reducing friction lowers the price of doing hard things, and when the price drops far enough, things that were permanently impractical cross over into worth doing. That is the real gift. Not a shorter list, but a longer reach.
I have started to think of it as the difference between the projects you can afford and the projects you can’t. Every ambition has a price, and the price is not mostly money – it is friction: the unfamiliar part, the tedious part, the part you dread, the forty times you will have to do the boring setup before you get to the good work. Most of what we call “someday” is not something we have decided against. It is something we have priced out. It sits on the far side of a wall of friction we have not been willing to climb. Lower the wall, and someday moves. It gets closer. Some of it becomes now. I spent years believing certain projects were simply beyond what one person with a full plate could do, and I was right, at the old price. I was wrong that the price was fixed.
Which brings me to the trap, and it is a real one, so let me name it plainly. Reclaimed capacity does not stay reclaimed on its own. Freed time is not self-directing. Clear a slot in your week or your head, and if you have not decided in advance what it is for, it will refill – and it will refill with the two things that flow in most easily: new friction and busywork. New friction, because life keeps generating potholes and you will drift right back to swerving around them. Busywork, because an empty slot feels uncomfortable and the fastest way to make the discomfort stop is to cram it with small, urgent, low-value motion that lets you feel productive while you accomplish nothing you would have chosen. I have done this. I have automated my way to a wide-open afternoon and then watched myself fill it with email I did not need to answer and tidying that did not need doing, and looked up at five o’clock having spent the very freedom I worked to create on nothing at all.
That is the whole game. Capacity leaks. It leaks silently, and it leaks toward whatever is easiest to pour in, which is almost never what you actually wanted the space for. Reducing friction opens the room. It does not furnish it. If you do not decide what goes in, the room does not stay empty. It fills with junk, and you will have done all that work to trade one kind of clutter for another.
So the move is simple to say and it is the only real discipline in this chapter: decide, in advance, what the capacity is for. Before you clear the slot, name what will go into it. Not vaguely, not “I’ll be less busy,” but specifically, the way you would name a destination before a drive. This project. That relationship. That thing I have been meaning to build for three years. When you attach the reclaimed space to something that matters before the space exists, you give it somewhere to go, and it goes there. When you don’t, it leaks. The naming is what turns saved time into spent-well time. It is the difference between clearing a table because you like the look of an empty table and clearing it because you are about to put something on it that you care about.
Let me show you both ends of that, because it works small and it works large.
On the personal side, I think about the hours I used to lose to the ordinary machinery of running a life, the errands and refills and small recurring decisions that each cost almost nothing and together cost a great deal. As I have clawed those hours back – one fix at a time – the temptation has been to just enjoy the slack, and some of it I do. But the piece I decided on in advance is time with the people I will not always have time with. That is the thing I aimed the capacity at before I had it, so that when a Saturday opened up, it did not quietly fill with a trip to the hardware store I could have batched. It filled with the thing I had already named. The friction reduction was never really about the errands. The errands were just what stood between me and the reason I was clearing them.
On the work side, the capacity has made room for projects I could not have attempted before, not because I lacked the ambition but because I could not afford the friction. I have spent years running a business where every good idea had to be weighed against the plain reality of who was going to do the tedious ninety percent of it. The honest answer was usually no one, so the idea died. As I have driven that tedious ninety percent down toward something a system handles, the calculation has flipped. Bigger builds have become practical. Things I had filed under “wonderful, and never going to happen” have moved onto the actual list, and a few onto the actual calendar. I am not going to retell those projects here. Some of them you have already met earlier in this book, and one of them – the one about leaving something behind for the people who come after me – I care about too much to summarize. I will just say that it lives in the space friction reduction opened, and it would not exist in a life that was still paying full tax on the road. The capacity did not make me more ambitious. It made my existing ambition affordable.
That is the reframe I want you to leave this chapter holding. We tend to justify friction reduction by pointing at the drudgery it spares us, and that is fine, but it undersells the whole enterprise. You are not clearing the road to travel less. You are clearing it to travel further, to places you had written off as too far. The drag was never just costing you minutes. It was quietly setting the ceiling on what you believed was possible, and every fix you make lifts that ceiling a little.
So when you free up the next slot, and you will, do not let it leak. Stand in front of the open space for a second and decide, on purpose, what it is for. Name the thing you have been pricing out. Then aim the capacity straight at it. That is how the small fixes add up to a large life instead of just a tidy one, and it is the whole reason we bother clearing the road at all. Not to do less. To finally have room for the things you were meant to do.
Let me ask you a question I had to ask myself, and it stung a little when I did.
If you already know you’re going to do the thing, and you already know how good it’s going to feel when it’s done, why on earth would you wait?
I don’t mean that as a scold. I mean it as an honest piece of arithmetic, because when I finally sat down and did the math on my own delays, the answer was worse than I expected. Take one of those projects I’d been carrying for years. When I finally cleared it, the relief was enormous, way out of proportion to the work involved. And the very first thing I felt – right underneath the relief – was a small, sheepish thought: that feeling was available the whole time. I could have had it two years ago. The fix didn’t get easier while I waited. It didn’t get harder either. It just sat there, the same size it had always been, while I paid to carry it.
That’s the whole chapter, so let me slow down and lay it out plainly.
Back in the carrying-tax chapter, I made the case that a deferred task costs you more than the fix. You pay the fix once, and you pay a second, quieter tax the entire time it stays undone. This chapter is about the obvious thing that follows from it, the thing I somehow managed to miss for most of my adult life.
Here it is. The fix costs the same today as it will a year from now. A flapper is a flapper. A battery is a battery. The paywall I couldn’t build in 2023 was the same paywall I couldn’t build in 2024, and when it finally got built it took an afternoon either way. The size of the job does not shrink because you waited. Waiting does exactly one thing: it delays the relief while the tax keeps running. You don’t get a discount for procrastinating. Doing the fix now is just a lane closure – cones out for an afternoon, then a smooth road – while putting it off keeps the rough patch open, billed daily, for as long as you drag it out.
Which means delay is close to pure loss. Not a trade-off, not a “maybe later is fine,” but loss. You pay more and you get the good part later. Once I saw it in those terms I couldn’t unsee it, and it changed the rule this whole book is built on.
You know the rule by now. If something slows you down more than once, fix it. I want to add one word to it here, and the word is sooner. If something slows you down more than once, fix it, and fix it sooner, because the fix costs the same either way, but the carrying costs more every single day you wait. That’s the version I’d tape to the mirror now. The old version tells you what to do. This one tells you when, and the when turns out to matter almost as much.
Now I have to be careful here, because “do it sooner” can be twisted into something I don’t believe in at all, and I’ve watched people twist it. It is not “do everything immediately.” It is not a productivity frenzy, not a challenge to move faster for its own sake, not permission for the little voice in your head to start cracking a whip. If you take this chapter as an order to sprint through your life, you’ve heard the opposite of what I’m saying, because the goal was never speed. The goal is to breathe easier. Speed is just the accident that sometimes happens on the way there.
Here’s the distinction that keeps it honest. “Do it sooner” only applies to things you have already decided you’re going to do. It is not about taking on more. It’s about closing the gap between the deciding and the doing. There’s usually a long, quiet stretch between the moment you commit to something and the moment you actually finish it, and that stretch is where the tax lives. It’s where the hum comes from. Doing it sooner means shrinking that gap. It does not mean saying yes to more things so you can have more gaps to shrink. If anything, this chapter assumes you’ve already done the hard work of the getting-to-zero chapter, where you figured out what genuinely belongs in your active system in the first place. First you decide what’s actually yours to do. Then, and only then, you close those loops promptly. Deciding to do less is still very much on the table. This is about the things that survived that cut.
So picture the two states you can live in.
In one, there’s that low background hum going all the time. It’s the sum of every open loop you’re carrying, every “I really should,” every project parked at ninety percent, every small annoyance you’ve been stepping over. No single one is loud, but together they’re a drone you’ve stopped consciously hearing. That’s the weight of the undone, and most people carry it as their normal.
In the other state, that drone is mostly off. Loops get noticed and closed while they’re still small, before they’ve had months to build up. The list is short and it’s real. You’re not white-knuckling your way through a backlog, you’re just living with a quieter head. That’s the state I want you to spend more of your life in, and the way you get there isn’t one heroic weekend of clearing everything. It’s making quick resolution your default, one loop at a time, until closing things promptly is simply how you operate rather than a special effort you have to summon.
Because here’s what I finally understood about why finishing feels so good, and it connects the whole thing. The relief you feel when you close a loop is not proportional to the size of the task. It’s proportional to how long and how loudly that loop was humming. That’s why fixing the garage remote, a job that objectively did not deserve any emotion at all, felt weirdly wonderful when I finally did it. I wasn’t relieved about the battery. I was relieved that a thing which had been quietly open for months was finally, actually closed. You were never carrying the task. The task is tiny. You were carrying the openness of it, the fact that it sat there unresolved, and openness is heavy in a way that has almost nothing to do with the weight of the actual work.
Once you know that, the case for doing it sooner stops being about efficiency and becomes about something better. Every week a loop stays open is a week you paid the hum for nothing, since you were going to close it eventually anyway. Close it sooner and you don’t just save the tax, you move the relief forward. You get to spend those weeks in the quieter state instead of the droning one. And unlike the friction itself, which compounds against you, this compounds for you. Each loop you close promptly is one less voice in the drone. Do it enough and the baseline itself shifts. You’re not calmer because you finished one thing. You’re calmer because you’ve stopped letting things pile up in the first place.
I’ll tell you the one enemy that undoes all of this, because it’s the one I still catch myself doing. It isn’t laziness and it isn’t a lack of time. It’s re-deferral. You notice the friction, you feel the flash of this again – and then you walk around the pothole one more time anyway. That’s the dangerous move, more dangerous than never noticing at all, because noticing and then re-deferring doesn’t just leave the loop open. It recharges it. You’ve now confirmed to yourself that the thing needs doing and chosen, in the same breath, not to do it, and that little act of walking past a thing you just admitted was a problem is its own small tax on your self-respect. The meta-moment is only half the machine. Notice it, then resolve it soon. Noticing without resolving is just a more articulate way of stepping over the same board.
So the practical shape of it is simple, even if it isn’t always easy. When you catch the flash, when you hear the this again, treat it as a two-part signal, not one. The first part says there’s a loose board here. The second part, the one we usually ignore, says close it while it’s small, before it has time to start humming. You don’t have to do it in that exact instant. Sometimes you genuinely can’t, and forcing it turns fix-it mode into just another kind of stress. But you do have to give it a real when, and the real when should be soon, and “soon” should not quietly slide into “someday” the way it always has before.
I keep coming back to the plainest version of this, because it’s the truest thing I know about the whole subject. You are going to feel the relief eventually. You’ve already decided the thing gets done, so the good part is coming no matter what. The only real question left is how long you’re willing to pay rent on the weight of it before you let yourself have that relief. And when you put it that way, the answer gets embarrassing fast, because there’s no good reason to keep paying. The dread doesn’t protect you from anything. The waiting doesn’t make the job smaller. The hum doesn’t serve you.
The relief you keep promising yourself for later is available a lot earlier than you think. That’s the part I most want you to walk away with. All those good feelings you’ve filed under “someday” – the lightness, the quiet, the sense that you kept a promise to yourself – they aren’t off in some future where you’ve finally got your act together. They’re sitting right on the other side of loops you already intend to close. Move the closing forward and you move the feeling forward with it.
Friction compounds against you if you let it. But this compounds the other way, into calm. So don’t wait for the relief to arrive on its own schedule. Go get it sooner. You’ve earned the quieter head, and it’s closer than it looks.
We started this book on a staircase, so let me take you back there for a minute. Phil Dunphy hits the loose board, grabs the rail, mutters his line, and keeps walking. Every episode, for eleven years. By now you know why it stuck with me. It isn’t that he doesn’t notice. He notices perfectly, every single time. It’s that noticing a thing and fixing a thing are two completely different acts, and almost none of us ever make the jump from the first to the second.
I want to leave you with the one question that makes the jump for you. It’s the question I ask myself now before I fix anything at all, and it has quietly reorganized how I spend my days. Before you deal with whatever is in front of you, before you swerve around the pothole one more time, stop for a second and ask: is this going to happen again?
That’s it. That’s the whole hinge. If the answer is no, if this is a genuine one-off, then just handle it and move on. Not everything needs a system, and a person who builds a system for every single thing is building themselves a new kind of prison. But if the answer is yes, if this is a thing that is going to keep coming back, then you are standing at a fork you probably didn’t know was there. You can do the task, which solves this one instance and leaves the next hundred exactly as expensive as this one was. Or you can improve the system, which costs a little more right now and makes every one of those next hundred cheaper.
That fork is the whole book in a single choice. It’s the difference between completing a task and improving a system. Completing a task feels productive, and it is. You cleared the thing. But you cleared exactly one, and the road that generated it is still there, still producing the same task tomorrow, still collecting the same tax. Improving the system feels slower and less satisfying in the moment, because you don’t get the clean little hit of “done.” What you get instead is that the thing stops generating work at all. One of those is addition. The other is multiplication, and multiplication is the only math that ever gets you ahead.
So here’s the rule I want you to carry out of this book, the sharper cousin of the one we opened with. When something is going to repeat, don’t just survive this instance. Make the next hundred times easier than the last ten. That’s the standard. Not “get through it.” Not even “get through it a little faster.” Make the next hundred easier than the last ten, and then go collect the difference for the rest of your life.
I’ve watched this play out at every scale, and the shape is always the same. A client emails a question, and I can answer that one email in four minutes, which feels like the responsible thing to do. Or I can notice that it’s the ninth time someone has asked me a version of that question, write the answer down once, put it somewhere people can find it, and never type it again. The four-minute answer is completing a task. The written answer is improving a system. It quietly serves the tenth person, and the fiftieth, without me in the room at all. Same fork on the vitamins, same fork on the garage remote, same fork on a project parked for two years. The scale changes and the choice doesn’t. Every repeated question is a broken system, and every repeated annoyance is a road asking to be paved. Once you see the fork, you can’t unsee it, and you start taking the multiplication branch more often than you used to – which is all the book was ever asking of you.
Which brings me, finally, to the question I planted back in the chapter on the carrying tax and have been letting sit ever since. The whole book has really been circling it. Here it is one more time, plainly: how many times am I willing to pay this tax before I fix the road? Because that is the actual choice, every time, whether you name it or not. You are not choosing between paying the tax and not paying it. You already have to get up those stairs. You are choosing between paying it once, in a lump, to fix the road – or paying it in small quiet installments forever. We almost always pick forever, because forever doesn’t send a bill. It just withdraws a little every day, from an account we never check.
I picked forever for years. I paid the six-lid vitamin tax every morning until I bought a pill box. I paid the ATM tax every Saturday until I started pulling a month at once. I walked to the other bathroom for weeks over a flapper, and I choreographed an entire daily dance around a dead garage remote that cost less to fix than one performance of the dance. And the expensive ones, the ones that actually hurt, were the projects I believed in and left parked at ninety percent because the last slice was something I didn’t know how to build. I paid the carrying tax on those for years. Not the cost of finishing them, which never changed. The cost of walking around them, every day, knowing they were still there.
Here is the difference between all of that and Phil Dunphy, the only difference that has ever mattered. It isn’t that I’m smarter, or more disciplined, or that I finally found the right app. It’s that this time I actually fixed the step. That’s all. The gap between the person who mutters “gotta fix that” for eleven years and the person whose stairs work is not a gap in character. It’s a single, unglamorous act, repeated: catching the flash of “this again,” and treating it as a cue instead of a feeling. You already notice. You’ve always noticed. The book was never trying to make you see your loose boards. You could list them right now. It was only ever trying to move you the short, hard distance from noticing to fixing.
And I want to be honest about what’s on the other side of that distance, because it’s the part I underestimated for most of my life. I thought fixing these things was about efficiency, about saving minutes, and I couldn’t get excited about saving minutes. It turned out not to be about the minutes at all. When I finally cleared the projects I’d been carrying, the feeling wasn’t “I’m so efficient now.” It was relief. A weight I’d stopped being able to feel, because I’d carried it so long it had become the baseline, lifted off. The guilt of the undone was never about being lazy. It was the quiet sense that I’d been breaking small promises to myself, over and over, the promises I made when I said “someday” and saved the box. Fixing the friction is how someday finally arrives. It’s how you keep the promise. And that feeling, the freeing one, is available to you sooner than you think. You’re going to feel it eventually anyway, on the day you finally do the thing. The only real question is how much carrying tax you’re going to pay before you let yourself feel it. So don’t wait for it to arrive on its own. Go get it sooner. Make quick resolution your default, and you’ll spend far more of your life breathing easy and far less of it humming with the weight of what’s still open.
That’s what all of this is for, and I don’t want the point to get lost in the tactics. Reducing friction was never the goal. It’s the clearing of ground. Every drag you automate, every pothole you fill, every repeated question you answer once and for all, gives you back a little capacity. Time, yes, but more than time. Attention. Patience. The mental room to think a real thought instead of managing another logistics problem. And that capacity is not meant to be spent on more efficiency. It’s meant to be spent on the things that don’t scale and shouldn’t, the effortful things that are effortful precisely because they matter. Which is why the line I’ve come back to more than any other in this book is two halves, and the second half is the one that keeps the first half honest. Automate the drag. Protect the meaning. Clear away the resistance that adds nothing, so that you have something left for the resistance that is the whole point.
I mentioned early on that this is one of three books, and I’ll close the loop on that briefly, because they’re really one idea wearing three coats. Digitize Your Life is about removing the friction from your stuff, your memories, and your papers – the physical and digital weight of a life. Crystal Ball is about removing the friction from planning and deciding, the fog that sits between you and a clear next move. This book, Reducing Friction, is the principle sitting underneath both of them. Find the resistance, and design it out. That’s the whole engine. The other two just point it at particular corners of a life. If you take only one thing from any of the three, take this one, because it runs everything else.
So we end where we started, on a stair, which feels right. Somewhere in your house, or your calendar, or that folder you don’t open, there is a loose board you’ve been stepping over for a long time. You know exactly which one it is. You’ve muttered the line about it more times than you’d care to count. You’ve built a workaround so smooth you’ve almost stopped noticing it’s a workaround. And every time you step over it, some small part of you says the same three words Phil says, and then you keep climbing.
This time, ask the question. Is this going to happen again? And when the answer comes back yes, the way it almost always does, don’t step over the board.
Fix it. You’ll be amazed how much lighter the stairs feel once you do.
Everything in this book comes down to a small set of tools you can carry with you. They show up throughout the chapters. They are collected here so you can find them without hunting. Keep this page somewhere you will actually see it, which, if the book did its job, you now know how to do.
When something feels harder than it should, it is almost always one of these. Naming the type is half of removing it.
The fast diagnostic. Run it on anything that keeps costing you.
The book’s core method. Seven steps, in order.
When you decide to fix something, you do not have to jump straight to automation. Climb only as high as you need to.
The higher the rung, the less the task will cost you next time, and the more it costs to build. Match the rung to how often you will pay the tax.
Every friction you address ends in one of three places: eliminate it, make it easier, or make it automatic.
When you can feel the friction but cannot find it, look here: your environment (what is around you and how it is arranged), your process (the steps you take and their order), and your knowledge (what you know and whether you can retrieve it).
Sort any task into one of these, and what to do becomes obvious: work you should do (keep it, this is where your judgment belongs), work a system should do (build the system once, then let it run), and work that should not exist anymore (remove the category).
If something slows you down more than once, fix it.
Automate the drag. Protect the meaning.
↑ Top