Okay — so this one's a bit different. No slides, no agenda really. I just want us to, to throw some ideas around on the sales team thing. You know, the fact that they're, they're still living in the old CRM.
"this one's a bit different" signals up front that this won't be a normal meeting. "no slides, no agenda" lowers the formality and puts people at ease. "throw some ideas around" is the classic brainstorm phrase (= let's put ideas out freely). "living in the old CRM" is light, humorous language. A good facilitator loosens the room first.
So — no bad ideas here, honestly. Just say whatever comes to mind, and we'll, we'll build from there. Who wants to start?
This is the core rule that frees people from self-censorship. "just say whatever comes to mind" and "we'll build from there" signal that ideas will be built on, not judged. In this setting, staying silent is worse than offering a half-formed idea — participation matters more than perfection.
I'll jump in. Um — what if we just, we just turn the old CRM off? Like, rip the plaster off. If it's not there, they have to use the new one.
"I'll jump in" = I'll go first / I'll volunteer. "what if we...?" is the MOST common way to pitch an idea in a brainstorm — memorise it. "rip the plaster off" (UK; US: "rip the band-aid off") = do something painful quickly, all at once (idiom). A bold, extreme idea is useful — it opens up the discussion.
Ha — bold. I like it, but, um — realistically they'd just, they'd revolt, right? We'd have a mutiny on our hands.
Priya disagrees, but she VALUES the idea first: "I like it, but..." — in a brainstorm you never kill an idea with a flat "no". "a mutiny on our hands" = we'd have a rebellion (humorous exaggeration). She softens the criticism with humour. "I love it, but" preserves the energy; "yes but" kills it.
But maybe, uh — maybe Tom's not totally wrong? Not turning it off, but... what if there was a date? Like, a deadline everyone knows about?
Marco doesn't KILL the idea, he develops it. "not X, but what if Y?" = takes an idea and offers an evolved version of it. This is the "yes and" technique: accept the idea (yes), then add to it (and). This is exactly what moves a brainstorm forward.
Oh, interesting — so a phased switch-off, with a clear date. Priya, does that, does that soften the mutiny problem?
David hears an idea, says "oh, interesting", reframes it clearly ("a phased switch-off with a clear date"), then directs it to someone else. The facilitator's job: catch good ideas, sharpen them, and make sure they get built on.
Yeah, actually — if people have, like, two months' notice and some support, that's, that's a lot fairer. And we could, um — oh, what if we did training sessions? Hands-on ones?
Priya first agrees ("that's a lot fairer"), then IMMEDIATELY adds a new idea: "oh, what if we did training sessions?" In a brainstorm ideas come in chains — one triggers the next. Starting with "oh" shows the idea just occurred to her — natural, spontaneous. That energy is the sign of a good brainstorm.
Yes! And — okay, building on that — what if the training's run by someone from sales? Not us. One of their own people. They'd trust that way more.
"Yes! And..." is the purest form of the "yes and" technique. "building on that" = taking someone's idea one step further — the MOST common phrase for it. Memorise it. Tom takes Priya's training idea and develops it: "let someone from sales run the training". The ideas are now stacking on each other — the brainstorm is in full flow.
Ooh, a champion. Like a, a sales champion who actually likes the tool.
Priya adds a name/concept to Tom's idea: "a champion" (someone who advocates for and drives something — a common business term). Sometimes a contribution isn't a long sentence, it's the one right word. "Ooh" = a spark of excitement.
Yeah, every team has that one person who, who loves new gadgets. Find that person.
Marco brings the abstract "champion" down to a real person ("the one who loves new gadgets"). Humour (a type everyone recognises) makes the idea memorable. In a brainstorm, humour feeds the energy.
Love it. Okay, keep them coming — what else? Totally different angle, maybe?
"keep them coming" = let the ideas keep flowing. "totally different angle" = a completely different direction. When one vein of ideas runs dry, the facilitator opens a new one. Brainstorms move in waves: one topic is exhausted, a new one opens.
Um — what about incentives? Like, gamify it? First team to fully switch gets, I dunno, a prize?
"what about...?" = another way to pitch an idea. "gamify" = turn it into a game. "I dunno" (= I don't know) shows the idea is half-formed, but he throws it out anyway — in a brainstorm, a half-formed idea still has value.
Hmm. I'm, I'm a bit torn on incentives, honestly. Sometimes they, they work short-term but people go back after.
"I'm a bit torn on..." = I'm undecided / caught between two views. Priya doesn't kill the idea, she adds a cautious observation. In a brainstorm, saying "I'm undecided, but" is far more constructive than a flat "no".
Yeah, that's fair. Maybe incentives are more of a, a nudge than the main thing.
David doesn't bin the idea, he gives it a role: "more of a nudge than the main thing" = not the core solution, but a gentle push. nudge = a light push/encouragement (popular behavioural-science term). A good facilitator finds a place for every idea.
Can I — this might be a bit silly, but... what if we actually asked the sales team why they don't trust the new one? Like, properly asked them?
"this might be a bit silly, but..." is the protective phrase for sharing a half-formed or tentative idea. This is exactly the moment non-native speakers most often stay silent — the fear of sounding stupid. But Marco says it anyway, and the idea is actually the most valuable one. Lesson: the idea you're afraid is "silly" is often the best one — use the protective phrase, but SAY IT.
No, that's — Marco, that's not silly at all. That's, honestly, that might be the smartest thing anyone's said. We've been designing solutions without actually knowing the real problem.
"not silly at all", "the smartest thing anyone's said" — if you reward a tentatively-shared idea, people share more. "designing solutions without knowing the real problem" is an important self-critique. A good brainstorm sometimes says "let's take a step back".
Yeah, to, to play devil's advocate though — do we have time for that? We're already, we're a bit tight on the phase one stuff.
"to play devil's advocate" = to deliberately argue the opposing view, to test an idea. Priya isn't against it, she's flagging a practical limit (time). This phrase is the polite way to say "I'm not against this, but let's consider this risk".
It wouldn't need to be a big thing though, would it? Just a few, a few conversations. Coffee chats, basically.
Tom answers Priya's "time" concern without killing the idea: "it wouldn't need to be a big thing, would it?" He makes it feasible by shrinking the scope. "coffee chats" = informal, short conversations. Answering a devil's advocate: acknowledge the concern, shrink the scale.
Actually — oh, these could, they could connect. We talk to sales first, we find out the real objections, and THEN we find our champion from the people who were, who were most open in those chats.
The most valuable brainstorm moment: separate ideas MERGE. Priya links two ideas (talk to sales + find a champion) into one flow: first talk → learn the objections → find the champion from the most open people. "these could connect" = these could link together. Ideas that are good on their own become stronger combined.
Yes! And the objections you hear, they, they become the training content. You teach exactly what they're worried about.
Marco adds a third link to the merged idea: objections → training content. "Yes! And..." again. The scattered ideas are now turning into one coherent plan — the facilitator needs to see this and capture it.
Okay, now we're cooking. This is, this is actually turning into a real plan.
"now we're cooking" = now it's working / we're doing well (an energetic idiom for when something is going great). David feeds the energy with words. Naming the momentum in a brainstorm strengthens it.
Okay — we've gone a bit quiet. That's usually a good sign, actually — means we're either done or thinking. One more push. Let's, let's flip it: what would make sales hate the new platform even MORE? What would guarantee they never switch?
Every brainstorm hits a lull (a quiet moment) — it's normal, not failure. A skilled facilitator names it calmly ("that's usually a good sign") instead of panicking. Then the technique: "let's flip it" = ask the OPPOSITE question. "How do we make them switch?" becomes "what would guarantee they never switch?" Reverse brainstorming restarts a tired room almost every time — and the answers, flipped back, become requirements.
Ha — easy. Make it slower than the old one. If a page takes three seconds longer, you've, you've lost them.
Or make them re-enter data they've already got somewhere else. That's the classic.
Notice how fast the answers come — people find it easier to say what would FAIL than what would work. "That's the classic" = the textbook mistake everyone recognises. The reverse question works because criticising is low-risk: nobody fears sounding stupid when describing failure.
Or train them with a, a forty-slide deck. Death by PowerPoint.
"Death by PowerPoint" = the universally understood joke about long, boring slide presentations. Humour keeps the energy up — and Marco's joke carries a real design principle: training must be hands-on, not slides (which connects straight back to Priya's earlier "hands-on ones?" idea).
Okay, so flip those back — it has to be fast, no double entry, and training that isn't slides. That's basically our requirements list, through the back door.
The second half of the technique: take each "how to fail" answer and reverse it into a requirement. "Through the back door" = arrived at indirectly. Three complaints became three design principles in under a minute. If you facilitate meetings, this two-step move — flip the question, then flip the answers back — is worth memorising.
Oh — one more, while we're at it. What if we redesigned the mobile app at the same time? Sales basically live on their phones.
"While we're at it" = since we're already doing this, why not also... — the phrase that quietly grows a project. The idea itself is reasonable; the timing is the problem. Watch how the team handles it without crushing Tom.
That's, um — that's a much bigger piece of work than it sounds. Like, months bigger.
"A much bigger piece of work than it sounds" — Priya doesn't argue against the idea, she sizes it. "Months bigger" makes the cost concrete. Responding to scope creep with size, not opinion, keeps it from becoming personal.
Yeah — good idea, wrong meeting, maybe. Let's park it. I'll stick it on the list so it doesn't get lost, and we look at it properly after phase one.
"To park an idea" = set it aside for later WITHOUT rejecting it — one of the most useful meeting phrases in English. The formula has three parts: value it ("good idea"), park it ("let's park it"), and promise it a future ("we look at it after phase one"). The written list ideas get parked on is often called the parking lot.
Fair enough. Parked, not binned.
Tom's summary is the whole point: parked (set aside for later) is not binned (thrown away — UK English, from "bin"). Because the idea was valued and given a future, Tom stays positive — and will keep contributing. How you park ideas decides whether people keep offering them.
Right — before we pull it all together, quick gut check. If we could only do ONE of these first, which one? Marco, you start.
"Gut check" = a quick instinct poll — no analysis, just first reactions. The forcing question "if we could only do ONE" is what makes it work: people can love five ideas, but ranking forces a real signal. This is the verbal version of dot-voting (where people vote on ideas with sticker dots).
The conversations. Everything else depends on, on what we actually hear.
Same. Talk first, decide after.
Marco doesn't just vote, he gives the logic: "everything else depends on what we hear" — the conversations aren't just first, they FEED the rest. Priya's "same" + four words shows a vote can be short. In a quick poll, one sentence of reasoning is enough; a speech is too much.
Yeah — chats first. Champion second, probably, once we know who's open.
That's three for the chats, champion right behind. Great — that makes the sequencing easy.
David states the result — "three for the chats" — so the group hears its own consensus. "Sequencing" = the order things happen in. A one-minute gut check turns "a pile of nice ideas" into an ordered plan, and makes the facilitator's final summary feel earned rather than imposed.
Let me, let me try to pull this together. We've got a few threads: talk to sales first to understand the real objections — that's Marco's, and I think it comes first. Then a peer champion, phased switch-off with a date, and training built around the actual objections. Incentives maybe as a nudge later.
"pull this together" = summarise it. "we've got a few threads" = we have several strands (thread = a strand of a topic). The facilitator lists every idea one by one (so no one's idea is lost) AND prioritises them ("Marco's comes first"). A brainstorm flows freely, but at the end it must be pulled together.
That, that actually hangs together really well.
"hangs together" = it's coherent / the parts fit together. Confirming that the scattered ideas have formed a meaningful whole. A sign of a successful brainstorm.
Right — so, first action. Tom, could you set up a couple of informal chats with sales this week? Just coffee, no clipboard.
Yeah, easy. I know a couple of the reps already, I'll just grab a coffee with them.
David turns the most valuable idea into a concrete step. "just coffee, no clipboard" = just coffee, no forms/survey → an informal, relaxed chat (a clipboard signals something formal/cold). "grab a coffee" = to set up an informal meeting.
And I'll, I'll start sketching what a phased switch-off might look like. Rough, just so we've got something.
Priya takes on an action herself: "I'll start sketching..." = I'll start drafting. "rough, just so we've got something" = roughly, just so we have something to work from → it doesn't need to be perfect, just a start. After a good brainstorm, everyone picks up a piece.
Perfect. This was good — really good energy. Let's regroup once Tom's had those chats and take it from there. Thanks all.
"good energy" = the measure of a brainstorm's success (lots of ideas, lively participation). "let's regroup" = let's meet again. "take it from there" = we'll continue from there. Closing on a positive note keeps people keen for the next brainstorm.