Skills / Run It in Production / Change & delivery

Run It in Production

Test Data Management

Finds the production data sitting in test, routes every dataset to a safe disposition, and makes safe data faster to get than a copy.

Book a working session

Private skill · shared by invitation · How access works

Illustrative output with sample data.

The challenge

Nobody knows how much production data is sitting in test.

Engineers route around the process

A three-week ticket loses to a copy of production.

Masking mandates, low adoption

Compliance-led programmes protect less than they claim.

Subsetting mistaken for safety

A 1% copy of unmasked data is just as sensitive.

Broken joins

Inconsistent masking kills cross-system tests.

How it works

From first question to finished output.

Assess

Establish source, disposition, refresh and owner for every non-production dataset.

Baseline

Exposure Ratio, Refresh Latency, Provision Lead Time and Determinism Coverage.

Route

Prohibit, Synthesise, Mask or Pass, first yes wins. Every Pass is argued and owned.

Design and execute

Deterministic masking, self-service provisioning, and delivery to closure.

What you get

Exposure Ratio, with Refresh Latency and Provision Lead Time beside it
Per-dataset disposition register: Prohibit, Synthesise, Mask or Pass
Deterministic masking design that survives cross-system joins

What goes in

Non-production environment inventory, refresh records, data request tickets, sensitive-data classification.

Time to answer

As a consulting engagement8 weeks3 people · 24 consultant-weeks

Running the skillHalf a day to 2 daysAssess mode · Design and Execute modes follow

Estimate by the same method; newer than the rest of the portfolio.

What it still needs from you

Deciding who is allowed to call a dataset Pass, and signing their name to it.

Also in Run It in Production

See where this fits in the sequence →

See Test Data Management in action.

Thirty minutes with Harveer, on your own data problem.