We were six weeks into a company-wide rollout of a new customer data platform (CDP), with about 30% of the marketing and product teams actively using it in their day-to-day workflows. Then, our executive sponsor and the primary team lead for the project—let's call him David—was unexpectedly promoted to a different division. The new lead, Sarah, came from a finance background and had a very different perspective on tool adoption and value measurement.
The project immediately stalled. Momentum died, weekly syncs became tense, and the "wait-and-see" resistors grew louder. I'm in marketing automation, so my workstream was directly blocked. Rather than let it fail, a few of us from the initial power-user group banded together to create a salvage plan. Here’s the step-by-step playbook we followed, focusing on concrete actions.
**First, we diagnosed the core disconnects:**
* **Language Gap:** Sarah spoke in terms of ROI, efficiency metrics, and risk mitigation. Our original rollout language was all about "single customer view" and "advanced segmentation capabilities."
* **Trust Deficit:** Sarah had no visibility into the early wins or the existing user commitment. She saw only a budget line item and a timeline.
* **Changed Priorities:** David’s "north star" was improving customer journey personalization. Sarah’s was proving tangible cost savings or revenue attribution within the next quarter.
**Our salvage plan had three phases:**
**Phase 1: Re-onboard the New Lead (Week 1-2)**
We requested a dedicated, 90-minute session with Sarah, but we didn't call it a training. We framed it as a "current-state deep dive and roadmap alignment." Critically, we:
* Presented data from the existing 30% adoption: showed specific email campaigns where using CDP-driven segments improved deliverability and open rates by verified percentages.
* Translated every feature into a business outcome. Instead of "real-time data sync," we said "reduces the manual segment export/upload lag for lifecycle emails from 4 hours to 10 minutes, cutting campaign launch time."
* Created a simple, one-page document linking her key performance indicators (KPIs) to CDP functionalities and the data we could now provide for her reports.
**Phase 2: Re-energize the Broader Team with Quick Wins (Week 3-4)**
With Sarah now cautiously supportive, we needed to rebuild broad team momentum.
* We identified two high-impact, low-effort use cases that could be completed in a week: cleaning up a critical suppression list and building a single high-value segment for an upcoming sale campaign.
* We ran a series of 30-minute, role-specific "clinic" sessions (e.g., one for email marketers, one for product analysts) focused solely on those quick wins. This was more effective than the earlier broad training.
* We publicly celebrated these wins in the team Slack channel, tagging Sarah and the contributors, which created visible evidence of progress.
**Phase 3: Co-create a Revised Milestone Map (Week 5-6)**
We didn't simply ask Sarah to sign off on David’s old plan. We facilitated a working session to build a new one together.
* We used a whiteboard to map out the remaining rollout, but we let Sarah define the success criteria for each phase. Her metrics became our metrics.
* We established a new, bi-weekly "health dashboard" for the project that included her preferred metrics (e.g., "time-to-insight" for analysts, "cost per resolved customer ticket" for support) alongside adoption numbers.
* We formally identified one of the resistors from the data engineering team—someone Sarah respected—and brought them into a pilot for the next phase, turning a resistor into a champion.
The key lesson was that a leadership change isn't just a personnel switch; it's a fundamental shift in project vocabulary and success definitions. You cannot just keep executing the old plan louder. You have to pause, translate, and integrate the new leadership's worldview into the rollout fabric.
I'm curious if others have faced similar mid-stream changes. Specifically:
* How did you handle the communication shift with the wider team who were already in motion?
* What methods did you use to identify and translate the new leader's implicit priorities into explicit project milestones?
~Heidi
Your identification of the language gap and trust deficit is the critical pivot. This is exactly where most technical projects fail under new financial oversight. The finance perspective isn't inherently wrong, but it speaks a different dialect.
You can't just translate your "single customer view" into her "ROI." You need to build a new dictionary. For example, "advanced segmentation capabilities" becomes "reduction in manual list-building hours, quantifiable as a 15% decrease in marketing ops labor cost per campaign." The value must be pre-calculated, not just described.
This is analogous to a cloud cost review where engineers talk about "high availability multi-AZ architectures" and FinOps needs to hear "reduced risk of revenue-impacting downtime, projected at $X per hour, versus the reserved instance commitment cost of $Y." The initial salvage effort must be that translation layer. Did your team start building that specific set of financial proxies for the early wins?
every dollar counts
Your point about financial proxies is exactly right, and it's a step we found we had to formalize. We didn't just translate the features, we instrumented the old process to establish a baseline cost. For instance, before we could claim a 15% decrease in manual labor, we had to log the actual hours spent on list-building in the legacy system over a two-week period, then run the same campaigns in parallel using the new CDP's segmentation. This gave us the hard, projectable numbers Sarah needed.
The caveat we discovered is that this translation must be continuous, not a one-time exercise. A finance-oriented leader will expect the same rigor for every proposed feature or next phase. We had to build a lightweight framework for this, essentially a shared spreadsheet where any proposed "capability" had to be paired with its "cost displacement" or "risk reduction" metric before it entered the development backlog. This shifted the entire team's communication style.
Without that ongoing discipline, the initial translation becomes just a temporary sales pitch, and the trust deficit reopens.