Branch Metrics Truth Test

This workflow turns “we have numbers” into “we have evidence.” It first tries to answer using your Calypso Knowledge Base (definitions, metric owners, measurement notes). If the request is messy—as real requests usually are—it routes the user into a short menu of decision-shaped prompts.

Each option returns a practical checklist written to prevent the most common failure mode in branch decision-making: data that looks clean enough to win a meeting, right up until it produces a confident wrong call.

• Uses a Knowledge Base assistant first, so definitions and local measurement rules are applied before advice.
• Button-based decision menu that maps to common branch signal pitfalls (trust, dirtiness, automation vs judgment, comparisons, culture).
• Provides “do-this-next” checks (owners, lag, denominator, selection bias, instrumentation) instead of abstract theory.
• Includes an escalation path to route complex cases to a human reviewer.

1. User Input starts the workflow when a user asks a question about branch signals, conversations, or decisions.
2. Knowledge Assistant attempts an answer from your Calypso Knowledge Base first (and falls back to routing if it can’t confidently respond).
3. Pick a decision presents a menu of common decision situations.
4. If the user selects Which branch numbers should I trust?, the workflow sends a checklist to separate “audited signals” from “polished noise.”
5. If the user selects How do I spot dirty signal fast?, the workflow sends red flags and quick tests before a meeting goes off the rails.
6. If the user selects Automation vs human judgment, the workflow sends rules-of-thumb for when to let automation decide—and when to keep a human in the loop.
7. If the user selects Comparing branches & attribution, the workflow sends a comparison playbook to avoid false winners and attribution traps.
8. If the user selects Build a signal culture, the workflow sends lightweight operating habits that help decisions happen (not just slides).
9. If the user selects Have someone sanity-check this, the workflow hands off to a human team for review.

• Optional (recommended): Populate your Calypso Knowledge Base with metric definitions (denominators, inclusion/exclusion rules), branch naming conventions, instrumentation notes, and metric owners.
• No external credentials required for this workflow template as shipped.
• Operational prerequisite: Decide which internal team should receive escalations (set the department name in the handoff node).