A 25-item Marketing Cloud backlog, scoped and taken to go-live
Took a stalled 25-item Marketing Cloud board, grouped it into five workstreams, and delivered it against a fixed scope through to go-live.
- Journey and template builds
- SFMC data modeling
- CloudPages and triggered sends
- UAT and go-live
The situation
Pryor Learning had a Marketing Cloud board with 25 open items on it and no clear path through. Individually each one was tractable. Together they had no sequence, no estimate, and no owner, so the board sat still — the familiar shape of a platform backlog that everyone agrees is important and nobody can start.
What we did
We estimated the whole board, then grouped it into five workstreams so the dependencies were visible and the work could be sequenced rather than picked at:
- Email templates and journeys — campaign-specific templates including flash sale, sign-up-for-savings, and weekly LMS and member category sends, plus the renewal journey.
- Data model, integrations and automations — updating the SFMC data model, importing Salesforce objects and fields, and building KPI and master subscriber automations.
- Triggers, CloudPages and technical setup — triggered sends, a topic-specific CloudPage editor, GitHub content versioning for Marketing Cloud assets, and UAT validation.
- Link and code updates across every asset — replacing URLs across all emails in the account, migrating express codes to promo codes, and updating footer template production links.
- Go-live and account cleanup — go-live actions, account and table cleanup, and renewal blast segmentation.
Two of those are worth drawing out. GitHub content versioning for SFMC assets is unusual and worth the effort: Marketing Cloud has no native version history, so a bad edit to a shared template is ordinarily unrecoverable. And the mass link and code update was the kind of work that looks trivial on a board and is miserable in practice — it touched every email in the instance.
Where it landed
Delivered against a fixed scope with a defined post-launch support window. The estimate came in at 255 to 330 hours against a scope sold as a single number, which meant the estimate risk sat with us rather than with Pryor.
Something similar on your side?
Thirty minutes, no deck. Tell me what's going on and I'll give you a straight read on it.
Book a working session