The evidence for structured work is accumulating faster than product managers can judge what belongs together.
Fast synthesis protects discovery time, while source-level traceability protects the distinction between a recurring need and a loud request.
Who you’d be doing this for
“I sent the same setup issue twice this quarter, and I still get asked which project I meant.”
Jayesh Gupta · Enterprise Project Manager
Uses custom fields and types to standardize recurring cross-functional work across several business teams.
What is at stake
Feedback on custom field and types is being read repeatedly because similar requests do not yet form trusted themes. You must weigh faster evidence synthesis against keeping product-manager judgment and source traceability intact.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- synthesis speed vs source traceability
- recurrence signals vs workflow nuance
- AI drafting vs PM problem framing
- local pilot learning vs centralized consistency
Why Asana
Custom field and types work determines whether enterprise customers can structure work for their own cross-functional workflows.
Written with these in mind
Not your kind of problem? 28 more at Asana, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.