Skip to content

Importing the Project Coordinator Onboarding into Asana

This folder contains two files that work together:

  • generate_asana_csv.py — generates the CSV for any start date
  • pc_onboarding_asana.csv — a pre-generated CSV with Day 1 = 2026-05-18 (next Monday from creation)

The goal: import once, save as Asana template, clone for every future project coordinator.

Step 1 — Generate the CSV for your project coordinator's start date

python generate_asana_csv.py --start 2026-06-02 --out my_project coordinator.csv
  • --start must be a Monday (the curriculum assumes Day 1 = Monday). The script warns if it isn't.
  • --out defaults to pc_onboarding_asana.csv.
  • Defaults to next Monday from today if --start is omitted.

The script computes due dates by business days — Day 5 is the Friday of Week 1, Day 6 is the following Monday, Day 30 is exactly 6 weeks after Day 1.

Step 2 — Create a new Asana project from the CSV

  1. In Asana, click + Create > Project > Import > CSV
  2. Upload the CSV
  3. Asana will auto-map columns. Verify the mapping:
  4. Name → Task Name
  5. Description → Description / Notes
  6. Section/Column → Section
  7. Due Date → Due Date
  8. Module, Tier, Energy → these should become new single-select custom fields. If Asana asks, choose "Create new custom field" for each.
  9. Dependencies → if your Asana plan supports CSV dependency import, map this to Dependencies. If not, leave it as a text field and resolve dependencies manually in Step 3.
  10. Click Import.

Result: a project with 71 tasks organized into 6 sections that reflect the curriculum phases:

  • Day 1 - Land (13 tasks)
  • Week 1 - Who We Are (14 tasks)
  • Week 2 - The Toolkit (14 tasks)
  • Week 3 - RevOps Domain (14 tasks)
  • Week 4 - Doing the Job (12 tasks)
  • Days 21-30 - Live Work + Day 30 Review (4 tasks)

All due-dated, with custom fields populated. Project coordinators complete tasks via Asana's native checkbox; no need to migrate them across status columns.

Step 3 — Wire up dependencies (if not auto-imported)

If your Asana plan didn't auto-import dependencies, manually add them. There are 11 dependency relationships in the curriculum — they keep tasks in logical order:

Downstream task Depends on
Write 'Cortado in my own words' Read Cortado philosophy + Read Our ICP + Read EM Playbook
Rewrite sample email in BLUF Watch BLUF video + Read Storylining
Attend one Steerco as silent observer Read Steerco Best Practices doc
Write Steerco observation note Attend one Steerco as silent observer
Watch first 20 min of Jan 2023 PMO All-Hands Read asana_kanban_waterfall_primer.md
Walk three live Cortado Asana boards Watch PMO All-Hands
Write 'stays same vs. changes' Read eHouse + Worksuite + Crownpeak + EverAg/Aqfer/CCL
Draft 1099 orchestration checklist Read 1099 source docs (ICA, AUP, Referral Sources)
Stand up Excel project plan Open GTM Project Plan Template
Convert plan to Asana board Stand up Excel project plan
Populate Steerco shell Steerco operational pack (schedule, agenda, deck shell)

Step 4 — Save as Template

Once the project looks right:

  1. Click the project name dropdown → Save as template
  2. Name it: Project Coordinator Onboarding — 30 Day Curriculum
  3. Choose Use original due dates as offsets from project start (this is the key setting — it makes all future clones auto-shift dates based on the new start date)
  4. Save

Step 5 — Clone for each new project coordinator

For every future project coordinator:

  1. In Asana, click + Create > Project > Use a template → pick the template
  2. Set Start Date = the project coordinator's Day 1 (a Monday)
  3. Set the project owner (the onboarding mentor)
  4. Add the project coordinator as project collaborator
  5. Done — they walk into a fully scheduled 30-day plan on Day 1

What this gives you that the markdown doesn't

  • Self-tracking: tasks move through the board as the project coordinator works
  • The onboarding mentor sees progress live — no need to ask "how's it going"
  • Dependencies enforce sequence (Asana grays out blocked tasks)
  • The Day 30 review has objective input ("you completed 67 of 71 tasks; here's what slipped and why")
  • Cloneable, so the work to build the first project coordinator's plan doesn't repeat

When the curriculum changes

Don't edit the Asana template directly — the source of truth is generate_asana_csv.py. Workflow:

  1. Update the TASKS list in the Python file
  2. Regenerate the CSV
  3. Re-import into a fresh Asana project
  4. Save as the new template (archive the old one)

That keeps the markdown curriculum, the CSV, and the Asana template in sync.