The award depends on promising enough AI value without creating an obligation the agency cannot govern.
The program office needs a credible path to faster cross-program coordination, while contracting, security, and finance need terms they can defend after award.
Who you’d be doing this for
“My deputy asked which team owns the next blocked handoff, and I still had to chase four status decks.”
Lena Jansen · Federal Program Manager
She coordinates delivery across several civilian agency program offices that currently report work through separate trackers.
What is at stake
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.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- award speed vs. defensible AI governance
- program-office urgency vs. security approval
- adoption value vs. future cost exposure
- broad deployment scope vs. contract clarity
Why Asana
AI Teammates and Dash now sit inside the commercial conversation for agency-wide work-management deployments.
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.