Asana Templates Are Hard to Find and AI Tokens Reset Per View
An Asana user says templates are difficult to locate and access within the product, and separately suggests AI tokens should only be consumed once per view rather than repeatedly. Two minor usability and pricing-mechanic frustrations bundled together.
Signal
Visibility
Sign in free to unlock the full scoring breakdown, root-cause analysis, and solution blueprint.
Sign up freeAlready have an account? Sign in
Deep Analysis
Root causes, cross-domain patterns, and opportunity mapping
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Solution Blueprint
Tech stack, MVP scope, go-to-market strategy, and competitive landscape
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Similar Problems
surfaced semanticallyAsana project template creation has poor UX
Teams using Asana find creating and managing project templates unnecessarily complex and unintuitive. The friction discourages standardization of workflows. This affects project managers trying to scale repeatable processes.
Asana Templates Are Static and Cannot Propagate Updates to Future Projects
Changes made to an Asana template do not apply to future projects created from that template, requiring manual updates every time. Teams managing evolving processes must update each project individually when workflows change. Dynamic/live template support would reduce this recurring maintenance burden.
Asana AI Assistant Misunderstands Commands and Creates Redundant Follow-Up Work
Asana's AI feature fails to correctly interpret certain user commands, requiring repeated requests to accomplish simple tasks. Rather than reducing workload, the AI creates additional interaction overhead for users who need to re-state their intent multiple times. This early-stage AI assistant experience undermines the productivity value proposition it is meant to deliver.
Monday.com AI template creation feels unrefined for real workflows
Users find Monday.com AI features, such as automated template creation, still too rough to reliably apply to real-world work. Reflects a broader gap between AI feature marketing and production-ready usefulness in PM tools.
Asana deprioritizes community-requested features in favor of AI additions
Users report that highly-voted community feature requests — including basic text formatting in task titles — go unimplemented for years while Asana ships AI features users find unreliable and off-target. This creates trust erosion between the product and its power user base.
Problem descriptions, scores, analysis, and solution blueprints may be updated as new community data becomes available.