Implementing Strategic Meetings Management

Implementation rarely fails on the technical work. Venue sourcing is a known discipline, so is supplier negotiation, and a monthly report on meetings activity is not a hard problem once the data exists. Programmes stall on the unglamorous questions: who owns this, what is in scope, and what happens when a department books a venue directly anyway.

Four pages here cover adjacent ground. What Strategic Meetings Management is defines the thing being implemented. The SMM programme sets out the anatomy — the components a programme is made of and who holds each. How to build an SMM programme is the worked step-by-step guide, with the detail you would use while doing it. This page is the sequencing: what happens in what order, and where it commonly goes wrong.

These stages overlap. Discovery does not finish before design begins, and the first sourcing usually happens while the policy is in draft. Treating them as a waterfall produces a long period in which nothing visibly improves, which is the fastest way to lose a sponsor.

Nothing else on this page works until these two things are settled. A sponsor is senior enough that a department head cannot simply decline to participate. The owner holds the category day to day — answers questions, maintains the supplier arrangements, produces the reporting and is accountable when it drifts.

They should not be the same person. A sponsor who is also the owner has no route of escalation, and an owner without a sponsor is running a suggestion rather than a programme.

Where ownership sits varies, and the answer depends less on the org chart than on who already has the relationships. What matters is that somebody is named, in writing, and known outside their own team.

Discovery is not a data request. Sending a spreadsheet to twelve department heads produces twelve interpretations of what counts as a meeting and a fortnight of silence.

What works is conversation: walking through how a real requirement arrived last month, who was involved and what was decided. You are mapping behaviour rather than process documentation, and the two are almost never the same.

A baseline is the number you will be measured against, so build it carefully and state its limitations in the same breath. The first one is usually partial: accounts payable, card data, a few departmental spreadsheets and some estimation. Say so. A figure described as approximate and later refined is credible; a precise-looking one that turns out to have excluded catering, accommodation or internal recharges undermines everything built on it.

The method is covered in how to measure meetings spend, and the reporting that eventually replaces it in meetings data and reporting. What you need now is a defensible starting point and an agreed definition of what is in scope.

Design is where the programme becomes something a person can follow. The temptation is to write everything at once — full policy, every threshold, a complete supplier list — and launch it as a document. Documents like that are read once.

Build the smallest version that works: one route in, a short meetings policy that fits on two pages, thresholds reflecting how the business already approves spend, and a handful of data fields captured for every requirement. Detail can be added once there is evidence about what people actually do.

The components are set out in full on the SMM programme page, the governance around them in meetings governance. The decision that matters most here is scope: which meeting types are in, which are explicitly out, and who adjudicates the edge cases.

Our position: start narrow. A pilot produces real data about your own organisation within weeks, and data settles arguments that opinion cannot.

Beyond the pilot there are three ways to extend, and organisations usually combine two.

The single worst way to announce an SMM programme is “we are centralising your bookings”. It tells every department that something is being taken away, names no benefit to them, and invites the entirely reasonable question of who asked for this.

The framing that works is service before control. The offer to a department head is that they stop spending Tuesday afternoon ringing round hotels, somebody else handles the negotiation and the contract, and they keep the decisions they care about — dates, location, format, delegate experience.

Control follows from that. A department that finds the route genuinely faster does not need compelling, which is fortunate, because compulsion in this category is hard to enforce. One route in, better visibility out — but the visibility is the organisation’s benefit, not theirs. Lead with the route.

Resistance is almost never about procurement policy. It is about a department believing it will lose speed, lose quality or lose the venue relationships it has built. Those are legitimate concerns and they should be answered rather than overridden.

The productive response is specific. If speed is the worry, agree a response time for briefs and meet it. If quality is the worry, keep the venues that genuinely work and bring them into the negotiated arrangements — a preferred list that excludes a department’s favourite venue without explanation gets ignored.

Where resistance is really about autonomy, name it. Some of what a programme does is a genuine reduction in unilateral choice, and pretending otherwise insults people who can see it perfectly well. The honest version: the organisation has decided this category must be visible, and here are the decisions that stay local. What rarely resolves is a department with a supplier relationship it would prefer not to explain — a governance matter, and one for the sponsor.

The early months are about proving the route works, not about coverage. A programme handling a quarter of the organisation’s meetings competently is in a better position than one handling everything badly.

We will not quote a timeline, and we would treat one quoted without knowledge of your organisation with suspicion.

The pace is set by internal agreement on ownership, scope and authority — not by the sourcing or supplier work. Sourcing moves at a predictable rate. Agreeing that procurement owns a category three departments currently consider their own can take a fortnight or two quarters, and nothing external influences which.

Say that at the start, because it changes where effort goes. If ownership is settled quickly, the rest follows mechanically. If it is not, no amount of activity elsewhere compensates.

It does not get done. It becomes business as usual — which sounds like a deflection and is actually the objective.

The marker is that the programme stops being a project. Nobody calls it an initiative, new starters are told about the briefing route as a matter of course, and the reporting arrives without anyone asking. The work then shifts to maintenance: keeping supplier arrangements competitive, keeping the data honest, and periodically asking whether the framework still matches how the organisation operates.

Where organisations go from there is the subject of the SMM maturity model. The later levels are less about buying meetings better and more about deciding which meetings should happen at all.