Lead: Workflows

# Workflows AI Skill Lead Area · Workflows Block · Decision Map · Oct 23, 2026 (v1.1) --- ## 1. What the Skill Does The Workflows skill helps teams connect design signals to the business functions that own the numbers. It is the second block in the Lead area of Glare's Decision Map, after Business Goals and before Mapping. Every company already runs on workflows: finding customers, keeping them, launching products, managing costs, reducing risk. The skill speaks each function's language across eight functions. | Function | Top metrics | Where design creates lift | |---|---|---| | Sales | Pipeline growth, conversion, quota attainment | Clearing friction from demos and trials | | Marketing | Lead quality, campaign ROI, acquisition cost | Clear messages and pages before the spend | | Product | Feature adoption, retention, product–market fit | Early proof of adoption and retention | | Engineering | Velocity, rework cost, defect rates | Catching usability failures before handoff | | Strategy | Market share, innovation rate, differentiation | Proving desirability before big bets | | Operations | Efficiency, support costs, internal adoption | Smoother flows and internal tools | | Finance | Revenue growth, margin, ROI | Making design ROI visible | | Legal | Compliance, liability cost, risk exposure | Clearer consent and accessible flows | In Focus, every bet names the workflow that owns its result, so that function knows the change is coming and which of its metrics should move. ### The Owner Rule Every KPI in the chain needs a function that owns it and acts on the verdict. A signal no function owns stays in a deck. The skill also runs the Quick Test: did users succeed without friction, did adoption or retention improve, and did it move a metric this function already tracks? ## 2. Business Benefit Design gets sidelined when it can't show its effect on the functions that run the business. Speaking their language puts design signals into decisions those teams are already making. This helps teams: - translate a finding into each function's own metrics - know who owns each KPI before the bet ships - bring functions into a test instead of reporting to them after - turn internal concerns into hunches Measure can test ## 3. Skill Output When used correctly, the skill produces a workflow map for a bet. The example below shows how this works for a mobile banking dashboard. | Field | Example Output (Mobile Banking Dashboard) | |---|---| | Bet | Back the redesigned home screen (from Focus → Bets) | | Owning Function | Product: owns sessions ending without an action and monthly active use | | Also Affected | Operations: owns support calls about balance. Marketing: loses promo space on the home screen | | In Their Language | Product: fewer abandoned sessions. Operations: fewer "where's my balance" calls. Marketing: promo clicks may drop; watch campaign ROI | | Internal Hunch to Test | Marketing believes moving promos lower will cut offer sign-ups (sent to Measure → Hunches) | | Failure Mode to Watch | Telling Marketing after launch. The function that loses something should hear about it before the bet ships. | | Next Step Handoff | → glare-lead-mapping to trace the chain from the user need to the business goal | ## 4. Prompt Strategies The prompts below show different ways to use this skill. Each example uses a mobile banking dashboard update. ### Prompt 1: Owner Entry: Find who owns the result *"We're backing the redesigned mobile banking home screen. Using the glare-lead-workflows skill, name the function that owns each KPI in the chain, and which other functions the change affects."* **Why this works:** It puts an owner on every number before the bet ships. **Best for:** - preparing a bet for launch - cross-functional planning ### Prompt 2: Translation Entry: Speak each function's language *"Our finding: first-click success on balance rose from 61% to 79%. Using glare-lead-workflows, translate it for Product, Operations, and Finance using each function's top metrics."* **Why this works:** The same finding means different things to different teams. Translating it gets it into their decisions. **Best for:** - stakeholder updates - leadership reviews ### Prompt 3: Concern Entry: Turn pushback into a hunch *"Marketing says the new mobile banking home screen will hurt offer sign-ups. Using glare-lead-workflows, turn this into an internal hunch with the KPI that would prove it, and send it to Measure."* **Why this works:** Pushback becomes something the team can test instead of argue about. **Best for:** - functions that resist a change - launch risk reviews --- *Glare Framework · glare-lead-workflows · Lead Area. Handoffs: glare-lead-business-goals · glare-lead-mapping · glare-lead-results · glare-measure-hunches (internal hunches) · glare-design-assessment*

⬇ Download SKILL.md