<div class="gn-article"><div class="gn-hero gn-reveal"> <div class="gn-hero__image"><img src="https://cdn.prod.website-files.com/687a235da6861294eec73166/6a3554ba3513d4a8b32045cc_top-10-brand-signals-banner-6a07286f4881c047004367.jpeg" alt=""></div> <div class="gn-hero__head"> <span class="gn-kicker"><span class="dot"></span>Growth</span> <h1 class="gn-title">Top 10: Internal Meetings Your Agency Should Stop Holding</h1> <div class="gn-meta"> <strong>The GO Network</strong> <span class="pip"></span> <span>11 June 2026</span> <span class="pip"></span> <span>7 min read</span> </div> </div> </div> <div class="gn-body"> <p class="gn-lede gn-reveal">The meetings described here share a common feature: they persist not because they are useful, but because cancelling them feels like a statement. Stopping a weekly status feels like you are not on top of the project. Ending the all-hands feels like you are hiding something. Cutting the finance review feels irresponsible. These feelings are worth examining, because they are often the reason ineffective meetings survive for years.</p> <div class="gn-list-item gn-reveal"> <div class="gn-list-item__head"> <span class="gn-list-item__num">#01</span> <h3 class="gn-list-item__title">The Weekly Status Nobody Updates</h3> </div> <p class="gn-reveal">This meeting exists because it was set up when a project launched. Nobody cancelled it. Now it recurs every Monday at nine, a team of six dials in, and the first ten minutes are spent establishing that nothing has changed since last week.</p> <p class="gn-reveal">The purpose of a status meeting is to surface blockers and move things forward. When the information being shared could be read in ninety seconds on a shared document, the meeting is not doing that job. It is substituting motion for progress.</p> <p class="gn-reveal">If your status meetings have a predictable section where someone says 'all on track', ask yourself whether you need a meeting to hear that. A brief async update, written and read in each person's own time, returns the hour without losing the information.</p> </div> <div class="gn-list-item gn-reveal"> <div class="gn-list-item__head"> <span class="gn-list-item__num">#02</span> <h3 class="gn-list-item__title">The Credentials Review With No Pitch In Sight</h3> </div> <p class="gn-reveal">Some agencies hold monthly or quarterly sessions where the credentials deck gets reviewed, refined, and debated by a committee. In theory, keeping the deck current is sensible. In practice, these sessions often become exercises in aesthetic disagreement with no immediate purpose driving the decisions.</p> <p class="gn-reveal">A credentials deck should be shaped by real conversations: what landed, what confused, what a specific prospect actually asked. Without a live pitch or a recent new-business meeting to anchor the review, the feedback is abstract and the changes are often cosmetic.</p> <p class="gn-reveal">Review your credentials when you have a reason to. An upcoming conversation, a sector you are targeting, a case study that just completed. Not because the calendar says it is time.</p> </div> <div class="gn-list-item gn-reveal"> <div class="gn-list-item__head"> <span class="gn-list-item__num">#03</span> <h3 class="gn-list-item__title">The All-Hands That Is Really a Broadcast</h3> </div> <p class="gn-reveal">All-hands meetings work when they are genuinely two-directional: leadership shares context, the team asks questions, decisions get explained rather than announced. What most agencies actually run is a broadcast with a questions slide at the end that nobody uses.</p> <p class="gn-reveal">When people sit in a room to receive information they could have read, the signal being sent is that their presence matters more than their time. The implicit message is that attendance equals alignment. It does not.</p> <p class="gn-reveal">If your all-hands has a low question rate and high passive attendance, it has become a ritual rather than a conversation. Consider replacing it with a written update and a smaller, optional session for people who want to discuss it.</p> </div> <div class="gn-list-item gn-reveal"> <div class="gn-list-item__head"> <span class="gn-list-item__num">#04</span> <h3 class="gn-list-item__title">The Brainstorm Held Too Early</h3> </div> <p class="gn-reveal">Brainstorms scheduled before the brief is properly interrogated produce a specific kind of waste. The room generates ideas enthusiastically, the ideas go on a board, and then the brief gets refined and half the thinking is irrelevant. The session has to happen again, or the team carries forward ideas that do not fit.</p> <p class="gn-reveal">This is not a problem with brainstorming. It is a problem with sequencing. Running creative ideation before the strategic question is clear means the energy goes into the wrong place at the wrong time.</p> <p class="gn-reveal">The fix is not a better brainstorm format. It is a rule: no ideation session until the brief has been signed off by someone with authority to do so. Holding that line saves the brainstorm itself.</p> </div> <div class="gn-list-item gn-reveal"> <div class="gn-list-item__head"> <span class="gn-list-item__num">#05</span> <h3 class="gn-list-item__title">The Finance Meeting Everyone Dreads</h3> </div> <p class="gn-reveal">There is usually one recurring finance or resourcing meeting in an agency's calendar that has a reputation. People arrive underprepared, the conversation circles the same topics, and it ends without clear decisions. Then it happens again next month.</p> <p class="gn-reveal">This kind of meeting tends to persist because the underlying problem, usually a lack of shared visibility into numbers or resource, has not been solved structurally. The meeting is a workaround for a system failure. It feels necessary because the system is not doing its job.</p> <p class="gn-reveal">Before the next one happens, ask whether the information being discussed in that room could be accessed by the relevant people without a meeting at all. Fixing the visibility problem removes the need for the workaround.</p> </div> <div class="gn-list-item gn-reveal"> <div class="gn-list-item__head"> <span class="gn-list-item__num">#06</span> <h3 class="gn-list-item__title">The Retrospective With No Decision Authority</h3> </div> <p class="gn-reveal">Post-project or post-pitch retrospectives are genuinely useful. Identifying what went wrong, what worked, and what to do differently is how agencies improve. The problem is when the people in the room have no authority to change the thing they are critiquing.</p> <p class="gn-reveal">A retrospective where the team identifies the same three structural problems they identified six months ago, and then files those observations somewhere they will not be acted on, is demoralising rather than developmental. It teaches people that reflection is performative.</p> <p class="gn-reveal">If a retrospective is worth holding, someone in the room needs to own the outcomes and have the authority to implement them. Without that, consider whether you are holding it for accountability or for appearances.</p> </div> <div class="gn-list-item gn-reveal"> <div class="gn-list-item__head"> <span class="gn-list-item__num">#07</span> <h3 class="gn-list-item__title">The Speculative New-Business Chat</h3> </div> <p class="gn-reveal">Growth leads and MDs often have a recurring slot for 'new business pipeline' conversations that are, on inspection, mostly speculative. Names on a list. Sectors that might be interesting. Contacts someone vaguely knows. The conversation feels strategic but produces little that is actionable.</p> <p class="gn-reveal">Pipeline conversations are valuable when they are anchored in real activity: conversations that have happened, briefs that have arrived, relationships that are warming. When they are anchored in aspiration, they tend to produce the same list of target names week after week.</p> <p class="gn-reveal">If your pipeline meeting regularly features the same companies in the 'to approach' column without movement, the meeting is not the problem. The absence of a follow-through system is. Fix the system, and the meeting either becomes useful or becomes unnecessary.</p> </div> <div class="gn-list-item gn-reveal"> <div class="gn-list-item__head"> <span class="gn-list-item__num">#08</span> <h3 class="gn-list-item__title">The Creative Review With Too Many Voices</h3> </div> <p class="gn-reveal">Creative reviews with large attendee lists produce a specific dynamic: the loudest voice in the room shapes the work, regardless of whether that person is closest to the brief or the client. Consensus feedback is rarely good feedback. It tends toward the safe and the generic.</p> <p class="gn-reveal">The more people in a creative review, the more the work gets negotiated rather than judged. This is how agencies end up presenting work that nobody in the building is excited about, because it has been softened by committee.</p> <p class="gn-reveal">Restrict creative reviews to the people whose opinion genuinely informs the decision: the creative lead, the strategist who wrote the brief, and the account lead who knows the client. Everyone else's view can be solicited separately, if at all.</p> </div> <div class="gn-list-item gn-reveal"> <div class="gn-list-item__head"> <span class="gn-list-item__num">#09</span> <h3 class="gn-list-item__title">The Onboarding Meeting That Replaces Documentation</h3> </div> <p class="gn-reveal">Many agencies onboard new starters through a series of meetings with senior people: the CEO, the heads of department, the finance lead. These sessions are well-intentioned but they are often a substitute for documentation that does not exist, or that exists but nobody trusts.</p> <p class="gn-reveal">When the only way to understand how something works is to meet the person who does it, that is a process problem wearing the clothes of a culture initiative. It also takes significant time from senior people whose involvement is not scalable as the agency grows.</p> <p class="gn-reveal">Proper onboarding should include human connection, but the informational content should live somewhere that does not require a meeting to access. Build the documentation once. Use the meeting time for the things documentation genuinely cannot do.</p> </div> <div class="gn-list-item gn-reveal"> <div class="gn-list-item__head"> <span class="gn-list-item__num">#10</span> <h3 class="gn-list-item__title">The Catch-Up That Has Outlived Its Reason</h3> </div> <p class="gn-reveal">One-to-ones and team catch-ups often start for a good reason: a new joiner needs support, a project is at a critical stage, a relationship needs investment. The problem is that they rarely end when that reason goes away. They simply continue, by default, indefinitely.</p> <p class="gn-reveal">A weekly thirty-minute catch-up between a director and a senior account manager might have been essential during a difficult client period. Eighteen months later, with the client relationship stable, both people are turning up out of habit rather than need.</p> <p class="gn-reveal">Every recurring one-to-one should have a stated purpose and a review point. Not to eliminate them, but to confirm they are still doing what they were set up to do. The ones that pass that test are worth keeping. The ones that do not are simply polite obligations.</p> </div> <div class="gn-divider gn-reveal" aria-hidden="true"></div> <h2 class="gn-reveal">What This Means in Practice</h2> <p class="gn-reveal">The practical starting point is an audit, not a culture change programme. Print the recurring calendar. For each item, ask one question: if this meeting did not exist, what would actually be lost? If the honest answer is 'not much', that is your answer. Do not restructure the meeting. Cancel it, and see what happens.</p> <p class="gn-reveal">Time is the one resource in an agency that cannot be billed twice, borrowed against, or recovered. The hours spent in meetings that should not exist are not a minor inefficiency. They are the hours that could have gone into better work, sharper thinking, and the client conversations that actually grow the business.</p> </div></div>