Why Your Meetings Don't Produce Decisions

"We discussed it in Monday's meeting."

You have heard that sentence offered as an answer to why something has not moved. It is not a lie. The thing was discussed. Eleven people, two hours and ten minutes, everyone spoke, several people wrote in notebooks. Four weeks later the same item is on the same agenda in the same words, and nobody finds that strange.

So you fixed the meeting. Agenda circulated in advance. Sixty-minute limit. An action-tracker sheet filled in during the last five minutes and never opened again. It worked for three weeks.

The claim here is narrow: your review meeting is not a decision forum running badly. It is a reporting forum running well.

It was built, without anyone designing it, to produce one output — information for the promoter. Everybody reports upward. You react. The reactions become the week's priorities. Judged against its real purpose it is efficient. Nothing was decided because deciding was never what the format was for, and tightening the agenda of a meeting pointed the wrong way only gets you there faster.

This sits inside a larger pattern — the five conditions ownership requires are in employees not taking ownership. This article takes the room.

The three meetings hiding inside your one meeting

A management team needs to do three distinct things together, and almost every Indian mid-market business does all three in one Monday-morning slot.

• Status. What happened. Who is where against the number. One-way, factual, best done in writing before anyone sits down.
• Problem-solving. What do we do about what went wrong. Argumentative, slow, needs the three or four people who know something about it.
• Decision. Who now owns what, by when. Short, dry, needs only the people with authority to commit resources plus the person taking the name.

These are not three phases of one meeting. Status wants a large attendee list and no debate. Problem-solving wants a small list and long silences. Decision wants authority in the room and a written record.

Run them together and you get the worst version of all three. Status expands to fill the time, because it is the safest activity in the room. Problem-solving gets what is left, in front of eleven people, six of whom have no stake. And the decisions get made in the last four minutes by whoever is still awake, with the promoter closing the item rather than settling it.

Why status wins every time

From your chair it is padding. From the attendee's side it is a rational choice.

Reporting is safe. Reporting is visible. Reporting commits you to nothing.

A manager who arrives with a detailed account of last month has bought forty minutes of being seen working and taken on no new obligation. Nothing in it can be held against him in six weeks: it describes the past, and the past is settled.

Now the manager who raises a live problem. The problem invites a discussion. The discussion invites a solution. The solution needs an owner, and he is standing there holding it in front of you — a comfortable forty minutes converted into a commitment with a date, in a room where being late is remembered far longer than being quiet.

He is not being cynical. He is reading the incentives accurately, and the smarter he is, the faster he reads them.

Which is why "we need better discussion in these meetings" never produces any. The room is not short of insight. It is short of reasons to expose it. This compounds downward: the middle layer learns to bring reports rather than positions, one of the mechanisms behind why middle management fails.

The Named Owner Rule

The intervention is one rule, deliberately small, because large meeting redesigns do not survive a busy quarter.

Nothing leaves the room without a named individual, a specific next observable event, and a date.

Its power is not the discipline it imposes on the follow-up. It is what it exposes at the moment of assignment.

A person, not a team

"The sales team will look at it."

That sentence is the single most common way an Indian company converts a decision into nothing, and it passes unchallenged because it sounds like agreement.

A team cannot be asked on Thursday how it is going. A team cannot be wrong. A team cannot be the one who decided. When ownership lands on a collective noun the item does not get done slowly — it does not get done at all, and no individual has behaved badly, because none of them was asked.

Understand why the collective noun gets used, or you will treat it as sloppiness. Naming an individual in front of their peers is a status act in an Indian office: uncomfortable towards someone senior, awkward across functions, mildly aggressive between equals. The collective noun is a courtesy — everyone leaves without having been publicly loaded. It is polite, and it is why your agenda has carried the same four items since February.

With no name attached, the real owner defaults to whoever most fears the consequence of it not happening — in a promoter-led business, almost always you. That is one of the routes by which work travels upward.

A next observable event, not an intention

"Will look into it." "Will follow up with the vendor." "Will work with production."

None of those is observable. The test: could someone who does not work at your company tell whether it happened? "Discount policy draft circulated to the four of us" passes. "Review the pricing structure" does not. "Terms confirmed in writing with the Nashik distributor" passes. "Sort out the Nashik issue" does not.

This is where most of the value sits: it pulls the vagueness forward. An item that cannot be reduced to a specific next event is one nobody has thought about properly, and you learn that on Monday rather than four Mondays later.

A date, and a way of checking it

The date matters less than what you do with it. A date in an action sheet nobody reopens is decoration.

What makes it real is the running order of the next meeting. First item: last meeting's names and dates, read out, one line each, done or not done. Not discussed, not explained — marked. Ten minutes at the start, before anyone reports on the past. That does more than any agenda template, because it is the first time being late has a fixed, public moment attached to it.

Gallup's 2023 study of 18,665 employees found only 47% strongly agree they know what is expected of them at work, down from 56% before the pandemic. Expectations are not mainly set in appraisals. They are set in rooms like this one, on Monday mornings — and when a room habitually ends with nobody's name against anything, less than half the building knowing what is expected of it is arithmetic, not a mystery.

If nobody will take the name, send it back

This is the part founders skip, and the part that does the work.

If no individual will own an item, it is not ready to be decided. Something is missing: information nobody has, authority nobody holds, or willingness nobody has. Sending it back is not a failure of the meeting. It is the decision — and it should be recorded that way, with a name and a date against getting the missing thing.

The second of those is the common one. People decline the name when they know they cannot execute without your signature. A named owner without authority is just a named victim, and they do not volunteer twice. That repair belongs in the decision register in the decision bottleneck, and it is the same reflex seen from the team's side in why your team waits to be told.

The empty-chair test

Cancel yourself from your own review meeting once, with no warning. Do not tell anyone it is a test. Let it run without you, then read the minutes.

• If nothing was decided, the meeting was never a decision forum, and your team has known that for years. They were waiting to hear what you thought, which was correct behaviour given how every previous meeting ended.
• If things were decided, and decided sensibly, you have just learned how much of your calendar is optional — uncomfortable in a more useful direction.
• If the meeting was postponed until you were free — the most common outcome, and the reason to run this without warning — you have your answer without reading anything.

That is not a judgement on your team. It is a measurement of the format.

Minutes that are useless and minutes that work

Most Indian companies keep meticulous minutes that are worthless, and the tell is the grammar: passive voice, past tense, paragraphs beginning "It was discussed that."

Minutes recording what was discussed are an archive, and nobody reads an archive. Their real function is protective — evidence the subject was raised, retrievable when someone later asks why nothing happened. A defence file, not a management instrument.

Minutes that record who now owns what are the only durable output a meeting has. Three pieces of information per line: the name, the next observable event, the date. Nothing about who said what.

The test to apply to yours this week: can a person who was not in the room read the minutes and know what they now have to do? If understanding them requires having been present, they are a memory aid, not a record of decisions.

Expect one shock. Honest decision minutes for a two-hour meeting run to well under a page, and the first set looks insultingly thin. That thinness is the accurate count of what the meeting produced. It always was. You were reading a longer document.

They matter most at the seams between functions — sales committing something operations must deliver — which is where most execution fails, as in why execution breaks down at scale.

The corridor conversation

Now the part specific to how Indian businesses run. In the room, nobody disagrees with the promoter. Heads move, notes are taken, the item closes. Then the real conversation happens in the corridor, or the car park, or on a WhatsApp group you are not in. That is where someone says what the plant will really do when this order lands, why the credit terms will not hold, and that the customer already said no in March.

The corridor is where the decision gets made and unmade. Not by defiance — nobody refuses. By a slow, deniable, respectful failure to execute that reaches your desk six weeks later looking like an operational problem.

The standard fix is to encourage open debate. You have probably said it: there is no hierarchy in this room, please speak freely. It cannot work, because it is an instruction to take a personal risk issued by the exact person the risk is about. Nobody accepts that invitation without testing it, and nobody wants to be the test.

The change that works is structural rather than cultural, and needs no announcement: the promoter speaks last.

If you state a view first, everything after it is a response to your view, and the room's job quietly becomes calibration — working out how strongly you hold it. If you speak last, the room has to produce a position before it knows yours. Same people, same hierarchy, different running order, and you find out what your management team actually thinks.

Two things support it. Ask for objections by function rather than by opinion — "Rakesh, you run the plant, what breaks if we do this?" is answerable in front of you, where "Rakesh, do you agree?" is not. And when someone raises a hard objection, watch what you do in the next ninety seconds, because the whole table is watching too. That response sets the price of speaking for six months — the same asymmetry described in the accountability gap.

You will know it is shifting when you stop hearing objections secondhand. If a serious concern reaches you two days later through a third person, it was in the room and chose not to appear.

Where to start

Do not redesign the meeting, split it into three, buy a tool, or announce a new discipline. Visible changes in a promoter-led business get performed rather than adopted.

Take the minutes of your last review meeting into your next one. Read out each item and ask one thing: who owns this, and what is the next observable event. Write the answers next to the line, or write "no owner" — and mean it.

The first pass will be slow and mildly embarrassing, and roughly half the items will not survive it. That half was never going to happen anyway. You did not have it written down.

To see how far this reaches beyond the meeting room, the Business Pulse diagnostic maps where decisions genuinely get made in your organisation, as against where the org chart says they do. Most promoters find the meeting was a symptom of that.