0
Skip to Content
UK plc case study
AI Audit
about
capabilities
experience
intelligence
Woolf
Woolf
contact
UK plc case study
AI Audit
about
capabilities
experience
intelligence
Woolf
Woolf
contact
UK plc case study
AI Audit
about
capabilities
experience
intelligence
contact

Session 11

15/12/2025

AI Voice-Over
Generate a VO and sound effects for an ad in multiple languages

Category
Production

  • https://elevenlabs.io/

Session 12

16/12/2025

Scaling image production

Using Google tools to massively increase the volume of outputs from Nanobanana

Category
Image generation

  • https://docs.google.com/presentation/d/1H8y77uB_Uxwbe55l7Wi6-KaQOdovDFxXpr82SBgWNTE/edit?usp=sharing

Session 13

17/12/2025

Synthetic Surveys

Use AI doubles to test ideas

Category

STRATEGY/RESEARCH

Session 14

18/12/2025

Video editing with AI

Edit, voice, corrections and graphics

Category

VIDEO PRODUCTION

Session 15

19/12/2025

Use AI to analyse large, messy data

Like survey responses, support tickets or other customer feedback

Category

STRATEGY/INSIGHT

  • [h/t @nate.b.jones]

    You are my 2-hour "voice of customer" intern.

    I will give you raw user feedback (e.g., CSV of survey responses, support tickets, or a long doc of quotes).

    Your job:

    - turn this swamp into clear themes,

    - pull out specific, repeated problems,

    - and translate it into product input I can use.

    Work in 4 phases and log after each phase.

    PHASE 1 – MAP & SAMPLE

    - Describe what this feedback set is:

    - where it seems to come from,

    - roughly how many items,

    - what fields/columns exist (if structured).

    - Do a quick sample read to get a feel for tone and topics.

    - Write a short paragraph: "Roughly, this is feedback from [who] about [what] with [tone]."

    PHASE 2 – CLUSTER & THEMES

    - Group feedback into 8–12 themes:

    - e.g., onboarding, reliability, performance, UX, pricing, support.

    - For each theme:

    - describe it in 2–3 sentences,

    - estimate its frequency (high/medium/low),

    - include 2–3 short, representative quotes (lightly cleaned, anonymized).

    - Call out any themes that surprised you or contradict our likely self-image.

    PHASE 3 – PROBLEM STATEMENTS

    For the top 5 themes by importance (intensity × frequency):

    - Write:

    - 1 sentence problem statement in the user's voice: "As a [user], I struggle with…"

    - 3–5 specific situations or workflows where this pain shows up.

    - Any signals of willingness to pay or churn risk if it's not fixed.

    PHASE 4 – PRODUCT BRIEF FOR PM/LEADERSHIP

    Produce a concise doc aimed at a PM / Head of Product:

    - "What users are trying to do" – 5–10 bullets in plain language.

    - "What's getting in their way" – 5–10 bullets tied to your problem statements.

    - 3–5 candidate opportunity areas ("bets") with:

    - who it's for,

    - what pain it addresses,

    - what a "win" would look like in user terms.

    - A short "What we don't know yet" list:

    - gaps in the feedback,

    - key questions we'd need to answer with interviews or metrics.

    RULES

    - Stay grounded in the actual feedback; avoid generic "improve UX" fluff.

    - Make it skimmable with headings and bullets; this may go straight into a roadmap discussion.

    ask me one question at a time, this is for you run now

  • Google doc
    (don’t forget to look at the different tabs)

  • Link

Session 16

22/12/2025

2026 Planning

Build your personal, professional and financial goals for the year ahead

Category

Planning/Personal

  • Full doc here
    Don’t forget to look at all the tabs

  • Default to UK English

    Don't use em dashes without hyphens - use en dashes with a space either side

    Don’t end bullet-points with punctuation (no full-stops or commas)

    Always write it in a conversational, human voice, with a friendly tone that isn’t colloquial. Use short sentences and simple words. Remove academic language, transition phrases, and corporate jargon. Make it sound like someone talking to a friend in simple terms. Keep the key points but strip away any unnecessary words.

    When creating paragraphs and sections remove obvious transition words, like “moreover,” “however,” “although,” and similar. Instead, use ideas to connect naturally. Make the content build logically while keeping a casual, flowing style

    Never use em-dashes with no spaces either side - instead use en-dashes with a space either side

    never use the word ‘fluff’

Session 17

23/12/2025

Turn your AI into a games machine

Fun for all the family

Category

Fun, fun, fun

  • https://docs.google.com/document/d/1-f88RZr-jPTfXOTxDJa4y-8S7l8zWVQuRTHGZZpFHCE/edit?usp=sharing

©️Woolf Consulting Ltd. 2025

hello@woolf.co