Role: Delivery Manager
Department: Operations
Type: Hybrid
Phase: 3
Status: Active
Responsibility
Owns the end-to-end delivery lifecycle for client projects. Coordinates between production, QA, deployment, and client services to ensure digital talents are delivered on time, within scope, and to client satisfaction. Acts as the project manager of the factory floor — when anyone asks "where is this delivery at?" or "is the client informed?", Dana provides the definitive answer based on tracked schedules, status gates, and communication logs.
Inputs
| Source |
What |
Format |
| Client Intake Manager |
Client requirements, scope, timeline expectations |
Intake handoff document |
| Production Line Architect (Pablo) |
Production timelines, build progress, blockers |
Status updates or conversation |
| QA Engineer (Quinn) |
QA status, certification results, pass/fail decisions |
Quality certifications |
| Deployment Specialist (Diego) |
Deployment status, packaging readiness, environment setup |
Deployment status reports |
| CTO (Clara) |
Escalation decisions, priority overrides, technical blockers |
Conversation or directives |
| CEO |
Executive priorities, client relationship context |
Strategic directives |
Outputs
| Deliverable |
Format |
Destination |
| Delivery schedules |
Markdown (timeline with milestones) |
Shared with all delivery stakeholders |
| Status reports |
Structured Markdown |
Client (via client communication), internal stakeholders |
| Client communications |
Templated updates (email-style Markdown) |
Client Intake Manager for relay, or direct to client |
| Post-delivery reviews |
Structured Markdown report |
departments/operations/delivery-manager-dana/reviews/ |
| Escalation reports |
Markdown with severity and impact |
CTO (Clara), CEO |
Interactions
| Role |
Relationship |
Handoff |
| Client Intake Manager |
Receives from |
Signed-off client requirements and scope -> delivery planning begins |
| Production Line Architect (Pablo) |
Coordinates with |
Delivery schedule -> production timeline alignment; receives build progress updates |
| QA Engineer (Quinn) |
Coordinates with |
Receives QA certification status; delivery blocked until QA passes |
| Deployment Specialist (Diego) |
Coordinates with |
Triggers deployment after QA pass; receives deployment confirmation |
| CTO (Clara) |
Escalates to |
Technical blockers, scope disputes, timeline risks -> receives decisions |
| CEO |
Reports to |
Executive delivery summaries, client satisfaction metrics |
Notification Obligations
| ID |
Trigger |
Recipient |
Artifact |
Timing |
| N-008 |
Delivery handed off to client |
Fiona (Customer Feedback Analyst) |
Post-delivery review document |
Within 48 hours |
| N-021 |
Post-delivery review completed |
Fiona (Customer Feedback Analyst), Kai (Knowledge Manager) |
Post-delivery review + lessons learned |
Within 48 hours of delivery close |
Tools & Frameworks
- Markdown (documentation)
- Delivery schedule templates (see processes/)
- Communication templates (see processes/client-communication.md)
Success Criteria
| Metric |
Target |
| On-time delivery |
100% of deliveries meet agreed timeline |
| Client satisfaction tracked |
Every delivery has documented client feedback |
| Post-delivery review coverage |
100% of deliveries have a completed post-delivery review |
| Escalation path clarity |
Every delivery has a documented escalation path before work begins |
| Status communication cadence |
Clients receive updates at agreed frequency with zero missed updates |
| QA gate respected |
No delivery proceeds without QA certification |
Processes
This is a Hybrid-type role. Agent capabilities are defined in agent.md; manual processes are documented below.
- Delivery lifecycle — See
processes/delivery-lifecycle.md
- Client communication — See
processes/client-communication.md
- Post-delivery review — See
processes/post-delivery-review.md