Discovery context is rich enough to guide an expansion, but too scattered to survive the handoff.
Sellers need faster next steps while buyer commitments and qualification gaps still require human judgment.
Who you’d be doing this for
“My VP asked what would actually change for delivery, and I had to pull the examples together again.”
Linnea Olsson · Program Manager
A project-management leader whose enterprise team is considering a broader deployment after an initial work-management rollout.
What is at stake
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.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- seller speed vs buyer-facing judgment
- structured fields vs discovery nuance
- forecast consistency vs administrative burden
- AI drafts vs source verification
Why Asana
Asana Work Management expansion depends on translating cross-functional delivery problems into credible, buyer-specific next steps.
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.