Pipeline Talk — Speaker Notes

Duration: 25 min + discussion

Audience: 10-person UX team, early with AI, concerned about job security

Deck: /for/lime

Key contact: Rachel (principal designer) — most likely champion for follow-up

Slide 1: Title — Mike (30s)

• "We're Mike and Alex, we run Goose Group. Small consultancy, builds AI software."
• "We're here to share how we work — the real process, not a pitch."

Slide 2: Who we are — Mike (1 min)

• "We build software for enterprise clients. Scheduling systems, workflow tools, operational products."
• "Over the last year we developed a process for building user-centric products with AI. This is what we learned."

Slide 3: Concentric boxes — Alex (2.5 min) ⭐

This is the frame for the whole talk. Land this clearly.

• "As a UX designer, your time goes three places. The outer ring is bureaucracy — sprint planning, design reviews, alignment. It's how organizations work. It's not bad. It's just not where your value is."
• "The middle ring is project management — tickets, status updates, handoffs."
• "The center is the actual work — talking to users, understanding their needs, designing solutions. This is where your unique judgment lives."
• "The goal with AI tools and pipelines: more time in the center. Project management should get smaller. Bureaucracy should get lighter. We're here to help you spend more time on the thing you're actually good at."

Slide 4: UX lifecycle — Alex (2 min)

• "This is your process. Three loops inside the problem-solving ring."
• "Loop 1: talk to customers, create mockups, show them, refine. Loop 2: write stories, work with engineers, they build. Loop 3: test it, meet the user again, verify."
• "This process is good. It doesn't change. What changes is you get tools inside each loop."

Slide 5: Tools in each loop — Mike (2 min)

• "In the research loop: AI structures your notes, spots patterns. You still run the interviews. You still decide what matters."
• "In the design loop: AI drafts copy, surfaces edge cases, checks designs against your principles. You make the calls. A natural place to start is the writing step — models are already good at writing."
• "In the engineering loop: AI writes user stories from your designs. Clear handoffs, fewer meetings."
• Do NOT reference the Gemini gem specifically. Just mention writing as a starting point.

Slide 6: Ripple effect — Alex (1.5 min)

• "Here's what we've seen: when you fix the center ring, the outer rings get lighter on their own."
• "Structured research means fewer alignment meetings. Clear specs mean faster design reviews. Complete handoffs mean engineers stop asking questions."
• "You solve for design. Everything else follows."

Slide 7: Our pipeline — Alex (1.5 min)

Show briefly. Don't walk through every phase. Frame as evidence.

• "We went through the same process. Started with the same loops. Built tools for each step over a year."
• "Blue is human. Green is automated. You can see where the judgment stays and where the busywork goes."
• "You don't need all of this. We didn't start here."

Slide 8: How it started — Mike (1 min)

• "The first thing we built: a tool to process interview transcripts. One conversation in, five structured documents out."
• "That revealed the next bottleneck. Then the next. A year later, 17 playbooks."
• "You need one. The first one shows you where the next problem is."

Slide 9: Playbooks — Alex (1.5 min)

• "A playbook is a structured recipe AI follows step by step. Your design system defines what a button looks like. A playbook defines how you turn research into requirements."
• "We have 17. Each one built because we kept doing the same thing manually."
• "They work with the tools you already use."

Slide 10: How we'd work together — Mike (2 min)

• "Three steps. First: find the bottleneck — at which altitude? Design, PM, or bureaucracy? Where are you spending time that should be spent on problem-solving?"
• "Second: build within your tools. Gemini, Figma, whatever you already use. We design around how you work."
• "Third: more time on design in 30 days. Better output, fewer meetings. The difference is tangible."

Slide 11: CTA — Alex (30s)

• "We'd be happy to spend more time with you on any of this."
• "We put together a starter kit with templates you can try Monday."

Reminders

Tone: Peers sharing, not experts presenting. Earnest with edge. These people are worried about their jobs — be empathetic and direct.

Core message: We're here to help you do MORE design, not less. Your judgment is the valuable part. The busywork is what goes away.

Do: Frame everything through their reality. Acknowledge the bureaucracy they're stuck in. Show empathy for the "am I going to be replaced?" fear.

Don't: Over-explain the pipeline. Name-drop tools they don't use. Reference the Gemini gem specifically. Sell. Use: unlock, synergy, scalable solutions, leverage, best practices.

Target: Channel excitement. If Rachel wants to talk more afterwards, that's success.

Total: ~18 min content + 7 min discussion