I once watched a $2 million project grind to a halt over a single, recurring software problem. It wasn't a catastrophic bug or a server meltdown. It was something far more mundane, hiding in plain sight within the project management tool we all used: Asana.
As a serial entrepreneur and angel investor in over 200 companies, I’ve seen it all when it comes to productivity software. I’ve lived through the rise and fall of countless tools, and I’ve personally used Asana to manage everything from small teams to entire companies. It’s slick, it’s popular, and for many things, it’s genuinely good. But after years of use, I’ve come to realize it has a deep, structural issue that nobody seems to talk about. An issue that creates a frustrating and inefficient experience for anyone trying to manage their own work while contributing to a team project.
The Two-Headed Monster: 'My Tasks' vs. Project Views
The core of the problem lies in the disconnect between two fundamental parts of Asana: the Project view and the 'My Tasks' view. On the surface, the idea is simple. Projects are where you collaborate with your team, laying out all the tasks required to get something done. 'My Tasks' is supposed to be your personal, consolidated to-do list, pulling in everything assigned to you from all your different projects.
It sounds great in theory. In practice, it’s a mess. The two views operate with different rules and, at times, feel like completely separate products. The way you organize, sort, and prioritize tasks in a project doesn't translate cleanly to 'My Tasks'. You end up with a jumbled, often overwhelming, list of assignments with little of the context you had in the original project.
Think of it like this: you have a beautifully organized library (the Project) where every book is in its right place, categorized by subject and author. Then, you have a personal reading list ('My Tasks') that just shows you a raw, unsorted pile of book titles. You know you need to read them, but you have no idea which one is for your history class, which is for your book club, and which one you just thought looked interesting. That’s what using Asana feels like every single day.
A Story of Two Startups
At my last company, RemoteTeam (which we sold to Gusto), we ran our entire 30-person engineering team on Asana. We had a master 'Product Roadmap' project with dozens of epics, each broken down into specific tasks. A new feature might have 50 tasks assigned to 10 different engineers. In the Project view, everything was perfect. We had columns for 'To Do', 'In Progress', and 'Done'. We had custom fields for priority and estimated effort. It was a project manager’s dream.
But then you’d talk to the engineers. They were living in their 'My Tasks' view, and it was chaos. A task that was clearly marked as 'High Priority' in the project would just show up in their list with no special distinction. The sections they created for themselves—like 'Today' or 'This Week'—were constantly being overridden by new tasks dumped in from other projects. They were spending at least an hour a day just trying to figure out what to work on next, manually cross-referencing their 'My Tasks' list with the half-dozen projects they were a part of.
We saw our sprint velocity drop by nearly 20%. Deadlines were being missed not because the work was hard, but because the system for managing the work was creating friction. It was death by a thousand paper cuts.
Contrast this with my experience at MovieLaLa (acquired by Gfycat). We were a much smaller team, and we used a simpler tool that didn't have this dual-brain problem. Your tasks were your tasks, and they existed within the context of the project. There was no separate, confusing personal view. The result? We moved faster. Communication was clearer. There was a single source of truth, and everyone knew where to find it.
The Real Cost of a 'Minor' Flaw
Some might say this is a minor issue. A matter of personal preference. I disagree. As someone who has invested in companies like Scale AI and Anthropic, I look for efficiency and scalability. A tool that introduces this much cognitive overhead at the individual level is a direct threat to both.
When your team members are spending a significant chunk of their day just trying to organize their to-do list, that's time they're not spending building your product or serving your customers. It’s a hidden tax on productivity. If you have a team of 20, and each person loses just 30 minutes a day to this kind of administrative wrangling, you're losing 10 hours of productive work every single day. That's more than a full-time employee's worth of work vanishing into thin air each week.
Furthermore, it creates a culture of learned helplessness. People stop trusting the tool. They start keeping their own separate to-do lists in notebooks or text files. Shadow systems emerge. Before you know it, you don't have a central project management system at all. You have a dozen different systems, and the original purpose of the tool—to create clarity and alignment—is completely lost.
It's a Symptom of a Deeper Design Philosophy
This isn't just a bug. It's a reflection of a design philosophy that, in my opinion, misunderstands the nature of modern work. The separation of 'My Tasks' and Projects seems to assume that individual work and collaborative work are two distinct modes that can be managed separately. They're not. They're two sides of the same coin.
My work is valuable because of how it fits into the larger project. Seeing it in isolation is not just unhelpful; it's actively misleading. I need to see my tasks in the context of the project's goals, deadlines, and dependencies. By stripping that context away, 'My Tasks' makes it harder, not easier, to do my job effectively.
Our Workaround
At RemoteTeam, we eventually had to declare bankruptcy on the 'My Tasks' feature. We issued a company-wide directive: Do not use 'My Tasks'. Your source of truth is the Project view. We created shared bookmarks for each team's primary project board and told everyone to live there. It was a crude fix, and it meant we were essentially ignoring a core feature of the software we were paying for, but it was the only way to restore sanity.
We even briefly explored using the Asana API to build our own custom 'My Tasks' view that actually worked, but we quickly realized that we shouldn't have to re-engineer our project management tool just to make it usable. We had a business to run.
A Tool Should Serve the User, Not the Other Way Around
I'm not writing this to bash Asana. As I said, it has many strengths. But this one, single flaw is so fundamental that it makes me hesitant to recommend it to the fast-moving startups I invest in. In the early days of a company, speed and focus are everything. Any tool that gets in the way of that is a liability.
For a company that prides itself on creating clarity at work, this is a surprising and significant blind spot. I hope they address it. Until then, if you're considering Asana, you need to go in with your eyes open. Be prepared to either live with the chaos of 'My Tasks' or to abandon it entirely. And if you're a current user feeling this pain, know that you're not alone. It's not you; it's the software.
Frequently Asked Questions
Can I switch later if I make the wrong choice?
In most cases, yes. The switching cost is usually lower than people fear. The bigger risk is analysis paralysis, spending months evaluating options instead of picking one and learning from real usage.
What factors matter most in this comparison?
For most founders, the three factors that matter most are: total cost of ownership, ease of implementation, and how well it integrates with your existing workflow. Features are important but often overweighted in decision-making.
Which option is best for startups?
It depends on your stage, budget, and specific needs. Early-stage startups should prioritize flexibility and low cost. Growth-stage companies can afford to optimize for performance and scalability. There's no universal answer.