I find the Inbox extremely difficult to parse quickly. Rather than helping me triage and interpret information, the UI forces me to slow down and decipher each notification. Right now, everything sits shoulder-to-shoulder visually and conceptually, and it slows down rather than speeds up my workflow.
Inbox could be a powerful tool if it leaned into hierarchy, purpose, and context.
I’d genuinely love to hear how others deal with this, and I hope Asana’s design/UX team will consider refining how Inbox functions—especially for users managing broad scopes of work.
Summary
In its current state, the Inbox UI:
- Compresses too much information into a single visual layer
- Lacks spacing and hierarchy
- Provides no way to sort notifications by intent or action type
- Creates friction where users should be able to parse immediately
Inbox could be dramatically more useful with:
- Better spacing and separation of elements
- Stronger visual hierarchy between notification elements
- More breathing room within notification cards on desktop
- Filtering and sorting by notification purpose (system, comment, project)
At a fundamental level, I want to look at the inbox and immediately know:
- What needs my attention
- Who needs input
- What can be ignored
- Where things are happening
Right now, the UI makes that very hard.
1) Visual Hierarchy Is Weak — Everything Blends Together
Almost every notification type looks visually identical. The components—project name, task title, comment preview, avatars, timestamp, metadata—are all presented at roughly the same visual “depth.” My eyes have to work to interpret what’s happening.
Nothing stands out as the primary object of attention.
On desktop, this produces a very flat experience:
- Similar font weights
- Similar colors
- Minimal contrast
- Tight groupings
It feels like a long wall of equally important elements, rather than a structured feed designed to help users parse information. I can’t easily scan.
2) Overly Dense Layout: Not Enough Negative Space
The notification cards feel compressed. A typical card might contain:
- Project name
- Task title
- Comment text
- “ mentioned you”
- Avatars and notification-related iconography like @ or a styled checkmark for status
- “See more…”
All of this often ends up within a single horizontal visual band.
Comments—arguably the most actionable part—are treated like metadata rather than content. The layout reads as if every pixel is trying to conserve space, instead of guiding the user’s eye and creating a natural reading flow.
I understand tight vertical layouts on mobile, but on desktop the current density makes the inbox harder to parse, not easier.
3) No Practical Way to Triage Notifications
Inbox is supposed to help me manage attention. Instead, everything is presented in one undifferentiated stream.
What I would love to see:
Sorting by Notification Type
- Comments & Mentions (actual human communication)
- System/Automation Events (rules fired, approvals, dependency changes)
These are fundamentally different categories of attention. Treating them the same creates cognitive overload.
Sort by Project
I know there is a “filter by project” option, but it forces users to search through a long list. I don’t want to select projects—I want to sort existing notifications by project so I can clear them context-by-context.
When you work across dozens (or hundreds) of projects, this matters a lot. Right now it feels like trying to manage text messages, calendar alerts, and system logs all in a single undifferentiated stream.