Method Fatigue: When Employees Do Not Want to Hear About the Next Framework

Method fatigue arises when employees are asked to learn new frameworks and rituals in quick succession without their work visibly improving. The resistance is then a response to the method as an imposition, and it is justified as long as nobody can say which problem the last method solved. The remedy is leadership that names the problem before every introduction, measures the effect and ends existing methods before demanding new ones.

This article describes the symptoms and causes of method fatigue and gives you a five-step approach with an inventory table, with which you decide which methods stay, which change and which end.

What is method fatigue?

Method fatigue is the exhaustion and scepticism that employees develop towards new ways of working after earlier introductions brought no visible benefit. It is a form of change fatigue and shows up first in the teams that experience the most methods: in IT and in product management, where Scrum, Kanban and scaling frameworks were introduced one after another or side by side.

The reason lies in the calculation each employee makes. A new method costs learning time and meetings and demands new habits. Set against that is a benefit that those involved can rarely check themselves. If the calculation comes out negative three times in a row, the conclusion is that the fourth method will bring no benefit either. That is rational, and it changes attitudes for good.

In 1974, in an address at Caltech, the physicist Richard Feynman coined the term “cargo cult science” for procedures that imitate the outward form of science and leave out its substance. Many employees transfer the pattern to method introductions: the rituals are there, the effect is missing. How to recognise such rituals is described in the article on agile rituals without effect.

How do you recognise method fatigue?

You recognise method fatigue by six symptoms that look harmless individually and show a pattern together.

1. Formal agreement without action: announcements are followed by nodding, but behaviour stays the same.
2. Humour about the method: its terms become punchlines during breaks, and roles get nicknames.
3. Relapse under pressure: as soon as a deadline tightens, the team returns to old ways.
4. Meetings without results: rituals take place, but their outcomes are not followed up.
5. Silence in retrospectives: nobody talks about what is really bothering them.
6. Departure of the experienced: those who lived through the previous introductions leave the project or the company.

The article on method FOMO describes the other side, namely why companies chase every new framework and so create the fatigue.

Why does method fatigue arise?

It arises from five causes that leadership can remedy.

The first cause is introduction without a problem. The method is introduced because a competitor, an adviser or a conference recommended it, and nobody formulated beforehand which waiting time should disappear. Without a baseline there is no proof later.

The second is pace. Whoever demands a scaling framework two years after the Scrum introduction and an organisational model a year later has never waited to see whether the first change works. As early as 1996, in “Leading Change”, the organisational researcher John Kotter described how changes fail when leadership declares success too early and the change is not anchored in the culture.

The third is the change of those responsible. Every new manager brings a new favourite method, and employees learn that methods attach to people and not to problems. Whoever sees this waits until the person moves on.

The fourth is missing safety. In a 1999 study of work teams, the researcher Amy Edmondson showed that teams learn when employees can voice mistakes and doubts without fear of disadvantage. Where that is missing, criticism of the method disappears from meetings and surfaces in corridors.

The fifth is the load on top. New methods are added to existing work without anything being dropped. The calendar fills with rituals, and the team has less time for the very thing the method was supposed to improve.

How do you overcome method fatigue?

You overcome method fatigue in five steps: listen, take inventory, end, set the effect and agree a rhythm for change.

1. Listen: hold conversations with employees from three or four teams and ask about methods that helped and about those that cost time. Expect criticism and respond without justifying yourself.
2. Take inventory: list all methods and rituals introduced in the last three years, with the problem each was meant to solve.
3. End: drop methods and rituals with no visible effect before you ask for anything new. Every ritual that ends is proof that leadership is listening.
4. Set the effect: agree a metric, a baseline and a review date for the methods that remain.
5. Agree a rhythm: decide how many changes a team can absorb at the same time, and hold to that limit. One change at a time is a good rule for most teams.

Which methods do teams really need?

Teams need as few methods as it takes to solve their delivery problems, and every method must be tied to a problem. The Agile Manifesto of 2001 puts individuals and interactions over processes and tools. The 2020 Scrum Guide describes Scrum itself as a deliberately incomplete framework that teams fill with their own practices. Both sources presuppose that people may adapt the method to their work.

A simple mapping helps with selection. If work waits for a long time, Kanban and limiting work in progress are effective. If outcomes have to be reviewed in short cycles, Scrum fits. If teams lose time through dependencies, team design and joint planning help, as described in Team Topologies and big room planning. A model such as Spotify's cannot be adopted as a whole, as the article on the Spotify model shows. With the Beta Codex, Niels Pfläging has formulated a counter-position, according to which companies need less method and more responsibility in the teams.

How do you raise method fatigue in leadership?

You raise method fatigue by locating responsibility for the number of changes with leadership. A leadership group that decides on new methods needs a shared view of all changes under way. In many companies each division introduces its own methods, and employees feel the sum. A list of all current changes per team shows where the load lies and allows introductions to be staggered.

Coaches also belong in this picture. A coach who keeps developing their own method has different interests from a team that needs calm to deliver. When external support helps and when it creates dependence is described in the article on agile coaches. Where the fatigue runs deep, a fresh start may serve better than another correction, which the article on restarting an agile transformation explains.

Overcoming method fatigue with Niehues Consulting

Niehues Consulting is a consultancy for AI management and organisation design from a delivery perspective, based in Düsseldorf. Founder Marin Niehues builds organisations that deliver, in projects ranging from VC-funded scale-ups to DAX 40 corporations and in more than 20 countries on six continents. The view starts from the outcome: what should be delivered, what hinders delivery, and which method removes that obstacle. The fashion of the year plays no part in the choice.

The approach follows the Niehues Delivery Model. Three of its test questions matter for method fatigue: Which business outcome should change measurably? What is the baseline, and how do we measure success? Are users enabled and workflows adapted? You start with a free initial consultation of 30 minutes, which you can book via the contact form. The scope and terms of an engagement are discussed in the free initial consultation.