Ninety days after the 360: what separates the managers who change from the ones who meant to

Six weeks after the debrief, the operations manager is running the six o'clock briefing again. Nobody asked him to. Two agency pickers failed to turn up on Monday, and the biggest customer has a promotion going through the warehouse. By Tuesday it looked quicker to do it himself. So he stands at the front of the goods-in bay with the pick sheets, answering each question before it is finished. The trailers leave on time.

The managing director sees it at a quarter past seven, on his way in. He commissioned the 360 in the spring. Two of his better shift leaders had gone quiet, and one had started asking about vacancies at another depot. The report confirmed what he had half suspected about the gap between how his manager saw himself and how the floor experienced him. But the debrief went well, and the plan that came out of it named three priorities: delegate day-to-day decisions, develop the shift leaders, and raise problems earlier. Everyone left the room meaning it. He decides this is not the week and goes upstairs.

Nothing here looks like failure. Yet this is how the change from a 360 tends to leak away. It goes one reasonable exception at a time, until ninety days have passed and the business runs as it did before the report arrived. The conversation that turns a 360 report into three priorities has its own article. This one picks up the morning after.

Why the sixth week is where it goes

The first weeks after a debrief carry themselves, because the report is fresh and the manager knows he is being watched. Week six is different. The report is in a drawer, and the business has moved on, but the new behaviour still takes effort every time.

That last part matters more than it sounds. Researchers at University College London followed ninety-six volunteers trying to make one small daily action automatic, such as eating a piece of fruit with lunch. For those whose progress could be modelled, it took a median of sixty-six days to get close to automatic, and estimates ran from eighteen days to more than eight months. Handing a briefing to a slower colleague is harder than eating an apple. So at week six, the new behaviour is still a daily decision. The old one is automatic.

Then the first bad month arrives, and in a business of seventy people one is always on its way. It tests the new behaviour where it is weakest. When the trailers have to leave by eight, the quickest route wins, and the quickest route is the one the manager has always taken. On Tuesday he did what he is best at, when the business most needed it. In the moment, nobody would call that a lapse, and that is why it goes unremarked. Twenty minutes put six weeks at risk.

Three priorities on paper, two behaviours anyone can see

Look again at the plan: delegate day-to-day decisions, develop the shift leaders, raise problems earlier. Each was sincerely agreed. But none of them says what the operations manager should do differently at six o'clock on a Tuesday.

This is where the ninety days are usually lost, on the morning after the debrief and well before the first bad week. Priorities written in the language of a competency framework describe a direction, not a visible action, so there is nothing for anyone outside the room to check week to week. The change then depends on the manager's goodwill in the very month he has least of it.

So on the morning after, two of the three priorities need translating into behaviours. Anyone who missed the debrief should be able to tell whether they happened. For the operations manager, the first might be that the shift leaders run the six o'clock briefing, and he arrives at ten past and speaks last. The second is that when a shift leader brings him a problem, he asks what she would do before saying what he would. Neither needs interpreting. His team will know within a week.

Why two, when the plan has three? Because the third tends to be a capability that takes longer to build, and raising problems earlier depends on judgement about which problems matter. That grows over the six to twelve months of coaching that follow. The two behaviours should show within ninety days. They also make room for the third, since a manager who has stopped running every briefing has an hour a day to think ahead.

The research supports this kind of precision, though its findings are more modest than the claims often made for 360 feedback. A review of twenty-four studies following managers over time found ratings improved only slightly. The authors concluded that improvement is more likely when managers set goals in response and act on them. In a separate study of 1,361 senior managers, those who worked with a coach afterwards were more likely to set specific goals. Their ratings also improved more, by a small margin. So the report does little on its own; what counts is what the manager commits to afterwards, and how precisely.

Who asks, and how often

Ask nobody, and a behaviour stays a private resolution that rarely survives a bad month. So the question for the first ninety days is who does the asking, and on this the evidence points one way.

First, the manager himself asks the people who rated him. A five-year study of 252 managers found that those who met their direct reports to discuss their feedback improved more than those who did not. They also improved more in the years they held that conversation than in the years they skipped it. A larger practitioner analysis of over 11,000 managers in eight companies pointed the same way. It was published by the executive coach Marshall Goldsmith and Howard Morgan. Leaders who discussed their priorities with colleagues and followed up regularly were seen to improve markedly, while those who did not improved barely more than chance.

Neither study proves that the conversation causes the change. The managers who go back may be the ones most set on changing anyway. But a manager who never asks has no way of knowing whether anything he is trying is visible. And his team has no evidence that he is trying at all.

In a business of seventy people, the conversation can be short. Every fortnight, at the end of the briefing he no longer runs, the operations manager asks his shift leaders one question. "Two weeks ago I said I would stay out of the briefing and ask before I answer, so what did you notice, and what should I do more of?" It will feel awkward the first time, and by the third it is routine. And the shift leaders will have learned that the 360 was more than a form they filled in and never heard about again.

The second person asking is the managing director, once a month. He needs twenty minutes and a specific question: did the shift leaders run every briefing this month, and what happened on the days they did not? That gets a real answer. And it tells the manager that whoever paid for the 360 is still reading it.

Owner-managed businesses tend to drop out at this point. The MD is busy, and the manager is senior, so asking starts to feel like supervision, and by the second month the diary slot has gone. Where a business has a manager everyone has agreed must change and nobody is following up, the gap is usually here. It opens between a debrief that went well and a follow-up that nobody owns.

I have sat in enough of these monthly reviews to know the diary slot is the first casualty, and it never goes with a decision, just a rescheduled meeting that no one rebooks.

Where a coach is involved, the work between those conversations is different again. In the structured, competence-based coaching I run after a 360, the plan from the debrief becomes the agenda for each session that follows. Much of it goes on the mornings the old behaviour came back, and on what the manager does when two pickers next fail to show. That is also where the third priority gets built, once the two behaviours are holding.

When the answer is no

At some point in the ninety days, the MD will ask about the two behaviours, and the answer will be no. And what he does next depends on which kind of no it is. From outside, they look alike.

The first comes from the manager who tried and slipped. He ran the briefing himself in the bad week and can say why. That is normal. The UCL researchers found that missing a single day did not materially set back the forming of a habit. Tell that to a manager who thinks one lapse has undone six weeks. So go back to that morning with him and agree on what he will do when the same pressure arrives next.

The second comes from the manager who has not tried. The priorities were agreed in the room and never accepted, and the fortnightly question has not been asked once. This is a different conversation. It is about what the job requires, and if it has to become a performance matter, it needs its own footing. The Acas Code of Practice covers poor performance as well as misconduct. And Acas guidance expects an employer to try to help someone improve before a formal procedure starts. That means a plan with specific objectives, a reasonable timeline and whatever support he needs.

The anonymous 360 ratings make poor evidence for that, and should not be asked to carry it. The people who rated him did so on the understanding that it was for his development. Turn their answers into evidence, and the next round will be politer. But the observable behaviour can carry it, with dates and costs written down at the time. That matters, because a performance process has to stand on evidence gathered for that purpose.

A less comfortable possibility belongs to the MD who commissioned the 360. Sometimes the answer is no because the business keeps pulling the manager back. An MD who agreed that the shift leaders should run the floor, then rings the operations manager at twenty to seven about a customer's order, has shown him which behaviour the business rewards. Before concluding that a manager will not change, check who got the first phone call when things went wrong.

What the team decides while everyone is being patient

The operations manager's team filled in the 360. They were asked in confidence what it is like to work for him, and some of them took a risk in answering. But the report stays upstairs, and what they see is Tuesday morning.

Teams form their view long before ninety days are up. Somewhere in the first two months, often on a morning like the one this piece began with, they decide what the feedback was for, and what the business will tolerate. If the old behaviour comes back and nobody says anything, they conclude the report was either never read or read and ignored. Both end the same way. The next 360 gets careful answers. And the shift leaders who went quiet in the spring start returning calls from other depots.

That cost is commercial. In UK research by the Chartered Management Institute and YouGov, half of the workers who rated their manager as ineffective planned to leave within a year. It also found that 82 per cent of those entering management had no formal training for it. The operations manager is very likely one of them. He was the best picker on the floor, and like many technically strong people made managers and left to work the job out, he was promoted for it. The 360 was the first time anyone had shown him how he leads. What happens in the ninety days afterwards tells him, and everyone who works for him, whether the business meant it. Part of the answer came the morning the MD walked past and went upstairs.

Day ninety

By day ninety the evidence of change is specific, and it comes from other people. The manager refers to his two behaviours without being prompted, and his team can name what is different without being asked. Behind both are three short conversations in the MD's diary, a month apart, about the same two things. Where they are missing, at least the MD knows which kind of no he faces.

One morning, probably in a bad week, the operations manager will run the briefing himself again. Whether he changes will be settled by whether anyone mentions it by Friday. The one person who can make sure somebody does is the person who commissioned the 360.

If a manager in your business agreed to change after feedback and you could not say today what the two things were, a short message gets a direct view on how to name them and who should be asking. It comes back from me, usually the same day.

Common questions

What should happen after 360 feedback?

The debrief should end with three development priorities. Within a day or two, two of them should be rewritten as behaviours specific enough for the team to see whether they happen. The manager then goes back to the people who rated him every few weeks to ask what they have noticed, and the MD or his line manager reviews the two behaviours by name once a month. The longer-term priority is developed through coaching over the following six to twelve months.

How long does it take to see change after a 360?

In our experience, specific behaviours that someone is following up become visible to the team within about ninety days. In a UCL study of everyday habits, the median time for a simple daily action to become close to automatic was sixty-six days among participants whose progress could be modelled, with wide variation, and leadership behaviours are more complex than that. Studies that followed managers over time found that ratings tend to improve modestly, with larger gains among managers who set specific goals and discussed their feedback with their teams.

Can 360 feedback be used in performance management?

It is safer to keep them apart. 360 ratings are normally given in confidence for development, and using them as evidence changes how people answer next time. If a manager's performance needs managing formally, the Acas Code of Practice applies to poor performance. Acas expects the employer to try to help first, with a plan setting specific objectives, a reasonable timeline and any support needed, and the evidence should be observable performance recorded at the time.