NextGen Pulse POS
SWAT Rollout
Program
SR. TECHNICAL WRITER / CONTENT STRATEGIST
REDUCTION
ZERO ROLLBACK
SATISFACTION
ACCURACY
6,000+ FRANCHISE LOCATIONS, ZERO DEDICATED IT SUPPORT, ONE SIMULTANEOUS ROLLOUT
Domino's was deploying a new POS system, NextGen Pulse, across its entire franchise network at once. Franchise operators had no on-site IT support, varying levels of technical fluency, and zero tolerance for downtime during peak hours. A failed adoption at any store meant lost orders and escalation calls to a support team stretched across thousands of locations.
No one had built documentation for the operational reality of a working pizza store. What existed was fragmented and disconnected from the workflows operators relied on mid-shift. The rollout needed a content infrastructure that could absorb 6,000+ franchise locations without a single on-site support visit.
A DIGITAL ADOPTION ECOSYSTEM BUILT FOR OPERATORS, NOT CORPORATE IT
Operators would never leave the POS mid-shift to open a manual. The architecture centered on in-app guidance: help that surfaced inside the software at the exact moment someone needed it, delivered through modals, hotspots, and tooltips via Inline Manual. Because a GM's daily workflow looks nothing like a crew member's, every content touchpoint was scoped by role and delivered in both English and Spanish.
QA/UAT documentation cycles tied to the product release calendar validated every piece of content in a cloud-native environment before it reached a franchise operator. A SWAT team deployment playbook standardized every rollout wave so each location received the same quality of support.
INTAKE → VALIDATE → AUTHOR → REVIEW → DEPLOY → LOCALIZE
Every code release followed a ten-stage production pipeline from JIRA intake through ES localization. The pipeline is demonstrated in full in the deliverable below.
- Operator Q&A Sessions — Bi-Weekly Feedback Loops Led bi-weekly Q&A sessions with frontline operators, capturing friction points and iterating the content architecture before each rollout wave. Operator feedback drove structural changes to walkthrough sequencing and role-based content scoping.
- Cloud-Native Validation — Jenkins Environment Testing Validated every release in cloud-native staging environments alongside Design, Engineering, and Product. Defined test scenarios from intake, executed hands-on in Jenkins, and surfaced defects pre-deployment. Zero post-deployment documentation defects across all rollout waves.
- Content Authoring — GPE Release Notes & Inline Manual Walkthroughs Authored GPE Release Notes per Domino's Confluence template and built Inline Manual walkthroughs for every feature release. Scoped each walkthrough to three guidance types (modal, hotspot, tooltip) matched to the operator's task context.
- SME & Editorial Review — Two-Pass Accuracy Gate Ran a two-pass review on every deliverable: first with Engineering, Product, and Design for technical accuracy, then with a peer writer for style, clarity, and template compliance. Maintained 98% documentation accuracy across 12–15 annual code releases.
- EN/ES Authorship — Spanish-Register Content, Not Translation Authored Spanish-register content for all Inline Manual walkthroughs. Original content creation scoped to the cognitive load of Spanish-primary operators, not vendor-managed translation of English source material.
- Deployment & Localization — Confluence + L10N Handoff Deployed final documentation to Confluence, updated existing pages, archived deprecated content, and prepared L10N packages for additional language markets beyond EN/ES.
THE MOST SUCCESSFUL ENTERPRISE POS TRANSITION IN DOMINO'S FRANCHISE HISTORY¹
The operators who had no IT support and no tolerance for downtime adopted the system at a 99% rate. Support tickets dropped 89% because the content met them inside the software at the moment of need. The content infrastructure I built became the operational standard for every subsequent NextGen Pulse rollout wave.
DOCUMENTATION PRODUCTION PIPELINE
Navigate the two panels — Pipeline View and Output View — to review the full scope of the production process: ten-stage pipeline from JIRA intake through ES localization, a completed GPE Release Note with content strategy annotations, and an interactive Inline Manual walkthrough simulation rendered in three UI states (tooltip, hotspot, manager override modal).