Wednesday at Noon

There is a particular kind of meeting that tells you almost everything you need to know about a project.

It usually happens early in the life of the project, though rarely at a convenient moment. A Wednesday at 12 noon, perhaps, with half the room arriving off the motorway and the other half refreshing their coffee and returning missed calls. Someone quietly reviewing their part of the project — checking interfaces, spotting overlaps and asking what might have been missed. Which, incidentally, is often a better indicator of leadership than most strategy presentations.

At this stage, the project is still forming. Nothing is fixed, but everything is being set.

Which is precisely why standards matter most.

People often assume standards reveal themselves later — in delivery, in deadlines, in whether the budget survives first contact with reality. In truth, standards are established much earlier, usually in the first serious meeting. They are set in the preparation, the tone, the agenda, the quality of questions and, perhaps most importantly, in what is allowed to pass without challenge.

The worst meetings are democratic in the least useful sense.

Twenty people. No chair. No structure. Everyone speaking, no one deciding. A kind of corporate jazz improvisation where the loudest voice becomes temporary policy and everyone leaves with a vague sense that something happened, although no one could quite explain what.

These meetings are expensive. Not because of the coffee, though that is often poor enough to warrant discussion, but because of wasted authority. Nothing erodes confidence faster than asking senior people to sit through ninety minutes with nothing to contribute and no clear purpose for being there.

People should arrive knowing why they are in the room.

There should be a clear agenda circulated beforehand — not a decorative attachment sent eleven minutes before the start, but a proper working document. Distinct points of discussion. Specific decisions required. Areas where agreement must be reached. One major issue, three smaller rocks and, ideally, no more than five key actions to move forward. Simplicity is not a lack of ambition; it is evidence of discipline.

And someone must chair it.

Not the apprentice. Not the person with the newest laptop. Someone with enough authority to stop the drift. Someone who can say, politely but firmly, “No, that is not the question we are here to answer.”

A chairperson is not there to dominate but to maintain the standard. To keep the conversation moving. To call out the vague. To distinguish between information and decision. To ensure that silence is not mistaken for agreement.

This is where leadership quietly appears.

Not in grand speeches, but in the willingness to say that something is unacceptable. That the previous approach — the free-for-all, the ambiguity, the lack of ownership — will not be repeated because it cannot be repeated.

Real leadership is often nothing more glamorous than refusing to tolerate confusion twice.

And some meetings, frankly, should not be on a screen.

There are moments when a video call will suffice, and moments when everyone needs to be in the same place, standing around the same problem. This is one of them. Walk the project. Visit the soon-to-be plant room. Get the measuring tape out. Reality is much harder to misunderstand when you are standing in front of it.

A visit in the real world has a way of exposing bad assumptions.

It also has a useful effect on language. People tend to become clearer when pointing at actual walls.

For meetings like these, an hour is ideal. Long enough to justify the journey and signal seriousness. Short enough to force concentration. Ninety minutes is the outer edge of credibility; beyond that, people are not collaborating, they are enduring.

The follow-up matters just as much.

Actions should be prompt, not merely timely, which is often corporate code for eventually. Critical paths do not respond well to polite delay. Notes should be clear, ownership explicit and deadlines attached to names rather than departments. “The team” is rarely guilty and never accountable.

This sounds obvious because it is.

And yet projects still fail in the same familiar way: ambiguity first, then drift, then the slow normalisation of mediocrity. Standards are rarely lost dramatically. They disappear quietly, usually while everyone is still discussing the agenda.

The first proper meeting is where that drift is either prevented or permitted.

It is where the standard is set.

And once set, it should be held.