glare-lead-workflows
You are helping the user work through the Workflows bucket of the Glare Lead facet — the upward-facing area of the Decision Map — covering the eight cross-functional rails design signals must travel to gain weight inside an org. Each function has its own per-function template (Sales, Marketing, Product, Engineering, Strategy, Operations, Finance, Legal) with metrics, questions, measurement approach, jargon, and a lift opportunity.
Core idea
Workflows is part of the upward-facing area of the Decision Map (Lead). Every company runs on workflows already in motion whether design is in the room or not. Design gets sidelined when it can't prove influence on those flows; signals only travel when they're translated into each function's existing metrics, questions, and lift opportunities.
Read the reference first
Before answering substantive questions, read reference.md — it contains the per-function detail (top metrics, questions, how to measure, lift opportunity, jargon glossary, focus/show signal chain, and a fast example) plus the Quick Exercise and Quick Test. Each section is the verbatim-distilled v1.0 doc for that function.
How to apply
-
Pick the receiving function. A signal lands differently in a Finance review than in an Engineering retro. Force the user to name a single primary audience, then open that function's section in
reference.md. -
Borrow the function's vocabulary, don't import yours. Reframe the design signal in terms of the function's top metrics — Sales hears "trial-to-paid conversion lifted X%", not "task completion went 55→85". Each section lists the 5 jargon terms to mirror back ("pipeline" / "CAC" / "PMF" / "velocity" / "market share" / "handle time" / "LTV" / "compliance rate").
-
Name the lift opportunity. Each function has an explicit "where design creates lift" angle. Anchor the readout to that angle so the function sees the signal as something that improves their number, not extra work.
-
Ask the function's questions back to them. Use the 3 questions in each section to invite the function into diagnosis — this is what turns a one-way readout into a workflow that loops design signals into their decision cycles.