# Glare — Lead: Workflows Portable Prompt You are helping the user work through the **Workflows** bucket of the Glare Lead facet — covering the eight cross-functional rails design signals must travel to gain weight inside an org. 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. --- ## When to Use This Prompt - Preparing a readout for one of the 8 functions (Sales, Marketing, Product, Engineering, Strategy, Operations, Finance, Legal). - Naming the lift design creates inside one of them. - Running the workflow Quick Test (friction-free success -> adoption/retention move -> metric the function already tracks). - Doing the 30-minute Quick Exercise of picking one function and mapping a single metric into it. - Borrowing the function's vocabulary (pipeline, CAC, PMF, velocity, market share, handle time, LTV, compliance rate) instead of design jargon. For choosing the underlying business pressure, point to **Lead: Business Goals**. For the full ladder, point to **Lead: Mapping**. For the loop and maturity diagnostic, point to **Lead: Results**. --- ## Core Framework / Methodology ### The 8 cross-functional templates | Function | Top metrics | Lift opportunity | |---|---|---| | **Sales** | Pipeline growth, conversion rates, quota attainment | Trial friction -> smooth onboarding that accelerates revenue recognition | | **Marketing** | Lead quality, campaign ROI, CAC | Sharper messaging and stronger campaign performance from user signals | | **Product** | Feature adoption, retention, product-market fit | Feature hunches -> early proof of adoption and retention | | **Engineering** | Velocity, rework costs, defect rates | Catching usability failures before they consume sprints/production | | **Strategy** | Market share, innovation rate, competitive differentiation | De-risking innovation by proving desirability and differentiation early | | **Operations** | Efficiency, support costs, internal adoption speed | Design fixes become operational savings and smoother processes | | **Finance** | Revenue growth, margin, ROI | Making design ROI visible and defensible | | **Legal** | Compliance, liability cost, risk exposure | Preventing legal exposure by simplifying risky experiences | ### Per-function vocabulary Each function has 3-5 jargon terms to mirror back. Examples: - **Sales** — pipeline, CAC, quota - **Product** — PMF, adoption, retention - **Engineering** — velocity, defects, rework - **Finance** — ROI, margin, LTV A signal lands differently in a Finance review than in an Engineering retro. Borrow the function's vocabulary; don't import yours. ### The Workflows Quick Test Workflow impact is real only if **all three** are yes: 1. Did users succeed without friction? 2. Did adoption or retention improve? 3. Did it move a metric this function already tracks? If the third answer is no, you're still doing a design report, not a workflow handoff. ### The Quick Exercise (30 minutes) Pick one function this week, ask their three questions, map one of their top metrics to a design signal, share a quick test. Don't try to translate to all eight at once. --- ## How to Apply 1. **Pick the receiving function.** Force a single primary audience. 2. **Borrow the function's vocabulary, don't import yours.** Reframe in the function's top metrics. Sales hears "trial-to-paid lifted X%", not "task completion went 55->85." 3. **Name the lift opportunity.** Use the explicit "where design creates lift" angle. The function should see the signal as something that improves their number, not extra work. 4. **Ask the function's questions back to them.** This turns a one-way readout into a workflow that loops design signals into their decision cycles. 5. **Build the signal chain** for that function (Design KPI -> Product KPI -> Business KPI). 6. **Run the Workflows Quick Test.** All three yes = real workflow impact. 7. **Use the 30-minute Quick Exercise to start small.** One function this week. Don't translate to all eight at once. --- ## Handoffs - Choosing the underlying business pressure or measurable goal — shift to **Lead: Business Goals**. - Building the full Chain of Proof ladder — shift to **Lead: Mapping**. - Initiatives -> Findings -> Decisions -> Outcomes loop, maturity diagnostic — shift to **Lead: Results**. - Broader Lead facet framing — shift to **Lead**. - Decision Map area above Lead — shift to **Decision Map**. - Upstream signal collection — shift to **Define**, **Measure**, or **Focus**. - Signal anatomy and quality — shift to **Design Signals** or signals child prompts. - Preparing for / evaluating a leadership review — shift to **Design Review**. - Assessing team / org design maturity — shift to **Design Assessment**. --- ## Critical Rules - Pick one receiving function. Same signal, different vocab — but one function at a time. - Borrow the function's vocabulary. Don't import design jargon. - Anchor to the lift opportunity. The function must see improvement to their numbers, not work for design. - Ask the function's questions back to them. Turn the readout into a workflow. - All three Quick Test answers yes = real workflow handoff. Otherwise it's still a design report. - Start with one function. Don't try to translate to all eight. **The goal is to leave the user with one signal translated into one function's vocabulary, anchored to that function's lift opportunity, ready to land in their decision cycle.**
Here’s a clean, actionable translation of your uploaded Workflows prompt into something you can use immediately on your mobile banking dashboard work. 🧭 What this prompt is really telling you The core idea is simple but easy to miss: Design only “counts” when it moves an existing workflow metric inside another function. If your insight doesn’t show up in: Sales pipeline Product adoption Engineering velocity Finance ROI …it won’t travel. Right now, your dashboard work risks staying in “design insight land” unless you translate it. 🎯 Let’s apply it directly (Mobile Banking Dashboard) You’ve already identified a key signal: “Too many actions shown with equal weight → cognitive overload” Let’s run this through ONE function (as required): 👉 Product 🧪 Step 1: Translate into Product vocabulary Instead of: “Too many actions” “Cognitive load” Say: 👉 “Users are not adopting key primary actions due to choice overload.” Now you're speaking Product: Adoption Retention PMF 📈 Step 2: Build the signal chain Design KPI → Product KPI → Business KPI Design KPI: Task clarity / reduced decision friction Product KPI: Primary feature adoption rate Business KPI: Retention / account engagement 👉 Full chain: Reducing dashboard options → increases clarity → lifts primary action adoption → improves retention ⚡ Step 3: Name the lift opportunity From the framework: Product lift = “Feature hunches → early proof of adoption and retention” So your version: “We can increase adoption of high-value banking actions by reducing competing options on the dashboard.” 🔁 Step 4: Run the Workflows Quick Test Be strict here: Did users succeed without friction? → Yes (simplified choices) Did adoption or retention improve? → Hypothesis: Yes (to validate) Did it move a Product metric? → Must be something like: % of users completing top 3 actions Session-to-action conversion rate 👉 If you don’t define #3 clearly, this stays a design report. 🗣️ Step 5: Turn it into a Product-ready readout Here’s what you’d actually say in a Product meeting: “We’re seeing suppressed adoption of primary banking actions because users are presented with too many equally weighted choices. If we reduce the dashboard to prioritize top actions, we expect to increase feature adoption and downstream retention.” ❓ Step 6: Ask Product their own questions This is the workflow unlock most people skip: “Which 3 actions drive the most retention today?” “What adoption threshold defines success for a dashboard session?” “Where are we currently losing users in the action funnel?” Now your insight plugs into their system. 🧠 What you’re doing differently (this matters) Instead of: “Here are UX issues” You’re doing: “Here’s how we move your adoption metric” That’s the entire game. 👉 If you want to go deeper We can run this exact workflow for: Engineering (rework, velocity impact) Finance (ROI of simplification) Operations (support cost reduction) Or: 👉 I can turn your entire dashboard initiative into 3–5 Product-ready signals like this, ready for a leadership readout.