Deployment Execution

Purpose

This playbook defines how Forward Deployment teams execute production deployments with clear ownership and low ceremony.

Deployment Timing

Deploy when:

• The release is ready.
• The deployment owner is available to monitor.
• The client communication owner is known for client-impacting releases.
• There is enough time to rollback or fix forward if needed.

Avoid deploying high-risk changes when:

• No Project Technical DRI or senior backup is reachable.
• The team cannot monitor after deployment.
• The client is in a critical business window.
• Required alerts or health checks are missing.

Deployment Roles

Role	Responsibility
Deployment owner	Runs the deployment and verifies the result.
Project Technical DRI	Reviews high-risk release readiness and helps with escalation.
Deployment Strategist	Handles client-facing communication when needed.
FDE	Owns technical verification for the change they implemented.

One person can hold multiple roles on small projects, but the roles must be explicit.

Standard Deployment Steps

1. Confirm release readiness in Notion.
2. Confirm the GitHub PR or commit being deployed.
3. Run the deployment workflow.
4. Watch deployment logs until completion.
5. Run health checks or smoke tests.
6. Verify the changed user/client workflow.
7. Update the Notion Release Log with result and deployment link.
8. Notify the relevant internal channel.
9. Notify the client only if the release plan requires it.

Communication Protocol

For low-risk releases:

• Internal deployment notification is enough.

For medium-risk releases:

• Notify internal channel before and after deployment.

For high-risk releases:

• Notify internal channel before deployment.
• Confirm Project Technical DRI approval.
• Keep the Deployment Strategist ready for client communication.
• Post completion or rollback result after verification.

Deployment Record

Every production deployment should leave a linkable record:

• Notion Release Log entry.
• GitHub Actions workflow run or equivalent deployment log.
• Deployed commit SHA.
• Result: success, rollback, failed, or cancelled.