25 Things Great Managers Do that Average Managers Skip

From weekly one-on-ones to early performance conversations, these 25 habits separate managers people remember for decades from managers people merely tolerate for a paycheck

Most people can name the best manager they ever had within seconds. They can also name the worst. The middle — the vast population of average managers — blurs together. Average managers are not villains. They approve time off, run the weekly meeting, pass along direction from above and stay out of the way. What they skip is the harder, less visible work: the early feedback conversation, the deliberate delegation, the career discussion that has nothing to do with this quarter’s deadline. That skipped work is precisely where great management lives.

The gap matters more than most organizations admit. Managers sit at the point where strategy becomes daily work. A company can have a clear mission, strong products and generous pay, and still lose good people because their direct manager never told them how they were doing, never explained why priorities changed and never noticed when they were drowning. The reverse is also true. People stay in imperfect companies for years because one manager made the work feel coherent and made them feel seen.

What separates great managers from average ones is rarely charisma or raw intelligence. It is a set of repeatable behaviors, most of which are unglamorous. Great managers write things down. They prepare for meetings they run. They say hard things early, when the stakes are small, instead of late, when the stakes are large. They treat one-on-ones as the employee’s time rather than a status update. None of these habits requires a leadership retreat or a certification. They require attention, consistency and a willingness to do uncomfortable things on a schedule rather than when a crisis forces the issue.

This list collects 25 of those behaviors. Some concern communication, some concern accountability and some concern the quiet administrative discipline that makes a team run without drama. Each one is a habit an average manager tends to skip — not out of malice, but because it is easier not to do it and the cost of skipping it arrives slowly. Read them as a checklist. Most managers already do a few. The great ones do most of them, most of the time.

1 / 25

They give feedback within days, not at review time

Credit:  MART PRODUCTION /  Pexels

Average managers save feedback for the performance review. Great managers deliver it while the work is still warm — within days of the event, sometimes within hours. The difference sounds procedural, but it changes everything about how a team learns.

Feedback delivered months later fails on two fronts. The person barely remembers the situation, so the conversation becomes an argument about what actually happened rather than a discussion about how to improve. And the behavior has had months to harden into habit, which makes it far more expensive to change. A presentation that ran long in March is a small note in March. Raised in November, it becomes a pattern, a paragraph in a review document and a source of resentment.

Great managers treat feedback as a routine, low-stakes act rather than an event. They mention the confusing email the same afternoon. They flag the meeting where someone talked over a colleague before the end of the day. Because the feedback arrives constantly and in small doses, no single piece of it feels like a verdict on the person’s worth. People stop bracing for it.

The habit also transforms the annual review itself. When feedback flows all year, the review contains no surprises. It becomes a summary of conversations already had, which is exactly what it should be. A review that shocks the employee is not a sign of a tough manager. It is evidence that the manager sat on information for months.

Speed applies to praise as much as criticism. Telling someone their analysis changed a decision means far more on the day the decision happened than as a bullet point 10 months later. Average managers assume people know when they have done well. Great managers know that silence reads as indifference, and they close that gap quickly. The rule is simple: if it is worth saying at review time, it was worth saying the week it happened.

2 / 25

They treat one-on-ones as the employee’s meeting

Credit: RDNE Stock project / Pexels

Average managers use one-on-ones to collect status updates. Great managers hand the agenda to the employee. That single shift changes the meeting from a reporting ritual into the most valuable half hour on either calendar.

Status can travel in writing. A dashboard, a project tracker or a two-line message covers what got done and what is blocked. When a manager spends the one-on-one asking “where are we on the launch,” they burn scarce private time on information they could have read. Worse, they signal that the meeting exists for the manager’s convenience.

Great managers open differently. They ask what is on the employee’s mind, what is frustrating them, what they want to talk about that has no other venue. The topics that surface — a conflict with a colleague, doubt about a career path, a process that quietly wastes hours every week — are exactly the ones that never appear in a status report and that fester when ignored.

Consistency matters as much as content. Average managers cancel one-on-ones whenever something urgent appears, which is often. Each cancellation sends a message: you are the most movable item on my calendar. Great managers protect the slot. They may shorten it in a brutal week, but they rarely delete it, because they know the meeting’s value compounds. An employee who trusts that the time will happen saves topics for it. An employee who expects cancellation stops bringing anything real, and the meeting decays into the very status ritual it was supposed to replace.

The manager still gets what they need from these meetings — arguably more. Problems surface earlier. Departures stop coming as shocks. And the manager builds the kind of specific, personal knowledge of each report that makes every other management task easier, from delegation to reviews. Average managers ask what happened this week. Great managers ask what is actually going on.

3 / 25

They explain the reasoning behind decisions

Credit:  Pavel Danilyuk  /  Pexels

Average managers announce decisions. Great managers explain them. The announcement takes one sentence; the explanation takes five minutes. Those five minutes are among the highest-return investments a manager can make.

People can execute an instruction they do not understand, but they execute it badly. They cannot adapt when circumstances shift, because they never knew the goal behind the instruction. They cannot make good judgment calls at the edges, because they have no model of what the manager would want. Every ambiguity becomes a question routed back up, and the manager becomes a bottleneck of their own making.

Explanation fixes this. A manager who says “we are prioritizing the enterprise customers this quarter because two contract renewals are at risk, and losing either would hurt more than delaying the new feature” has given the team a decision-making tool. Now an engineer choosing between two bug fixes can pick correctly without asking. A support lead knows which tickets to escalate. The reasoning scales in a way the instruction never could.

Explaining reasoning also builds durable trust, particularly around unpopular decisions. People accept outcomes they dislike far more readily when they understand the logic and the constraints. A hiring freeze explained — here is the budget picture, here is what leadership weighed, here is what would need to change — lands very differently from a hiring freeze announced. Silence invites people to fill the gap with the worst available theory.

There are limits. Some context is confidential, and great managers say so directly: “I cannot share everything behind this, but here is what I can tell you.” That honesty preserves trust even when full transparency is impossible. What great managers never do is default to “because that is the decision.” That phrase saves five minutes and costs weeks of second-guessing, misalignment and quiet cynicism. Average managers relay conclusions. Great managers transfer understanding.

4 / 25

They delegate outcomes, not tasks

Credit:  Vitaly Gariev  /  Pexels

Average managers hand out tasks. Great managers hand out outcomes. The distinction determines whether a team develops judgment or merely develops throughput.

Task delegation sounds like this: write a summary of the customer calls, format it as a slide, send it to me by Thursday. Outcome delegation sounds like this: the leadership team needs to understand what customers are telling us before Friday’s planning meeting — figure out the best way to get that across, and it is yours. The first version produces a slide. The second version produces a slide and a person who now thinks about audiences, formats and deadlines on their own.

Delegating outcomes requires managers to give up control of the method, which is exactly why average managers avoid it. The report might approach the problem differently than the manager would. The first attempt might be worse than what the manager could produce in half the time. Great managers accept that short-term cost because they are buying something more valuable: a team member who can own the whole problem next time without instruction.

The habit demands clarity up front. Great managers spell out what success looks like, what constraints exist, what the deadline is and how much risk the person can take without checking in. Then they stop. They do not hover, rewrite drafts in secret or reclaim the work the moment it wobbles. Reclaiming delegated work once teaches a person never to fully commit to delegated work again.

Outcome delegation also solves the manager’s own scaling problem. A manager who delegates tasks must generate every task, which caps the team’s output at the manager’s imagination. A manager who delegates outcomes multiplies themselves. Over a year, the difference is visible in who gets promoted from each team. Task-managed teams produce reliable executors. Outcome-managed teams produce future managers.

5 / 25

They say hard things early, when the problem is small

Credit:  Edmond Dantès  /  Pexels

Average managers wait for problems to become undeniable before addressing them. Great managers speak up when the problem is still small enough to be a conversation rather than a confrontation.

The pattern is familiar to anyone who has worked on a team. Someone starts missing small deadlines. The manager notices but says nothing — it seems petty, the person is busy, maybe it will self-correct. Three months later the misses are chronic, teammates are compensating and resentful, and the manager finally schedules the talk. By now the conversation carries the weight of months. The employee, blindsided, asks the reasonable question: why didn’t you say something sooner?

Early intervention changes the math entirely. A manager who mentions the first or second missed deadline can be genuinely light about it: “I noticed the last two handoffs slipped — anything going on?” The question costs 30 seconds. It might surface a workload problem, a personal issue or a simple misunderstanding about priorities. Whatever the cause, it gets addressed while it is cheap to address.

Delay has a second cost that managers underestimate: the rest of the team is watching. When a performance or behavior problem goes visibly unaddressed, high performers draw conclusions. They conclude that standards are optional, that the manager avoids discomfort and that carrying a weaker colleague is now part of their job. Nothing erodes a strong team faster than watching a manager tolerate what everyone can see.

Great managers also apply the early-conversation rule to interpersonal friction, scope disagreements and their own concerns about a project’s direction. The discipline is the same in every case: the discomfort of raising something now is always smaller than the discomfort of raising it later, and the gap widens every week. Average managers optimize for a comfortable today. Great managers accept a slightly awkward today to avoid a genuinely painful quarter.

6 / 25

They give credit in public and criticism in private

Credit:   Tima Miroshnichenko  /  Pexels

Average managers get this backward more often than they realize. They critique work in group settings, where the audience raises the stakes, and they deliver thanks in private asides, where it builds nothing. Great managers hold the line on the old rule because they understand what each direction of feedback is actually for.

Public credit does two jobs at once. It rewards the person who did the work, and it teaches everyone else what the manager values. When a manager tells the whole team that someone’s careful documentation saved the launch, every person in the room updates their sense of what gets noticed here. The praise has to be specific to work — naming the exact contribution and its effect — or it reads as favoritism rather than standards. “Great job, as always” builds resentment. “Your test plan caught the billing bug before customers did” builds culture.

Public criticism does damage far beyond the moment. The person being criticized stops processing the content and starts managing their humiliation. Colleagues feel a mix of relief and fear. And everyone learns the real lesson: do not take risks in front of this manager. Even mild corrections — a pointed “we talked about this” in a meeting — accumulate into a team that hides problems.

Private criticism, by contrast, lets the actual message land. Behind a closed door, a person can ask questions, push back, admit confusion or simply absorb the point without an audience tracking their reaction. The conversation can be direct precisely because it is private.

Great managers also route credit upward correctly. When their own boss praises a project, they name the people who did the work, specifically and immediately. Average managers absorb that praise, sometimes without even noticing they are doing it. Teams always notice. Few things reveal a manager’s character faster than watching where credit goes when it arrives from above.

7 / 25

They admit what they do not know

Credit:  Alena Darmel   /  Pexels

Average managers treat “I don’t know” as a confession of weakness. Great managers use it as a working tool. The difference shapes how honest an entire team can afford to be.

A manager who bluffs teaches the team to bluff. When the boss confidently answers questions they cannot actually answer — about the reorg, the roadmap, the reason a deal fell through — people eventually catch the pattern. From then on, every statement from that manager gets discounted. The team starts triangulating truth from other sources, and the manager loses the one asset that makes managing possible: being believed.

The honest version costs little and buys a lot. “I don’t know, and here is how I will find out” is a complete, respectable answer. So is “I don’t know, and I may not be able to get an answer on that.” Teams handle uncertainty well. What they handle badly is discovering that certainty was faked.

Admitting ignorance also unlocks better work. A manager who pretends to understand the technical architecture cannot ask the basic question that exposes a flawed plan. A manager who says “walk me through this like I have never seen it” often surfaces the assumption everyone else was too embarrassed to question. Senior people asking junior questions is a marker of strong teams, and it starts at the top.

There is a related discipline: admitting mistakes. When a great manager calls a project wrong, they say so plainly — I made that call, it was wrong, here is what I am changing. No passive voice, no “mistakes were made,” no quiet reassignment of blame. That admission does not diminish authority. It defines it. People follow managers who own errors far more willingly than managers who launder them, because they know that when things go wrong on their own work, the response will be honest rather than political.

8 / 25

They prepare for the meetings they run

Credit:  Felicity Tai /  Pexels

Average managers walk into their own meetings and improvise. Great managers treat every meeting they call as a claim on other people’s time that has to be justified in advance.

The math explains why. A one-hour meeting with eight people consumes a full workday of collective attention. An unprepared manager who spends the first 15 minutes figuring out what the meeting is about has burned two hours of team capacity on their own lack of discipline. Do that weekly and the waste compounds into weeks of lost work per year — all of it invisible on any budget.

Preparation does not mean elaborate decks. It means answering three questions before the invitation goes out. What is this meeting supposed to produce — a decision, a plan, shared understanding? Who actually needs to be there for that to happen? What do attendees need to see beforehand so the meeting starts at the interesting part instead of the recap?

Great managers send the relevant document or data in advance and expect people to arrive having read it. They open by stating the goal in one sentence. They notice when discussion drifts and pull it back, and they notice when the goal has been reached and end early. Ending a scheduled hour after 25 minutes because the decision is made signals respect more clearly than any speech about valuing people’s time.

They also cancel meetings that have lost their reason. Recurring meetings are where average managers hide — the weekly sync that no longer syncs anything, kept alive because deleting it feels like admitting it was never needed. Great managers audit their recurring calendar a few times a year and kill what no longer earns its slot.

The team notices all of it. A manager who runs tight, purposeful meetings earns the right to call one on short notice and have people show up engaged. A manager known for meandering meetings trains people to bring laptops and half their attention.

9 / 25

They ask questions before offering solutions

Credit:  RDNE Stock project  /  Pexels

Average managers hear a problem and start solving it, often before the person has finished describing it. Great managers ask questions first. The restraint looks passive but it is one of the most active things a manager does.

Jumping to solutions fails in predictable ways. The manager solves the problem as stated, but the stated problem is often a symptom. An employee complaining about a slow approval process may actually be describing a trust problem with a specific stakeholder. A manager who fires off a process fix has treated the fever and missed the infection. Questions — what have you tried, what do you think is really going on, what would you do if the decision were yours — surface the underlying issue that a quick answer would have buried.

Instant solutions carry a second cost: they train people to stop thinking. When every raised problem returns a manager-issued answer, reports learn that the efficient move is to escalate early and think little. Within a year the manager is the team’s only functioning brain, drowning in decisions that should never have reached them. Managers who ask “what do you recommend?” before offering anything build teams that arrive with proposals instead of problems.

The habit requires tolerating a pause. The manager often does know a workable answer within seconds, and holding it back feels inefficient. It is inefficient — once. Over dozens of repetitions, the questions produce people who solve their own problems, which is the only efficiency that scales.

There are exceptions, and great managers know them. In a genuine emergency, decisiveness beats Socratic method. When someone is far out of their depth, teaching beats quizzing. And when a person explicitly asks “just tell me what you would do,” a direct answer respects their time. The default, though, stays the same: questions first, solutions second. Average managers demonstrate how smart they are. Great managers demonstrate how smart their team can be.

10 / 25

They write decisions down

Credit:  Moe Magners /  Pexels

Average managers rely on memory and hallway consensus. Great managers write decisions down — what was decided, why, by whom and what was explicitly ruled out. The habit looks bureaucratic and turns out to be the opposite.

Undocumented decisions do not stay decided. Three weeks after a meeting, two attendees remember two different conclusions, a third remembers no conclusion at all, and the argument reopens with the same points as before. Teams can burn entire quarters relitigating choices they already made, purely because no one wrote down the outcome. A five-line summary sent after the meeting — decision, reasoning, owner, date — closes that loop permanently. Anyone who disagrees can object now, in writing, rather than through quiet noncompliance later.

The reasoning matters as much as the ruling. Six months on, circumstances change and someone asks whether the decision still holds. If only the conclusion was recorded, nobody knows whether the original logic still applies. If the reasoning was recorded, the question takes five minutes: the assumptions either held or they did not. Documented reasoning also spares new hires the archaeology of asking why things are the way they are, one veteran at a time.

Writing things down protects people, too. When a decision goes wrong, undocumented history gets rewritten fast, and blame drifts toward whoever is least senior or least present. A written record keeps accountability where it belongs — often with the manager who made the call. Great managers accept that exposure. Average managers sometimes prefer the fog, which is its own tell.

None of this requires heavy process. A running decision log, a pinned message, a short email with a clear subject line — the format matters far less than the habit. The test is simple: could someone who missed the meeting reconstruct what was decided and why from the record alone? On great managers’ teams the answer is yes, which is why those teams spend their meetings on new questions instead of old ones.

11 / 25

They manage up as deliberately as they manage down

Credit: Vlada Karpovich /  Pexels

Average managers treat their own boss as weather — unpredictable, occasionally destructive, to be endured. Great managers treat the relationship upward as part of the job, and their teams benefit as much as they do.

Managing up starts with removing surprises. Great managers make sure their boss never learns about a problem from someone else first. Bad news travels upward fast and framed honestly: here is what happened, here is the impact, here is what we are doing. A boss who trusts the flow of information delegates more, checks in less and defends the team when questions come from above. A boss who has been blindsided twice starts micromanaging, and the whole team pays for it.

The second element is translation. Executives do not need 40 slides on the project; they need to know whether it is on track, what it needs and what decision, if any, is theirs to make. Great managers compress ruthlessly and lead with the point. They also learn how their particular boss consumes information — some want a written brief before the meeting, some want the meeting cold — and adapt rather than complaining that the boss should adapt to them.

Third is advocacy. The team’s work does not speak for itself; someone has to speak for it in rooms the team never enters. Great managers make their people’s contributions legible upward, by name, especially when promotion and budget decisions are forming. Average managers assume good work gets noticed. It does not. It gets narrated, and if the manager will not narrate it, no one will.

None of this is politics in the pejorative sense. It is plumbing. Resources, protection and opportunity all flow through the relationship between a manager and their boss, and a manager who neglects that pipe starves the team no matter how well they run the weekly standup.

12 / 25

They tailor their approach to each person

Credit: Mapbox / Unsplash

Average managers manage everyone the same way — usually the way they themselves like to be managed. Great managers run a different playbook for each person, because the same message, delivered identically to two people, produces two different results.

The variations are concrete. One engineer does their best thinking out loud and needs a manager who will spar in real time. Another needs the question the day before the meeting and will return a better answer than anyone in the room. One person hears “this needs work” as useful direction; another hears it as a career verdict and spirals for a week. Praise energizes one report and embarrasses another in front of the team. A manager who ignores these differences is not being fair. They are being lazy while calling it fairness.

Great managers gather this information deliberately. They ask directly: how do you like to receive feedback? What kind of work drains you? When you were at your best in a previous job, what did your manager do? The questions take one one-on-one and pay off for years. They also watch — who goes quiet in big meetings, who over-commits and then drowns silently, who does their best work at strange hours.

Tailoring style is not tailoring standards. The bar for quality, honesty and delivery stays fixed for everyone; what varies is the route each person takes to reach it. One report may need weekly check-ins on a project while another needs to be left alone for a month. Both are being held to the same outcome. Average managers confuse uniform process with fairness. Great managers know fairness is giving each person what they need to meet the same standard.

The payoff shows up in retention. People rarely stay for a management philosophy. They stay because their specific manager understood how they specifically work — and built around it.

13 / 25

They talk about careers, not just workloads

Credit:  Christina @ wocintechchat.com M / Unsplash

Average managers discuss the next deadline. Great managers also discuss the next five years — and not just during the annual review, when the conversation is contaminated by ratings and raises.

The career conversation average managers skip is a simple one: where do you want to go, and what would have to be true for you to get there from here? Skipping it feels safe. Raising ambitions can be awkward, especially when the honest answer involves a path the current team cannot provide. But the silence has a cost. People do not stop having ambitions because their manager never asks about them. They pursue them quietly, with recruiters.

Great managers hold this conversation on a regular cadence — a couple of times a year, separate from performance discussions. They ask what kind of work the person wants more of, what skills they want to build and whether management or deeper individual expertise looks more appealing. Then they do the part that distinguishes them: they connect the answers to real work. A report who wants to move toward product strategy starts getting invited to roadmap discussions. Someone building toward management gets an intern to mentor or a small project to lead. The career plan becomes assignments, not aspirations.

They are also honest about ceilings. If the promotion the person wants does not exist on this team, a great manager says so and helps them think about paths elsewhere in the company — or, sometimes, outside it. That honesty seems to risk losing people. In practice it does the opposite: people work hardest for managers they believe are invested in their trajectory rather than their retention.

The compounding effect is a reputation. Managers known for developing people attract the strongest internal candidates and get the benefit of the doubt from every new hire. Average managers fill roles. Great managers build alumni networks that keep sending talent back.

14 / 25

They make expectations explicit instead of assumed

Credit: Alena Darmel  /  Pexels

Average managers assume their expectations are obvious. Great managers know that “obvious” is where most performance problems are born, so they state expectations out loud, in specifics, and check that they landed.

The gap shows up everywhere. A manager expects a “draft” to be near-final; the employee delivers an outline. A manager expects proactive updates on a project; the employee assumes no news is good news. A manager expects a deadline of Friday to mean Friday morning; the employee ships at 11 p.m. None of these people is wrong by their own definition. They are operating from different unstated definitions, and the employee usually pays for the mismatch at review time.

Great managers close the gap at the start of every significant assignment. They specify what done looks like, when it is due, how much polish it needs, what budget of time it deserves and how often they want to hear about progress. Then they invert the check: rather than asking “does that make sense?” — a question that always gets a yes — they ask the person to play back their understanding. Thirty seconds of playback catches misalignments that would otherwise surface as a failed deliverable two weeks later.

The same discipline applies to behavioral norms. What counts as a conflict worth escalating? Is it acceptable to disagree with the manager in a group meeting? How responsive do people need to be after hours — genuinely, not officially? Average managers let people discover these rules by breaking them. Great managers state them before anyone has to guess.

Explicit expectations also make accountability fair. A manager who never defined the bar has no standing to be disappointed when someone misses it, though average managers manage to be disappointed anyway. When the bar was stated clearly and missed anyway, the resulting conversation is clean: here is what we agreed, here is what happened, what went wrong? No archaeology, no hurt feelings about moving goalposts — just a solvable problem.

15 / 25

They notice good work specifically, not generically

Credit: Andrea Piacquadio /  Pexels

Average managers say “great job.” Great managers say what was great about it. The distance between those two sentences is the distance between noise and information.

Generic praise fails quietly. “Great work on the launch” tells the person nothing about what to repeat. Was it the timeline management? The way they handled the last-minute scope change? The documentation? Praise without specifics is pleasant, forgettable and — when it arrives on schedule regardless of quality — eventually meaningless. Teams learn to tune out managers who praise everything the same way, which means the praise stops functioning as feedback at all.

Specific recognition works because it proves attention. “The way you restructured the report around the customer’s three questions is why the meeting went well” tells the person their manager actually read the report, understood the choice they made and connected it to an outcome. That sentence takes 10 extra seconds to compose and does three jobs at once: it rewards, it teaches and it signals that careful work gets seen here.

Specificity also forces the manager to actually look. A manager cannot describe what was good about someone’s work without engaging with the work, which is exactly the point. Average managers skim outputs and praise effort. Great managers read closely enough to name craft — the edge case someone anticipated, the stakeholder someone quietly pre-briefed, the ugly-but-correct decision to cut a feature.

The habit matters most for work that succeeds invisibly. Firefighting gets noticed automatically; prevention never does. The engineer whose careful design meant there was no outage, the coordinator whose planning meant the event had no crises — their best work looks like nothing happening. Great managers hunt for that invisible competence and name it in public, because whatever gets recognized gets repeated. A team praised only for heroics will manufacture emergencies to be heroic in. A team praised for prevention will quietly stop having emergencies.

16 / 25

They remove obstacles instead of just tracking them

Credit: Andrea Piacquadio /  Pexels

Average managers ask about blockers in every standup, nod, write them down and move on. Great managers treat a reported blocker as their own to-do item. The question is not “what is blocking you?” but “what is blocking you that I can go kill today?”

The distinction defines what a manager is for. Individual contributors are hired to do the work. Managers are hired, in large part, to clear the path — to handle the cross-team dependency that has been stuck for two weeks, the approval sitting in a vice president’s inbox, the vendor contract that legal has not touched, the colleague in another department who will not respond. These problems are often trivial for a manager to solve and nearly impossible for the individual to solve, because they run on relationships and authority the individual does not have.

Average managers invert this. They track blockers in a spreadsheet while pressing the team to work around them, which converts a management failure into individual overtime. Or they offer sympathy — “yeah, that team is slow” — as if commiseration were a service. The team keeps a private ledger of every blocker the manager acknowledged and never touched, and that ledger is where credibility goes to die.

Great managers close blockers loudly enough that the team sees it. They walk out of standup, message the other manager, escalate the approval, and report back the same day: that one is unblocked. The visible follow-through changes what people report. Teams stop mentioning only safe, minor blockers and start surfacing the real ones — including the awkward category where the blocker is the manager themselves, or the manager’s boss.

There is a diagnostic buried in this habit. A manager should occasionally tally what kinds of obstacles keep recurring. The same approval bottleneck appearing every month is not a blocker; it is a broken process wearing a blocker costume, and fixing the process is the higher-leverage move.

17 / 25

They protect the team’s focus time

Credit: Edmond Dantès /  Pexels

Average managers treat their team’s calendar as infinitely divisible. Great managers treat uninterrupted time as the raw material of the team’s output and defend it accordingly.

Most knowledge work — writing, coding, analysis, design — requires long stretches of unbroken concentration. A schedule shredded into 30-minute gaps between meetings produces days that feel busy and yield nothing, because no gap is long enough to load a hard problem into working memory. The employee ends the week exhausted and behind, and the manager wonders why velocity is down.

Great managers attack this structurally rather than exhorting people to focus. They establish no-meeting blocks — a full day or two half-days a week — and then actually honor them, including against their own impulse to grab time. They batch their own requests instead of pinging reports six times a day. They ask, before every recurring meeting they own, whether it could be a document instead. And they push back on outside claims: when another department tries to pull a team member into a fourth weekly sync, the great manager absorbs that fight so the report does not have to.

They also model the norms they want. A manager who sends messages at 11 p.m. — even with “no rush” attached — trains the team to check messages at 11 p.m. Great managers schedule the send for morning. A manager who answers every message within four minutes teaches the team that instant responsiveness is the real performance metric, whatever the stated values say. Great managers respond on a human cadence and say explicitly that others should too.

The underlying belief is simple: attention is the scarcest resource the team has, and every claim on it should have to justify itself. Average managers spend the team’s attention freely because the cost never appears on any report. Great managers act like it does, because in the output, it always does.

18 / 25

They onboard new hires deliberately

Credit: RDNE Stock project  /  Pexels

Average managers treat onboarding as an IT ticket and a seat assignment. Great managers treat the first month as the highest-leverage month they will ever have with that employee, because it is the one window when habits, relationships and expectations are all still wet cement.

A neglected first week teaches lessons no orientation deck can undo. The new hire who spends three days without access, a clear task or a scheduled conversation learns that this team improvises, that nobody quite expected them and that they should figure things out alone rather than ask. Those inferences harden fast and take months to reverse.

Great managers script the opening. Before day one, the laptop works, the accounts exist and the calendar already holds a first-day one-on-one. The manager has written a 30-60-90 day outline — not a rigid plan, but a clear answer to the question every new hire silently asks: what does doing well look like here in the first three months? There is a real task in week one, small enough to finish and real enough to matter, because early wins convert anxiety into momentum.

They also engineer the relationships. New hires get a named peer to ask small questions, a list of the 10 people they should meet and a manager who books several of those introductions personally. Average managers tell new people to “get to know the team.” Great managers know that unstructured networking advice mostly produces lunch with whoever sat closest.

The deliberate part extends to context. Great managers spend real time on why — why the team exists, why the current priorities are the priorities, why certain past decisions were made. They also invite the reverse flow: a new hire’s first month is the only time they can see the team’s dysfunctions with fresh eyes, so great managers explicitly ask what looks strange. Then they listen, because some of it will be right.

19 / 25

They address underperformance instead of routing around it

Credit: Sora Shimazaki /  Pexels

Average managers route work around a struggling employee. Great managers route the problem through a direct, structured conversation — because rerouting work is not a solution, it is a tax on everyone else.

The routing pattern is easy to fall into. Someone’s work is unreliable, so the manager quietly stops assigning them anything critical. Important tasks flow to the two or three people who never drop things. On the surface, delivery continues. Underneath, the strong performers are absorbing extra load without extra recognition, the struggling employee is confused by their shrinking role, and the manager has converted one person’s performance problem into a whole team’s morale problem. High performers read the situation with perfect clarity: the reward for competence here is more work, and the consequence of incompetence is less.

Great managers do the harder thing. They sit down with the person and name the gap specifically — not “your work needs improvement” but “the last three analyses each had errors that others caught, and here they are.” They ask what is going on, because the honest answer is sometimes a fixable cause: unclear expectations, a skills gap training can close, a personal crisis, a role mismatch. Then they agree on what has to change, by when, with what support — and they write it down.

They also follow through on both branches. If performance recovers, they say so explicitly, because people who have been through a hard conversation need to hear when they are out of the woods. If it does not recover, they act, working with HR toward a role change or an exit, handled with as much dignity as the process allows. Average managers hope the situation resolves itself. It resolves itself in exactly one way: the best people leave first, and the manager is left running the team their avoidance built.

20 / 25

They shield the team from noise without hiding the truth

Credit: Yan Krukau /  Pexels

Great managers act as a filter between their team and the wider organization — passing through what matters, absorbing what does not and never confusing filtering with concealment. Average managers fail in one of two opposite directions.

The first failure is the open pipe. Every rumor, every executive mood swing, every strategy draft that will be reversed in two weeks flows straight to the team. The manager mistakes this for transparency. The team experiences it as anxiety: constant reprioritization, whiplash from provisional decisions treated as final and hours lost to speculation about reorganizations that never happen. Half of what churns above a team never becomes real, and a manager who transmits all of it makes the team pay for every false alarm.

The second failure is the wall. The manager decides the team should “just focus on the work” and shares almost nothing. This feels protective and reads as contempt. Adults notice when they are being managed like children, and information voids never stay empty — they fill with rumor, usually a darker version than the truth. When real change finally lands, it lands as a blindside, and the manager’s credibility goes with it.

Great managers run the filter consciously. Provisional turbulence — the strategy debate still in flux, the budget fight not yet settled — they hold, or share with explicit framing: this is not decided, do not act on it. Real signal — a decision that will affect the team, even an unpleasant one — they deliver early, directly and with context, before the rumor mill does. When they cannot share something, they say that plainly: there are things in motion I cannot discuss yet, and I will tell you the moment I can.

The test of the filter is trust in both directions. Leadership trusts the manager to translate honestly downward. The team trusts that silence means “nothing actionable yet,” not “something is being hidden.” Average managers earn neither form of trust, because a broken filter is visible from both sides.

21 / 25

They let people make recoverable mistakes

Credit: Pavel Danilyuk  /  Pexels

Average managers prevent every mistake they can see coming. Great managers sort mistakes into two piles — recoverable and catastrophic — and deliberately let the first pile happen, because recoverable failure is how judgment gets built.

The preventive instinct is understandable. A manager watching a report head toward a flawed approach can usually see the failure three steps ahead. Intervening feels responsible: it saves time, protects quality and spares the person embarrassment. But a manager who intercepts every error also intercepts every lesson. The report ships cleaner work and learns nothing, because the manager’s judgment did the learning. Two years later the person has two years of experience executing someone else’s foresight, which is not the same as two years of experience.

Great managers hold their tongue on the recoverable pile. The presentation structured the wrong way, the estimate that will prove optimistic, the vendor negotiation opened too softly — these failures cost days, not careers, and the lesson they teach sticks in a way no advice can. The manager’s job shifts from prevention to preparation: making sure the person knows the goal, has the context and understands the stakes, then letting the attempt run.

The sorting is the skill. Catastrophic risks — anything touching customer trust, legal exposure, safety, security or a colleague’s career — get intercepted without apology. Great managers are explicit about the boundary with their teams: here is the zone where you should experiment freely, and here is where you check with me first, every time. That clarity is what makes the freedom usable. People take smart risks when they know exactly which risks are theirs to take.

The final piece is how failure gets handled when it arrives. A blame-heavy postmortem converts one recoverable mistake into a team-wide lesson in self-protection. Great managers ask what happened, what the person learned and what changes — then move on visibly, so everyone watching learns that intelligent failure here is survivable.

22 / 25

They handle departures and exits with care

Credit:  Vitaly Gariev /  Pexels

How a manager behaves when someone leaves — voluntarily or not — tells the remaining team more about that manager than a year of all-hands speeches. Great managers know they are performing for the people staying, and they act accordingly.

Start with resignations. Average managers take them personally. Some turn cold, cutting the departing employee out of meetings and conversation for their final two weeks. Others get extractive, treating the notice period as a last chance to squeeze out work. Great managers respond with grace: congratulations on the new role, a genuine question about what drove the decision, a clean transition plan and a public thank-you that names the person’s actual contributions. They also conduct a real exit conversation — not the HR form, but an honest ask: what should I have done differently? Departing employees are the only people with no incentive to flatter, which makes them the best feedback source a manager ever gets.

Involuntary exits demand even more care. When a termination or layoff happens, the departing person’s dignity is the first obligation — no perp walks, no vague all-team emails that invite speculation, no character assassination after the fact. Great managers say what they can say honestly, protect what should stay private and never bad-mouth the person who left, because everyone listening silently substitutes themselves into the story. A manager who trashes former employees has told the current team exactly what awaits them.

Great managers also stay in touch. Former team members become hiring pipelines, customer contacts, references and — often — boomerang employees who return more skilled than they left. Average managers treat a departure as a betrayal and a dead end. Great managers treat it as a graduation, and their alumni behave accordingly, sending candidates back and speaking well of the team in a labor market where reputation compounds quietly and permanently.

23 / 25

They take real vacations and model sustainable pace

Credit: Chen Mizrach / Unsplash

Average managers talk about work-life balance. Great managers demonstrate it — visibly, personally and in ways the team can safely copy. On this subject, nothing a manager says outweighs what a manager does.

The mechanism is simple. Teams calibrate acceptable behavior by watching the boss, not by reading the handbook. A manager who answers messages from the beach has amended the vacation policy for everyone, no matter what the policy says. A manager who wears exhaustion as a badge — back-to-back days, visible all-nighters, lunch as a weakness — has set the real performance bar, and ambitious people will match it until they burn out or leave. The stated culture is whatever is written down. The actual culture is whatever the manager survives doing.

Great managers therefore treat their own boundaries as a management tool. They take full vacations and go genuinely dark, with a named person covering decisions in their absence — which doubles as a development opportunity and a test of how well the team runs without them. A team that functions during the manager’s two-week absence is evidence of good management, not a threat to it. Average managers quietly fear that discovery, which is one reason they never fully leave.

The modeling extends to ordinary weeks. Great managers are open about leaving for a child’s recital or a doctor’s appointment, because naming it grants permission. They watch for the report who has not taken a day off in eight months and push them out the door, treating unused leave as a warning sign rather than dedication. When a genuine crunch demands unsustainable hours, they name it as an exception, put an end date on it and honor the recovery afterward.

The business logic is unsentimental. Chronically depleted teams make more errors, take fewer creative risks and quit more often. A manager who protects the team’s recovery is protecting the asset. Average managers spend the asset and call it commitment.

24 / 25

They hire slowly and are honest in the process

Credit: Radission US / Unsplash

Average managers hire to fill a gap, fast, with the best candidate in this week’s pipeline. Great managers treat every hire as the highest-stakes decision they make — one that will outlast most projects and reshape the team’s culture either way.

The discipline starts before any interview. Great managers write down what the role actually requires — the three or four capabilities that determine success — and design interviews that test those specifically, rather than running the same generic conversation for every role. They involve the team in the process, both because colleagues spot things managers miss and because people commit harder to the success of someone they helped choose.

They also hold the bar under pressure. The strongest test of a manager’s hiring standards is month four of an open role, when the workload hurts and a mediocre candidate is available. Average managers rationalize: we can coach the gaps, warm body beats no body. Great managers have learned the true price of that trade. A wrong hire costs the ramp-up, the eventual painful exit, the second search — and, in between, months of the team quietly absorbing substandard work. An empty seat is a known, bounded cost. A bad hire is an unbounded one.

Honesty is the other half. Average managers sell candidates a polished version of the job — the interesting parts of the work, the best-case trajectory — and then act surprised when the new hire sours in month three upon meeting reality. Great managers describe the job as it is: this role is 40% maintenance work, this stakeholder is difficult, the promotion path from here is real but slow. Some candidates walk away, which is the system working. The ones who accept arrive with accurate expectations, and accurate expectations are the cheapest retention program that exists.

They also hire people better than themselves at the craft, without flinching. Average managers hire people they will not be threatened by. It shows in the org chart within two years.

25 / 25

They ask for feedback on themselves and act on it

Credit: Tima Miroshnichenko /  Pexels

Average managers give feedback. Great managers also collect it — about themselves, on purpose, and then do the one thing that makes the collection worthwhile: visibly change something.

Asking is harder than it sounds, because the power gap distorts everything. “Any feedback for me?” tossed at the end of a one-on-one reliably produces “no, all good,” and average managers accept that answer as evidence they are doing fine. Great managers know silence is a measure of safety, not satisfaction, so they engineer better questions. They ask narrow and specific: what is one thing I did in the planning process that made your work harder? What should I stop doing in team meetings? What do I not want to hear right now? Specific questions give people a socially safe container for honesty in a way that open-ended ones never do.

Then comes the part that determines whether feedback ever flows again: the reaction. A manager who argues with feedback, explains it away or — worst — becomes cooler toward the person who offered it has ended the experiment permanently, and the news travels to the whole team within a day. Great managers respond the way they wish people responded to their own feedback: thank you, tell me more, give me an example. They can disagree later, after understanding. Defensiveness in the moment is the one unaffordable luxury.

The visible follow-through closes the loop. Great managers name what they heard and what they are changing: several of you said my late-day requests wreck your planning, so I am batching them into the morning. They report back on the change a month later. Nothing teaches a team that honesty is safe — and useful — like watching their words alter their manager’s behavior. Average managers ask for feedback annually because a survey requires it. Great managers ask continually because their own performance is the highest-leverage thing they can improve.

Source: qz.com