The setting
' is a customer data platform that merges scattered customer records into single profiles and builds audiences for marketing. It lets marketing and data teams use customer data without copying it into a separate system.
Tonight's cutover puts journey continuity against consent evidence that is still incomplete.
The scheduled sends protect customer continuity, while withdrawal histories limit which profiles are defensible to activate.
Who you’d be doing this for
“I've got tomorrow's journeys queued, and now 84,000 profiles have a question mark beside their permission.”
Tao Song · Marketing Operations Manager · a character in this brief
Responsible for scheduled journeys crossing the replacement boundary.
What is at stake
A CDP replacement has 84,000 profiles without provable consent history hours before its first send. You must weigh continuity against evidence that cannot be cheaply checked before contact becomes irreversible.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- journey continuity vs provable permission
- remaining source access vs depth of validation
- rehearsed exclusion vs evidence-dependent inclusion
- fast mapping generation vs costly confirmation
Why Databricks
Unity Catalog's current consent values and Lakewatch's activation telemetry do not by themselves establish the historical permission needed for replacement.
Written with these in mind
Not your kind of problem? 115 more at Databricks, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Databricks. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Sr. Solutions Architect (CustomerLake) (opens in a new tab)
- Sr. Partner Solutions Architect - Customer Lake & Lakewatch (opens in a new tab)
- Drive Partner-Led Platform Consumption: Co-architect complex partner solutions that accelerate customer adoption, deployment velocity, and platform usage across Customer Lake environments
- You serve as the definitive technical authority and trusted advisor for partner technical practices, empowering them to architect, position, and deploy enterprise solutions built on o ur Customer Lake platform, while leveraging Lakewatch for data quality and system monitoring.
- Sr. Solutions Architect, Customer Lake (opens in a new tab)
- Facilitate and influence Executive stakeholders while aligning technology strategy to business value and ROI
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about an irreversible change forced by a fixed date.
In sampled profiles, 17% hold subscription states that conflict across regions, and exception reports disagree with manual checks.
You decide what gets verified, and by whom, before a cutover you cannot undo.
One record in twenty conflicts across text and email or has no clear history, and the old store loses support next quarter.
You have to decide, for each conflict, whether silence or a message is the safer error.
Ambiguous consent records could put opted-out shoppers into the first SMS flow.
You must weigh the launch date against excluding every record that cannot be verified.
The same setting, from another role
Each is set around Databricks’s CustomerLake, written for a different role. They’re separate briefs, not the same scenario.
Campaign totals change after platform refreshes, leaving marketing operations unable to tell a restatement from a broken normalization path.
You must decide what evidence AI can assemble and what engineers must still confirm.
Marketing operations cannot reliably forecast what a large audience activation will consume.
You must weigh a fast estimate against the governance and accuracy needed for it to be trusted.
Incorrect Android identity merges have put household members into each other’s audiences.
You must weigh immediate consent protection against preserving the event history needed to rebuild profiles.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make a hard-to-reverse product decision feel clear and defensible before customers are bound by its consequences.
Deleted records now eat 31% of retention cost, and recovery is slowing in large bases before a fixed storage migration.
You have to cut the cost without removing data that customers expect to get back.
Routing differs by region, so time to the right owner varies threefold, and the slowest paths enter the next filing peak unchanged.
You decide what must be true before launch, since the new path is hard to undo.
A migration review found 14,600 old invoices the new service calculates differently, 430 with conflicting exemption evidence.
You decide what counts as correct before a switch you cannot undo.