As we move into the second half of the year, I’ve been thinking about when teams actually talk about workload.
In many organizations, those conversations happen only after someone is already overwhelmed.
A deadline slips.
A priority gets missed.
A team member says they are at capacity.
A manager realizes too much work is sitting with one person.
Someone finally says, “I can’t keep up.”
By then, the conversation is no longer about planning.
It is about recovery.
One of the most important operational shifts a team can make is creating visibility into workload before capacity becomes a crisis.
Even when projects and tasks are documented in Asana, the full picture is not always visible. Work can still be scattered across:
- Slack messages
- email threads
- recurring meetings
- personal task lists
- side conversations
- “quick asks” that never make it into the system
When work is missing from the shared system—or recorded without enough context—it becomes difficult to see what is competing, what is at risk, and where decisions need to be made.
As we close out the second quarter, I’m using a simple three-part capacity check-in:
- Look back: What work was added, and what was actually completed?
- Look across: Where are priorities competing, work becoming concentrated, or responsibilities still sitting outside of Asana?
- Look ahead: What needs to pause, move, or be clarified before the next quarter begins?
The same framework can be used weekly, monthly, or quarterly. The time frame changes, but the goal stays the same: understand what shifted, identify where pressure is building, and make decisions before the workload becomes unsustainable.
That check-in is only useful if the work is visible enough to support a decision. In Asana, that can mean:
- Keeping the full picture current: Review active projects, update statuses, and capture the administrative or coordination work that might otherwise remain hidden.
- Making pressure easier to spot: Use fields such as priority, effort, urgency, or project stage, and review deadlines across projects rather than one project at a time.
- Turning visibility into tradeoffs: Build capacity reviews into your regular rhythm and, whenever new work is added, decide what should move, pause, or be deprioritized.
This topic is personal for me because I know how easy it is—especially when you are used to being dependable—to keep absorbing work without stopping to question what has changed.
I have learned that waiting until the workload feels unsustainable leaves very little room for thoughtful decisions. At that point, the conversation is usually about immediate relief rather than priorities, tradeoffs, or long-term capacity.
That is why I am working to make these check-ins a regular part of how I plan, not something I reach for only when the pressure is already high.
Capacity conversations do not need to begin with “I’m overwhelmed.” They can begin much earlier, with a clearer view of the work and a willingness to decide what matters now.
What practices have helped your team make those conversations part of regular planning in Asana?