What Great Managers Do Differently

Quick Answer: what great managers do differently: Five behaviours separate managers people stay with from managers people tolerate. They run one-to-ones that are actually two-way. They give feedback the same day rather than at review time. They make decisions clearly and explain the reasoning once. They take the blame publicly and the learning privately. And they coach rather than instruct — giving people the judgement to make a decision you would have made, instead of making the decision for them.

What this guide covers

• The five behaviours that distinguish great managers
• How to run a one-to-one that changes performance
• Why fast feedback works and how to deliver it
• Making and closing decisions without ambiguity
• Taking responsibility publicly and learning privately
• Moving from instruction to coaching, in three steps

Most managers are managing tasks

The difference between a competent manager and a great one is not effort or intelligence. It is the object of their attention. Average managers spend most of their time on the work: tracking tasks, chasing status, approving things, resolving what came up this week. Great managers spend most of their time on the people who do the work — and that is why their teams perform without constant supervision.

The five behaviours below are the observable version of that shift. None of them requires a different personality or a new framework. Each requires a change in what the manager spends their attention on.

1. They run one-to-ones that are actually two-way

The weekly one-to-one is the most valuable meeting a manager has, and it is the most commonly wasted. The standard version is a status update in both directions: the report says what they did, the manager says what they need done. It produces nothing that a shared task list would not.

The great version inverts the order. The report’s agenda comes first; the manager’s items go at the end, and only if there is time. The agenda is the report’s — the thing they want to discuss, the decision they are stuck on, the problem they cannot solve alone, the thing they think the manager is not seeing.

Three questions make this work:

• “What do you want to talk about today?”
• “What is on your mind that you have not said out loud?”
• “What do you need from me, and by when?”

The third question is the one most managers skip, and it is the one that makes the meeting worth having — because it turns the conversation into commitments with owners and dates.

The failure mode is a manager who fills the first ten minutes with their own agenda, which teaches the report that this meeting is not safe. The habit worth building is a genuine thirty seconds of silence at the start.

2. They give feedback the same day

The single biggest behavioural difference, and the one covered in depth in the one leadership skill that changes everything. The summary: feedback given on the day it happened is coaching, and the same words given a week later are a verdict. Memory fades, defensiveness grows, and the connection between the action and the consequence disappears.

Three properties make it land. Specific: the behaviour, not the character. Consequential: what it affected, so the person can calibrate what deserves attention. Directive: what you want next, concretely enough to act on.

Great managers also deliver the positive version with the same rigour, because vague praise teaches nothing. “Great job on the report” cannot be repeated; “the way you opened with their own numbers instead of our claims is what got them engaged — do that every time” can be repeated on Thursday.

3. They make decisions clearly and close them

A great manager makes a decision and says four things: what the decision is, who owns it, why it was made, and what it ends. That last one is the one teams need most and rarely get.

Most frustration inside teams is not caused by bad decisions. It is caused by ambiguity — a decision that was made but not communicated, or communicated without an owner, or left technically open while everyone behaves as if it were settled. The result is the specific exhaustion of people not knowing whether they should act.

The structure that removes it is short: state the decision, name the owner, give the reasoning once, and state what it closes. “We are moving the deadline to the 15th. Priya owns it. We are doing it because the client asked for a week earlier. This closes the question of whether to delay again — I do not want it reopening.”

Explaining the reasoning once matters because it is the part people need in order to apply the decision to a situation you did not anticipate. Deciding is not the same as justifying; it is not a referendum.

4. They take the blame publicly and the learning privately

When something goes wrong, the team watches what the manager does in the next ten minutes, and they learn more from that than from any values statement.

The strong pattern is consistent: in front of the team, the manager takes responsibility without qualification — “this was our miss, and here is what we are doing about it” — and does not speculate about causes or name anyone. Privately, with the person involved, the full learning conversation happens, including what they would do differently and what the manager got wrong.

The pattern that damages teams is the reverse: public analysis of who caused it, private reassurance to the person concerned. It teaches everyone that failure is dangerous to be associated with, which is precisely when you need people to bring you bad news.

The behaviour is also self-reinforcing. Managers who absorb the heat once earn the right to be blunt later, because the team already knows the criticism is not a personal verdict.

5. They coach instead of instructing

This is the behaviour that scales a manager, and the hardest to learn because instructing feels faster.

Instruction: “Send the quote with the 15% discount and mention the implementation timeline.” The work gets done, and the person learned nothing transferable.

Coaching: “What would you do about the discount request?” They work through it, arrive at something close to the right answer, and now own the reasoning for next time.

The test of coaching is whether the person could handle a similar situation you were not present for. If the answer is no, you instructed rather than coached.

Three steps to move from instructing to coaching:

Ask before telling. “What are your options here?” Most managers cannot wait for the answer; the pause feels like a stall. The pause is where the learning happens.

Ask for their reasoning, not just their answer. Two reps can reach the same conclusion, one by reasoning and one by luck. “How did you get there?” builds judgement; “what did you decide?” does not.

Transfer the consequence. “You decide, and I will check in on Friday.” The point at which you intervene should be agreed in advance, otherwise coaching becomes hovering.

Coaching is slow at first and it compounds. A team of people who can make your decisions when you are not in the room is the only version of a manager that scales — and it is what makes building a winning team culture possible rather than aspirational.

Putting it into practice this month

One-to-ones: change the order this week. Their agenda first, your items at the end, and ask “what do you need from me?” every time.

Feedback: deliver one piece of specific feedback today — observed, affected, next. Note how it feels to do it, because the discomfort is what stops most managers doing it consistently.

Decisions: for the next decision you make, say all four parts out loud, including what it closes.

Blaming: the next thing that goes wrong, own it publicly in one sentence and save the analysis for the private conversation.

Coaching: pick one recurring decision you currently make for someone, and let them make it this week with an agreed checkpoint.

None of this needs a training budget. It needs the acknowledgement that a manager’s attention is the scarce resource, and that most of it is currently spent on work that people are capable of doing.

Related reading

• The One Leadership Skill That Changes Everything
• How to Build a Winning Team Culture
• Why Employees Quit and How to Prevent It

Frequently asked questions

What do great managers do that average managers do not?

Five behaviours: they run one-to-ones where the report’s agenda comes first and the manager’s items go last; they give feedback on the day it happened rather than at review time; they make decisions with four explicit parts — what, who owns it, why, and what it closes; they take responsibility publicly when something goes wrong and do the learning privately; and they coach rather than instruct, so people can handle the next similar situation alone. The common thread is attention: great managers spend it on people rather than on the work itself.

How often should a one-to-one meeting happen?

Weekly is the working answer for most teams. It is frequent enough that small problems surface early and infrequent enough that it does not become a reporting ritual. The meeting only works if the report’s agenda comes first and the manager’s items go at the end — if the manager spends the first ten minutes on their own priorities, the report learns that this meeting is not safe and stops bringing anything real to it.

Why is fast feedback so much better than a review cycle?

Because memory fades and defensiveness grows with distance. Feedback on the day is heard as coaching because the action and the consequence are still connected; the same words a week later arrive as a verdict, and the person cannot reconstruct what they did. The other reason is diagnostic: in the moment you know exactly what happened and what you want instead, so the feedback can be specific enough to act on rather than a general impression.

How do I coach without micromanaging?

Ask before telling, ask for the reasoning rather than just the conclusion, and transfer the consequence explicitly. “What would you do about the discount request?” then “How did you get there?” then “You decide and I will check in on Friday” — with the checkpoint agreed in advance so it does not become hovering. The test is whether the person could handle a similar situation without you present. If not, you instructed rather than coached.

What does a great manager do when a mistake happens?

Takes responsibility in front of the team without qualification — “this was our miss, and here is what we are doing” — without speculating about causes or naming anyone, then holds the full learning conversation privately with the person involved, including what they would do differently and what the manager got wrong. The reversed pattern, public analysis and private reassurance, teaches the team that failure is dangerous to be associated with, which is exactly when you need people bringing you bad news.

How do I give feedback to someone senior or more experienced?

Use the same structure, and lead with respect for their judgement. The specific version that works: what you observed, why it matters in this context, and what you want — with a genuine question at the end about what they see that you do not. The temptation with senior people is to soften everything, which removes the actionable content; the alternative is to soften the framing and keep the substance. Being told “this will be hard to read at the customer” is more useful than “maybe consider simplifying the layout”.

Can a new manager build these habits quickly?

Faster than most people expect, because these are behaviours rather than traits, and the two fastest are the cheapest. Moving the one-to-one agenda to the end of the meeting changes the dynamic in a single week. Delivering one piece of specific feedback per week builds tolerance for the discomfort in about a month. The slower ones — coaching instead of instructing, absorbing blame publicly — take longer because they require a change in how the team experiences you, and that needs repetition before it is believed.

Written by SkilBrill Training Institute

November 5, 2026 · 11 min read