Case Study 02 · Programme & Rollout

The FullStory
Programme

Standing up an enterprise Digital Experience Intelligence platform on a live B2B product — the governance, the enablement and the rollout — as the sole design lead, influencing a cross-functional stakeholder map without owning any of it.

Role  Programme & Design Lead — sole lead· Scope  Governance · enablement · rollout· Timeframe  Oct 2025 – Jul 2026
~10k
agent sessions a day captured across a live enterprise platform
10+
stakeholder functions coordinated — governance to exec
20
training guides authored for the enablement rollout
Sole lead
of the programme end to end — a team of one
The challenge

A powerful tool, capturing almost nothing

The business had committed to a new behavioural-analytics platform to replace a legacy tool that no longer scaled. On paper: unlimited seats, session replay, StoryAI, a data pipeline to the warehouse. In practice, it launched fully masked by default — for good, deliberate privacy reasons — which meant it could see too little to be analytically useful.

So the real work was never “install the tool”. It was three harder things at once: get the governance right so we could safely see what mattered, build the capability so teams could use it, and roll it out without breaking trust on a platform handling ~10,000 agent sessions a day.

Buying the platform was the easy part. Making an organisation trust it, understand it, and act on it — that was the programme.

The Programme

Phase by phase
Late 2025

Commit & Onboard

Replaced a legacy analytics tool that no longer scaled with an enterprise DXI platform. A structured, multi-week onboarding with an external delivery partner set the foundations — instrumentation, orgs and access.

Early 2026

Prove the Structure

  • Two orgs stood up: main product + a lower-risk proving ground, under one umbrella
  • Enterprise SSO live; users identified by hashed ID only — no PII stored
  • A three-part domain-component-action naming standard agreed for tagging
Mid 2026

Unblock Governance

  • Defined a two-tier masking policy with the DPO and Cyber
  • Tier 1 structural UI confirmed systematically unmaskable — unblocking element tagging
  • Tier 2 customer data held behind a formal exceptions process
Summer 2026

Enable & Roll Out

  • Authored a 20-guide training knowledge base, staged for the internal hub + LMS
  • Brought the platform into an AI-assisted workflow via a live connector
  • Phased rollout: proving-ground org first, then domain-by-domain with champions

Leadership & Influence

Team of one

No line authority over any of these functions — the job was to align them. I set the direction, framed every decision so the right owner could say yes, and kept an exec sponsor informed at the altitude they needed. This is influence-without-authority at programme scale.

Stakeholder map

Ten-plus functions, coordinated from a single lead position.

Internal
Data Protection OfficerCyber / Security Data ArchitectureProduct — Platform Product — Account LifecycleHead of Design / DX EngineeringResearch Domain team leadsExecutive sponsor
External partners
Onboarding delivery partnerPlatform vendor (AE)Learning-platform vendor

Unblocking the Data

Safely

“Just unmask it” was never an option; “leave it all masked” made the platform pointless. I worked with the DPO and Cyber to define a two-tier masking policy that everyone could stand behind — the framework that turned a stalemate into a repeatable decision.

Tier 1 — Structural UI
  • Buttons, headers, navigation, labels, empty states — components that exist in code and carry no personal data.
  • Systematically unmaskable — no individual sign-off needed, which unblocked element tagging across the product.
  • Outcome: confirmed and approved — the analytics could finally see the interface.
Tier 2 — Customer data
  • Names, addresses, account identifiers, reads, balances — customer-owned, personally identifiable.
  • Masked by default, released only through a formal exceptions process with DPO + Cyber sign-off.
  • Outcome: privacy held the line while insight moved forward.
Belt and braces on privacy. No personal data stored in the platform — users identified by hashed ID only, access behind enterprise SSO, and one dev environment kept live specifically to test masking rules before anything reached production.

Enablement

Digital learning

A platform nobody knows how to use delivers nothing. So a core part of the programme was enablement: I authored a 20-guide knowledge base — from a “101” through features, access and element tagging — and staged it for both the internal training hub and the learning-management platform, iterating it across multiple versions as the product and the audience matured.

20
structured guides — 101, features, access, tagging
2
delivery channels: internal training hub + LMS
Phased
proving-ground org first, then domain-by-domain with champions
A plain-English glossary explaining the tooling to non-specialists
Enablement is a writing job. Adoption lives or dies on whether people understand the tools — so I translated the stack into plain English, like this glossary. I also worked with engineering to bring the platform into an AI-assisted workflow via a live connector, pairing quantitative behaviour with qualitative research so the two could be read together.

The impact

From shelfware risk to an adopted capability

The programme moved a powerful-but-blind platform to a governed, enabled, and rolling-out capability — with the privacy framework, the training and the operating model all in place. It gave the business behavioural evidence to reduce cost-to-serve, to challenge or confirm what customers say with what they do, and to make investment and deprecation calls on data rather than instinct.

For me, it’s the clearest evidence of leadership at scale: aligning governance, engineering, product, research and the executive around a single direction — and doing the unglamorous enablement work that makes adoption actually happen.

Next case study
Meter Reads · MCP →
← All case studies