Asana
Each of these is a real decision Asana is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
Asana is a subscription-based, cloud-hosted collaborative work-management platform that helps teams from individuals to large enterprises plan projects, assign and track tasks, manage workflows, set goals, and report on progress. It also offers purpose-built products for client management, enterprise service management, and software delivery. Its offerings include AI Studio, AI Teammates, Dash, and Stack AI. AI Teammates are autonomous agents embedded directly into enterprise workflows that reason, act, and proactively drive work forward. Asana also offers Command, a new offering that product development organizations deploy. Amazon is one of Asana's largest and most strategic customers globally. The Work Graph is where customers' work lives, and Asana provides APIs that let people and AI agents act on it. Asana's tech stack includes AWS, Kubernetes (EKS), CloudFront, Istio, Cilium, MySQL (RDS), OpenSearch, DynamoDB, Redis, Terraform, Datadog, TypeScript, Scala, Go, and Python. Asana runs a FedRAMP programme and supports audit cycles and control frameworks across SOC 2 and ISO 27001.
Your first one is free. No card.
29 live right now.
The rest
Shape consolidation paths while Slack still carries the status work
Six pilot customers need evidence that governed workflows can replace duplicate coordination. You must weigh a repeatable programme against each customer’s established operating model.
Settle workflow ownership before the renewal committee meets
Approval workflows across 240 customer projects are paused after owners changed roles. You must weigh immediate delivery continuity against an access decision the customer cannot casually undo.
Restore portfolio reviews before Slack becomes the status record
Forty portfolio leads are bypassing Project Overview and asking for Slack summaries instead. You must weigh a fast familiar path against rebuilding the shared review habit.
Structure discovery notes before expansion momentum fades
Pilot opportunities are carrying conflicting account context across Salesforce and your project tool after discovery calls. You must weigh faster seller follow-through against keeping every buyer promise under human review.
Win commitments on AWS Marketplace without leaning on discounts alone
Enterprise buyers are favoring tools already covered by cloud commitments while questioning AI value. You must weigh a faster procurement path against a package that proves better delivery visibility.
Save an agency award while AI terms divide the reviewers
A 12-office agency deployment can miss its procurement vehicle because AI scope, pricing, and controls remain unresolved. You must weigh a faster award against terms the agency can operate and defend.
Reframe the expansion while procurement questions AI costs
A $420,000 expansion is stalled because procurement cannot connect included AI tools to a defensible delivery outcome. You have to weigh a faster commercial narrative against evidence the programme sponsor can stand behind.
Trace stalled jobs while customer handoffs wait
Stalled asynchronous jobs leave project managers waiting for task handoffs while engineers piece together causes across systems. You have to weigh faster investigation against evidence an engineer can trust before shipping a fix.
Explain agent usage when finance questions project activity
Administrators cannot connect an AI Teammate usage event to the project action that produced it. You must weigh usable accountability against exposing execution details.
Recover API handoffs without writing customer work twice
Approval tasks are missing after API-created work enters projects, even though the tasks are visible. You must weigh fast recovery against irreversible duplicate actions in customer workflows.
Align renamed fields with search before reports drift
Renamed custom field values remain stale in search after the task itself has changed. You must weigh a fast indexing correction against protecting asynchronous job throughput for active workspaces.
Cluster setup feedback while every theme stays traceable
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.
Reuse project structure without forcing one workflow
Project managers are rebuilding fields and types for recurring work, leaving portfolio reports inconsistent. You have to weigh fast reuse against the flexibility enterprise workflows need.
Settle ownership of paused Automations before approvals miss again
Approval tasks are disappearing after Automation owners lose access, leaving active projects falsely on track. You must weigh uninterrupted handoffs against the governance cost of letting old ownership persist.
Fix the choice of field type in setup so more projects finish
Only 46% of eligible enterprise projects finish custom field configuration. You have to weigh faster setup against the structure that makes reporting reliable.
Route identity alerts while responders still own severity
Unusual Okta permission alerts force responders to rebuild evidence across several systems before they can decide. You must weigh faster routing against the review needed to keep an identity-control decision defensible.
Protect AI changes while projects still need to move
Administrators are holding AI Teammates to draft-only work because project changes lack a tested recovery path. You have to weigh fast agent action against a recovery boundary that preserves permissions and project trust.
Contain a suspect dependency while AI Teammate work stalls
AI Teammate actions are failing for some enterprise projects as a suspect npm package appears in build activity. You must weigh a fast clean rebuild against preserving the evidence needed to establish customer impact.
Shield task updates when Automation runs collide
Concurrent Automation runs are delaying task updates for enterprise projects. You must weigh workflow throughput against keeping the shared dependency responsive.
Connect milestones to engineering work without a second backlog
Program managers are rebuilding engineering status because milestone reviews cannot show live dependency risk. You must weigh a useful shared view against the engineering team’s need to keep its existing workflow intact.
Choose a cutover path this week instead of running two approval records
Approved changes still show as waiting in the new work-management system while the ticketing system and CI/CD show them complete. You must weigh launch continuity against a cutover that cannot be casually reversed.
Fix duplicates in release tasks without losing history
The next release cycle is generating duplicate tasks for approved changes and corrupting the delivery view. You must weigh a fast mapping correction against preserving the task history that release leads rely on.
Choose predicted unblocks over action counts until evaluations agree
Project managers are rebuilding delivery evidence because completed agent actions do not show what they unblocked. You must weigh a useful impact prediction against permission-safe evidence and retrieval cost.
Settle the retrieval boundary for AI Teammates before rollout widens
AI Teammates are surfacing work from projects users can no longer open. You must weigh retrieval speed and cross-project usefulness against a permission boundary that cannot be casually reversed.
Tune blocked-work search while old updates crowd out handoffs
Blocked-work queries are surfacing old project updates instead of actionable tasks. You have to weigh ranking precision against retrieval latency and context cost.
Settle who stays accountable after an AI Teammate acts
Project managers are reconstructing AI Teammate actions from comments and meetings. You need to weigh a clear accountability trail against a task experience that stays quick to scan.
Choose a recovery flow for paused Automations before migration
Paused Automations have left approval tasks uncreated after owners lost access. You need to weigh rapid restoration against a review flow that prevents work from running under the wrong permissions.
Recover task ownership before requests vanish into active projects
Thirty-one percent of captured tasks still have no owner after 24 hours. You need to weigh faster capture against the accountability project managers need to move work forward.