Adobe Implementation Playbook

Finish

After the build

Phases 6–9 · QA/UAT → Go-live → Hypercare → Closure

The same gates apply to every tool: QC checklist executed and UAT signed off, production cutover, a hypercare window, then a handoff pack.

0 of 0 done

6. QA / UAT

Gate: QC checklist executed — UAT sign-off

ToolWhat to do
AEPRow-count reconciliation, null/duplicate SQL, identity spot-checks, blocked-activation test
Adobe AnalyticsSDR validation; reconciliation with source systems
Launch (Tags)Debugger/Assurance, cross-browser, opt-out test, performance
MarketoTest-lead walkthrough, rendering, two-way sync
RTCDPPrecedence tests, consent exclusion, blocked activation, small-audience export
AEMAccessibility, SEO, performance, cache, broken links
TargetFlicker, metric on every variant, audience bucketing
AJOTest mode on every branch, proofs, dry run, consent and cap tests
CJAReconcile with Analytics/source; stitching spot-check; access test
6. QA / UAT evidence (test log, cutover checklist, monitoring or handoff pack)
Screenshot 6. QA / UAT evidence (test log, cutover checklist, monitoring or handoff pack)Add screenshots/phases/phase-6.png

7. Go-live

Gate: Production cutover — Go-Live sign-off

ToolWhat to do
AEPPromote via sandbox packages; start Prod dataflows
Adobe AnalyticsCut over (parallel run if migrating)
Launch (Tags)Publish to Prod with rollback; remove old tags
MarketoActivate campaigns; domain warm-up
RTCDPActivate Wave 1 audiences
AEMDNS/CDN cutover; redirects
TargetActivate first activities
AJOPhased activation; IP warm-up
CJAShare projects; schedule reports
7. Go-live evidence (test log, cutover checklist, monitoring or handoff pack)
Screenshot 7. Go-live evidence (test log, cutover checklist, monitoring or handoff pack)Add screenshots/phases/phase-7.png

8. Hypercare (2–4 weeks)

Gate: Daily monitoring; fixes — Hypercare Exit sign-off

ToolWhat to do
AEPDataflow failures, ingestion lag, profile counts
Adobe AnalyticsData anomalies, broken variables
Launch (Tags)Beacon errors, duplicate hits, page speed
MarketoDeliverability, sync errors
RTCDPMatch rates, sync failures, audience size drift
AEMError logs, cache, author issues
TargetTraffic split, page performance
AJOBounces, complaints, step-event errors
CJAIngestion lag, data view issues
8. Hypercare (2–4 weeks) evidence (test log, cutover checklist, monitoring or handoff pack)
Screenshot 8. Hypercare (2–4 weeks) evidence (test log, cutover checklist, monitoring or handoff pack)Add screenshots/phases/phase-8.png

9. Closure & handoff

Gate: Handoff pack: runbooks, access list, training, open backlog

ToolWhat to do
AEPRunbook for failed dataflows and schema changes; final SDR; access list; training
Adobe AnalyticsSDR handoff, Workspace training, governance cadence
Launch (Tags)Property documentation, publishing process, audit schedule
MarketoProgram templates, operations runbook, SLA review
RTCDPAudience naming and ownership guide; destination runbook; governance doc
AEMAuthor training, component docs, release process
TargetResults repository, roadmap process, governance
AJOJourney catalog, template library, deliverability runbook, training
CJAData dictionary, project catalog, access model
9. Closure & handoff evidence (test log, cutover checklist, monitoring or handoff pack)
Screenshot 9. Closure & handoff evidence (test log, cutover checklist, monitoring or handoff pack)Add screenshots/phases/phase-9.png

Final rows of the master sequence

#ToolConfigurationDepends onOutputPhase
23All toolsEnd-to-end test: one synthetic person from web visit → profile → audience → journey → report1–22End-to-end test logQA / UAT
24All toolsGo-live in waves; hypercare monitoring across dataflows, activations, journeys, tags23Go-Live and Hypercare Exit sign-offsGo-live & hypercare
25All toolsHandoff: runbooks, SDR/SDD final versions, access list, training, backlog24Closure and handoff packClosure

Interview questions

What happens in UAT?

Business users test agreed scenarios against acceptance criteria in a production-like environment, log defects, and sign off when criteria are met.

What is in a go-live plan?

Cutover steps and owners, timing, rollback plan, communication, smoke tests after launch and who approves go/no-go.

What is hypercare?

A 2–4 week period of heightened support after go-live where the delivery team monitors daily and fixes issues before steady-state support takes over.

What goes into a handoff pack?

Runbooks, final SDR/SDD, access list, training materials, open backlog and support contacts.

A critical defect appears on launch day. What do you do?

Assess impact, decide fix-forward or rollback with the sponsor, communicate, then run a root-cause review.