Data governance programme
Measurement, feedback and contingency
Pre-programme baseline, the Voice your blocks feedback loop, complete measurement arc, and what happens when participation is lower than expected.
Three baseline questions — embedded in the diagnostic, before any session
Baseline Q1
Role clarity confidence
Measures starting point for session 1's primary objective.
On a scale of 1–5, how confident are you that you understand what your new role is responsible for — and where it stops?
Repeated at day 30. Delta = role clarity score.
Baseline Q2
Decision confidence
Measures starting point for session 2's primary objective.
On a scale of 1–5, how confident are you that you could make a data-related decision in your role today without asking someone else to make it for you?
Repeated before session 2 and at day 30. Delta = decision confidence score.
Baseline Q3
Application readiness
Measures starting point for the overall programme outcome.
On a scale of 1–5, how ready do you feel to start performing the responsibilities of your new role effectively in the next 30 days?
Repeated at day 30. Delta = overall programme impact score.
These three questions take 90 seconds to complete and sit at the end of the diagnostic. Without them, every other metric measures change from session 1, not from day zero. The baseline is what makes the measurement story complete.
How Voice your blocks responses actually shape the programme
Learner submits Voice your blocks
Learner · optional · 10 min
Three anonymous questions before the programme starts. Responses go directly to the facilitator — not to managers, not to HR.
Facilitator reviews before session 1
Facilitator · 15 min
Facilitator identifies the two or three themes that appear most frequently. These themes determine which scenarios are prioritised in session 1.
If "I'm worried about talking to other departments" appears → prioritise the cross-department conflict scenario in session 1 debrief.
If "I don't have time for this" appears → open session 1 by addressing the time ask directly.
Facilitator acknowledges responses in session 1
Live session · first 3 minutes
The facilitator opens session 1 with a single sentence that signals the responses were read and used. Not: "Some of you said X." Instead: "A number of you flagged concern about cross-departmental conversations — that's exactly why we're starting with this scenario."
Learners who completed it hear their input mattered. Learners who didn't see the programme is shaped by real concerns, not assumptions.
Responses inform cohort 2 design
L&D Lead · post programme
Voice your blocks responses reviewed alongside day-30 data after the programme ends. Patterns that appeared pre-course and remained unresolved at day 30 become design inputs for the next cohort.
This closes the design loop: learner concern → programme adjustment → measurement → next cohort improvement.
The feedback loop is what turns Voice your blocks from a survey into a design tool. Without the acknowledgement in session 1 and the post-programme review, it's just data collection. With them, every cohort makes the next one better.
Complete measurement arc — from day zero to day 30
Day zero — before anything
Three baseline scores
Role clarity · decision confidence · application readiness. Embedded in diagnostic. 90 seconds.
After session 1
Role clarity score
Same 1–5 question repeated. Delta from baseline = session 1 impact. Collected via one-question pulse at end of session.
Before session 2
Pre-decision confidence
Same 1–5 question repeated in 8-min pre-work. Creates anchoring — learners commit to a confidence level before the simulation reveals what they don't know.
After session 4
Action plan quality
Facilitator rates each 30-day action plan on specificity — real behaviour or vague intention? Collected in the room before participants leave.
Day 30
Behaviour change metrics
Role clarity · decision confidence · application readiness all repeated. Action plan completion reviewed by manager. Cross-role relationship confirmed.
Post programme
L&D aggregate report
All deltas combined into one report for leadership. No individual scores — only programme-level patterns. Shared with DCM for cohort 2 planning.
Six measurement moments, none longer than 90 seconds except the day-30 manager check-in. The full arc answers: where did people start, what changed at each session, and what changed in the job 30 days later.
What happens when participation is lower than expected
Trigger
Fewer than 50% complete Voice your blocks
Do not mention learner responses in session 1 opening
Use the default scenario bank — designed to surface common concerns regardless
Open session 1 with a live version of the three questions verbally
Trigger
Fewer than 50% complete the diagnostic
Run a 5-minute live version at the start of session 1
Run a single track using Track B scenarios — designed to work for everyone
Flag to manager sponsor — low completion signals low manager buy-in
Trigger
Fewer than 50% complete day-30 action plans
Send one reminder at day 20 — framed around the upcoming manager check-in
Report completion rate to manager sponsor as a programme health signal
Review session 4 facilitation notes — vague action plans don't get completed
Trigger
A session has fewer than 3 participants
Sessions 1–3 minimum 3 participants — below this, reschedule rather than run a degraded version
Session 4: if a role is missing, substitute with a programme alumnus as role-player
Self-paced pre-work continues on schedule — only the live session is postponed
Every contingency has a trigger, a designed response, and a signal to investigate root cause. Low participation is never a learner problem — it is always a design, manager, or environment problem.