Stakeholder interviews
The judgment that makes a workflow actually work is usually tacit: a dozen unwritten rules in your best person's head about what's urgent, what's an exception, what to never do. It's the most valuable thing about how the work runs, and it's nowhere in any system. A stakeholder interview is how Compass captures it.
How it works
Start an interview and send the share link to whoever knows the work. No account needed — they open the link and talk through how they actually do the job, guided by the conversation. When they're done, the transcript is saved to your workspace and attached to whoever the interview was about, so it sits with the person rather than floating loose on the map.
So the unwritten rules end up written down and connected to the work they govern.
Why it matters for the map
An interview is the richest way to feed the map. What it produces:
- grounds the changes you surface for that workflow — they reflect how the work is really done, not how someone assumes it's done;
- becomes drafts you review in the Inbox — the people, systems, and steps the interviewee mentioned, waiting for you to keep or drop.
It's the difference between mapping the work from the outside and mapping it from the people who live in it.