Metrics Trust Coach for Confident Decisions

This workflow turns “we have data” into “we have evidence we can bet on.” It starts with your Knowledge Base for quick answers, then guides the user through a menu of decision-shaped checks: which branch numbers deserve trust, how to catch dirty signal before a meeting, when automation is safe, and what teams routinely misread.

It’s built for the common failure mode: data that looks clean enough to win the room—right up until it drives a confident wrong decision. The flow nudges users toward practical guardrails without turning the conversation into an academic lecture.

• Uses the Calypso Knowledge Base first, then routes into a structured coaching menu if the KB can’t confidently answer.
• Interactive menu routes users to specific decision scenarios (trusting metrics, dirty signal detection, automation vs judgment, attribution pitfalls).
• Advice responses are short, operational, and meeting-ready (what to check, what usually lies, what to do next).
• “Return to menu” loop enables quick multiple checks in one session.
• Optional handoff to a human analyst for high-stakes or disputed numbers.

1. Trigger: A user starts the workflow (Input).
2. Knowledge Base pass: The workflow attempts to answer using your Knowledge Base Policy (best for “What does this metric mean?” or “How do we define X?”).
3. Decision menu: If the KB doesn’t resolve it, the user sees a menu of coaching paths (Interactive Message).
4. Routing by choice: The workflow routes based on the selected button (If nodes):
   1. Which numbers to trust → a checklist for reliability (Text Message), then returns to the menu.
   2. Spot dirty signal fast → fast “pre-meeting” tripwires (Text Message), then returns to the menu.
   3. Automation vs judgment → when to let systems decide and when to intervene (Text Message), then returns to the menu.
   4. Messy evidence → usable insight → how to summarize without “cleaning away the truth” (Text Message), then returns to the menu.
   5. Comparing branches & attribution → the misreads that break comparisons (Text Message), then returns to the menu.
   6. Build a signal culture → habits that produce decisions, not slides (Text Message), then returns to the menu.
   7. Talk to an analyst → hands off to your Research Ops / Analytics team (Fallback).

• Calypso Knowledge Base: Recommended. Populate entries for metric definitions, branch reporting rules, attribution logic, and known data caveats.
• Department for handoff (optional): Configure the “Research Ops / Analytics” department so the fallback handoff goes to the right team.
• No external credentials are required by this workflow.