--- name: stakeholder-coverage-map description: "How much of the population you actually need to reach is even tracked, and, within what's tracked, how completely each unit's required roles have a real named contact — both computed, not asserted, with dark units and systemically-missing roles flagged plainly. Use when: A commitment or a market depends on real, named engagement across more units than you can track from memory, and you want an honest measure of how complete that engagement actually is. Not for: You need to calculate or model the population size itself — that's a sizing exercise (firmographic filtering, technographic signals), a different discipline from this one; this tool takes a stated population size as given and starts from there. You don't have any real contacts yet for any unit — that's fine as a starting point, but write the population and roles first and let the map show 0% honestly rather than padding it with guesses." --- # Stakeholder coverage map How much of the population you actually need to reach is even tracked, and, within what's tracked, how completely each unit's required roles have a real named contact — both computed, not asserted, with dark units and systemically-missing roles flagged plainly. Family: Kaizen events · Format: .xlsx · Domain: core ## What it is A stakeholder coverage map answers two separate completeness questions honestly, not one blended impression. First: of the whole population you need real engagement across, how much is even tracked as a named unit — a department, a site, an account? Second: within what's tracked, how completely does each unit's required roles have a real, named contact, not just a company or department name on a list? Both are computed from what you actually enter, never asserted. Every tracked unit with zero real contacts is named directly as a dark unit, and every role that's systemically under-covered across the tracked population is flagged the same way — the honest-gap discipline this catalogue applies everywhere, here applied to a real person's name rather than a number. ## When to use it Use it when: - A commitment or a market depends on real, named engagement across more units than you can track from memory, and you want an honest measure of how complete that engagement actually is. - You want to know which units have no real contact at all, and which required roles are systemically missing across the population you do track — before either becomes a problem. - You have a rough sense of the whole population's size and want to see honestly how much of it is even on your radar yet, not just how good the part you're tracking looks. Not when: - You need to calculate or model the population size itself — that's a sizing exercise (firmographic filtering, technographic signals), a different discipline from this one; this tool takes a stated population size as given and starts from there. - You don't have any real contacts yet for any unit — that's fine as a starting point, but write the population and roles first and let the map show 0% honestly rather than padding it with guesses. - The population is small enough to track from memory without losing anyone — a handful of units doesn't need a coverage map; use judgement, not process, for a small population. ## How to fill it in - **targetUnits** — Describe the scope roughly — a first-pass list of tracked units gets drafted, each with a segment. Add or correct with the real ones you're actually tracking; the gap between this list and your stated scope size is itself a real finding. - **contacts** — Only enter a contact where you actually have a real, named person for a real unit and role. An empty cell is a real gap — never invent a plausible-sounding name to make coverage look better than it is. - **coverage** — Computed for you from your target units, required roles, and known contacts — nothing to enter here. - **narrative** — Drafted from the map actually built. - **nextSteps** — What will you do about a dark unit or a systemic role gap, ranked by impact and effort, owned and dated. ## What good looks like The example below tracks a regional safety-protocol rollout — only 8 of the region's 12 sites are actually tracked yet, one tracked site has no contact at all, and Union safety rep is honestly named as the systemically under-covered role rather than smoothed over. Full worked example, on-screen and as a downloadable .xlsx: https://www.katafacts.com/katas/stakeholder-coverage-map ## Common mistakes - **Treating a company or unit name on a list as real coverage.** — A unit with no named contact behind it is a dark unit, not a covered one — this tool exists specifically to stop a long list from being mistaken for real reach. - **Inventing a plausible-sounding contact to make a gap look filled.** — A fabricated name defeats the entire point of this tool — the honest gap is the useful signal; papering over it just moves the discovery of the real gap to a worse moment. - **Building the map once and never revisiting it.** — A contact that was real six months ago and never reverified isn't reliable coverage today — this is a living measure, not a one-time snapshot. ## What it connects to Upstream: - **Kaizen event charter** (`kaizen-charter`) — A kaizen event's roster names who's on the team; a stakeholder coverage map is the same discipline applied to a much larger population that can't be tracked from memory. Downstream: - **Implementation plan** (`implementation-plan`) — A newly-identified contact for a dark unit is exactly the kind of real, named dependency an implementation plan's milestones get built around. ## Where AI helps Judgement — stays with you: - Deciding whether a drafted target unit or required role actually reflects the real population - Deciding which dark unit or role gap to chase down first Analysis — AI helps: - Drafting a target-unit list and required roles from a rough description of the scope - Drafting the narrative from the map actually built Drudgery — automated: - Computing list coverage and contact coverage percentages - Flagging dark units and tallying role gaps - Exporting to xlsx in the house format --- Stakeholder coverage map is licensed [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Attribution: Katafacts (katafacts.com). ## Using this skill Apply this method as part of whatever broader task, instructions, or deliverable you're already working on -- it's a method to use, not a standalone conversation to start. There is no generation tool for this catalogue yet, so draft the artifact's actual content yourself, following the fields above, the same way a person filling this out by hand would. The canonical guide page and a downloadable worked example (.xlsx) are at https://www.katafacts.com/katas/stakeholder-coverage-map.