Governance workshops your team plays, not sits through

We've all sat through the governance training. Someone puts up the DMBOK wheel, defines a data steward, walks through a maturity ladder and asks whether there are any questions. There are never any questions. Nothing was at stake, half the room is on email, and two weeks later the only measurable outcome is the attendance list.

That isn't the content's fault. Governance is a discipline of trade-offs, and you can't teach a trade-off by describing it. You have to make somebody choose, show them what their choice cost, and then let the room argue about it. The arguing is the part people remember. The slides are the part people endure.

So this format is a game instead.

What actually happens in the room

A session runs two to three hours for a group of eight to forty. Twenty minutes of framing — decision rights, quality dimensions, what an owner actually owns — then everyone gets their phone out and plays a round on a scenario simulator. Framing, round, argument, repeat.

Each round drops the group into a situation with no clean answer. Two departments both claim the customer record. A regulator asks where a number came from and the lineage stops at somebody's spreadsheet. A quality rule is failing 14% of the time and fixing the source means asking another director to change a process they're measured on. Everyone chooses, the choices are scored on governance consequence rather than on being right — which is disorienting in a useful way — and then the leaderboard goes up on the screen. Rooms get competitive faster than anyone expects them to.

The debrief is where the session really happens. People argue about their own organization, with their own examples, having just watched a colleague they respect choose the opposite thing. That argument is the knowledge transfer; the simulator is only what starts it. Sessions have run half an hour over because two directors wouldn't let go of a definition, and that is the format working rather than failing.

Your own private, branded version

This is the part that doesn't exist anywhere else. The three simulators on this site are public: one worldwide leaderboard, generic scenarios and nothing to take away afterwards; what those public boards show is a summary of everyone's runs and a set of general lessons, not a reading of any one organization. For a workshop I open a private space for your organization instead, with your name on it and the scenarios rewritten around your systems, your teams and the arguments you actually have.

What you keep afterwards

The facilitator report is what makes this more than a good afternoon. It ranks the dimensions your group was weakest on, first and most prominently, with maturity bands and per-question timings. It's a diagnosis of your organization's governance instincts, produced by forty people choosing under mild time pressure rather than by a survey they had a week to think about.

In practice it does two things. It tells you where next quarter's effort should go, and it gives you something to put in front of a sponsor: not "the team enjoyed the workshop", but "here are the three areas where our own people didn't know who decides, ranked".

You keep the CSV export too, and the space stays open for the length of the license, so a second cohort, a follow-up session, or the same team retaking it in six months all land on the same leaderboard and turn into a comparison.

Which scenario suits your room

There are three, and they play very differently.

• Data Governance Day-to-Day: a week in the life of a governance lead — competing requests, a failing rule, an escalation, a definition nobody agrees on. Best for a governance team, a steward network, or a leadership group that needs to feel what the role involves rather than read the job description.
• Who Owns This?: a disputed ownership claim between two departments, played to the end. Best when ownership is the real blocker, and hard to beat with both departments in the room at once.
• Data Literacy: raising literacy with no training budget. Best for a broad business audience rather than a data team.

A three-hour session usually takes one scenario in depth; a full day takes two.

The practical bits

Sessions run remotely or on site, in English, Spanish or Portuguese, and one session can mix all three, because each participant picks their own language and they all share a single leaderboard. Everyone needs a phone or a laptop and a browser. No accounts, no installs, no app — one access code for the whole room.

Workshops are priced per session, with the private space, the rewritten scenarios, the facilitator report and the license period included. Tell me the dates, the group size, and which systems and teams the scenarios should name.

Booking one

Use the contact form and include your dates, the number of participants, the language mix and one sentence on what you want the room to walk out understanding. I'll come back with a scenario recommendation and a quote.

If the workshop is part of something bigger, the advice and support page describes where it usually fits — most often as the opening move of an operating model design, because a room that has just argued about ownership is a room that will engage with a decision-rights grid.