The situation
A fraud-detection data source was being replaced with a new provider. Because fraud data feeds both live operations and reporting, the migration had to happen without a wobble in the outputs teams depended on.
What actually needed solving
The challenge was not only rewiring pipelines. It was maintaining trust in operational and analytical outputs through the transition, while coordinating stakeholders with genuinely different priorities and tolerating a fair amount of ambiguity.
What I had to work within
- Live outputs that could not visibly degrade during the switch
- Upstream and downstream dependencies that were not fully documented
- Several stakeholders with different, sometimes competing, priorities
- Ambiguity that had to be actively managed rather than waited out
How I moved it forward
- 01
Mapped upstream and downstream dependencies to understand what the change actually touched.
- 02
Updated data pipelines and transformations to the new provider while preserving the meaning of the outputs.
- 03
Supported the corresponding reporting and dashboard changes so consumers saw continuity, not disruption.
- 04
Coordinated technical and business stakeholders through the transition, keeping change visible and predictable.
The trade-offs that mattered
Preserve meaning, not just schema
Matching field-for-field is easy; keeping the outputs semantically equivalent is what preserves trust.
Treat it as change management
With fraud data feeding decisions, communication and sequencing were as important as the pipeline work.
Make ambiguity explicit
Surfacing the unknowns early let stakeholders align rather than discover surprises mid-flight.
What changed
- A completed provider migration with operational and analytical outputs kept trustworthy.
- Reporting and dashboards transitioned without loss of confidence.
- Stakeholders with different priorities kept aligned through the change.
What I took from it
- In cross-functional data work, coordination and trust are usually the binding constraint, not the implementation.
- Ambiguity managed openly is a shared problem; ambiguity hidden becomes a personal one.