How I'm planning to take the PoC from a working prototype into production — starting with one team and expanding from there.
The PoC is built and working in a Salesforce Developer Org. The next step is getting it into the hands of a real team — not rolling it out to everyone at once, but piloting with one business unit to test it with real campaigns and real people.
The reason for this approach is simple: a system that works in a test environment doesn't always work the same way when real people use it under real pressure. I want to find the issues early, fix them, and build confidence before expanding.
I'm not setting specific percentage targets yet — I want to baseline first during the pilot. But these are the questions I'll be asking:
If the pilot goes well, the plan is to roll out to other business units over the following weeks — 2 to 3 BUs at a time. Each one gets the same training and onboarding support.
The goal is to get all campaigns running through Salesforce and fully decommission Teams Planner as the ops tool.
| Risk | How I'd Handle It |
|---|---|
| Team prefers the old process — people go back to email and Excel | Involve the ops team in design from the start. Run parallel for a few weeks so it's not a sudden switch. Show the time savings early. |
| BU pushback on the intake form — they don't want to fill in structured fields | Keep the form simple. Only required fields. Show BUs that structured briefs = faster delivery and better visibility. |
| Assignment logic doesn't feel right — builders feel it's unfair | Review assignment data weekly during pilot. Adjust the complexity weighting if needed. Ops lead can always override. |
| Something breaks in production — Flows fail, notifications don't send | Test thoroughly in sandbox first. Run parallel with old process during pilot. Have a rollback plan. |
The PoC is built. The rollout plan is defined. The next step is getting approval to pilot with one team and proving that this works with real campaigns, real people, and real deadlines.