Two problems, usually present together. The privacy team needs to be better at the parts of the job that aren’t written down anywhere. And the business units they support need to be able to make routine decisions without asking, because a function of four cannot be the approval route for an organisation of four thousand.
The problem this addresses
At scale, the constraint on a privacy function is rarely knowledge of the law. It is judgement under time pressure, the ability to give a defensible answer quickly, and the standing to be consulted before a decision rather than after it. None of those come from a course.
The second constraint is reach. Where every question has to route through the central team, two things happen: the team becomes a bottleneck, and the business learns to stop asking. The second is considerably more dangerous than the first.
What the engagement covers
- Working sessions with the privacy team on live matters rather than hypotheticals. The fastest way to transfer judgement is to exercise it on something real
- Assessment practice: writing DPIAs that survive scrutiny and reach a conclusion rather than cataloguing considerations
- Building or reviving a privacy champions network in the business units, with a scope narrow enough that the role is doable alongside a day job
- Role-specific material for the functions that generate the most risk: product, marketing, HR, procurement, data science
- Board and executive briefings, pitched at decisions rather than at awareness
- Where a team is preparing for professional certification, structured support towards it
How it runs
Built from your own material: your processes, your systems, your real escalations, rather than something delivered from a standard deck. Generic content is what teams at this level have already sat through and correctly discounted.
Usually a series rather than an event. Capability that arrives in a single day leaves in about a fortnight.
What you’re left holding at the end
A team that escalates less and decides more, and a business that asks earlier because asking has stopped being expensive. Alongside that, the material itself, the sessions and scenarios and decision aids, in a form you can run again without us for new joiners.
The deliberate aim is to be needed less afterwards. An engagement that creates a dependency has solved the wrong problem.