Data governance programme · manager alignment
Manager strategy
Role-specific passports, touchpoint sequence, and handling resistance — designed for a time-poor corporate environment.
Role-specific manager passports — click a role to preview
DO
Manager passport — Data Owner
What you need to know before the programme starts
What your team member's role means
They are now accountable for how a specific set of data is defined, protected, and used across the organisation. They make decisions — not IT.
They will need time to attend three workshops and one cross-role simulation across six weeks. This is part of their role, not extra work.
What to expect in the next 30 days
They will set one data quality target for their domain — they may ask for your input on priorities
They will make one data access decision without escalating to IT — support this even if it feels unfamiliar
They will establish a working relationship with their Data Steward — you may be asked to facilitate an introduction
Your three questions at day 30
Question 1
What data access or quality decision have you made this month that previously would have gone to IT?
Question 2
Have you met your Data Steward? What did you discuss?
Question 3
What is one thing you're still unsure about in this role — and what do you need from me to move forward?
Manager touchpoint sequence — before, during and after the programme
Week −2
Pre-launch
Manager Intelligence Briefing
45-minute onsite session framed as a strategic briefing, not a training admin meeting. Managers learn what their team member's role means, what the programme will produce, and what they need to be ready for. Ends with the Manager Passport distributed — one page, role-specific, keep it.
45 min · onsite · all managers together
Week 1
During programme
Early access preview
After session 1, managers receive a one-paragraph summary of what their team member is working on — not a report card, a conversation starter. Framed as: "Here is what your team member identified as their biggest challenge in their new role. You may want to have a conversation before session 2."
Email · 2 min read · no action required
Week 3
During programme
Guest reviewer moment
Managers are invited to attend the last 20 minutes of session 3 as a guest reviewer — not an evaluator, a curious senior colleague. They hear their team member practise a real governance conversation or use case pitch. They leave invested in the outcome. No preparation required.
20 min · optional · high impact
Week 4
Cross-role simulation
Manager visibility at session 4
Managers are notified that session 4 is the cross-role simulation — the culmination of the programme. They are not required to attend, but they receive a brief debrief note the same day summarising how their team member performed in the collaborative scenario.
Same-day debrief note · 1 page
Day 30
Transfer
Structured day-30 check-in
Not a casual catch-up. Managers use the three questions from their role-specific passport. 20 minutes. The conversation guide tells them what a good answer sounds like and what to do if their team member is stuck. L&D receives aggregate completion data — not individual scores.
20 min · structured · 3 questions
Four common resistance patterns and how to design around them
Resistance 1
"My team member doesn't have time for this on top of their real job."
Reframe: this is their real job now. The passport makes that explicit. The briefing reinforces it. If the manager still resists, escalate to the Data Governance lead — this is a role accountability issue, not a scheduling issue.
Resistance 2
"I don't understand this role well enough to support them."
This is the passport's job. Two sentences. No jargon. The manager doesn't need to understand Data Governance — they need to understand what their person is now accountable for and what to ask at day 30.
Resistance 3
"Why do I need to do a check-in? That's L&D's job."
Because L&D can't create the conditions for transfer — only the manager can. The check-in is framed as a performance conversation, not a training follow-up. The questions are about what the person did, not what they learned.
Resistance 4
"My team member told me the training wasn't relevant to their actual work."
This is a design signal, not a manager problem. If this comes up in the day-30 data, go back to the action map. The session that felt irrelevant is the one where the scenarios weren't close enough to real work. Fix the scenario bank, not the communication.
The design principle behind all four responses
Manager resistance is almost always a symptom of unclear expectations, not bad intent. Design the manager experience with the same rigour as the learner experience — personas, touchpoints, failure states, and a transfer plan. If you've done that, resistance becomes a data point, not a problem.