Why Working Harder Is Not Always the Answer
Most of us have been raised on a familiar productivity gospel: work harder, stay longer, collaborate more, and multitask like a pro. But what if those habits are precisely what's holding you back? According to Melissa Swift, founder and CEO of the consulting firm Anthrome Insight and author of the new book Effective: How to Do Great Work in a Fast-Changing World, many of the frustrations we experience at work are not personal failures at all. They are structural problems baked into the way our jobs, tools, and organizations are designed.
Swift has spent decades advising companies through consulting leadership roles at Capgemini, Mercer, Korn Ferry, and Deloitte. Her quarterly columns in MIT Sloan Management Review regularly rank among the most-read articles on the platform, and her insights have appeared in the New York Times, The Washington Post, and Newsweek. In short, she knows a thing or two about what it actually takes to perform well in a complex, fast-moving work environment.
Below, we unpack five counterintuitive lessons from Swift's thinking that could fundamentally change the way you approach your workday.
1. Your Productivity Problems Are Probably Not Your Fault
This might be the most liberating insight in the entire book: the reason you feel overwhelmed, scattered, or ineffective at work is very likely rooted in poor system design, not personal weakness. When organizations pile on meetings, ambiguous priorities, and misaligned tools, no amount of personal discipline will fully compensate.
Swift encourages workers to step back and ask a radical question: is the structure of my job actually set up for success? Before blaming yourself for dropping balls or losing focus, examine whether your work environment is providing the conditions that good performance requires. This shift in perspective alone can reduce stress dramatically and help you focus your energy on the levers that actually matter.
2. More Collaboration Is Not Always Better
Collaboration has become something of a corporate religion. Open-plan offices, endless group chats, and back-to-back syncs are presented as signs of a healthy, connected team. But Swift challenges this assumption directly. Not every task benefits from group input, and over-collaboration can actually dilute accountability, slow decision-making, and fragment your most productive working hours.
The key is being intentional about when collaboration genuinely adds value versus when it is simply organizational habit. Some of your best thinking happens alone. Protecting time for deep, focused, individual work is not antisocial — it is strategic. Learning to distinguish between tasks that need collective input and those that need concentrated solo effort is one of the most powerful things a professional can do to work more effectively.
3. Multitasking Is Quietly Destroying Your Output
Despite decades of research showing that the human brain is not wired for true multitasking, the modern workplace continues to reward the appearance of doing many things at once. Responding to Slack messages mid-meeting, skimming emails while on a call, or context-switching between five different projects in a single afternoon all feel productive. They are not.
Swift's work underscores what cognitive science has long told us: multitasking increases error rates, reduces the quality of your thinking, and leaves you mentally depleted faster. The counterintuitive move is to do less at once. Batch similar tasks together, protect blocks of uninterrupted time, and give your full attention to one thing before moving to the next. You will likely accomplish more in less time, and the quality of your work will improve visibly.
4. Getting Clearer on What Your Work Actually Is Changes Everything
One of Swift's most striking observations is that many professionals have only a vague understanding of what their job truly requires them to produce. They are busy, certainly — but busy doing what, exactly? When the answer is unclear, people default to activity: attending meetings, generating reports, and staying visible. None of this is necessarily the same as delivering real value.
Getting radically honest about what your work is — what outcomes you are actually responsible for, what decisions only you can make, and what tasks are genuinely yours to own — provides a filter for everything else. It becomes much easier to say no, to prioritize intelligently, and to measure your own effectiveness against something concrete. Clarity about your core work function is not a luxury. It is the foundation of working more effectively.
5. Effort Is Not the Same as Effectiveness
Perhaps the most counterintuitive tip of all: working harder is not the same as working better. Many high performers are trapped in an effort-for-effort's-sake culture where long hours and visible hustle are rewarded regardless of outcomes. Swift argues that this is a trap — one that burns people out while delivering diminishing returns.
True effectiveness is about working in ways that produce the greatest impact relative to the energy you invest. That means making smarter choices about where to focus, reducing friction wherever possible, and being willing to let go of low-value work even when it feels expected. It also means recognizing that rest, recovery, and strategic thinking are not the opposite of productivity — they are essential components of it.
Start Working Smarter, Not Just Harder
The insights Melissa Swift shares in Effective: How to Do Great Work in a Fast-Changing World are a timely reminder that the modern workplace is overdue for a rethink. By challenging deeply held assumptions about collaboration, multitasking, and effort, she offers a more honest and ultimately more sustainable path to high performance.
If you have been feeling like no matter how hard you try, you can never quite catch up, the problem may not be you. It may be the way work itself has been designed around you. The good news is that once you see those patterns clearly, you can start making choices that let you do truly great work — without burning out in the process.