[{"data":1,"prerenderedAt":187},["ShallowReactive",2],{"/en/workflows/signal-to-decision-reality-coach":3},{"id":4,"slug":5,"locale":6,"translationGroupId":7,"localeSwitchApproved":8,"title":9,"description":10,"documentationMarkdown":11,"workflowJson":12,"category":168,"tags":169,"integrations":172,"difficulty":173,"author":174,"verified":33,"featured":33,"date":175,"modified":175,"icon":7,"imageSrc":7,"path":176,"alternates":177,"seo":178},"172aa0aa-889d-4069-98b6-12abb3295406","signal-to-decision-reality-coach","en",null,true,"Signal-to-Decision Reality Coach","An advisor-style decision helper that routes leaders through practical checks for branch numbers, dirty signals, automation vs. judgment, and building a signal culture—without turning it into an academic lecture.","## How it works\nThis workflow helps leaders turn messy branch signals (numbers, conversations, attribution, “what we’re hearing”) into decisions that won’t embarrass them later. It starts by offering a knowledge-base answer when possible, then routes the user into one of four decision-shaped mini-coaching tracks.\n\nIt’s designed for the real world where bad data usually looks “pretty reasonable” right up until someone presents it confidently in a meeting. The flow gives quick, usable checks: what to trust, what to question, and what typically breaks first.\n\n## Key features\n- Knowledge-base first response to capture existing playbooks before reinventing them.\n- Button-based routing into four practical coaching tracks (trust, dirty signal, automation vs. judgment, signal culture).\n- “Sense-check” guidance focused on branch comparisons, conversations, and attribution pitfalls.\n- Clear fallback handoff to a dedicated Data & Insights team when the situation is ambiguous or high-stakes.\n\n## Step-by-step\n1. **Trigger:** A user starts the workflow.\n2. **Knowledge base policy:** The workflow attempts to answer using your knowledge base first (and only routes if needed).\n3. **Menu:** The user chooses what they need help with:\n   - *Which branch numbers deserve trust?*\n   - *How to spot dirty signal fast*\n   - *When to trust automation vs. human judgment*\n   - *How to build a signal culture that drives decisions*\n4. **Routing:** The workflow checks which button was clicked and sends the matching coaching response.\n5. **Fallback (if no match):** If the selection is unclear, the workflow hands off to **Data & Insights** with a short explanation message.\n\n## Setup requirements\n- No credentials are required.\n- To get the most value, connect this workflow to an active **Knowledge Base** in Calypso (recommended, not required).\n- If you want live escalation, ensure your **Data & Insights** department is available to receive handoffs.",{"id":13,"teamId":14,"name":9,"version":15,"workflowVersion":16,"nodes":17,"connections":142,"routingEnabled":8,"active":33},"wf_signal_decision_reality_coach_v1","calypso-public-library","1.0.0",1,[18,34,40,52,77,87,96,102,108,114,120,126,132],{"id":19,"name":20,"type":21,"typeVersion":16,"position":22,"parameters":24,"category":32,"deletable":33,"connectable":33},"node_flowcfg","Workflow settings","flow-configs",[23,23],0,{"name":9,"description":25,"tags":26,"triggerType":31},"Routes leaders through practical signal checks: branch-number trust, dirty-signal spotting, automation vs judgment, and decision-driving signal culture.",[27,28,29,30],"signal-design","decision-systems","branch-metrics","data-quality","input","policy",false,{"id":35,"name":36,"type":31,"typeVersion":16,"position":37,"parameters":39,"category":31,"deletable":33,"connectable":8},"node_input","Start",[23,38],160,{},{"id":41,"name":42,"type":43,"typeVersion":16,"position":44,"parameters":46,"category":51,"deletable":8,"connectable":8},"node_kb","Knowledge base answer (if available)","knowledge-base-policy",[45,38],240,{"enabled":8,"fallbackToRouting":8,"sticky":33,"stickyMode":47,"activationOpener":48,"personalization":50},"default",{"enabled":8,"instruction":49},"Answer from the knowledge base when you can. If the user is asking for judgment, tradeoffs, or a reality-check, route them to the menu.",{"useContactName":33},"response",{"id":53,"name":54,"type":55,"typeVersion":16,"position":56,"parameters":58,"category":51,"deletable":8,"connectable":8},"node_menu","Choose your decision check","interactive-message",[57,38],520,{"messageType":59,"headerText":60,"bodyText":61,"footerText":62,"sectionTitle":63,"buttons":64,"ctaDisplayText":63,"ctaUrl":63},"button","Research, signal design, and decision systems","Pick what you’re trying to decide. I’ll give you a fast reality-check you can use before the meeting gets… confident.","If a number is too clean, the mess moved upstream.","",[65,68,71,74],{"id":66,"title":67},"trust_branch_numbers","Trust branch numbers",{"id":69,"title":70},"spot_dirty_signal","Spot dirty signal",{"id":72,"title":73},"automation_vs_judgment","Auto vs judgment",{"id":75,"title":76},"signal_culture","Build signal culture",{"id":78,"name":79,"type":80,"typeVersion":16,"position":81,"parameters":84,"category":86,"deletable":8,"connectable":8},"node_if_trust","If: trust branch numbers","if",[82,83],760,120,{"buttonId":66,"operator":85},"equals","routing",{"id":88,"name":89,"type":90,"typeVersion":16,"position":91,"parameters":94,"category":51,"deletable":8,"connectable":8},"node_text_trust","Coach: numbers you can trust (and the polished noise)","text-message",[92,93],1000,80,{"text":95},"Here’s the quickest way to tell “decision-grade” branch numbers from polished noise:\n\n1) **Trust numbers that have friction.** If the metric is hard to game (tied to cash, audited events, or constrained capacity), it’s usually more trustworthy.\n2) **Distrust numbers that get better with storytelling.** If a metric improves when someone re-labels categories, changes attribution, or tweaks the definition—treat it like a mood, not a fact.\n3) **Compare branches only after you normalize the boring stuff:** opening hours, staffing, local demand, product mix, and rollout timing. Otherwise you’re mostly comparing context.\n4) **Look for “one-metric miracles.”** If only one KPI improves while upstream drivers (traffic, leads, inventory, call volume) don’t move, you’re likely seeing reporting drift.\n5) **Ask the reliability questions out loud:**\n   - What changed in logging/definition this month?\n   - Where does the number come from *before* it becomes a dashboard?\n   - If a branch wanted to look good, how would they do it?\n\nRule of thumb: **If you can’t explain how it breaks, you don’t understand it enough to bet on it.**",{"id":97,"name":98,"type":80,"typeVersion":16,"position":99,"parameters":101,"category":86,"deletable":8,"connectable":8},"node_if_dirty","If: spot dirty signal",[82,100],220,{"buttonId":69,"operator":85},{"id":103,"name":104,"type":90,"typeVersion":16,"position":105,"parameters":106,"category":51,"deletable":8,"connectable":8},"node_text_dirty","Coach: dirty signal before the meeting derails",[92,100],{"text":107},"Dirty signal rarely announces itself. It shows up as **clean-looking confidence with weird little seams**. Here are the fastest tells:\n\n- **Definition drift:** “conversion,” “qualified,” or “resolved” quietly means something new. Trend lines lie beautifully when definitions change.\n- **Timing games:** end-of-week spikes, end-of-month heroics, or sudden ‘catch-up’ batches. Real behavior doesn’t usually look like payroll.\n- **Missingness that isn’t random:** if one branch (or one rep) has lots of blanks, it’s not just a data issue—it’s a process issue.\n- **Too-perfect consistency:** identical outcomes across days/teams often means defaults, copy-paste, or auto-fill.\n- **Attribution that flatters the org chart:** when credit maps neatly to who needs the win.\n\nA practical meeting move: **ask for the “ugly table.”** One page of raw counts by branch, by week, with the definition printed on top. If nobody can produce it, the deck is doing more work than the data.",{"id":109,"name":110,"type":80,"typeVersion":16,"position":111,"parameters":113,"category":86,"deletable":8,"connectable":8},"node_if_auto","If: automation vs judgment",[82,112],320,{"buttonId":72,"operator":85},{"id":115,"name":116,"type":90,"typeVersion":16,"position":117,"parameters":118,"category":51,"deletable":8,"connectable":8},"node_text_auto","Coach: when to trust automation vs human judgment",[92,112],{"text":119},"Automation is great at consistency. It’s terrible at noticing when reality changed.\n\n**Trust automation when:**\n- The input signal is stable, well-instrumented, and hard to game.\n- The decision is reversible (you can roll it back quickly).\n- The cost of being slightly wrong is low, and the cost of being slow is high.\n\n**Require human judgment when:**\n- The metric can be optimized without improving reality (classic Goodhart’s Law territory).\n- You’re crossing a threshold decision: staffing cuts, branch ranking, incentive payouts, compliance actions.\n- The environment is shifting: new product, new script, new market, new CRM fields—anything that changes how data is produced.\n\nPractical guardrail: **automate the routine, escalate the edge cases.** If your automation can’t explain *why* it chose something (inputs + rule), it’s not decision support—it’s a coin flip with better UI.",{"id":121,"name":122,"type":80,"typeVersion":16,"position":123,"parameters":125,"category":86,"deletable":8,"connectable":8},"node_if_culture","If: signal culture",[82,124],420,{"buttonId":75,"operator":85},{"id":127,"name":128,"type":90,"typeVersion":16,"position":129,"parameters":130,"category":51,"deletable":8,"connectable":8},"node_text_culture","Coach: build a signal culture that helps decisions happen",[92,124],{"text":131},"A good signal culture doesn’t produce more dashboards. It produces **faster, calmer decisions**.\n\nBuild it with a few habits that sound small but change everything:\n\n1) **One metric, one use.** If the same KPI is used for learning *and* punishment, people will optimize appearances. Split “learning metrics” from “score metrics.”\n2) **Write the definition next to the number.** Every time. If you can’t fit the definition, the metric is too vague.\n3) **Make “disconfirming evidence” a status signal.** Reward the person who says, “This branch looks bad, but here’s why the comparison is unfair.”\n4) **Track the production line, not just the outcome.** Where did the data come from? Which fields were optional? What was auto-filled?\n5) **Do post-decision audits.** Pick 3 decisions/month and ask: Were we right? What signal misled us? What would we change upstream?\n\nWit-and-wisdom version: **If the culture only celebrates certainty, you’ll get certainty—manufactured on demand.**",{"id":133,"name":134,"type":135,"typeVersion":16,"position":136,"parameters":137,"category":141,"deletable":8,"connectable":8},"node_fallback","Escalate to Data & Insights","fallback",[92,57],{"handoffMessage":138,"departmentId":139,"departmentName":140},"This looks like a high-stakes or ambiguous signal question. I’m handing this to Data & Insights so they can sanity-check definitions, data lineage, and branch comparability before you act on it.","dept_data_insights","Data & Insights","terminal",[143,146,148,150,153,156,158,160,162,164,166],{"id":144,"source":35,"target":41,"sourceHandle":47,"targetHandle":47,"type":145},"conn_input_kb","edge",{"id":147,"source":41,"target":53,"sourceHandle":47,"targetHandle":47,"type":145},"conn_kb_menu",{"id":149,"source":53,"target":78,"sourceHandle":47,"targetHandle":47,"type":145},"conn_menu_if_trust",{"id":151,"source":78,"target":88,"sourceHandle":152,"targetHandle":47,"type":145},"conn_if_trust_true","true",{"id":154,"source":78,"target":97,"sourceHandle":155,"targetHandle":47,"type":145},"conn_if_trust_false_to_dirty","false",{"id":157,"source":97,"target":103,"sourceHandle":152,"targetHandle":47,"type":145},"conn_if_dirty_true",{"id":159,"source":97,"target":109,"sourceHandle":155,"targetHandle":47,"type":145},"conn_if_dirty_false_to_auto",{"id":161,"source":109,"target":115,"sourceHandle":152,"targetHandle":47,"type":145},"conn_if_auto_true",{"id":163,"source":109,"target":121,"sourceHandle":155,"targetHandle":47,"type":145},"conn_if_auto_false_to_culture",{"id":165,"source":121,"target":127,"sourceHandle":152,"targetHandle":47,"type":145},"conn_if_culture_true",{"id":167,"source":121,"target":133,"sourceHandle":155,"targetHandle":47,"type":145},"conn_if_culture_false_fallback","automation",[27,28,29,30,170,171],"attribution","leadership-ops",[],"intermediate","Calypso","2026-05-27T11:03:11.804Z","/en/workflows/signal-to-decision-reality-coach",{"en":176},{"title":179,"description":180,"ogDescription":181,"twitterDescription":182,"canonicalPath":176,"robots":183,"schemaType":184,"alternates":185},"Signal to Decision Reality Coach","Route leaders to practical checks for branch metrics, dirty signals, automation judgment calls, and decision ready insights.","A decision coach that turns messy branch signals into trustworthy choices—branch numbers, dirty data, automation vs judgment, and signal culture.","Make better calls with messy signals: branch metrics trust checks, dirty signal spotting, automation vs judgment, and culture guardrails.","index,follow","HowTo",[186],{"hreflang":6,"href":176},1780761213320]