How to run effective meetings using the 4 Ps framework
Most bad meetings are a design problem, not a time problem. The 4 Ps (Purpose, People, Process, and Product) give you a practical structure for running meetings worth showing up to.
Most of us have sat through a meeting that could have been an email. The problem usually isn't that meetings exist, it's that they get scheduled out of habit rather than intention.
A bit of structure goes a long way. The 4 Ps framework is one of the most useful tools I've come across for this.
Do the planning before you send the invite
Use the calendar invitation to communicate the purpose, agenda, and intended outcome. Most people decide whether to attend (and how to prepare) based on what's in the invite. A blank description is a missed opportunity.
Send it at least 24 hours in advance and invite input. People engage more when they've had a hand in shaping what gets discussed.
Think carefully about agenda item order. Most people list things in the order they thought of them, but sequencing by complexity works better. For established teams, open with a mid-level issue, tackle the hardest item in the middle when energy is still high, then close with something straightforward. For groups that don't know each other well, start with an easy win first to build momentum.
Think about how different people process information. Some think well in the room, others need time to sit with a question first. Sharing discussion questions or context documents ahead of time lets everyone show up ready in their own way. This matters especially for neurodivergent thinkers or introverts.
For hybrid or remote meetings, check that your setup works for everyone. Captions, good audio, and a clear note-taker are basics, not extras.
On recurring meetings: if it repeats weekly or fortnightly, make sure it still has a recurring purpose. A useful practice is to set a 6-week trial on any new recurring meeting with a deliberate go/no-go point. Without that check-in, recurring meetings have a habit of outliving their usefulness.
Follow the 4 Ps framework
Purpose: decide if the meeting needs to exist at all
Before you invite anyone, ask: does this need to be a meeting?
Meetings earn their keep when you need collaboration, joint decision-making, or genuine Q&A. One-way information sharing (status updates, announcements, progress reports) is almost always better as an email or short recording.
If the agenda is mostly "updates from each person," a shared doc or async check-in will likely do the same job.
When you do need a meeting, write the purpose in a single sentence first. "Align on Q2 campaign direction" is a purpose. "Catch up on the project" is not.
People: invite the right people, and reconsider everyone else
Every meeting pulls someone away from focused work. It should be worth it to their role, not just yours.
Before finalising the invite list: who genuinely needs to be in the room, and who would be just as well served by receiving the notes and actions afterward? A clear follow-up is often more respectful of someone's time than pulling them into a session for two minutes of relevance.
For decision-making meetings specifically, five to seven people is the sweet spot. Beyond that, discussions get harder to manage and accountability tends to diffuse.
Use the optional attendee flag intentionally. If attendance is discretionary, mark it as such and let people make their own call.
If required attendees span different time zones or flexible work arrangements, find the line of best fit — and if synchronous time is genuinely hard to find, that's a signal to reconsider whether an async format would work better.
Assign roles before the session:
Facilitator — keeps things on track; works best when this is a separate person from the note-taker
Note-taker — captures decisions and actions; AI tools can help here, but check your organisation's IT policy first, and be explicit with prompts if you use them ("capture this action, assign to Jess" produces much better output than passive capture)
Timekeeper — watches the clock so the facilitator doesn't have to
Rotating roles builds shared ownership of how meetings run.
Not everyone jumps in naturally, especially in larger groups. A good facilitator invites quieter voices and creates room for dissent. "Does anyone see this differently?" is a simple prompt worth using.
Process: structure the session so it produces something
How you run the meeting sets the tone. A few things that consistently make a difference:
Start on time. Waiting for stragglers trains people to be late.
End at :25 or :55, not on the hour. It gives people transition time between sessions and signals you're not going to run over.
Park tangents. Write them down, commit to a separate conversation, and move on. Don't let one thread take over.
Give everyone a chance to speak. A simple "anything else before we move on?" draws out people who wouldn't otherwise contribute.
Close with clarity. Every meeting should end with clear answers to: what did we decide, who's doing what, and by when.
Product: define the output before you go in
Be clear on what the meeting needs to produce — a decision, a plan, a list of actions, a shared understanding. If you're not sure, the purpose statement needs more work.
After the meeting, send a follow-up within 24 hours:
Key decisions made
Actions assigned, with owners and deadlines
Anything parked for a future conversation
Keep it short. A long set of meeting minutes nobody reads isn't accountability. A concise summary or task list in your project management tool is more useful — and logging actions directly into your system means nothing falls through the cracks.
Treat meeting culture as something worth improving
Running better meetings is a habit, not a one-time fix. Ask your team periodically: what's working about how we meet, and what would you change? When people see that feedback shifts something, they're more likely to raise problems early.
FAQ
How long should a meeting be?
As short as it can be while still achieving the purpose. If you default to 60 minutes, try 45. Most meetings expand to fill whatever time is allocated.
What if there's no clear decision to make?
That's fine, but be honest about it. A team check-in or relationship-building catch-up is legitimate — just name it as that rather than framing it as a working session.
How do I handle people going off-topic?
Acknowledge it without following it: "Worth discussing — I'll note that down for a separate conversation." Then bring the group back.
What if people have different accessibility needs?
Ask directly. Some people need captions, some need agendas sent early, some prefer async input alongside live discussion. Design for participation, not just attendance.
What tools work well for meeting notes and follow-ups?
Notion works well: a simple template capturing agenda, decisions, and actions in one place, linked to related project pages. Whatever tool you use, consistency matters more than which one you pick.
How do I know if meetings are improving?
A simple check: are people leaving with more clarity than they arrived with? If the answer is regularly no, the design needs work. A quick "was that a good use of your time?" after a meeting gives you real data fast.