What Deming Would Change About Your Weekly Meeting

It is not that they are a waste. It is that they could be doing real work and are not.

W. Edwards Deming spent fifty years studying what makes organisations actually improve. He did not write a book about meetings, but his framework — what he called the System of Profound Knowledge — gives you a clean way to look at your weekly stand-up and see what is missing. Here are five things a typical SME weekly meeting gets wrong, and what Deming would do instead.

1. It optimises individuals, not the system

The classic weekly meeting goes around the table. Each person reports on what they did. Each person hears what they need to do next. The meeting is, in effect, a series of one-on-ones held in public.

Deming would point out that this is optimising the wrong unit. People do not produce results. Systems do. He estimated that around ninety-four percent of variation in performance comes from the system people operate inside — its tools, its handoffs, its incentives, its constraints — and only about six percent from individual effort.

If your weekly meeting is mostly people reporting on their individual outputs, you are working on the six percent. The ninety-four percent — the structural things that determine what any individual can possibly produce — never comes up because no one is asked about it.

A meeting that worked on the system would sound different. It would spend less time on what each person did, and more on where work got stuck between people. The question shifts from “what is your update” to “where did the work slow down this week, and what would unstick it next week?”

2. It reports backwards but does not study

Deming organised improvement around four steps he called Plan, Do, Study, Act — the PDSA cycle. Most weekly meetings do two of those four. They Plan (set tasks) and they Do (report on tasks done). The Study and Act steps are usually missing.

Study means looking honestly at the gap between what was planned and what happened, and asking what that gap teaches you. Act means changing the plan or the process based on what the gap revealed. Without those two, you have a meeting that runs every week but never gets meaningfully smarter.

A small change makes this concrete. Spend the first ten minutes of the meeting on three questions instead of updates.

What did we expect to happen this week?
What actually happened?
What did we learn?

That is a Study segment. Everything else can follow. Most teams that do this find their meetings get shorter, not longer.

3. It treats variation as someone’s fault

When something goes wrong in a typical weekly meeting, the conversation pulls toward who. Who did not get it done. Who dropped it. Who needs to fix it. Some weeks no one is the right answer to “who”, and the conversation gets uncomfortable.

Deming distinguished between two sources of variation. Common-cause variation is built into the system itself — it is what the system produces on a normal day. Special-cause variation is a genuine, identifiable disturbance that pushed the result outside the normal range. They look identical from the outside, but they require completely different responses. A common-cause result needs the system changed. A special-cause result needs the disturbance addressed.

Most teams treat every variation as special-cause. They look for who. They find someone. They address that person. The system that produced the result is left intact, and the same kind of variation shows up next week with someone else’s name on it.

A meeting that handled variation the way Deming would handle it asks two questions before anyone gets named. Is this result within the range of what the system normally produces? And, if not, what disturbed it? Those two questions take a minute. They prevent hours of misdirected accountability.

4. It runs on fear

The point Deming was most consistent about, across all of his writing and teaching, is that fear destroys improvement. He used the phrase “drive out fear” so often it became one of his fourteen points. The reason he was so insistent is that fear changes what gets said in the room. People stop reporting honest information because honest information has consequences. Meetings full of careful answers and confident updates often look productive and are actually starved of the data they would need to be useful.

Joy at Work — Deming’s other consistent theme — is not a soft idea. It is the operational condition that lets people share the bad news early, when bad news is still cheap to fix. A weekly meeting where people are slightly afraid to say “this is not working” is a meeting that loses money every week.

The simplest test: in the last month, has anyone in your weekly meeting said the words “I do not know” or “I was wrong”? If no, you do not have honest reporting. You have managed reporting. The meeting is producing the appearance of progress rather than progress itself.

5. It has no theory of knowledge

The last and most philosophical of Deming’s elements is what he called the theory of knowledge — the idea that everyone in the system is operating from some theory of how it works, and that those theories should be made explicit, tested, and updated.

In practical terms, most weekly meetings make decisions without naming the theory the decision rests on. We decide to add a step to the process, but we do not say what we believe will happen as a result. We hire someone, but we do not write down what we expect them to change. A month later we have no way to tell whether the decision worked, because we never said what working would look like.

A meeting with a theory of knowledge in it leaves a small trail. Decisions get logged with their expected result. Next month, the result is compared to the expectation. Where they match, the underlying theory is reinforced. Where they do not, the theory gets revised. Over time, the team’s understanding of its own system gets sharper, instead of every week being approximately the same.

Where to start

You probably do not want to overhaul your weekly meeting next Monday. Most attempts to do that fail, because the meeting is more habit than design and habits rarely change on a single decision.

But you might pick one of the five and try it for four weeks.

The cheapest one is the Study question — ten minutes at the top of the meeting on what you expected, what happened, and what you learned. It costs nothing, it does not require buy-in, and it produces noticeably different conversations within a month. People who were quiet start contributing, because there is finally space for “I am not sure” without it sounding like underperformance.

The hardest one is fear. You cannot drive it out in a meeting; the meeting only reveals whether it is there. But the Study question is also the place fear becomes most visible. The first time you ask “what did we learn this week?” and no one says anything for thirty seconds, you have your answer about how much honest reporting your meetings have been carrying.

If you want a broader picture of where Deming’s thinking sits, and how it changes what owners actually do day to day, the Joy at Work framework page goes deeper into the system view.

FAQs – Frequently Asked Questions