Hi all,
Looking for some real-world perspective from people who’ve been through this.
Before Asana, task and project tracking at our company was completely chaotic — emails, Discord, verbal requests, you name it. At some point leadership decided to roll out Asana, which was a great call in principle. The problem was the rollout itself: people were simply told “start using Asana,” with no guidelines, no training, and no follow-up on how it was actually being used.
More than a year later, we’re still dealing with the consequences. Some people maintain their My Tasks carefully and consistently. Others have tasks sitting there with due dates from months (or over a year) ago, because they simply don’t work out of Asana — they have their own workarounds. Projects tend to be structured around departments or task types rather than actual initiatives, and the internal consistency of each project depends entirely on whether that particular owner cared enough to set it up properly.
The bigger issue: information doesn’t flow properly between colleagues, task assignment isn’t consistent, and ownership of tasks/projects is often unclear. Even among people who genuinely try to use Asana well, it’s still common for actual work to be assigned via comments instead of tasks or subtasks.
So — a few questions for the community:
- Have you been in a similar spot — a large-ish organization with inconsistent adoption a year+ after rollout? What actually worked to turn it around?
- Basic ground rules: We can’t even agree on something as simple as “every task needs an Assignee and Due Date.” One counterexample: we have a project where we log invoices as tasks and share it with Finance, specifically to avoid messy email threads — and forcing an Assignee/Due Date on every invoice task doesn’t really make sense there. How do you handle exceptions like this without the “rule” collapsing into “well, it depends”?
- Non-project work: Most Asana tutorials seem to assume you’re managing project-based work, which fits a marketing team reasonably well. But we also need a consistent way to track everyday, ongoing responsibilities that aren’t tied to a specific project, while still keeping things auditable/traceable.
- The “My Tasks” clutter problem: Say I own a campaign task with a Due Date, work happens via subtasks assigned to others, the campaign launches, and there’s nothing left for me to do until a follow-up phase later. The parent task still needs to stay open (the campaign isn’t “done”), and I’m still the Assignee — so it just sits in my My Tasks indefinitely, even though I have no current action item. Ideally My Tasks should reflect what’s actually actionable for someone right now. How do you handle long-running “umbrella” tasks like this without cluttering My Tasks?
I know Asana has a huge library of training material, but honestly, if we can’t even agree on the fundamentals as a team, I’m skeptical that pointing people to lengthy courses will actually solve anything. Curious how others have approached driving real behavior change (not just tool adoption) in a larger org.
Thanks in advance!