<script data-pm-proxy="intercept"></script><?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Main Letter]]></title><description><![CDATA[Main Letter is a weekly note on getting real work done in a world that keeps inventing new ways to interrupt it.
]]></description><link>https://mainletter.substack.com</link><image><url>https://substackcdn.com/image/fetch/$s_!JDpc!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F970cfbdb-4fe7-4064-8681-c7b318376406_1254x1254.png</url><title>Main Letter</title><link>https://mainletter.substack.com</link></image><generator>Substack</generator><lastBuildDate>Fri, 04 Sep 2026 07:01:23 GMT</lastBuildDate><atom:link href="/__u/mainletter.substack.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Aman]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[mainletter@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[mainletter@substack.com]]></itunes:email><itunes:name><![CDATA[Aman]]></itunes:name></itunes:owner><itunes:author><![CDATA[Aman]]></itunes:author><googleplay:owner><![CDATA[mainletter@substack.com]]></googleplay:owner><googleplay:email><![CDATA[mainletter@substack.com]]></googleplay:email><googleplay:author><![CDATA[Aman]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Your second draft is where the writer actually shows up.]]></title><description><![CDATA[The first draft was a machine getting the thoughts out. The second is where the human takes over.]]></description><link>https://mainletter.substack.com/p/your-second-draft-is-where-the-writer</link><guid isPermaLink="false">https://mainletter.substack.com/p/your-second-draft-is-where-the-writer</guid><dc:creator><![CDATA[Aman]]></dc:creator><pubDate>Mon, 31 Aug 2026 12:04:15 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/b3629e04-06bf-47b6-a837-fa91f56be883_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><span>There is a common misunderstanding about how good writing gets made.</span></p><p><span>The misunderstanding is that writing happens in the drafting. You sit down. You write the piece. You clean it up. You publish. Under this model, the first draft is roughly the finished piece, minus some polish. The polish is cosmetic. The real work was the drafting.</span></p><p><span>Actually, the drafting is a completely different activity from the writing. The drafting is you getting the raw material out of your head and onto the page. It is a mechanical, roughly transcriptive process. It is what your brain does when you give it permission to say whatever comes to mind about a topic.</span></p><p><span>Almost nothing produced by drafting is actually good. It is not supposed to be. Its job is to give you something to work with. The writer does not show up during drafting. The writer shows up during the second draft, when you sit with the raw material and start making the decisions that shape a piece.</span></p><p><span>Most writers do not know this. They think the second draft is a proofreading pass. Which is why their pieces plateau at the level of &#8220;cleaned-up drafting.&#8221; They never made it to the actual writing stage. They just tightened the transcription and shipped it.</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://mainletter.substack.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="/__u/mainletter.substack.com/subscribe"><span>Subscribe now</span></a></p><h2><strong><span>What the second draft actually is</span></strong></h2><p><span>The second draft is where you decide what the piece is about.</span></p><p><span>Not in the general sense. In the specific sense. The first draft was you exploring the territory. By the end of it, you have some vague sense of the terrain, but you have not yet decided which parts matter, which parts to cut, which parts should be foregrounded, which parts should be structural, and which parts were just you thinking out loud on the way to the actual argument.</span></p><p><span>The second draft is where those decisions get made. It requires a different mode of attention than the drafting did. In drafting, you were generative. In the second draft, you are editorial. You are looking at your raw material as if a stranger produced it, deciding what it should actually be, and doing the work of transforming it into that.</span></p><p><span>This is the work most writers avoid, because it is more expensive than drafting. Drafting has flow. It feels good. It produces words. The second draft has friction. It requires cutting things you liked, restructuring paragraphs you were proud of, and confronting the fact that the piece you drafted is not the piece you should publish.</span></p><p><span>Writers who cannot make it through this friction publish first drafts with light polish. Which is why their work stays flat. Not because they lack talent. Because they never actually wrote the piece. They just transcribed themselves and shipped the transcription.</span></p><h2><strong><span>The specific work of the second draft</span></strong></h2><p><span>You read the draft as if someone else wrote it.</span></p><p><span>You notice which paragraph the piece actually starts in. Usually not the first one. The first one was warm-up. You cut it. The piece now starts where it should have.</span></p><p><span>You notice which claim is doing the load-bearing work. Usually it is not the one you thought you were making when you started. You reshape the piece around the real claim, cutting the material that was supporting the fake claim you thought you were making.</span></p><p><span>You notice which examples land and which examples were you searching. You keep the landing ones. You cut the searching ones. The piece gets shorter and sharper.</span></p><p><span>You notice where the language is coasting. Every sentence that is not earning its place is either rewritten to earn its place or removed. Nothing stays because it is neutral.</span></p><p><span>You notice what the piece is actually saying, versus what you thought it was going to say when you started. If those diverge, you restructure the piece around what it turned out to be about, not what you set out to write.</span></p><p><span>By the end of this pass, the piece is roughly two-thirds the length of the draft, dramatically sharper, and finally the piece you were trying to write.</span></p><h2><strong><span>The move</span></strong></h2><p><span>Take your last piece. Read it as if someone else wrote it. Do the second draft you never did.</span></p><p><span>Cut the opening. Find the real claim. Rewrite the paragraphs that are coasting. Restructure around what the piece actually became, not what you meant to write.</span></p><p><span>You will discover that the piece you published was not the piece you had. It was the piece minus the actual writing.</span></p><p><span>Do the writing next time.</span></p><div><hr></div><p><span>P.S. The 30-Minute Writer is the last piece of writing input I&#8217;d recommend for anyone stuck in this pattern - because it&#8217;s designed to end the input phase and start the output phase. Frameworks + a 30-day plan built for shipping, not studying. click </span><strong><a href="http://danstuff.gumroad.com/l/30-MinuteWriter">here</a></strong><span>.</span></p>]]></content:encoded></item><item><title><![CDATA[You cannot write well if you cannot sit alone.]]></title><description><![CDATA[Writing is done in a specific room, in a specific silence, that most modern lives are structured to prevent.]]></description><link>https://mainletter.substack.com/p/you-cannot-write-well-if-you-cannot</link><guid isPermaLink="false">https://mainletter.substack.com/p/you-cannot-write-well-if-you-cannot</guid><dc:creator><![CDATA[Aman]]></dc:creator><pubDate>Fri, 21 Aug 2026 12:03:47 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/933703fa-e6b9-4652-ad76-e200a9a2e854_1672x940.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><span>There is a physical requirement for good writing that nobody in the writing-tips industry names, because it does not sell.</span></p><p><span>You have to be able to sit alone, in a quiet room, without input, for extended periods, and let your mind do the slow work of composing sentences.</span></p><p><span>That is it. The whole prerequisite. Everything else, all the frameworks and techniques and rituals, is downstream of this one capacity. If you can sit alone with your thoughts for two hours and let the writing emerge, you will get better. If you cannot, you will not, no matter how much writing advice you consume.</span></p><p><span>Most people who want to be writers cannot do this. Not because they lack discipline. Because their nervous systems have been trained, for years, to reach for stimulation whenever attention wanders. Which is precisely the moment writing was supposed to happen. The wandering attention was the raw material. The reach for the phone consumed the material before it could become anything.</span></p><p><span>You do not have a writing problem. You have a sitting-alone problem. And no amount of craft work will fix a sitting-alone problem, because craft is what you produce during the sitting, not what makes the sitting possible.</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://mainletter.substack.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="/__u/mainletter.substack.com/subscribe"><span>Subscribe now</span></a></p><h2><strong><span>What the sitting actually looks like</span></strong></h2><p><span>You are alone. There is nothing to do except write. Your phone is elsewhere. The tabs are closed. The room is quiet. You have committed to being here for a specific length of time, regardless of what happens.</span></p><p><span>At first, nothing happens. You feel restless. You want to check something. You want to stand up. You want to remember suddenly that there was an email you were supposed to send. All of this is your nervous system trying to escape the specific state you have deliberately put it in.</span></p><p><span>If you stay, the escape impulses gradually subside. Your mind, denied its usual escape routes, begins to do the thing it can only do under these conditions. It starts composing. Slowly. Circling ideas. Trying phrases. Discarding sentences that do not work. Building something out of the attention that only becomes available when nothing else is competing for it.</span></p><p><span>This is where good writing comes from. Not from techniques. Not from frameworks. From this specific state, sustained over long enough for something to actually get made.</span></p><p><span>If you cannot reach the state, you cannot make the writing. And most people cannot reach the state, because they have trained themselves out of it, one small escape at a time, over years.</span></p><h2><strong><span>The specific damage of interrupted work</span></strong></h2><p><span>You cannot write well in fifteen-minute increments.</span></p><p><span>Not because fifteen minutes is not enough time to put words on a page. It is plenty of time for that. But writing that lands, writing that has any depth or specificity, requires a specific kind of sustained attention that takes about thirty to forty minutes to enter. Which means fifteen-minute writing sessions never get you into the state where the good writing happens. You produce surface-level output because you never got past the surface layer of your own attention.</span></p><p><span>The writers whose work you envy write in blocks. Long blocks. Not because they are more disciplined than you. Because they know that the first half of the block is warm-up, and only the second half is where the real work gets done. Which means you cannot get to the real work in a block that is shorter than the warm-up.</span></p><p><span>If your writing schedule consists of stolen fifteen-minute increments, you have been producing warm-up material. Constantly. Never reaching the state where the actual writing happens. Wondering why the work is not compounding, when the compounding requires an ingredient you have never provided.</span></p><h2><strong><span>The move</span></strong></h2><p><span>Block two hours this week. One session. Alone. Quiet. Phone in another room.</span></p><p><span>Sit down and write. Not to produce anything specific. Just to prove to yourself that you can still enter the state.</span></p><p><span>If you cannot make it through the first thirty minutes without escaping, that is your diagnostic. It is not a writing problem. It is a sitting-alone problem, and you need to rebuild that muscle before any other writing advice will do you any good.</span></p><p><span>Do this once a week. Extend it to three hours. Then four. Watch what happens to your writing.</span></p><p><span>You are not blocked. You have just forgotten how to be alone with your own mind for long enough to write something real.</span></p><p><span>Remember.</span></p><div><hr></div><p><span>P.S. The 30-Minute Writer is the last piece of writing input I'd recommend for anyone stuck in this pattern - because it's designed to end the input phase and start the output phase. Frameworks + a 30-day plan built for shipping, not studying. click </span><strong><a href="http://danstuff.gumroad.com/l/30-MinuteWriter">here</a></strong><span>.</span></p><p></p>]]></content:encoded></item><item><title><![CDATA[The first line is not an introduction. It is a filter.]]></title><description><![CDATA[Every reader who does not stop for the first line is a reader who was never going to stay.]]></description><link>https://mainletter.substack.com/p/the-first-line-is-not-an-introduction</link><guid isPermaLink="false">https://mainletter.substack.com/p/the-first-line-is-not-an-introduction</guid><dc:creator><![CDATA[Aman]]></dc:creator><pubDate>Mon, 17 Aug 2026 17:44:57 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/bb8c9df4-f8f2-4c5c-9489-da244c55ddc7_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><span>Most writers think of the first line as an entry point.</span></p><p><span>Something soft. A gentle way to bring the reader into the piece. Set the scene. Establish tone. Give them a warm handshake before the real work begins. Under this model, the first line is a doorway, and the reader passes through it politely on their way to the substance in paragraph three.</span></p><p><span>This model is completely wrong for how reading actually works now.</span></p><p><span>Your first line is not a doorway. It is a filter. Its job is not to gently welcome. Its job is to stop the reader who was going to leave anyway, and to lose the reader who was never going to read carefully. It is the specific mechanism by which your piece self-selects the audience that will actually read it. And a soft, welcoming, doorway-style first line is worse than useless, because it fails to do the filtering the piece needed.</span></p><p><span>Every reader who did not stop at your first line was a reader you were going to lose eventually. The first line is where the loss becomes efficient. If it does not filter, they leave in paragraph two, or three, or five. If it does filter, they leave immediately, and you have your remaining reader, ready to receive the actual work.</span></p><p><span>You have been trying to keep everyone. Which means keeping no one. Filter first.</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://mainletter.substack.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="/__u/mainletter.substack.com/subscribe"><span>Subscribe now</span></a></p><h2><strong><span>What a filter first line does</span></strong></h2><p><span>It commits.</span></p><p><span>It makes a claim, or a scene, or a specific move that the reader either wants to follow or does not. Not both. Both is what soft openers try to do, and both is why soft openers produce weak retention. A first line trying to appeal to everyone appeals to no one, because it does not commit to anything specific.</span></p><p><span>A filter first line commits. It says something specific enough that some readers will lean in and others will lean out. The leaning-in readers are your readers. The leaning-out readers were not going to stay. The first line just made the sorting fast.</span></p><p><span>Look at the writers you actually read. Their first lines almost never introduce anything. They drop you into the middle of something. A claim. A scene. A confrontation with an assumption. Something that requires you to decide, in three seconds, whether you are the kind of reader who wants what this piece is offering.</span></p><p><span>You have not been doing this. You have been trying to hold on to the leaning-out reader by softening the first line. Which loses the leaning-in reader in the process, because the leaning-in reader wanted commitment and got vagueness, and moved on to find a writer who would commit.</span></p><h2><strong><span>The math of filtering</span></strong></h2><p><span>A first line that keeps ten percent of readers with high engagement outperforms a first line that keeps forty percent with low engagement.</span></p><p><span>Not by a small margin. By an order of magnitude. Because the ten percent who stayed after a filtering opener are the specific readers who will finish the piece, share it, quote it, and come back. The forty percent who stayed after a soft opener are mostly going to leave in paragraph three anyway.</span></p><p><span>Your metrics have been misleading you. Retention through the first paragraph is not the metric that matters. What matters is retention with intensity through the whole piece, and intensity retention correlates inversely with soft openers. The pieces you envy, the ones that get quoted and forwarded, almost always had filtering first lines. That is not a coincidence.</span></p><p><span>The filter is not costing you readers. It is producing the right readers.</span></p><h2><strong><span>The move</span></strong></h2><p><span>Look at the first line of your next draft.</span></p><p><span>Ask yourself: does this line commit to anything specific? Would it produce a leaning-in or leaning-out response? Or is it a soft doorway, designed to be inoffensive to as many readers as possible?</span></p><p><span>If it is a soft doorway, rewrite it. Make it commit. Make it filter. Make it something that some readers will love and others will bounce off of, in the first three seconds.</span></p><p><span>You will feel like you are being too aggressive. You are not. You are finally doing the sorting the piece needed on your behalf, so the remaining work can be read by the specific people who wanted it in the first place.</span></p><p><span>The first line is not the beginning of the piece. It is the audition. Write it accordingly.</span></p><div><hr></div><p>P.S. If you want the specific system I use to actually produce work at this level, on a schedule, without waiting to feel ready - <strong><a href="https://danstuff.gumroad.com/l/30-MinuteWriter">The 30-Minute Writer</a></strong> is where I put it. Frameworks, idea engine, and a 30-day plan built for shipping.</p><p></p>]]></content:encoded></item><item><title><![CDATA[You don't need a to-do list. You need a "not this" list]]></title><description><![CDATA[Focus is not what you add. It's what you refuse.]]></description><link>https://mainletter.substack.com/p/you-dont-need-a-to-do-list-you-need</link><guid isPermaLink="false">https://mainletter.substack.com/p/you-dont-need-a-to-do-list-you-need</guid><dc:creator><![CDATA[Aman]]></dc:creator><pubDate>Sun, 02 Aug 2026 14:55:41 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/9abb7a26-2d28-452f-be4b-ce884c47ef78_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><span>uYou&#8217;ve been managing your life with an inclusive list.</span></p><p><span>Every task, every idea, every possibility, every commitment - added to a list, prioritized, re-prioritized, migrated to a new system when the old one got unwieldy. The whole apparatus is built around the same premise: more items, better sorted, will produce more output.</span></p><p><span>It won&#8217;t. It hasn&#8217;t. It&#8217;s not going to.</span></p><p><span>Because the problem was never that you couldn&#8217;t remember your to-dos. The problem is that the list is </span><em><span>inclusive by design.</span></em><span> It says yes to everything that arrived on your radar and asks you to sort by priority. Which sounds reasonable - except priority-sorting doesn&#8217;t remove anything. Every item stays on the list. Every item still occupies mental space. Every item is still, technically, a commitment your brain is tracking.</span></p><p><span>What you actually need is not another to-do list. It&#8217;s a </span><em><span>not this</span></em><span> list.</span></p><p><span>The specific catalog of things you have consciously decided you are not going to do - even though they&#8217;re reasonable, even though someone would judge you for not doing them, even though you might feel a small twinge of should about them. You looked at them. You said no. And now they&#8217;re not competing for space in your head.</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://mainletter.substack.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="/__u/mainletter.substack.com/subscribe"><span>Subscribe now</span></a></p><h2><span>Why inclusion feels safer</span></h2><p><span>Adding a task to a list feels like handling it.</span></p><p><span>You don&#8217;t have to decide about it right now. You logged it. It&#8217;s captured. You&#8217;ll get to it eventually. The list is doing the emotional labor of holding the item so you don&#8217;t have to consciously carry it.</span></p><p><span>But you </span><em><span>are</span></em><span> still carrying it. That&#8217;s the trick. Every item on your list is a small ambient commitment your brain is tracking, even if you&#8217;re not actively working on it. A hundred logged tasks is not neutral storage - it&#8217;s a hundred low-volume threads whispering at you, all day, requesting attention.</span></p><p><span>Meanwhile, a &#8220;not this&#8221; list has the opposite effect. Each item you consciously put on it </span><em><span>releases</span></em><span> mental space. You looked at the possibility, evaluated it, and closed the loop with a definitive no. It&#8217;s not sitting somewhere waiting for you to circle back. It&#8217;s off the board.</span></p><p><span>Every meaningful productivity gain comes from moving items off the board - not from optimizing how you manage the items on it.</span></p><h2><span>What belongs on a &#8220;not this&#8221; list</span></h2><p><span>Not just tasks. Categories of things.</span></p><p><span>The types of meetings you no longer take. The kinds of client work you&#8217;ve stopped accepting. The friend requests to catch up you politely never schedule. The projects with the wrong return profile. The commitments made under old versions of your priorities that never got updated when the priorities changed. The favors you keep saying you&#8217;ll do and never actually do.</span></p><p><span>Some of these are trivial. Some are structural. Both belong on the list - because their removal from your active consideration is where the mental space comes from.</span></p><p><span>The most productive people are not the ones with the best productivity systems. They&#8217;re the ones with the longest and clearest &#8220;not this&#8221; lists. They&#8217;ve done the hard work of subtraction. They&#8217;ve decided, on many fronts, that a whole category of thing is simply not happening for them anymore. Which frees their entire operating capacity for the small number of things that are.</span></p><p><span>You&#8217;ve been trying to be productive by adding better management to an ever-growing list. That&#8217;s not going to scale. Nothing scales that way. The only durable productivity gain is </span><em><span>elimination.</span></em></p><h2><span>The move</span></h2><p><span>Sit down today. Make a &#8220;not this&#8221; list.</span></p><p><span>Ten things. Doesn&#8217;t matter if they&#8217;re small (a specific type of meeting) or big (an entire category of work). Ten items you are consciously committing to </span><em><span>not doing,</span></em><span> effective immediately.</span></p><p><span>Then behave accordingly. When the type of meeting is proposed, decline. When the category of request arrives, redirect. When the specific favor is asked, offer an alternative that doesn&#8217;t require your time.</span></p><p><span>The list will grow. That&#8217;s the point. Every quarter, add ten more. Every year, forty items you&#8217;re no longer doing get subtracted from your operating space.</span></p><p><span>Compare that to a decade of tweaking your to-do system. One of these produces a life you can actually live. The other produces a very well-organized cage.</span></p><p><span>What are three specific things you&#8217;d put on a &#8220;not this&#8221; list today - if you gave yourself permission?</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://mainletter.substack.com/p/you-dont-need-a-to-do-list-you-need/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="/__u/mainletter.substack.com/p/you-dont-need-a-to-do-list-you-need/comments"><span>Leave a comment</span></a></p>]]></content:encoded></item><item><title><![CDATA[You're not busy, you're just bad at deciding]]></title><description><![CDATA[Every task on your list is a decision you deferred.]]></description><link>https://mainletter.substack.com/p/youre-not-busy-youre-just-bad-at</link><guid isPermaLink="false">https://mainletter.substack.com/p/youre-not-busy-youre-just-bad-at</guid><dc:creator><![CDATA[Aman]]></dc:creator><pubDate>Sun, 26 Jul 2026 15:25:28 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/ca17cc7e-7fa2-4594-a150-a8eeefa380be_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>You&#8217;ve been telling everyone you&#8217;re busy.</p><p>It&#8217;s the answer to every question. Why haven&#8217;t you called back? Busy. Why did the project stall? Busy. Why are you exhausted at the end of every week? Busy.</p><p>The word has become such a reliable shield that you&#8217;ve stopped noticing what it&#8217;s actually shielding.</p><p>Not your time. Your decisions.</p><p>You are not overworked in the way you think you&#8217;re overworked. You have the same twenty-four hours as every person who&#8217;s less overwhelmed than you. The difference isn&#8217;t the workload. It&#8217;s that they&#8217;ve decided what matters, and you haven&#8217;t. Which means everything on their plate is <em>chosen,</em> and everything on yours is <em>accumulated.</em></p><p>Chosen work is finite. Accumulated work is infinite. And infinite work makes you busy in a way that will never resolve, no matter how efficiently you execute.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://mainletter.substack.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="/__u/mainletter.substack.com/subscribe"><span>Subscribe now</span></a></p><h2>Why busyness feels like a workload problem</h2><p>Because when you haven&#8217;t decided what matters, everything on your list weighs the same.</p><p>The email that should take thirty seconds and the strategic decision that will define your next two years - same list. Same visual weight. Same claim on your attention. Your brain, faced with fifty equally-weighted things, does what any exhausted system does: it processes them roughly in the order they arrived, giving each one a fair share of the available bandwidth.</p><p>That&#8217;s the source of the drowning feeling. Not that you have too much to do. That you never sorted it. So everything is competing for the same slice of attention, and the strategic work loses to the urgent-feeling small stuff, and you end each day having answered emails while the thing that would actually move your life forward sits untouched for the eleventh week in a row.</p><p>You call this being busy. It&#8217;s actually being <em>unsorted.</em></p><h2>The decisions you&#8217;re avoiding</h2><p>Behind every overloaded to-do list is a small number of decisions you haven&#8217;t made.</p><p>The client you should let go, but haven&#8217;t. The project you should kill, but keep half-alive. The meeting you should stop attending, but keep showing up to out of politeness. The role you outgrew, but haven&#8217;t outgrown <em>out loud.</em> The relationship that&#8217;s costing you weekly bandwidth and giving you nothing in return.</p><p>Each of these is one decision. Each one, once made, would eliminate dozens of downstream tasks - the emails you wouldn&#8217;t have to answer, the follow-ups you wouldn&#8217;t have to do, the meetings you wouldn&#8217;t have to attend, the mental space you wouldn&#8217;t have to allocate.</p><p>You&#8217;re not deferring one task. You&#8217;re deferring the single decision that would eliminate ten of them.</p><p>The reason you keep deferring is simple: decisions cost something. The client fires back. The project stakeholder is disappointed. The meeting host takes it personally. Making a decision means owning the fallout of the decision. Not deciding lets you avoid the fallout - while paying an invisible tax in daily overwhelm.</p><p>You&#8217;ve decided the daily tax is cheaper. It isn&#8217;t. It&#8217;s just less legible.</p><h2>What decisive people actually do</h2><p>The people whose lives look calm and whose output is disproportionately good aren&#8217;t more disciplined than you. They&#8217;re not managing their time better. They haven&#8217;t found the right app.</p><p>They&#8217;ve made a small number of upstream decisions that eliminated whole categories of downstream work.</p><p>They said no to the client that would have been fine but wasn&#8217;t great - and now they don&#8217;t have to think about that client for the next year. They killed the project that was still mildly promising - and reclaimed the fifteen hours a week they&#8217;d been spending on it. They stopped attending the meeting that felt important but wasn&#8217;t - and got four hours of thinking time back per month.</p><p>None of this looks like productivity from the outside. From the outside, they just look like they have less on their plate. Which they do - because they decided to have less on their plate. Not because their life is easier. Because they were willing to make the decisions you&#8217;re not.</p><h2>The move</h2><p>This week, make one decision that eliminates ten tasks.</p><p>Not a scheduling optimization. Not a new to-do system. A decision. The kind that produces uncomfortable emails, awkward conversations, or the specific silence of no longer being copied on a thread you shouldn&#8217;t have been on for two years.</p><p>You&#8217;ll feel worse for a day. You&#8217;ll feel dramatically better for a year.</p><p>Being busy is not what happens when you have too much to do. It&#8217;s what happens when you keep avoiding the decisions that would change what you have to do.</p><p>Stop being busy. Start being decisive.</p><p>What&#8217;s the one decision you keep deferring - the one that would eliminate half your workload if you made it this week?</p><p>&#8211; Dan</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://mainletter.substack.com/p/youre-not-busy-youre-just-bad-at/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="/__u/mainletter.substack.com/p/youre-not-busy-youre-just-bad-at/comments"><span>Leave a comment</span></a></p>]]></content:encoded></item></channel></rss>