How to run your first data-mapping workshop

The person best placed to know where personal data actually lives is rarely the person filling in a spreadsheet alone — it's whoever runs support, sales ops, HR, or the systems day to day. A workshop gets that knowledge out loud, in the room, instead of guessed at from an org chart.

The goal of the first session isn't a complete map. It's a rough first pass you can refine — waiting for perfect information before starting usually means never starting.

One person from each team that regularly touches customer or employee data: typically support, sales, HR, finance, and whoever manages your core systems. Keep the first session small — four to six people is usually enough to cover the main data flows without the conversation losing focus.

It helps to have someone from IT or engineering in the room too, since they'll often know about systems and integrations the business teams don't think to mention.

Walk through your main products, services, or business processes one at a time, and ask a simple question for each: what personal data comes in, where does it go, and who else sees it along the way? Sticky notes or a shared doc work fine — the format matters less than getting people actually talking through the flow together.

Expect surprises. It's common to discover a spreadsheet, a personal email folder, or an old tool nobody remembered was still holding customer data. That's a normal, useful outcome of the exercise, not a sign it went badly.

Turn what you captured into rows in a Processing Register: one row per activity, not per system, so the same system can show up across several rows if it supports different processes. Assign an owner to each row before the meeting ends, while people are still in the room — an unowned list rarely gets finished later.

Plan to revisit it. A data map is a snapshot, not a one-time deliverable — new tools and processes get added faster than most teams expect.