Selected work

Case studies

Architecture, migration and recovery work on Adobe Experience Platform programmes: leading a CJA migration, resetting multi-vendor governance, and consent-aware activation through Destination SDK. Client details can be shared under NDA where relevant.

Discuss your customer data challenge ← Back to homepage
CJA Migration Enterprise organisation (EU)

Adobe Analytics → Customer Journey Analytics migration leadership

A migration that had stalled on disputed measurement. Getting stakeholders to agree on measurement, data model and adoption took the programme from months of debate to a delivery plan.

Situation

Migration had stalled. Baseline logic was disputed, the target data model was undefined, and multiple partners were delivering in parallel without a shared decision framework. Each steering meeting ended without a clear owner or next step.

My role

Independent governance lead. I set the decision cadence, had assumptions validated before anything was built on them, and turned the alignment conversations into an implementation-ready backlog with quality gates, so progress could be tracked.

Outcome

Within weeks the programme moved from debate to delivery. The measurement baseline was validated, identity and consent implications were resolved, and I handed over a plan with clear ownership.

  • →Defined target measurement model and decision cadence for stakeholders
  • →Validated baseline logic, identity/consent implications before scaling
  • →Converted findings into implementation-ready backlog with governance guardrails
  • →Quality gates installed so delivery stayed on track after handover
Stack: Adobe Analytics CJA Web SDK Identity / Consent Data governance

Key outcome

Within weeks

From debate to a backlog the team could build from, with decisions clear at every stakeholder level.

Recovery Complex multi-vendor enterprise programme

Programme recovery & multi-vendor governance reset

A high-risk AEP programme where governance and decision-making had broken down. Resetting both turned constant firefighting into progress people could plan on.

Situation

Ownership was unclear across multiple vendors. Architecture had drifted from the agreed design. Escalation paths didn't exist, and the team had shifted into permanent firefighting mode. Steering wanted options, not status updates.

My role

Recovery lead. I diagnosed the delivery setup, the ownership gaps and the architecture risk, then put practical governance in place: sign-offs, escalation paths and quality gates. Playbooks meant progress did not depend on me being there.

Outcome

Within two weeks steering was taking decisions again. Escalation paths and quality gates were in place, progress became predictable, and the programme continued independently after handover.

  • →Rapid diagnosis across delivery, ownership, and architecture risk
  • →Governance reset: sign-offs, escalation paths, quality gates per workstream
  • →Vendor alignment re-established with clear accountability
  • →Playbooks and runbooks so progress continued after handover
Stack: Governance Architecture review Multi-vendor delivery Enablement

Key outcome

2 weeks

Until decisions were being taken again. Firefighting gave way to a delivery cadence people could plan on.

AEP · RT-CDP Regulated online business (EU)

Destination SDK integration for consent-aware activation & suppression

Built a custom Destination SDK connector for auditable activation and suppression. Compliance risk came down without slowing delivery.

Situation

Compliance required reliable suppression of at-risk audiences, but key activation endpoints were not fully under client control. Existing workarounds created audit risk and fragile consent flows that broke with campaign changes.

My role

Designed and implemented a custom Destination SDK connector. Defined data contracts, built operational monitoring, and validated consent-aware behaviour end-to-end. Governance checkpoints built in to keep the consent and suppression rules enforced as campaigns change.

Outcome

A stable, auditable activation and suppression pipeline with clear ownership and less dependency on third parties. Suppression is enforced at the source of the pipeline, with the checks visible in the logs.

  • →Custom Destination SDK connector with monitoring and operational runbooks
  • →Consent requirements aligned to downstream delivery and validated end-to-end
  • →Governance checkpoints for consent and suppression rules
  • →Reduced third-party dependency and audit surface
Stack: AEP RT-CDP AJO Destination SDK Consent / GDPR

Key outcome

At the source

Suppression enforced where the pipeline starts, with the consent checks visible in the logs.

Work together

Recognise the shape of your own programme?

These engagements started in different places: a design that needed validating, a migration that needed sequencing, a programme that had stopped moving. A short conversation is usually enough to see which one yours is.

Discuss your implementation ← Back to homepage