There is a moment, usually a few weeks into a significant change, when the room turns. The new process is slower than the one it replaced. The reports do not look right yet. Someone who was excellent at the old way of working is now visibly clumsy in front of their peers. A quiet consensus forms that this was a mistake, and that the sensible thing would be to go back.
I have watched that moment arrive in programme after programme. What is striking is how little it tells you about whether the change was the right one.
The dip is structural
Competence is mostly fluency. It is knowing where things are, who to call, which fields matter, which step can be skipped without consequence. Almost none of that is written down. It lives in the hands of the people who do the work, and it took them years to build.
Every meaningful change takes that fluency away before it gives anything back. The workarounds stop working. The spreadsheet that quietly held the old system together no longer connects to anything. Output falls, effort rises, and confidence falls fastest of all, because people notice their own awkwardness long before they notice their progress.
Organisations then measure the dip and treat it as a verdict. Cycle times are up. Error rates are up. Sentiment is down. The measurement is usually accurate. The interpretation is usually wrong. What is being measured is the cost of not being good at something yet, and that cost is not evidence of a bad decision. It is the price of admission for any decision at all.
This is the sense in which discomfort is not a sign that you are doing it wrong. It is a sign that you are doing something new, and doing something new has a shape. The shape includes a period of being worse.
Comfort is a reliable measure of exactly one thing: how well your current habits fit your current situation. That is genuinely useful information when the situation is stable. It is close to worthless when the situation is the thing that changed.
A team can be entirely comfortable inside an operating model that stopped serving the business two years ago. Comfort will not raise the alarm. It never does. It reports only on the fit between habit and environment, and it reports most confidently just before that fit disappears.
The trap is that discomfort is not self-justifying either. Some things feel wrong because they are wrong. Treating every objection as resistance is one of the most expensive mistakes available to a leader, and it is expensive twice over. It removes the organisation's early warning system, and it teaches people that honest feedback will be reinterpreted as fear. After that has happened once or twice in public, you no longer hear anything worth hearing.
So the useful skill is not tolerating discomfort. It is reading it.
Reading the signal
A few distinctions have held up for me across very different organisations.
The first is direction over time. Learning discomfort decays. It is sharpest in week one, duller in week four, and by week ten people have stopped mentioning it because they have absorbed the new work into their hands. Design discomfort does not decay. It recurs at the same point in every cycle, with the same people raising the same objection, because the friction is in the thing itself rather than in the newness of the thing.
The second is location. Is the difficulty in the skill or in the structure? Not knowing yet is a skill problem and time will solve it. Being asked to do something that cannot be done well, because two parts of the new design contradict each other, is a structural problem and time will only entrench it. People on the ground can almost always tell you which one they are experiencing, if they believe the question is sincere.
The third is distribution. If the discomfort lands entirely on the people with the least authority to change anything, while the people who designed the change experience only its benefits, that is not a growth curve. That is a design fact, and it will eventually be paid for.
The fourth is information. Healthy discomfort tends to arrive with new visibility. People say they can now see the queue, or the handover, or the real cost of a decision, and they do not like what they see. Unhealthy discomfort arrives with lost visibility. People can no longer see what they used to see, and they are being asked to work blind while calling it maturity.
Discomfort tells you that something has changed. It does not tell you whether the change was wise. That question has to be answered on its own terms, with evidence, and not by consulting how the week felt.
The better question
If comfort is the wrong instrument, something has to replace it. The question I keep returning to is whether the thing I am doing builds capacity for what comes next.
Capacity is the range of situations you can meet without falling apart. It is broader than skill. It includes the ability to sit inside partial understanding, to work with people whose judgement differs from yours, to hold a decision open one day longer than is comfortable. Capacity is only ever built in the period where you are not yet good at the thing. There is no other window.
The question also has a demand hidden inside it. It asks you to name what next actually is. A change that is preparing an organisation for a specific and describable future is one thing. A change with no destination beyond its own momentum is another, and the discomfort it produces has nowhere to go. When leaders cannot answer the question, the objection from the floor is not resistance. It is accuracy.
This is currently visible everywhere in the way teams are adopting new tools. Applied AI makes capable people feel briefly incompetent, and the reaction is often to retreat to the old method where they were fast. The honest question is not whether the tool feels natural in the first month. It is whether the person is building judgement about where it helps, where it misleads, and what still requires them. That judgement cannot be acquired from a distance. It is only available to people willing to be slow in public for a while.
Most of the changes that mattered in my own career did not announce themselves as insight. They announced themselves as awkwardness, and I only understood them later, once the awkwardness had turned into something I could use. I do not think there is a version of this where you get to feel entirely like yourself and become someone new in the same season.
The discomfort is not the achievement. It is the weather you work in while the capacity is being built.