--- name: marketing-go-see-protocol description: "The go-see protocol's structured walk pointed at commercial data — verifying at the source systems, the customer relationship management (CRM) and enterprise resource planning (ERP) systems, that a visibility board or marketing key performance indicator (KPI) tree's numbers are actually true, not just true on the dashboard built from them. Use when: You want to verify that a visibility board or marketing KPI tree reflects what's actually true in the CRM or ERP, not just what a sync job reported. A data-sync issue has happened before and you want a real, repeatable check rather than trusting it's stayed fixed. You want to catch channel-attribution drift or reporting gaps before they shape a budget decision. Not for: The check is genuinely a one-off, not a repeatable practice — a work instruction adds structure a single check doesn't need. You'd be walking the data to catch someone doing something wrong rather than to verify the numbers themselves — that's not what a go-see walk is for." --- # Marketing go-see protocol The go-see protocol's structured walk pointed at commercial data — verifying at the source systems, the customer relationship management (CRM) and enterprise resource planning (ERP) systems, that a visibility board or marketing key performance indicator (KPI) tree's numbers are actually true, not just true on the dashboard built from them. Family: Visual management · Format: .xlsx · Domain: commercial ## What it is A marketing go-see walk is a gemba walk with real technique behind it, pointed at commercial data instead of a shop floor — the same work instruction shape (major step, key point, reason) the core go-see protocol already applies to observation. Describe the walk roughly, and real steps get drafted: which numbers to re-check directly at the source system, how to sample real records rather than trust the dashboard, and why each technique matters. ## When to use it Use it when: - You want to verify that a visibility board or marketing KPI tree reflects what's actually true in the CRM or ERP, not just what a sync job reported. - A data-sync issue has happened before and you want a real, repeatable check rather than trusting it's stayed fixed. - You want to catch channel-attribution drift or reporting gaps before they shape a budget decision. Not when: - The check is genuinely a one-off, not a repeatable practice — a work instruction adds structure a single check doesn't need. - You'd be walking the data to catch someone doing something wrong rather than to verify the numbers themselves — that's not what a go-see walk is for. ## How to fill it in - **purpose** — What does this walk verify, and what would go unnoticed without it? - **steps** — Drafted from your description of the walk — major steps, each with zero or more key points and, for every key point, the reason it matters. - **narrative** — Drafted from the steps actually built. ## What good looks like The example below checks Beacon Analytics' visibility board and marketing KPI tree against the real CRM and ERP records — three of four steps have a real key point tracing back to a genuine sync-job finding, and the fourth, channel misattribution, is honestly left flagged rather than padded. Full worked example, on-screen and as a downloadable .xlsx: https://www.katafacts.com/katas/marketing-go-see-protocol ## Common mistakes - **Re-reading the dashboard more carefully instead of checking the source system it's built from.** — A dashboard built from a broken sync can look internally consistent while being wrong — only checking the CRM or ERP directly catches that class of drift. - **Asking the marketing ops analyst leading questions about the known sync issue instead of open ones.** — A leading question gets confirmation of what you already suspect, not a real, fresh answer about what's actually slow or manual right now. ## What it connects to Upstream: - **Marketing key performance indicator (KPI) tree** (`marketing-kpi-tree`) — A driver metric named there (like sync-data completeness) is exactly what this walk exists to verify at the source, not just trust as fixed. - **Visibility board** (`visibility-board`) — A go-see walk exists to verify the board's own numbers against reality, the same relationship the core go-see protocol has with a visual board. ## Where AI helps Judgement — stays with you: - Deciding whether a step genuinely needs a key point or is simple enough not to - Deciding what a drifted number actually means for the team Analysis — AI helps: - Drafting major steps, key points, and reasons from a description of the walk - Drafting the narrative from the steps actually built Drudgery — automated: - Counting steps and key points - Identifying which steps still have no key point - Exporting to xlsx in the house format --- Marketing go-see protocol 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/marketing-go-see-protocol.