Why Teams Stop Suggesting Improvements

Early in a new job, many people notice things. The form that asks for the same detail twice. The report that nobody reads. The step that exists because of a problem that was solved years ago. They mention it in a team meeting. Someone nods, someone says it is a good point, and the meeting moves on.

A few months later they notice something else and mention that too. Same result. By the end of the first year, they still notice things. They have simply stopped saying them out loud.

This is a familiar pattern in many workplaces, and it is easy to misread. From the outside, a quiet team can look content, or settled, or short of ideas. Often it is none of those. It is a team that has learned, through repetition rather than any single event, that raising an improvement does not change anything.

What the evidence says about speaking up

The CIPD, the UK professional body for HR and people development, describes employee voice as the ability of employees to express views, concerns and suggestions, and for these to influence decisions at work. The second half of that definition matters. Voice is not only the chance to speak. It includes the expectation that speaking can make a difference.

The CIPD's factsheet on voice notes that its research found about a quarter of employees experience high levels of silence, choosing not to speak up even when they have concerns. It links this to power dynamics, to whether information challenges established views, and to doubt that speaking will lead to change. It also connects involvement in decision-making with wellbeing, motivation and job satisfaction.

The UK Health and Safety Executive's Management Standards for work-related stress approach the same territory from a different angle. Its standard on control describes how much say a person has in the way they do their work, and lists states to aim for, including that employees are encouraged to use their skills and initiative and are consulted over their work patterns.

These are UK sources and should not be read as a measurement of South African teams. They support a general point: whether people offer ideas depends heavily on whether the organisation is set up to receive them.

How suggestions disappear

It is rarely hostility that ends the flow of ideas. More often it is the absence of anywhere for a suggestion to go. Some common mechanisms:

Suggestions are spoken, not recorded. An idea raised in a meeting exists only in the memory of the people present. If nobody writes it down with a name against it, it effectively did not happen. Mellorca has written about meetings that leave no durable trace in the meeting that could have been a shared record.
Nobody owns the decision. Even a well-received idea needs someone with the authority to say yes, no or not yet. When that person is unclear, ideas stall in polite agreement.
Nobody closes the loop. The person who suggested the change never hears what happened. Silence is read as rejection, even when the idea is still being considered.
The system cannot be changed locally. Some improvements need a change to software configuration or a supplier's template. If the team has no route to request that, even good ideas are dead on arrival.
The cost of raising it is personal. A suggestion can sound like criticism of the person who designed the current process. In a small business, that person may be the owner.

None of these require anyone to behave badly. They are features of how the work and its systems are arranged.

The human tax

The tax here is autonomy and, over time, confidence. People who notice a better way to do their work but cannot act on it, or even get it heard, lose a small amount of control over their own working day. They keep doing the step they know is unnecessary. Some will find another route, building their own workarounds that work for them but are invisible to everyone else. Others simply stop looking.

It would overstate the evidence to say that everyone experiences this the same way. Some people are content to do the work as designed and have no wish to redesign it. That is a legitimate choice. The concern is for people who would contribute and have learned not to.

An illustrative team

Consider an illustrative case: a Johannesburg accounting practice with fifteen staff. Every Monday the team meets to review the week. Over two years, junior staff have raised the same few points: client documents arrive by email and WhatsApp and must be filed by hand; the same client questions are answered from scratch each time; the month-end checklist includes steps for a system the practice stopped using.

Each point was acknowledged. None was assigned. The partners were busy with client work and assumed someone would pick it up. In this scenario, the Monday meeting has slowly become a status update with no improvement agenda, and the junior staff have stopped bringing suggestions. The partners interpret the silence as satisfaction.

What could realistically change

The fix is less about encouraging people to speak and more about giving their suggestions somewhere to land.

Keep a simple improvement log. One shared list, visible to the team, with the suggestion, who raised it, who will decide, and the current status. A spreadsheet or a list in the team's existing tools is enough.
Give every item an owner and a date. Not a promise to implement, but a commitment to decide.
Close the loop every time. A clear no, with a reason, respects the person more than an open-ended maybe.
Let small changes be made locally. Agree in advance which kinds of change a team can make without escalation, such as rewording a template or removing an obsolete checklist step.
Protect a little time. Ten minutes in an existing meeting, set aside only for improvements, signals that the business wants them.

Toyota's description of its production system offers a useful reference point. It says that only humans can implement kaizen, its term for continuous improvement, and describes a commitment to developing people who can think independently and make improvements. The approach is not easily transplanted, and the context is manufacturing. But the principle that improvement comes from the people doing the work, and needs a structure to support it, applies widely.

What changes first, and the human dividend

The first change is visible: suggestions stop vanishing. People can see their ideas on a list, see who is deciding, and see the outcome. The business outcome follows from that. Small inefficiencies get removed rather than tolerated, and the cost of repetitive work mistaken for necessary work starts to fall.

The human dividend is autonomy: a measure of influence over how one's own work is done. For some people, that is a significant part of what makes work feel like theirs rather than something done to them.

The trade-offs

Not every idea is a good one. A visible log means visible rejections. Handled badly, that can discourage people more than silence did.
Decisions take management time. Committing to decide on every suggestion has a real cost for owners and managers who are already stretched.
Local change can create inconsistency. If each team adjusts its own process, the business can end up with several versions of the same procedure.
Voice can become an obligation. Some people would rather not be expected to contribute ideas, and improvement schemes should not turn into another performance measure.

Why it matters

A team that has stopped suggesting improvements still works. It may even work well. But it has quietly given up some of its say over how that work is done, and the business has lost a source of insight that cost nothing to collect.

Mellorca's interpretation is that silence in a team is often a design outcome, not a personality trait. When suggestions have a recorded place to go, a named person to decide and a reliable reply, people who notice things tend to keep saying them. That is a small structural change with a meaningful human consequence: work that people are allowed to help shape.

Sources and further reading

Management Standards - Control - HSE (last verified 10 October 2026)
Toyota Production System - Vision & Philosophy - Company - Toyota Motor Corporation Official Global Website (last verified 10 October 2026)