Hi there! 👋
The five power meetings that will change your life as a T/PgM
And how to lead them like a boss
Dr Carrie Goucher | FewerFasterBolder
Google T/PgM community, 2026
Then everyone arrives...
You called the meeting. You wrote the agenda. You sent the invite. And you are, in theory, the one running this!
Synchronous time is the scarcest resource you have.
Time is a non-renewable resource
You are the authority
Authority: authorship
Auctor [latin; noun]:
The one who originates something, drives it forward, takes responsibility for how it turns out.
Process authority
The authority of being the person who designed how the room thinks together.
Reference: State of Facilitation Report, 2025. Survey of 1,000 facilitators across 78 countries.
Your 5 power meetings (think: plays)
1
2
3
5
4
1
The flipped sync
Stay in sync, surface blockers (no status theatre)
A 50 thousand year old problem
50,025 BC
1525
1825
2025
Meetings are ‘office age’ tribal
safety
danger
What a sync is really for
> The signal you can't get from a doc.
> The highly inconvenient issue nobody wants to raise
> The early warning that saves you a fortnight later.
Don't kill the sync, flip it!
Same slot in the diary, completely different play.
The flipped sync: how it works
Before
Async update in shared doc or channel
4 sharp headings:
DURING — 20-3 min, not 60
Opening round: top cross-programme question/concern/idea
Filter to 1–3 topics
Deep dive (timeboxed)
Capture
After
Capture canvas shared transparently
Capture canvas
Decisions
Things we decided (and want to remember we decided!)
Actions
Specific next step (and who will do them by when)
Heads up
Don’t forget!
Car park
For another session.
The authority move
The line you need to create a new social contract
"Come ready to raise your top cross-programme question/concern/idea (not your own update - complete this before)."
Why it works
There is a stage at the start of every meeting where attendees transition from individual work into a group. Flipped sync designs this in.
Bedingfield, C. (2021). Doctoral research, University of Cambridge.
Coming up in Talk 2
Async deserves its own session
Three more ways to use async to dramatically reduce meeting load.
If the flipped sync got your attention, Talk 2 will give you a lot more norms and tooling.
Your turn
What’s ONE thing you’re loving about this power meeting?
What question needs answering to make it work for you?
Type in the chat
Turn on your mic
2
The problem sprint
For the cross-discipline knot you can't untangle in a doc.
"One bad problem-solving meeting doesn't just cost the hour. It costs the three more meetings you now have to schedule (and the weeks of delay while you wait for slots)."
The problem sprint: four phases
1. Shared problem statement (5 min)
Agree the actual problem in one sentence.
2. "How might we...?" (5 min)
Reframe as a solvable question with constraints named.
3. Brainwriting in silence (5 min)
Silent writing in a shared doc, sticky notes, chat.
4. Evaluate together (5 min)
Add data:
Capture and share: problem statement + HMW question + options + votes + next step.
Authority move: signpost and hold boundaries between phases
What to say: when someone jumps to solutions
"That's a great point. We're going to come to solutions in just a few minutes. For now let’s make 100% sure we all understand the problem the same way."
Why this move works
Separating idea generation from idea evaluation reduces fixation, lowers the threat response in our brains and avoids conversations at cross purposes
Jones, Cravens, Zaresky & Ngai (December 2024). Psychological safety and idea evaluation in research teams.
Three phrases to redirect without drama
(write these down)
For off-topic but useful points
"That's a useful broader point. I want to capture it, and stay with the specific question for now."
For spiralling discussions
"It's been a really helpful discussion on X. We're about halfway through, and I'd like to use the next few minutes to get to a decision."
For dominant voices
"Thank you for the contributions so far. I want to make sure we hear from people who haven't had a chance yet."
Smart6 meeting invite
Goal “We will achieve this specific outcome”
Session “The questions we’ll answer are”
Scope “We will... but we won’t...”
Role “In this session, please would you...”
Norms “What’s helpful / allowed / expected is...”
Preparation “Come ready to” (including tech)
Your power meeting assistant
Prompt guide
Knowledge file
All the prompts you need to problem solve, design and create the materials for each meeting
A markdown file (small, portable) with deep knowledge of the 5 power meetings and the whole FewerFasterBolder philosophy.
Your turn
What’s ONE thing you’re loving about this power meeting?
What question needs answering to make it work for you?
Type in the chat
Turn on your mic
3
The 30-minute decision meeting
One shot, one slot, how not to waste it!
The scarcity problem: you get one shot
You finally got 30 minutes on the VP's calendar.
A decision meeting that doesn't produce a decision isn't a wasted 30 minutes. It's another week of delay.
Or worse: you get a decision, the VP reverses it the following week because 'I didn't have all the information.' You're back where you started, with less goodwill.
Two kinds of decision
ONE WAY DECISION
TWO WAY DECISION
Decision on a page
One name
One name
One way
How might we?
Decision type
Problem statement
Decider
Owner
Decision making format
Stakes
By when?
What depends on this decision
Consultation outcomes
The 30-minute choreography
0–2 min
Frame
2–5 min
Consultation outcomes
5–15 min
Options + structured input
15–25 min
Decider Q&A
25–28 min
Decision stated
28–30 min
Capture
Problem, decider, type of meeting. Name the question the decider needs to answer.
Texture of what people said, especially the cautions.
This is the last mile, not the whole marathon
Recommendation presented. A round for each person to add anything not covered in consultation.
Decider asks questions. Group addresses concerns.
Or: what they need + by when, if they genuinely can't decide now.
Decision, rationale, next actions, who needs to know. Share within the hour.
"VPs reverse decisions when they feel concerns weren't heard. The consultation outcomes field is your insurance policy."
Coming up in Talk 3
This is an Adult-to-Adult move
And we will talk in detail about how to develop an Adult-to-Adult way of working together in your teams and wider project groups in Talk 3....
Your turn
What’s ONE thing you’re loving about this power meeting?
What question needs answering to make it work for you?
Type in the chat
Turn on your mic
4
The generative working meeting
Where experts produce (instead of discussing what they'd produce if they had time 🤦🏻♀️)
Three kinds of meetings
DISCUSSION
"We talked about it."
Output: notes, maybe actions
Most common.
Often over-used.
DECISION
"We decided it."
Output: a decision
High stakes. Often run sub optimally. Needs clear prep and crisp design.
GENERATIVE ★
"We made it."
Output: the actual thing
Most powerful.
Almost nobody deliberately designs one.
The expensive pattern and how to break it
THE OLD WAY
1. Meeting — everyone shares verbally
2. You take notes
3. You go away and write the draft
4. Send for comments
5. Get conflicting feedback
6. Schedule another meeting
THE NEW WAY
The design: micro-sprint structure
PLAN — 5 min
Social contract: what we're making, what done looks like, questions to answer.
Divide questions across the room, not by discipline.
DO — 30–35 min
Pairs/threes working in parallel.
Create straight into a shared doc, live.
REVIEW — 10 min
Each pair presents, 2–3 min each.
Full group asks clarifying questions and stress-tests.
REFLECT — 5 min
What did we produce?
What's still missing? What's next?
Who owns what?
Adapted from micro-sprint methodology — Owen & Wasiuk, University of Manchester, 2023
Owen & Wasiuk, University of Manchester (2023). Micro-sprint methodology.
Divide the work, not the people
FUNCTIONAL SPLIT (old default)
Engineers do the engineering bit
Legal does the legal bit
Ops does the ops bit
→ Feels efficient
→ Until you have to integrate it all afterwards
→ Then you need another meeting to reconcile
QUESTION SPLIT (micro-sprint)
Each pair: engineer + product person + ops lead
All working on the same question
→ Cross-functional answers as you go
→ No integration meeting needed
→ Much more honest reflection of how the work fits together anyway
"We are not going to talk about the risk assessment, we’re going to write it. In the next 35 minutes you are going to produce the actual content. I'm going to hold the process and keep us on track."
The boldest authority move on the list!
Your turn
What’s ONE thing you’re loving about this power meeting?
What question needs answering to make it work for you?
Type in the chat
Turn on your mic
5
The learning loop
The meeting that improves everything else - your 10x tool (because no one else is doing it)
Friction is taxing your team, hard.
It cannot be fixed in a 1:1 or a doc.
It requires the whole team in the same room, with permission to name what's actually going on.
The learning loop is the only meeting designed to mine these signals.
The learning loop: three questions
Question 1 (don't skip this)
What has been most satisfying since we last did a learning loop?
Question 2
What is one thing you think we MUST focus on now as a team?
Question 3 (this question is doing a lot of work)
What is concerning you, if anything, that we haven't properly addressed?
"This is how we stay fast. Friction we don't surface slows us down more than any technical blocker on the roadmap."
The authority move: create the space at all. Reframe it (in your head first, then to your team) as essential programme hygiene, not soft optional extra.
Your turn
What’s ONE thing you’re loving about this power meeting?
What question needs answering to make it work for you?
Type in the chat
Turn on your mic
Bonus
Three rituals that make all five meetings work better
Ritual 1: The async check-in
Ritual 2: The "How Might We" habit
Turn problems into puzzles.
When someone raises a barrier, the team reframe it as "how might we...?" Out loud.
"We can't ship by Friday — legal review hasn't happened." → "How might we get the review unblocked?"
How Might We...?
Ritual 3: The capture and share norm
Shared transparently, within the hour.
Eliminates 'I thought we agreed X / no we agreed Y.' Ownership trust goes up — everyone can see what everyone else committed to.
Capture canvas
Decisions
Things we decided (and want to remember we decided!)
Actions
Specific next step (and who will do them by when)
Heads up
Don’t forget!
Car park
For another session.
Your turn
What ritual will you use / adapt?
What question needs answering about these rituals?
Type in the chat
Turn on your mic
Your 5 power meetings (think: plays)
1
2
3
5
4
You are the authority
Clarity Everyone knows the job to do
Structure People know how to contribute
Service Everything you're doing is in service of the group and its outcomes
When people feel that you are holding the process for them, not over them, defences come down.
Your turn
What’s the ONE most useful thing you’ve heard today?
Type in the chat
Turn on your mic
You are the authority.
The one who designed the container that made the outcome possible.
Take what's useful (leave the rest) and put it into your own words and style.
The Power Meeting Playbook
A reminder - and a language deep dive for each meeting
Next time
"My diary is full and Chat's on fire!"
Async is a hot mess. Let’s make it work for us.
I'm rooting for you!
Email me any time: carrie@fewerfasterbolder.com
01
The flipped meeting
03
The 30-minute decision meeting
02
The problem sprint
04
The generative working meeting
05
The learning loop
Stages
Stages
Stages
Stages
Stages
Key tip
Raise a concern from someone else's update, not your own.
Key tip
Decision Request vs Decision Frame. Use Request 80% of the time.
Key tip
Silence during brainwriting is non-negotiable. Everyone writes before anyone speaks.
Key tip
"We are not here to talk about it, we’re going to actually make it.”
Key tip
Frame as maintenance, not therapy: "This is how we stay fast."
When to use
Status updates eat the meeting; cross-programme blockers aren't surfacing early enough
When to use
A decision is blocking progress and you have time with the person who can make it
When to use
A cross-discipline problem is going in circles and you can't afford another follow-up meeting
When to use
You need a complex output (plan, risk assessment, design) in one session instead of three drafting loops
When to use
You can feel friction slowing the team down but there is no forum to name what's really going on
The five power meetings that will change your life as a T/PgM
And how to lead them like a boss