All I Want Is Everything

The Problem With Wanting Everything

I spent three years building a morning routine that covered sleep tracking, cold exposure, intermittent fasting, journaling, meditation, and a 47-page reading list before I realized most of it was just anxiety in disguise. The phrase All I Want Is Everything isn't a philosophy. It's a description of a specific failure mode that shows up in productivity culture, software design, and basically every area where people try to optimize their lives. When you actually sit down and map out what "wanting everything" looks like in practice, you get a list that's both hilarious and deeply uncomfortable. You want to be healthy but also eat cake. You want to save money but also travel constantly. You want deep relationships but also complete autonomy. You want to work hard but also never stress. The list fills a page, and every item on it contradicts at least two others.

Why This Pattern Is So Persistent

The reason this pattern survives isn't because people are irrational. It's because the alternative feels worse. Admitting you can't have everything requires a kind of grief work that most systems around us don't teach you to do. You grow up in a culture that treats constraint as failure. The business world rewards expansion. Social media rewards abundance. Even self-help books often just repackage the same desire with different language. I ran into a specific edge case with a client last year that made this clear. They were building a project management tool and kept adding features because users asked for them. Kanban boards, Gantt charts, time tracking, resource allocation, integrations with every major platform. Two years in, the codebase was 800,000 lines, the average user only touched 3 of the 47 features, and the support tickets were all about bugs in features nobody used. We spent six weeks stripping it down to just the three features that mattered. The product got faster, the bugs dropped by 70 percent, and revenue actually went up because people could understand what the thing did. The counterintuitive part nobody tells you is that constraint isn't the enemy of quality. It's the primary input variable. Every system with maximum feature density has a specific failure mode where the complexity itself becomes the product you're selling. You're not selling functionality anymore. You're selling the illusion that you've solved everything.

How To Actually Work With This Impulse

There's no clean framework for this because the impulse itself is the problem. What actually works is a combination of deliberate frustration and forced prioritization. I use a method that feels almost crude: write down everything you want, then force yourself to pick three. Not the top three priorities. Just three. If you can't narrow it to three, you haven't actually thought about it yet. The second step is weirder but more important. You have to schedule time for the things you're choosing not to do. This sounds backwards. If you're not doing something, why schedule it? Because the absence of a plan for your refusals means they'll happen to you anyway. When I commit to reading two books a month instead of trying to read everything, I block out Saturday mornings for that. When I commit to one creative project instead of five, I schedule the abandonment of the other four as a formal decision. The scheduling makes the constraint real instead of just theoretical. A rough timeline for this process depending on your situation is two to four weeks for the initial triage, then ongoing maintenance. The first week is usually miserable because you're sitting with the discomfort of not having a plan for every possibility. By week three, most people report that the mental load drops significantly. The relief comes from not having to decide everything every day.

What This Approach Doesn't Fix

I need to be blunt about the limitations here because the self-help industry rarely is. This doesn't solve structural problems. If you're in a job that requires you to do everything, no amount of personal prioritization will fix that. If you're a small business with twelve competing stakeholders, you can't just choose three things and ignore the rest. The method works best when you have actual agency over your constraints, which is a smaller circle of people than you might think. There's also a specific demographic where this backfires noticeably. High-performers who have built their identity on being the person who does everything tend to use this framework as another optimization tool rather than a genuine constraint. They create elaborate systems for choosing their three things and then judge themselves harshly when they slip. I've seen this turn a genuinely useful practice into another source of anxiety. The difference between using this as a tool and using it as a whip is usually whether you're allowing yourself to actually stop. If you're in a situation where you genuinely cannot reduce your scope, the alternative is to focus on system-level changes instead of personal ones. This means renegotiating expectations, restructuring workflows, or in extreme cases changing environments. The personal optimization approach assumes a level of control that simply doesn't exist for everyone. Acknowledging that isn't defeatist. It's accurate.

The practical tradeoff is that you will miss things. You will see opportunities pass by because they weren't in your three. You will feel a specific kind of FOMO that's distinct from regular FOMO because it's about your own choices rather than external pressure. This feeling usually decreases after about six weeks but it doesn't disappear. Some people find that acceptable. Others don't. There's no universal answer to whether that cost is worth it.

A Specific Case That Changed How I Think About This

Three years ago I was managing a team of eight developers and we had twelve concurrent projects. The leadership team insisted we could do everything because "that's what excellence looks like." I spent four months trying to make that math work. What actually happened was predictable. Nobody had deep focus. Context switching consumed 40 percent of available time. Quality dropped across all twelve projects. People started leaving. The projects didn't ship on time. Leadership concluded the team needed to work harder. The breakthrough came when I stopped trying to optimize the impossibility and started optimizing the choice instead. I took the twelve projects and ranked them by actual business impact using a framework that wasn't particularly clever but was consistently applied. We kept four. We formally killed three by communicating the decision to stakeholders with specific reasoning. We deferred five with documented timelines. The team of eight then focused exclusively on the four kept projects. Velocity doubled in six weeks. Quality improved. Three people who were planning to quit stayed. The leadership team eventually accepted the framework because the metrics spoke for themselves. The thing that surprised me wasn't the outcome. It was how much energy the team had been wasting on the psychological burden of trying to do everything. The visible work was only part of the cost. The invisible cost was the chronic low-grade anxiety that comes from knowing you're failing at something even when you're working sixty hours a week.

How To Know When You're Actually Ready

There's no checklist but there is a signal. You're ready when the idea of giving something up feels like relief rather than panic. This usually arrives after you've spent enough time feeling the pain of overload that the alternative starts looking attractive. Most people hit this point somewhere between a breakdown and a genuine conversation with someone who isn't invested in their hustle culture. The practical test is simpler than you might expect. Take your current list of commitments and remove the bottom third. Not the ones you like least. The ones where your actual engagement is lowest. If you can do that without immediate catastrophic consequences, you were already overcommitted. If removing anything causes immediate failure, you might actually need help rather than a prioritization framework. I've found that the most durable version of this practice isn't a monthly review or a weekly planning session. It's a daily question that takes about thirty seconds. Not "what should I do today?" but "what am I explicitly not doing today and why is that okay?" The second question does more work than the first because it forces you to acknowledge the constraint rather than pretend it doesn't exist. Most people spend their entire professional lives avoiding that question.

The numbers vary widely depending on your starting point but people who stick with this for six months typically report a 30 to 50 percent reduction in perceived workload stress. The actual hours worked don't change much. What changes is the gap between what they're doing and what they think they should be doing. Closing that gap is where the relief comes from. It's not about achieving everything. It's about stopping the arithmetic of impossibility. There's a version of this that applies to software and product design that follows the same logic but with different vocabulary. Feature is just prioritization with a different stakeholder group. The mathematics are identical. You can't ship everything so you choose what to ship and accept that the unshipped features will be someone else's problem. The people who figure this out early tend to build better products than the people who treat every feature request as a moral obligation.

The Specific Language That Helps

Words matter more than you'd expect when you're trying to rewire a deeply ingrained impulse. The phrase I find most useful isn't particularly poetic. It's "this is a choice not a compromise." The distinction matters because compromise implies you're losing something you wanted. Choice implies you're gaining the ability to actually deliver on what you kept. The emotional valence of the same situation flips entirely depending on which frame you're using. Another phrase that's helped me is "I'm protecting my attention the way I protect my time." This sounds grandiose until you actually track where your attention goes for a week. Most people discover they've been voluntarily handing it out like loose change. The framing makes the protection feel less like denial and more like stewardship. The phrases that don't work are the ones that sound like they come from a poster. "Choose joy" or "focus on what matters" are empty without the operational detail of what choosing actually looks like on a Tuesday afternoon when everything is on fire. The specific language needs to survive contact with your actual calendar.

I've stopped recommending most books on this topic because the ones that actually work tend to be the ones people finish and then immediately return to their old patterns. The ones that stick are usually the ones where the author describes their own failures in enough detail that you recognize yourself. If a book makes you feel like you finally understand but gives you no new actions, it's entertainment not education. Both have value. Don't confuse them. The most honest answer I can give about All I Want Is Everything is that it's not really a problem to solve. It's a tension to manage. The desire for everything will show up again. It shows up when you see someone else doing something you want to do. It shows up when a new opportunity presents itself. The work isn't eliminating the desire. It's building a system that can hold the desire without letting it dictate every decision. That system looks different for everyone but the architecture is always the same: make the constraint explicit, schedule the refusal, and accept that missing out is the price of being able to actually finish something. If you want a concrete starting point that takes less than twenty minutes, write down ten things you want. Circle three. Block time for the seven you're not doing. That's it. The rest is maintenance.