Priya Parker, 2025

“The biggest mistake we make when we gather is we assume that the purpose is obvious and shared.”

Facilitator Priya Parker made this point in a 2025 TED podcast conversation about gatherings and community. She explained that familiar labels such as staff meeting or celebration can conceal different expectations unless a host first names the actual need. The business lesson is that a calendar invitation is not a purpose. Meetings become vague, oversized, or ritualized when participants do not know what decision, learning, relationship, or work the gathering must make possible. The quotation becomes operational only when leaders connect it to the design of work rather than to enthusiasm alone. Managers should describe the causal chain they expect: the action, the immediate response, and the outcome worth improving.

A host can write a one-sentence purpose, invite only people with relevant knowledge or authority, and design the agenda around participation needed to achieve it. Prework and asynchronous updates should replace time that does not benefit from being together. Evidence should come from people experiencing the process as well as from aggregate performance. A review date protects the idea from drifting into a permanent initiative that nobody can evaluate or end.

Strong purpose should not become coercive choreography. Participants need enough context to opt out, challenge the frame, or raise an issue the host missed. Accessibility, time zones, status differences, and psychological safety affect who can truly participate. Boundaries matter because a practice that helps one context may transfer cost or risk in another. It should include the strongest credible objection, not only evidence most favorable to the proposal.

Hybrid work has multiplied meetings while weakening many of their social cues. Parker’s observation gives teams a direct filter: if the purpose cannot be named and shared, the gathering should be redesigned or canceled. Review the next recurring meeting and ask each participant what it is for. Resolve the differences, state the intended outcome, remove anyone who can be updated later, and end the meeting with a decision, owner, and next review. A transparent review lets the team preserve what worked while changing assumptions that no longer fit. That habit strengthens trust because people can see that learning, not defending the original author, is the purpose of measurement. The strongest evidence will combine a measurable outcome with a clear account of how the result was produced. Numbers show scale and direction, while interviews, observations, and exception logs reveal why the pattern occurred. Using both protects the organization from chasing a convenient average and helps it identify which customers, roles, or locations need a different design before the practice expands. A brief public summary should record what continued, changed, or stopped after the test.