Asana Project Manager

$80-$85 per hour

Seattle, WA

Contract

Duration: 3 months Contract

• The client is a drone delivery service scaling commercial operations across the United States. The Service Expansion team manages end-to-end launch execution of drone delivery sites — from site selection through regulatory approval, construction, hiring, and operational launch.

• In 2026, the team is executing site launches across 27 states and 48 metros, coordinated through Asana as the central schedule management system spanning 63 cross-functional teams.

• Asana is the backbone that coordinates this execution. Every site launch flows through integrated schedules in this system, making its reliability directly tied to the team's ability to hit network expansion targets.

• The Project/Program Manager will serve as an Asana Subject Matter Expert and Platform Architect, responsible for managing and optimizing a large-scale Asana environment supporting dozens of concurrent drone delivery site launches.

• This is an enterprise-scale Asana environment, not a small-team project management setup. The role requires someone who can understand complex program dependencies, redesign an organically grown Asana workspace, repair dependency networks, improve automation, establish governance, and drive adoption across a large cross-functional organization.

The candidate will manage 59 active integrated schedules spanning 63 separate teams .

Each schedule contains:

• 175+ tasks

• 39+ custom fields per task

• Portfolios

• Cross-project dependencies

• Standardized templates across four site configuration types

This is an enterprise-scale scheduling environment where architectural decisions affect hundreds of users and thousands of active tasks simultaneously .

The candidate must be comfortable managing 65+ schedules and making architectural decisions that maintain consistency, usability, and reliability at scale.

The Asana environment manages T-minus countdown schedules . Each of the 59 active site launches has a schedule where every task is defined as a fixed offset from a T-0 launch date, such as T-180, T-55, or T-30.

These schedules span approximately 15 cross-functional teams per site , including:

• Construction

• Regulatory

• Hiring

• Supply Chain

• Startup

• Infrastructure

• Safety

• Other launch functions

Dependency Challenges

Within a single site:

Tasks have predecessor/successor relationships across teams — for example:

Permits approved → Construction start → Equipment installation → Safety audit → Site handoff

These dependency chains have degraded over time. When a permit slips, downstream tasks do not automatically move, requiring Launch Managers to manually cascade changes across 175+ tasks per site.

Across sites:

Multiple sites share constrained resources. For example:

• Training capacity: 6 concurrent launches per week

• Ground handlers: 160 per week maximum

Cross-project dependencies should identify resource conflicts when launch clusters overlap, but these currently require manual deconfliction.

The contractor must understand multi-team, milestone-driven program schedules and be capable of rebuilding dependency logic so that a delay in one activity can appropriately cascade through downstream activities.

For example:

Construction delay in Week 4 → Hiring trigger in Week 10 → Launch impact in Week 16

This is not generic task linking. It requires rebuilding the underlying logic of how approximately 15 teams interlock to deliver a single site launch .

The contractor must be able to develop and deliver platform training for diverse user groups, including:

• Launch Managers who use Asana daily as hands-on schedule operators

• Cross-functional teams

• Executive leadership consuming portfolio-level dashboards

Responsibilities include:

• Creating documentation

• Developing quick-reference guides

• Establishing governance standards

• Conducting office hours

• Monitoring adoption

• Driving sustained adoption through structured change management

The objective is not simply to rebuild the system, but to ensure that users understand, adopt, and consistently use…