Reference · People

Team registry

Everyone involved in enterprise implementations — their project role, what they own, and what to ask them about.

Showing 10 of 10 team members

  • Account Executive

    Enterprise Account Executive

    Sales — Account Executive

    Runs Stage 0a Triage and Stage 0b Solution shaping, and owns the qualification outcome. Either enterprise AE may hold the deal. Sends the Evaluate before contract and completes the AE Opportunity Record (internal handover) at contract signature, before kickoff. No delivery decision rights after ESC Delivery Lead accepts it.

    Triage & tieringSolution shapingPromises made in the sales cycleAE Opportunity Record

    Stages 0, 0.1, 0.2, 1

  • Delivery Lead

    SVP, Strategic Delivery & Solutions

    Enterprise Solutions Consulting — Delivery Lead / Solution Architect

    Asana project owner. Architects the solution jointly with the Engineering Authority, covering process, workflow and delivery design while Engineering covers the technology side. Owns scope, scheduling and approval-gate tasks; accountable for executive sign-offs. For custom development, prepares the custom development template, sends it to the Engineering team for assessment, then tracks progress and status through build and acceptance.

    Scope & schedulingApproval gatesCustom dev template & statusEscalationsExecutive sign-offs

    Stages 0.1, 0.2, 1, 2, 3, 4, 5, 6, 7, 8, 10, 11, 11.1, 12, 13

  • Engineering Authority

    CTO

    Engineering Authority

    Architects the solution jointly with the Delivery Lead, carrying the technology side: architecture decisions, integrations, technical escalations and serious bug resolution. For custom development, reviews the Delivery Lead's template and owns the assessment (approach, effort, cost and timeline) and the build with the Engineering team. Attends every internal kickoff and scope kickoff; customer kickoff when integrations or complex migration are in scope; the first data mapping session for each source system; Stage 5, 7 and 8 gate reviews; and check-ins while an S1/S2 or architecture item is open.

    Architecture decisionsCustom dev assessment & buildTechnical escalationsSerious bugs (S1/S2)Scope & data mapping calls

    Stages 0, 0.1, 0.2, 1, 3, 4, 5, 6, 7, 8, 9, 11, 11.1

  • Scope Approver

    SVP of Client Services

    Scope Approver — Client Services Leadership

    Approves the scope baseline at Stage 5 (G5) and is the sole waiver authority. Co-approver on custom development.

    Contract reviewScope-gate approvalGate waivers

    Stages 5

  • Customer Success Lead

    VP Client Services

    Customer Success — Leadership

    Assumes the customer relationship at Stage 12 handover and is the accountable owner from Stage 13. Does not own delivery gates.

    Go-live meetingsHandover acceptanceConfiguration ownership

    Stages 12, 13

  • Customer Success Manager

    Senior Customer Success Manager

    Customer Success — Manager

    Enterprise CSM. Receives the account at Stage 12 and absorbs all post-launch operational ownership, including MAC, plus quarterly business reviews and renewal readiness.

    Account ownershipQBRsRenewal readiness

    Stages 11.1, 12, 13

  • Training Lead

    Training & Success Associate

    Adoption & Training

    Owns the training plan, Part G category schedule, readiness checks and training sign-off across the implementation.

    Training design & deliveryPart G categoriesPost-load reconciliation

    Stages 1, 2, 3, 8, 9, 11

  • Training Specialist

    Training & Success Associate

    Trainer

    Delivers role-based sessions, records attendance and outcomes, and supports post-load reconciliation activities.

    Training design & deliveryCrosswalk gapsPost-load reconciliation

    Stages 1, 2, 3, 8, 9, 11

  • MAC Specialist

    MAC Specialist

    MAC Implementation

    MAC product implementation only — every assignment is limited to MAC workflow scope. Not a governance owner, scope author or commercial participant. Post-launch ownership transfers to the CSM at Stage 11.

    MAC configurationMAC workflowsMAC training

    Stages 1, 2, 3, 6, 8, 9, 11

  • Data Migration Lead

    Data & technical

    Data Migration

    Owns extract, transform, load and reconciliation evidence, and runs the Stage 7 migration cutover.

    Data migrationReconciliationStage 7 cutover

    Stages 1, 2, 3, 6, 7, 8, 9, 11

Need someone not listed? Escalations route through Delivery Lead (scope, gates & status) or Engineering Authority (technology & custom development) — they architect jointly.

RACI by stage

Who is Responsible, Accountable, Consulted and Informed at each stage. Exactly one Accountable per stage — that person owns the outcome and the gate decision even when others do the work. Columns are roles; the name underneath is whoever holds the role today.

StageAccount ExecutiveAccount ExecutiveESC Delivery LeadDelivery LeadEngineering AuthorityEngineering AuthorityScope ApproverScope ApproverCustomer Success LeadCustomer Success LeadCustomer Success ManagerCustomer Success ManagerAdoption & TrainingTraining Specialist / Training LeadMAC ImplementationMAC SpecialistData MigrationData Migration LeadCustomerSponsor / system adminsExecutive SponsorCEO / President
Phase 1 — Evaluate
0a Triage (internal)G0ACCC
0b Solution shapingG0bACCR
0c Commercial and securityG0cACCR
Phase 2 — Commit
1 HandoffG1RACRCRI
2 SetupG2ARCR
3 Customer kickoffG3ACRCRC
Phase 3 — Define
4 DiscoveryG4ACRRRC
5 Scope sign-offG5SignedRRARI
Phase 4 — Build
6 BuildG6ACRR
7 Data migrationG7SignedACRR
8 TestingG8SignedARRCRR
9 TrainingG9ARRC
Phase 5 — Launch
10 Go-liveG10SignedARRRRRRI
11 HypercareG11ACRRCR
11a Steady-state HandoverG11aACRR
Phase 6 — Adopt
12 HandoverG12ARRI
13 GrowG13CAR
  • AAccountable — owns the outcome
  • RResponsible — does the work
  • CConsulted — gives input before it ships
  • IInformed — kept in the loop

Stages 0a–0c are run by the Account Executive — either enterprise AE may hold the deal. Customer Success assumes the customer relationship at Stage 12; delivery keeps commitment accountability through Stage 13.

MAC assignments are limited to MAC workflow scope throughout, and post-launch operational ownership sits with the Customer Success Manager. The Stage 10 cutover coordinator is named per engagement at go-live planning.

Source: internal governance record.