20 principles of good management that most managers don't practice

Most managers are promoted because they were good at something else. They hit sales targets, wrote clean code, closed deals, or ran tight operations. Then someone decided that competence in a domain meant readiness to lead the people who work in it. That assumption is responsible for a great deal of workplace misery.

The principles of good management are not obscure. They have been written about, taught in business schools, and repeated in leadership seminars for decades. The problem is not that managers haven't heard them. It's that hearing something and consistently doing it under pressure — when you're stretched thin, when a deadline is looming, when a difficult conversation needs to happen — are entirely different things. The distance between knowing and doing is where management fails.

What distinguishes genuinely effective managers is not a special talent or an innate gift for leadership. It is a set of habits and commitments that they practice with enough discipline to hold up even when circumstances make it inconvenient. They give feedback before it becomes overdue. They ask questions instead of issuing commands. They protect their people's time, take accountability seriously, and resist the urge to manage through control rather than trust.

None of this is complicated in theory. A manager who has been in the workforce for more than a few years could almost certainly recite a version of these principles back to you. But ask the people who report to that manager how consistently those principles show up in daily practice, and the answers are often very different from what the manager believes.

This list is not about the most exotic or counterintuitive ideas in management. It is about the foundational ones — the principles that have the most impact on whether people do their best work, stay engaged, and trust the person they report to. These are the ones that most managers, despite knowing better, tend to skip when things get busy or hard. They are worth revisiting not because they are new, but because the cost of not practicing them is higher than most managers want to admit.

Credit: Los Muertos Crew  / Pexels 

Feedback that arrives once a year in a formal review setting is almost useless for development. By the time a manager raises a pattern they've observed for months, the employee has already formed habits, made decisions, and in some cases, internalized a self-image that the feedback is now trying to dislodge. The longer feedback waits, the more it lands as judgment rather than guidance.

The most useful feedback is given close to the moment it becomes relevant. Not during the action — that's rarely the right time — but soon enough after that the situation is still fresh and the employee can connect the observation to a specific behavior they remember. This kind of feedback is easier to absorb because it feels like input for improvement rather than a verdict on character.

Managers often delay feedback for understandable reasons. They don't want to seem nitpicky. They hope the problem will resolve itself. They're not sure how the employee will react. They want to gather more evidence before saying anything. All of these hesitations have costs. A problem that might take five minutes to address in the moment can metastasize into something that requires a formal performance process six months later.

There's also an asymmetry in how feedback affects trust. Positive feedback delivered promptly reinforces good work and builds confidence. Positive feedback delivered months later in an annual review feels like a formality. Constructive feedback delivered promptly signals that the manager is paying attention and invested in the employee's growth. The same feedback delivered in a review — especially if it's unexpected — signals neglect.

The other piece managers tend to miss is the importance of positive feedback as its own discipline. Pointing out what's working is not a soft courtesy before getting to the real feedback. It is substantive information that tells people which behaviors to continue and which instincts to trust. Managers who only give feedback when something is wrong train their people to associate the manager's attention with problems. That is its own kind of dysfunction.

Developing the habit of prompt feedback requires managers to slow down enough to actually observe the people they manage, reflect on what they're seeing, and say something. That's a higher cognitive load than most managers realize they've been avoiding.

Credit:  RDNE Stock project / Pexels 

The instinct to answer is strong in managers, especially managers who were promoted from expert roles. They got where they are because they knew things. Their knowledge was valued. The move into management often doesn't immediately disrupt that identity — so they keep applying it, showing up to conversations ready to offer solutions and correct thinking.

The problem is that a manager who always has the answer trains their team not to think for themselves. When the manager consistently jumps to conclusions, the team learns to present problems rather than bring analyses. They bring raw information and wait for direction rather than working through complexity and arriving with recommendations. Over time, this produces a team whose effectiveness is capped by the manager's own bandwidth and perspective.

Asking questions does several things at once. It surfaces information the manager doesn't have — the person closest to a problem often sees things the manager cannot. It forces the person being asked to think more rigorously, which develops capability. It signals that the manager values the employee's judgment, which builds ownership and motivation. And it prevents the manager from steering based on incomplete understanding.

This doesn't mean managers should withhold genuine expertise or refuse to share what they know. When someone is genuinely stuck and doesn't have the knowledge to work through something, providing the answer is the right call. The discipline is in noticing when the default to answering is driven by the manager's own need to be useful — or to be in control — rather than by what the employee actually needs.

There's a specific version of this that comes up in one-on-ones. Many managers run their one-on-ones as status updates: they ask what's happening, get a report, and move on. A better use of that time involves asking what's blocking progress, where the employee is frustrated, what they're uncertain about, and what would make their work easier. The answers to those questions produce different and more useful information than a status report.

Learning to wait out silence is part of this. Managers who ask a question and then rush to fill the quiet before the person has answered are really just setting up their own next statement. Letting a question actually land — giving the person a moment to think — is a discipline in itself.

Credit: Campaign Creators / Unsplash

Decision-making is one of the most misunderstood aspects of management. Many managers conflate being decisive with being involved in every decision. They keep final call authority on things that don't require it, create bottlenecks in their own teams, and slow down work that could move faster with less oversight.

The principle is straightforward: push decisions down to the level where the best information lives. The person closest to the problem almost always has more relevant context than the manager. Requiring that context to travel up the chain so the manager can make the call, and then travel back down as an instruction, is a slow and lossy process. It also signals a lack of trust in the people doing the work.

The managers who reserve decision authority tend to frame this as accountability — they're responsible for outcomes, so they need to control inputs. But accountability and control are not the same thing. A manager can be fully accountable for outcomes while distributing the decisions that produce those outcomes across the team. What that requires is clear expectations, good information flow, and the confidence to let people make calls that might not be exactly the call the manager would have made.

When managers do make decisions — especially ones that affect how people work or what they prioritize — explaining the reasoning matters more than most managers appreciate. A decision communicated without reasoning leaves the team to guess at the logic. They may comply with the outcome while disagreeing with it internally, or they may misapply the decision in adjacent situations because they don't understand what principle it reflects.

Explaining reasoning also teaches. When people understand why a decision was made, they develop better judgment about similar situations in the future. A team that understands the decision-making logic of their manager can operate more independently, because they can ask themselves what the manager would weigh and arrive at reasonable answers on their own.

This takes more time in the short run. Writing a brief explanation of a decision or taking two minutes to walk through the reasoning in a meeting is slower than just issuing a directive. The payoff comes over months, as the team develops judgment that reduces how many decisions need to escalate.

Credit:  Mikhail Nilov  / Pexels 

A large proportion of the frustration that exists between managers and employees comes from expectations that the manager assumed were obvious and the employee assumed didn't exist. Both people can feel wronged by the outcome of a situation they were never in full agreement about to begin with.

Managers often set expectations through implication. They point to a successful example of work and say "like this." They describe a project and assume the person will infer the quality bar. They mention a deadline in passing and assume the employee has registered it as firm. Then when the output doesn't match what they had in mind, the feedback feels unfair to the employee, because no explicit target was set.

Explicit expectations are harder to set than they appear. They require the manager to do the work of thinking through what they actually want — which level of polish, which format, which decisions the employee should make independently and which to escalate, what done looks like. That thinking is often skipped because it feels like overhead. But it is the work of management. Defining the target so clearly that a person can aim at it without guessing is a core managerial function.

This is especially true for new employees or employees taking on new kinds of work. When someone is in a context they don't have full mental models for yet, they rely heavily on explicit framing. Assuming they can infer expectations from context is asking them to read a room they just walked into.

The other side of this is that explicit expectations create shared accountability. When the expectation is clear, it's also clear when it has or hasn't been met. That clarity benefits everyone. The employee knows when they're on track. The manager has a concrete reference point for feedback. And when something falls short, the conversation is about the gap between an agreed-upon expectation and the actual outcome — not about a manager's retroactive disappointment.

Setting expectations explicitly doesn't mean micromanaging. A manager can define a clear destination and leave significant latitude in how to get there. The latitude is what enables autonomy. The clear destination is what makes the autonomy functional.

Credit:  Felicity Tai  / Pexels 

A manager's decisions about meetings, processes, and communication norms have a direct and often underestimated effect on whether their team can do deep work. A team that spends its hours in status meetings, responding to non-urgent messages in real time, and context-switching between competing priorities is a team that is busy but not productive.

The calendar is one of the most consequential management tools, and it is one that most managers treat carelessly. They schedule one-on-ones at irregular times, accept meetings that don't require their presence but include them anyway, and allow their team's schedules to fragment in ways that eliminate sustained focus time. They then wonder why output is slow or quality is inconsistent.

Time protection requires managers to make active choices, not passive ones. It means auditing recurring meetings and canceling the ones that no longer serve a clear purpose. It means declining meetings where the team's presence adds nothing. It means protecting blocks of time for focused work — and communicating clearly that those blocks exist and should be respected.

Communication norms are another lever. Teams where the expectation is immediate response to every message operate in a state of constant interruption. That expectation is usually implicit — driven by observed behavior rather than stated policy. Managers who respond to every message within minutes, send messages at all hours, and appear to be always available create an implicit standard that their team feels pressure to match. Changing that norm requires the manager to model it, not just announce it.

This is also about prioritization. When managers add work to a team's plate without removing anything, they are effectively deciding that the new thing is more important than everything already on the list — without making that trade-off explicit. Helping the team triage what deserves attention and what can wait is a management function. A team that tries to do everything tends to do everything poorly.

Credit: Canva Images

When a team fails to meet an expectation, misses a deadline, or produces flawed work, the manager's first public move tells the team a great deal about what kind of leader they're working for. A manager who immediately looks for who on the team dropped the ball — before examining whether the conditions they created contributed to the failure — loses trust fast.

Taking accountability doesn't mean that individuals on the team are never responsible for their own work. They are. But the manager is responsible for the conditions: the clarity of the expectation, the adequacy of the support, the appropriateness of the timeline, the health of the team dynamic. If any of those were off, the manager owns that part. Separating the question of individual accountability from the question of systemic accountability requires honesty that many managers resist.

The managers who take accountability clearly and quickly — who say "I should have caught this earlier" or "I didn't give this team enough context" when those things are true — build something durable with their teams. People are far more willing to own their own mistakes in an environment where the manager models it. Accountability becomes a norm rather than a punishment.

The opposite dynamic is also self-reinforcing. A manager who consistently deflects or assigns blame creates a team culture of self-protection. People learn that the goal in a failure postmortem is to not be the person who gets blamed, so they document defensively, communicate ambiguously, and avoid taking risks that might not pay off. The team's capacity for honest reflection disappears.

There's also a practical dimension. A manager who blames external factors or team members when things go wrong signals to their own leadership that they're not in control of their team. The manager who says "here's what happened, here's my role in it, here's what I'm changing" signals something very different — competence, self-awareness, and the kind of judgment that earns trust upward as well as downward.

Credit: Jack Sparrow / Pexels 

Autonomy is a frequently stated management value that is frequently not delivered. The pattern is familiar: a manager tells an employee they're empowered to make decisions, and then second-guesses, overrides, or revises those decisions whenever they differ from what the manager would have done. The employee learns quickly that the autonomy is conditional — it exists only when they arrive at the same conclusion the manager would have reached.

That is not autonomy. It is the performance of autonomy, and it tends to be more corrosive than straightforward oversight, because it carries a false promise. Employees who are told they have authority and then discover it's illusory experience a specific kind of frustration — a sense of being set up to fail or being managed through a fiction.

Real autonomy requires managers to accept that other people will make decisions differently than they would, and that different doesn't mean wrong. It requires being explicit upfront about which decisions the employee truly owns, which require consultation, and which require approval. That clarity is what makes autonomy operational rather than theoretical.

It also requires resisting the urge to offer opinions on decisions that fall within the employee's remit. A manager can share perspective when asked, but unsolicited opinions on decisions the employee was supposed to own function as direction, not guidance. The employee who regularly hears "that's not how I would have done it" from their manager learns to route decisions upward for pre-approval, because the cost of diverging is too high.

The practical benefit of genuine autonomy is significant. People who are trusted to make real decisions develop faster, take ownership more deeply, and bring more creative thinking to their work. They are also more likely to stay — not because the work itself is different, but because the relationship to it is. Work done under genuine autonomy feels different from work done under monitored delegation.

Credit: Edmond Dantès  / Pexels 

Active listening is one of the most cited management skills and one of the least consistently practiced. The problem is that it requires managers to do something cognitively demanding: stay genuinely open to being changed by what they hear, rather than processing the incoming information through a filter of what they've already decided.

Most of the listening that happens in management settings is evaluative listening. The manager has a frame, and they're classifying what the employee says against it — agreeing, disagreeing, looking for evidence for or against a position they already hold. The conversation looks like listening. The other person is talking, the manager is making eye contact and nodding. But nothing is being genuinely absorbed.

The tell is what happens after. If the manager's response was essentially predetermined before the employee finished speaking, if it doesn't reflect any of the specific things the employee actually said, then the listening was a formality. The employee senses this, often quickly, and adjusts their behavior accordingly — they stop bringing complex problems, because there's no point. The manager already knows what they think.

Genuine listening requires the manager to tolerate uncertainty, to sit with information that doesn't fit their current view, and to be willing to say "I need to think about that" rather than arriving at a conclusion on the spot. It requires asking follow-up questions that are designed to understand rather than to challenge. It requires remembering that the manager's perspective is always incomplete — they are not in the work the way the employee is.

This becomes especially critical when employees are raising concerns or dissenting views. A manager who physically listens to disagreement but cognitively dismisses it before it's finished is signaling clearly that the only acceptable inputs are those that confirm existing thinking. Over time, that manager becomes effectively isolated from the team's real perspective — hearing what people think they want to hear, not what's actually true.

Credit:  Christina @ wocintechchat.com M / Unsplash

Motivation is not uniform across a team, and managing as if it were is one of the most consistent errors that otherwise competent managers make. One person is driven by the opportunity to develop new skills. Another is motivated primarily by recognition. A third cares most about the impact of their work on the end user. A fourth is motivated by autonomy and will disengage if they feel closely supervised. Treating all four with the same management approach will get mediocre performance from at least three of them.

Understanding individual motivation requires actually asking — directly, not through inference or assumption. Many managers assume they know what motivates people based on surface signals: the high performer who works long hours, they assume, is motivated by ambition. The person who asks a lot of process questions, they assume, is risk-averse and detail-oriented. These assumptions are often wrong, and acting on them produces management that misses the person entirely.

The questions that surface motivation are not complicated. What kind of work do you find energizing? What do you want to be doing in two years? Is there a kind of project you'd like to take on that you haven't had a chance to try? These questions, asked sincerely and followed up on over time, produce a picture of what a person actually values — not what the manager projected onto them.

Acting on what you learn is the other half. If a person says they want to develop a particular skill and the manager continues assigning them only work they already know how to do, the stated interest in their development becomes hollow. If someone says recognition matters to them and the manager consistently gives feedback privately while staying silent in group settings, the disconnect is noticed and interpreted as disregard.

This is not about coddling or customizing every aspect of someone's work to their preferences. It's about knowing enough about what drives each person to make deliberate decisions about how to deploy, develop, and engage them. That knowledge is what separates management that gets good work from management that gets excellent work from people who stay.

Credit: Vitaly Gariev / Pexels 

A significant amount of management failure consists of deferred conversations. The manager sees a performance problem, a behavioral pattern, an interpersonal dynamic, or a competency gap — and doesn't say anything. They tell themselves the person might figure it out. They tell themselves they'll bring it up after the busy period. They tell themselves they'll gather more evidence. And weeks or months pass.

By the time the conversation finally happens, a great deal of damage has accumulated. The employee has continued in a pattern they weren't told was a problem. Other people on the team have been affected. The manager's stored-up frustration has made the conversation harder to have neutrally. And the employee, on hearing the feedback, often responds with some version of "why didn't you tell me sooner?" — a completely reasonable question.

Avoiding difficult conversations is, in most cases, a choice to prioritize the manager's short-term comfort over the employee's long-term development. The manager who dreads the awkwardness of a hard feedback conversation, and so puts it off, is essentially protecting themselves from discomfort while allowing a problem to worsen. That is not a neutral act.

The conversations that feel most difficult to initiate are often the ones that matter most. The employee who is close to missing a performance bar needs to hear that before it becomes a formal process — not after. The two team members whose working relationship is creating friction need that named before it metastasizes into a team culture problem. The high performer who is considering leaving because they feel undervalued needs to be shown that the manager sees them before they've made up their mind.

Difficult conversations become easier with practice — not in the sense that they become comfortable, but in the sense that the manager develops skill and confidence in navigating them. The manager who has the conversation once realizes the feared outcome rarely materializes. The relationship does not end. The person does not fall apart. In most cases, they are relieved someone finally said something.

Credit: Timur Weber / Pexels 

When something goes wrong, managers face a choice in how they interpret the situation: is this a problem with a process, a structure, a mismatch of skills and role, or a deficit in this particular person? That interpretive choice shapes everything that follows — what gets addressed, how, and with what expectation of change.

Many managers default to person-centric interpretations. Something went wrong, and someone failed to prevent it. The solution, in this framing, is to hold that person accountable, give them feedback, and expect better performance. This framing isn't always wrong — individual behavior and judgment matter. But it misses the significant proportion of failures that are produced by systems rather than individuals.

Process problems recur across people. If one employee keeps making a certain type of error, it might be a skill gap. If several employees make the same type of error, it is almost certainly a system problem. The meeting that consistently runs over time is probably not full of inconsiderate people; the format is likely structured in a way that invites overrun. The project that always hits delivery problems probably has a planning or scoping issue at the structural level.

Making this distinction accurately requires a specific kind of intellectual honesty that is uncomfortable for managers, because a system problem is something the manager is responsible for. If the process is broken, the manager's job is to fix it. Diagnosing it as a personnel problem is easier — it assigns the work of change to someone else. But it doesn't actually fix anything.

At the individual level, the distinction matters in how conversations are framed. A person who hears "you keep doing this wrong" experiences that differently from a person who hears "this part of the process isn't set up well for what you need to do — let's work on that together." Both might point at the same behavior, but the second one doesn't attach the problem to the person's identity, which makes it easier to address without defensiveness.

Credit:  Vitaly Gariev / Unsplash

Development happens in most organizations by accident. Someone gets a stretch assignment because they happened to be available when a project opened up. Someone learns a new skill because they were curious and found a resource on their own. Someone gets feedback that shifts their trajectory because a manager had an unusually candid day. None of this is planned.

Deliberate development requires the manager to think explicitly about what each person on their team needs to grow, where the gaps are between their current capability and where they're headed, and what specific experiences or feedback would close those gaps. That thinking needs to happen before the staffing conversation, not during it.

The most effective development happens through the work itself — through assignments calibrated slightly beyond current capability, that require the person to learn by doing. But that calibration requires the manager to actually understand where the person is. Giving someone work that's well within their comfort zone doesn't develop them. Giving them work so far beyond their current capability that they can't succeed doesn't develop them either. The zone where growth happens is specific, and finding it requires the manager to pay attention.

Sponsorship is a related responsibility that many managers underperform. Advocating for their people — in promotion conversations, in project staffing, in visibility opportunities — is part of what managers owe the people who report to them. A person can do good work indefinitely without anyone above the manager level knowing about it, if the manager doesn't take the step of making it visible. That invisibility carries real career costs.

Development conversations — what someone wants to get better at, what opportunities they're looking for, what they feel underprepared for — should happen regularly and be followed up on. A manager who has a development conversation annually in the context of a review and then never revisits it has not made development a practice. They have made it a paperwork exercise.

Credit: Amy Hirschi  / Unsplash

The times when a manager's character is most visible are not the ordinary days. They are the moments when a deadline is missed, when a project is failing publicly, when the manager is under pressure from their own leadership, when a team member makes a consequential mistake. How a manager behaves in those moments tells the team far more about who they are than any number of ordinary interactions.

Managers who are warm and supportive in low-stakes situations but sharp, blame-oriented, or distant when things go wrong create a specific dynamic: their team learns to manage the manager's emotional state rather than focusing on the work. They withhold bad news because they've learned bad news changes how the manager treats them. They avoid surfacing problems early because problems generate a version of the manager they'd rather not deal with.

Consistency does not mean the same emotional register in every situation. It means predictability in values: that the manager will remain fair when under pressure, that they won't sacrifice a team member to deflect criticism from above, that their standards don't shift based on their mood or the audience. Behavioral consistency of this kind is what people mean when they say a manager "has their back."

For managers whose natural response to pressure is to escalate emotionally — to become more demanding, more critical, more reactive — this requires active work. Not suppression, but genuine management of behavior. The work of staying consistent under pressure is not about being unaffected by difficult situations. It's about recognizing that how the manager reacts will have effects on the team that outlast the immediate situation.

Trust, once broken by inconsistency, is slow to rebuild. A team member who saw their manager respond to a difficult moment with blame or volatility carries that experience forward. It shapes how much they share, how much risk they take, and how much goodwill they extend in the next difficult moment.

Credit: The Jopwell Collection / Unsplash

In many organizations, managers are rewarded primarily for their own visibility and profile with senior leadership. They get credit for their team's accomplishments, present the team's work upward, and are known by the work their team produces. The less functional version of this dynamic is one in which the manager's cultivation of their own reputation happens at the expense of making their team members visible.

A manager who takes credit for their team's work — through omission rather than outright appropriation — damages the people who report to them in concrete ways. Promotions, stretch opportunities, and sponsorship decisions depend on people above the manager level having a clear picture of who did what. If the team's output is attributed to the manager in every upward conversation, the individuals on that team become invisible to the people making those decisions.

Genuine advocacy means making the team's work and the individuals' contributions visible in ways that don't depend on the manager's presence. It means saying, in leadership conversations, "that came from someone on my team — her name is X $TWTR, and here's what she figured out." It means putting team members in the room for presentations where the manager isn't strictly needed but visibility matters. It means actively preparing people for promotion rather than waiting for a committee to notice them.

This requires managers to feel genuinely secure in their own standing — secure enough that the team's success doesn't feel like it diminishes them. The manager who feels threatened by a high-performing team member is a common type, and it produces subtle but real harm. The strong team member is given less visible work, kept out of high-stakes meetings, never introduced to senior people. The manager's behavior is protective, not promotional.

The inverse is also worth naming: teams whose members know that their manager will advocate for them, give them credit publicly, and create visibility for their work are teams that tend to be exceptionally loyal. The knowledge that your manager wants you to succeed — not just for what it does for the team's performance but for what it does for your career — changes the nature of the working relationship entirely.

Credit: Thirdman / Pexels 

One of the more reliable symptoms of a poorly managed team is that the manager doesn't actually know what the team thinks. They believe they have a good read on morale and concerns, but if pressed, most of what they can report is what people said in formal settings — what came out in one-on-ones where the power dynamic was fully present, what was shared in performance reviews where people had reasons to manage their message.

Honest upward feedback — the kind where a team member tells their manager something the manager doesn't want to hear — requires conditions that most managers inadvertently make difficult. It requires the team member to believe that saying something difficult won't result in visible or subtle retaliation. It requires them to believe the manager will actually sit with the input rather than dismiss it or reverse-engineer a response to it. It requires them to have seen, at least once, that honesty led somewhere good rather than somewhere bad.

Managers create those conditions slowly, through sustained behavior. One way is by explicitly inviting dissent and then visibly rewarding it when it happens. When a team member raises a concern or pushes back on a plan, and the manager responds with genuine engagement — asks questions, takes time to reflect, comes back with a revised view — that interaction becomes a data point the rest of the team observes. The norm shifts.

Another is by sharing their own uncertainties and mistakes openly. A manager who presents themselves as never wrong or never uncertain signals to their team that uncertainty and mistakes are not safe to surface. Modeling the opposite — acknowledging limits, naming things they got wrong, asking for help — creates room for others to do the same.

Anonymous feedback channels have a role, but they're not a substitute for a culture where honesty is safe enough to be direct. A manager who relies entirely on anonymous surveys to find out what the team thinks has usually already lost the conditions that make direct honesty possible.

Credit:  Mina Rad / Unsplash

In any organization, some kinds of work are inherently more visible than others. Presenting in a large meeting is visible. Closing a client is visible. Publishing a report or landing a public win is visible. Writing the documentation that makes a system usable, resolving the conflict that was quietly making a team dysfunctional, mentoring a newer team member through a difficult learning curve — these things are often invisible, at least to people outside the immediate situation.

Managers who reward primarily visible work, whether consciously or not, create incentives that distort how people spend their time. Team members learn to optimize for recognition over impact. They take on the project that puts them in front of leadership over the one that would genuinely move the work forward. They present work at meetings rather than doing it. They invest in producing outputs that look good over outputs that serve the actual purpose.

The manager's job, in part, is to see past the visibility proxy and evaluate contribution on substance. That requires actually knowing what's happening in the work — not just what's presented. It requires having enough context to recognize when someone's quiet work was load-bearing, when the visible success was built on a foundation someone else laid.

This is particularly consequential in performance evaluations and promotion decisions. A manager who evaluates primarily based on what they've personally observed — which tends to be the visible work — systematically undervalues people who do important things that don't naturally surface. Over time, this shapes who gets promoted and who stays flat, regardless of actual contribution.

Creating visibility for under-the-radar work is part of managing it fairly. Naming it in team settings, including it in performance conversations, describing it to senior leaders — these acts close the gap between contribution and recognition. They also communicate to the team that the manager is actually paying attention, not just reacting to what appears in front of them.

Credit:   Lyubomyr Reverchuk / Unsplash

Every job has constraints that are genuinely non-negotiable — regulatory requirements, safety standards, ethical lines, commitments to other parts of the organization. And every job has a much larger set of preferences, habits, and defaults that are labeled non-negotiable but are actually just the way the manager has always done things.

Managers who treat preferences as requirements create unnecessary friction. When a team member asks why something has to be done a certain way and the honest answer is "because that's how I prefer it," but the manager says "because that's how it's done," the team member learns to stop asking. They also learn that the stated reason for policies can be disconnected from the real reason, which erodes trust in the manager's explanations more broadly.

Being genuinely clear about what is non-negotiable — and letting everything else be discussable — gives the team more latitude and the manager more credibility. When the manager does say something is non-negotiable, it lands differently if it's rare. If everything is non-negotiable, nothing is.

This requires the manager to examine their own defaults with some rigor. Is this a meeting that needs to happen at this time, or is this just when it's always been scheduled? Is this the format the report needs to be in, or is this the format the manager is used to? Is the process this way for a good reason, or did it calcify around a constraint that no longer exists? Asking these questions — and being honest about the answers — tends to produce a leaner set of actual requirements and a more flexible working environment.

The practical benefit for team members is significant. People who understand which constraints are real and which are preferences can exercise judgment about the others. That's a form of autonomy that costs the manager nothing and gives the team a great deal.

Credit:  Vitaly Gariev / Unsplash

A management approach that works for someone in their first professional role is poorly matched to someone with 10 years of experience. A management approach tailored to someone who is new to a specific type of work will be suffocating applied to a domain expert. The failure to adapt management style to the actual experience level of the person being managed is one of the most common — and most avoidable — sources of friction.

For someone new to a role or an organization, more structure is genuinely useful. They need clear expectations, frequent check-ins, direct feedback, and explicit context that would be unnecessary for someone who has been doing similar work for years. Providing that structure isn't micromanagement — it's appropriate scaffolding for someone who doesn't yet have the mental models to operate without it.

For someone who is competent in their domain, the same level of structure is infantilizing. They have the judgment to make decisions, manage their own work, and identify problems without being guided through every step. A manager who applies the same hands-on approach to an experienced person as to a newcomer communicates, implicitly, that they don't trust the person's capability. That communication tends to be accurate in its effect, even if it wasn't the intent.

The adjustment isn't just about frequency of check-ins. It's about the nature of the conversation. With a newcomer, the conversation is often instructional. With an experienced person, it should be more collegial — the manager is thinking alongside them, offering perspective rather than direction. The shift in tone matters as much as the shift in frequency.

The mistake many managers make is defaulting to the management style that feels most comfortable to them, regardless of who they're managing. A manager who is naturally directive applies that style universally. A manager who is naturally hands-off does the same. Effective management requires noticing where someone actually is — their current level of confidence, competence, and context — and calibrating to that.

Credit: Rebrand Cities  / Pexels 

The fastest way to destroy a standard on a team is for the manager to exempt themselves from it. A manager who requires punctuality and regularly runs late to their own meetings has not set a standard — they have set a hierarchy. The rule applies to everyone except the person with authority to enforce it.

Team members are finely attuned to this kind of inconsistency. They notice when the manager's behavior diverges from the stated norms. They may not say anything — especially if calling it out feels risky — but they register it, and it shapes how seriously they take the norms themselves. Standards that are visibly optional for management tend to become de facto optional for everyone, over time.

This applies across the range of professional behaviors: communication style, preparation for meetings, quality of work, treatment of colleagues, adherence to process. If the manager wants the team to write clear documentation, the manager's own documentation should be clear. If the manager wants the team to give candid feedback, the manager needs to model giving and receiving it. If the manager expects a certain level of follow-through, they need to demonstrate it.

The positive version of this principle is a significant management asset. A manager who consistently operates at the standard they expect — or above it — builds legitimacy that no amount of stated authority can manufacture. When that manager sets expectations, the team understands that the standard is real because they have seen the manager hold themselves to it. That makes the expectation easier to receive and more credible to follow.

There's also a developmental dimension. Managers who model the skills and habits they want to see in their teams are actively teaching, not just evaluating. Watching someone navigate a difficult conversation well, handle uncertainty transparently, or do careful analytical work is an education that no formal training can entirely replicate. The manager who operates with excellence in view of the team creates a curriculum by example.

Credit: Alena Darmel  / Pexels 

A manager's job is not only to direct production. It is also to build a team capable of producing well over time — including when the manager is not present. That second objective gets systematically deprioritized in most management contexts, because output is measured and team health is harder to quantify.

A team that produces good results through constant manager intervention is a fragile system. It depends on the manager's availability, attention, and judgment in ways that make it vulnerable. When the manager is out, things slow down or fall apart. When the manager leaves the organization, the team loses its functioning center. The output was real, but it wasn't the product of a capable team — it was the product of a capable manager with a group of people in support roles.

Building the team means attending to the quality of relationships within it, not just between each member and the manager. It means creating conditions where people communicate directly with each other, share context across functions, and solve problems collectively rather than routing everything through the manager. It means being attentive to team dynamics — the interpersonal tensions, the collaboration patterns, the informal hierarchies — and addressing them when they become obstacles.

It also means thinking about the team's collective capability over time. Which skills are missing? Where is the team fragile — where does one person leaving create a major gap? What's the plan for that person's development, and what's the contingency if they go? Managers who think about these questions are building something durable. Managers who focus entirely on the current project are operating in a shorter time horizon than their actual responsibility requires.

The return on investment for team-building is slow and therefore easy to skip. It shows up in resilience, in the team's ability to navigate situations the manager didn't anticipate, in the quality of what gets produced when no one is watching. Those returns are real, even when they're hard to see in any individual week.