How to Tell If You Are a Micromanager: A Self Diagnosis Guide for Leaders

Managers who believe they are demonstrating care through constant involvement often create the opposite effect on their teams. When leaders review every decision, attend every meeting, and touch every deliverable, employees interpret that behavior as distrust rather than support. The result is disengagement, reduced initiative, and a team that has quietly stopped trying.

The Manager in the Mirror: How to Know If You Are the Problem

There is a particular kind of manager who works harder than anyone else on the team, arriving before the others and leaving after them, their calendar packed wall to wall, their inbox never quiet, touching every deliverable before it leaves the building because they genuinely believe that is what good leadership looks like. Their own boss admires their dedication. Their team has quietly stopped trying.

This post is for that manager. More specifically, it is for the version of that manager who does not yet know they are that manager.

Research from executive coaches working with leaders at organisations ranging from midsize firms to Fortune 500 companies [1] has produced a consistent finding: when senior leaders are asked whether they think they are micromanagers, the answer is an emphatic no. When those same coaches ask the leaders’ direct reports, the answer is reliably different. The gap between those two responses is the entire subject of what follows.

1. What Micromanagement Actually Is, and Is Not

Before going further, it is worth being precise about what micromanagement means, because the popular caricature does real damage to self awareness. The caricature is of someone obviously unreasonable, petty, and incompetent. That version is easy to disidentify with, which is exactly the problem.

A research team studying over 2,000 workers across industries identified three defining ingredients of micromanagement: controlling behaviour, close monitoring, and excessive focus on detail. [2] The critical qualifier is that those behaviours only become a problem when they are excessive, sustained, and unnecessary. Reviewing a junior team member’s first deliverable is mentoring. Reviewing a senior team member’s work every day for six months despite a clean delivery record is micromanagement. The behaviour is the same. The context makes it either development or control.

Micromanagement is characterised by excessive scrutiny, overinvolvement in employees’ work, hyperfocus on minor details, inflexibility, and an unwillingness to allow team members to operate without sign off. [3] What it is not, necessarily, is hostile or unkind. Many micromanagers are warm, well intentioned people who have simply never interrogated the gap between how they see themselves and how their behaviour lands on the people around them.

It is also worth acknowledging upfront that there are environments where close, detailed control is not only appropriate but essential. Nuclear operations, surgical teams, aviation, active incident response, banking production outages, and security operations all operate under conditions where high control is exactly what people want and what the situation demands. In those contexts, tight oversight saves lives and prevents catastrophic failures. The argument in this post is not that control is inherently bad. The argument is that unnecessary control, applied habitually in environments that do not require it, is damaging. The word that matters in the research definition is excessive. The behaviour becomes a problem when it is sustained and unnecessary, and the distinction between a high stakes moment requiring direct oversight and a default operating mode of perpetual supervision is one that most micromanagers have never consciously drawn.

There is a useful single question diagnostic worth sitting with early: is your team boss obsessed or outcome obsessed? [4] In a boss obsessed team, the only thing that matters is what you think. Not the customer, not the mission, not the result. The most important features of any project become your idiosyncratic preferences. Every significant decision routes through you. People are afraid to be honest. Everyone quietly knows they are delivering something inferior to what they are capable of, and nobody feels like they are doing their best work.

2. Governance Versus Control: Where the Line Actually Is

Before diagnosing behaviour, it helps to establish what legitimate oversight looks like, because one of the most common deflections from this conversation is the claim that any scrutiny of oversight is an argument for letting things run without accountability. It is not. The question is never whether to have standards; it is whether the standards are applied at the right level of the organisation and calibrated to actual risk.

Approving a capital expenditure above a defined threshold is governance. Approving every line item on a team’s monthly expenses is control. Setting architectural principles that guide how systems are built is governance. Reviewing every pull request personally, indefinitely, regardless of the engineer’s track record, is control. Defining the quality bar for a customer facing deliverable is governance. Rewriting a completed document because the sentence structure does not match your preferences is control. The pattern in each case is the same: governance operates at the level of standards, boundaries, and outcomes, while control operates at the level of methods, steps, and moment to moment decisions.

The distinction matters because it gives managers a practical frame for examining their own behaviour. Ask yourself whether the involvement you are considering is setting a standard that the team can apply independently going forward, or whether it is substituting your judgement for theirs in a specific instance. The former scales. The latter does not, and it signals to the team that their judgement is not trusted, which over time becomes a self fulfilling outcome as capable people stop exercising the judgement that is never called upon.

It is also worth separating accountability from micromanagement, because the two are frequently conflated in a way that lets controlling behaviour hide behind the language of rigour. A highly accountable leader can give enormous autonomy, holding people firmly responsible for outcomes while leaving the method entirely to them. Conversely, a leader can delegate everything visibly while remaining intensely controlling through an unending cycle of reviews, revisions, and second guessing. Accountability is about owning outcomes. Micromanagement is about owning decisions that should belong to someone else. The confusion between the two is one reason controlling managers so often describe themselves as simply maintaining high standards.

3. Why It Happens: The Roots of the Behaviour

The instinct to over control is not a character flaw but a response to accumulated experiences, unexamined anxieties, and organisations that reward the wrong signals. Understanding where the behaviour comes from is not about providing cover for it; it is about making it possible to change.

It is also worth naming something the reviewer of an earlier version of this post observed: most organisations accidentally manufacture controlling managers rather than simply tolerating them. Every production incident that escapes notice generates a new approval gate. Every cost overrun creates another sign off requirement. Every quality failure adds a review step. Over time, a well intentioned organisation builds a system in which the only way to feel safe is to tighten oversight, and the managers who do this most thoroughly get rewarded for it because nothing goes wrong on their watch. The system selects for control, and then the organisation is surprised when control is what it gets.

3.1 Fear and Anxiety Dressed as Diligence

Micromanagement does not typically happen because leaders enjoy controlling every detail of their team’s work. More often it stems from anxiety. Leaders feel pressure to deliver results, and when they do not fully trust their teams to execute, they fall back on the belief that the only way to get things done right is to oversee every step personally. This anxiety intensifies in fast paced environments where stakes are high and deadlines are close. [5]

The anxiety is real, but the response to it is the problem. Tightening control feels like it reduces risk, when in practice it transfers that risk from the manager’s inbox to the team’s psychology and, eventually, to retention.

3.2 The Promotion Trap

According to Harvard Business Review, one significant driver of micromanagement is the difficulty many managers experience when transitioning to more senior roles. Moving up typically means moving away from operational work and toward strategy. For managers who built their identity and confidence through execution, this transition can feel threatening. Micromanaging direct reports becomes a way to stay connected to the ground level and counteract the discomfort of feeling less certain about their value. [3]

The person who was brilliant at doing the work does not automatically become brilliant at enabling others to do it, and that transition requires a genuinely different identity that not everyone makes cleanly.

3.3 The Imposter Syndrome Engine

Leadership coach Dr. Patricia Bonnard observes that imposter syndrome typically leads to isolation, micromanagement, and failure to delegate. The hovering is a symptom of a manager whose own anxiety has taken control of their actions. [6] A person who secretly doubts their right to be in the role cannot afford to let the team fail, because every output becomes a test of whether they belong, and the logical response from inside that fear is to control everything that could go wrong.

3.4 Inherited Behaviour

Managers who were micromanaged themselves often repeat the pattern without realising it. When senior leadership demands constant updates, middle managers frequently pass that pressure downward, sometimes without any conscious decision to do so. [7] The behaviour was modelled for them as the normal shape of thoroughness. It never occurred to them to question it because nobody around them questioned it either.

3.5 Cognitive Style and the Wrong Role

Some people are genuinely detail oriented and more naturally comfortable with specifics than with people management or strategic thinking. They may have been promoted into a leadership role that does not actually suit them, and would be more effective as high performing individual contributors. A related driver is a form of arrogance: the conviction that nobody else could possibly be as capable, thorough, or conscientious, which nothing will dislodge unless genuine humility enters the picture. [8]

3.6 Lack of Self Awareness and Leadership Development

Some managers assume micromanagement is simply the best way to ensure work gets done. They hold an immature and rigid model of leadership in which they cannot conceive of leading without direct observation. They often lack access to forums where they might encounter honest feedback and develop their leadership weaknesses. [9]

4. The Inner Experience: What Micromanagement Feels Like From the Inside

This section matters because most writing on micromanagement describes the behaviour from the outside, from the perspective of the person being managed. But if you are the manager in question, the outside description does not match your experience at all. You need to recognise the internal signals, not just the external ones.

These are the feelings and internal states that tend to accompany micromanagement tendencies. They are not diagnostic on their own, but patterns across several of them warrant honest reflection.

The discomfort of not knowing. You feel a specific, low grade unease when you are not across the detail of what your team is doing. It is not fear exactly, but it is not neutral either. Something about not knowing what is happening in a project makes it hard to concentrate on other things. You find yourself opening a document to check progress, not because you were asked to, but because the not knowing sits uncomfortably.

The urge to improve finished work. A team member hands you something completed and you can see that it is good, but you notice yourself reaching for the edit button anyway because there is something about leaving their version unchanged that feels like a failure of your own standards, even when you cannot articulate what is actually wrong with it.

The belief that your involvement lifts quality. You do not frame this to yourself as distrust but as contribution, as the natural application of experience they do not yet have. Research consistently demonstrates, however, that this conviction, even when partly true, creates a team that stops developing and begins performing only to your preferences rather than to genuine quality. [8]

Discomfort when decisions happen without you. Someone on your team makes a reasonable call and moves forward without checking, the outcome is fine, and yet you notice a flicker of irritation or anxiety about the fact that you were not consulted. You might frame this to yourself as a communication issue, but it is worth examining honestly whether it is actually a control issue.

The feeling of being the only reliable one. There is a persistent, often unspoken belief that if you were not watching, things would deteriorate. Your team members are capable, but not quite capable enough to be trusted without oversight. This feeling may be dressed up in the language of high standards, but research links it directly to imposter syndrome and personal insecurity rather than genuine assessment of team competence. [6]

Anxiety about delegation. You delegate, but the task stays in the back of your mind. You find reasons to check in that you rationalise as supportive. When the work comes back and is not exactly how you would have done it, the instinct is to correct the method rather than evaluate the outcome.

Comfort in the operational and discomfort in the strategic. Strategy requires tolerating ambiguity and trusting others to execute. Operations give you something concrete to hold. If you are honest with yourself, you tend to drift toward the operational, not because it is the best use of your time, but because it feels safer and more certain.

Resentment that nobody else seems to care as much. You work harder than everyone around you, you are across things they have let slip, and you carry a kind of quiet resentment that your dedication is not matched by the team. What you may not have examined is whether your omnipresence has systematically removed their reasons to take initiative, because when every decision routes through the manager, team members learn that their own judgement is not trusted and stop exercising it. [4]

The need for the work to reflect you personally. There is a difference between holding high standards and needing the work to carry your fingerprints. If you regularly rewrite things that were already correct, if you find yourself frustrated that a team member’s approach was effective but not your approach, you are in control territory rather than quality territory.

5. Observable Traits: What Your Team Sees That You Do Not

Beyond the internal experience, there are specific behavioural patterns that others observe from the outside. These are worth reading not to match them perfectly but to notice whether more than a few feel uncomfortably familiar.

Consider the engineering lead who has ten senior engineers and still insists on approving every pull request personally. The engineers have years of experience and clean delivery records, but nothing merges without their sign off. The stated reason is quality. The actual effect is that the team queues behind one person, development slows, and the engineers gradually stop taking ownership of the code they nominally write. Or consider the manager who rewrites every presentation before it goes to a customer, not because the content is wrong but because the phrasing does not match their preferred register. The person who built the deck eventually stops trying to make it good and starts trying to make it easy to edit. The output looks polished. The capability behind it is atrophying.

These are not caricatures. They are patterns that recur across industries and seniority levels, and they share a common structure: the manager’s involvement has become the mechanism for quality rather than the team’s own judgement, and the team has adapted accordingly.

You resist delegating work, preferring to retain direct control over tasks even when capable people are available to own them. [10] When you do delegate, you provide instructions so detailed that the recipient has no real room to apply their own thinking.

You ask for updates more frequently than the complexity or risk of a task would justify. [7] You need to be copied on email chains where your involvement adds nothing to the conversation.

You redo work that meets the brief because it does not match your preferred method. You do this without necessarily explaining why, which over time produces team members who have learned that their best efforts are insufficient and who have stopped trying to bring their own thinking to problems. [11]

Your meetings focus on reviewing what has been done rather than enabling what needs to happen next. [4] Your one on ones feel like status reports rather than development conversations.

You struggle to take leave without maintaining access to team communications. The organisation does not actually function differently when you step back, but you have not tested that in a long time.

You spend the majority of your working time on operational and day to day activity rather than on the strategic thinking that your seniority actually requires. [12] The operational work crowds out the strategic work, and over time you drift further from the conversations that would most benefit the organisation.

When a team member makes a mistake, you increase your oversight of everything they do rather than addressing the specific failure. This spreads a culture of distrust throughout the team and produces people who stop taking initiative because initiative carries too much personal risk. [13]

6. What It Does to the People Around You

The damage is not abstract, and it accumulates faster than most managers realise.

A Trinity Solutions survey found that 71% of workers felt micromanagement interfered directly with their job performance, and 85% reported a significant negative impact on morale. Nearly 75% of workers identify micromanagement as the most serious workplace red flag, and 46% say it is sufficient reason to leave a job. [14]

The psychological consequences extend well beyond job dissatisfaction. Micromanaged employees frequently experience anxiety, depression, stress, and frustration. Research shows they are three times more likely to seek medical help for psychological issues, and these effects compound over time, making it progressively harder for people to stay motivated and committed to their work. [13]

One psychologist working directly with affected employees described the following observation: a client had begun rereading emails multiple times before sending them, worrying about wording and tone after repeated experiences of having their manager correct even minor details. What had previously taken minutes gradually became a source of tension and significant self doubt. [14]

The talent consequences are equally serious. Research shows that 36% of employees have already changed jobs because of a micromanager, while 69% have seriously considered doing so. [15] In most cases, the departure is a surprise to the manager, because the signals were suppressed long before they became visible.

The organisational cost extends beyond the people who leave. When every significant decision routes through a single manager, that manager becomes a bottleneck and the team’s throughput is permanently capped by one person’s bandwidth. Work queues. Decisions that could be made in minutes take days because they are waiting for a diary slot. The team learns to batch their questions and suppress their initiative, and the organisation loses not just morale but velocity. Control feels efficient in the moment because it improves the quality of today’s decision. Autonomy feels inefficient in the moment because it accepts that people will occasionally make mistakes. What that trade off obscures is that control quietly destroys next year’s organisation while appearing to protect this week’s output.

7. Self Diagnosis Questionnaire: The Honest Mirror

Before the full questionnaire, try this simpler test. If your team cannot ship, decide, or move forward while you are on annual leave, you are not leading a team; you have built a dependency. And if every genuinely difficult decision eventually lands back on your desk regardless of who nominally owns it, your organisation has centralised authority in practice regardless of what the structure chart says. Both of those are worth sitting with before working through the questions below.

Read each question and score your response: Never (0), Sometimes (1), Often (2), Almost Always (3). Answer alone, without an audience, and without filtering for how you want to see yourself.

1. Do you review or rewrite work your team has already completed, even when it meets the brief?
2. Do you find it difficult to assign a task without specifying exactly how it should be done?
3. Do you ask for progress updates more than the complexity of the task would justify?
4. Do you feel uncomfortable when you are not copied on emails related to your team’s work?
5. When someone completes a task differently from how you would have done it, do you correct them even if the outcome is acceptable?
6. Do you find it hard to let time pass on an active project without checking in, even when you have no specific reason to?
7. Do you feel a sense of unease when team members make decisions without consulting you first?
8. Do you spend more time on operational work than on strategic thinking or your own professional development?
9. When work is delegated to a trusted team member, do you still monitor the detail closely?
10. Do your team members typically ask for your approval before acting, even on relatively small matters?
11. Do your one on one meetings tend to focus on reviewing work in progress rather than on development or future thinking?
12. Have you ever substantially revised completed work without explaining your reasoning to the person who did it?
13. Do you believe the quality of your team’s output depends primarily on your personal involvement?
14. When a team member makes a mistake in one area, do you increase your oversight of their work more broadly?
15. Would you find it genuinely difficult to take two weeks of uncontacted leave without significant anxiety about what might be missed?

Scoring and Interpretation

0 to 9: Low tendency. Some situational oversight is healthy, especially during periods of high stakes delivery or team transition. Your default posture appears to be trust.

10 to 19: Moderate tendency. Patterns exist here that are worth examining carefully. Identify the questions where you scored highest and spend time with the question of why. This range often reflects situational micromanagement that has not yet hardened into a default style, and it is the most responsive range for change.

20 to 29: Significant tendency. Your team is very likely experiencing this, even if they have not said so directly. The absence of feedback is not evidence of absence. People under significant control have learned not to surface it. This range warrants active and deliberate intervention in your own behaviour.

30 to 45: This is the dominant pattern in your leadership, not an occasional occurrence. The gap between how you see yourself and how your team experiences you is almost certainly substantial. The earlier sections on internal feelings and observable traits are worth rereading not as general descriptions but as direct observations of your current situation. The work starts now.

8. Managing the Urge: Practical Retraining for the Willing Manager

The urge to over control does not evaporate once you recognise it; it needs to be actively and repeatedly managed. These strategies are not simple fixes but practices that compound over time.

8.1 Name the Actual Fear

Before you act on the urge to check in, rewrite, or reexamine a piece of work, stop and ask: what specific outcome am I actually afraid of? Write it down. Then ask whether that fear is proportionate to the evidence. Micromanagement most often stems from fear of failure, where managers who have previously been blamed for team mistakes overcorrect by trying to control every possible outcome. [7] Naming the fear precisely tends to reduce its power.

8.2 Shift from Method Control to Outcome Agreement

Before any delegation, be explicit about what a successful outcome looks like. Define the quality bar, the deadline, and the constraints. Then leave the method entirely to the person. The defining difference between micromanaging and coaching is that micromanaging fixates on minor mistakes and the work style of the individual, while coaching builds an ongoing relationship based on trust, collaborative conversation, and shared accountability for results. [4]

8.3 Build a Personal Trust Ledger

Start recording evidence of your team operating well without you. Every time a team member delivers without your involvement, note it; every time they make a good independent decision, record it. This is not a performance management exercise but a counterweight to the anxiety driven internal narrative that your oversight is what keeps things functioning. Over time, the ledger becomes the evidence base for loosening control deliberately and measurably.

8.4 Make Your Check ins Scheduled, Not Reactive

Replacing reactive, unplanned check ins with structured weekly or fortnightly touchpoints is one of the most immediately effective changes a manager can make. Even modest adjustments to cadence significantly change how team members experience oversight. [5] The discipline of waiting for the scheduled conversation rather than reaching out whenever the urge strikes trains both the manager and the team toward a healthier rhythm.

8.5 Seek the Feedback You Are Not Getting Voluntarily

The team is almost certainly not telling you how this feels. Employees are frequently reluctant to give honest critical feedback to their managers, particularly when the culture does not make that safe. Anonymous surveys or private one on one conversations framed as genuine curiosity rather than performance conversation can begin to surface what is not being said in group settings. [5] Asking for this feedback is uncomfortable, but not asking for it is considerably more expensive.

8.6 Reckon with the Cost of Your Involvement

There is a trade off that most micromanagers have never honestly calculated. Leaders who fail to delegate spend roughly 90% of their time on operational and day to day activity, leaving only 10% for the strategic thinking their seniority actually demands. The cost is twofold: the organisation loses strategic thinking time at a critical level, and the team loses the development that comes from doing work without a safety net. [12] Your involvement in the detail is not free. It has a price paid by the team’s growth and by the organisation’s future capability.

8.7 Recognise That Good Intentions Do Not Cancel Impact

Micromanaging is not only a trait of bad managers. A thoughtful, genuinely caring manager can do it too. The critical understanding is that intention does not determine impact. The road to hell, as the expression goes, is paved with good intentions. What matters is what lands on the person receiving the behaviour, not the reasoning behind it. [16]

9. Why the Leaders Above Cannot See It

This is the organisational failure that allows the problem to persist at scale. Most senior leaders are not negligent; they are simply working with the wrong information in a system that is not designed to surface the right kind.

9.1 The Performance Optics Problem

A micromanaging boss is typically more concerned with how they are perceived than with the success of the team. As long as they appear to be hardworking and industrious, other considerations recede. Leaders who prioritise their image over team wellbeing tend to miss the obvious signs of burnout and disengagement that are visible to everyone else. [6]

From above, a micromanager frequently looks exemplary. Their deliverables are polished. They are always across the detail. Nothing seems to slip through. What is entirely invisible from that vantage point is the mechanism producing those outputs: a team that has stopped thinking independently, that routes every decision upward, that produces work designed to please rather than to solve, and that is quietly exhausting itself.

9.2 The Distance Problem

In more senior positions there is a genuine need to shift from operational focus to strategic oversight. Some leaders struggle to make that transition and default to their operational strengths, becoming too involved in the day to day work of their team. They often lack access to forums where they can gain honest insight into their blind spots and work on developing their leadership weaknesses. [9]

Senior leaders cannot see what is happening at the layer below them with any real resolution; they see outputs, not the dynamic that produced them. A team that delivers cleanly may be running on suppressed initiative and accumulated resentment, and from a distance those two things are indistinguishable.

9.3 The Silence Problem

Micromanaged teams frequently develop a veneer of cohesion and positivity. The internal reality mirrors that of genuinely unhappy teams: fear, paralysis, and suppressed honesty. Nobody takes responsibility. Everyone is afraid to be candid. The team produces an inferior version of what it is capable of, and the safest social contract is to maintain the appearance that things are fine. [4]

Teams under significant control do not typically escalate. They have learned, often painfully, that escalation is risky, that the organisation tends to protect the person with authority, and that the manager in question is invested in their own image. The signal that eventually becomes visible is attrition and stagnation, neither of which is immediately legible as a management problem from a distance.

9.4 What Senior Leaders Can Actually Do

The mechanisms for surfacing this are specific and require deliberate design. Structured engagement surveys with questions specifically about autonomy, decision making authority, and trust, analysed at the team level rather than the department level, will begin to show the shape of the problem. Exit interview data, disaggregated by the departing employee’s direct manager rather than by function, is one of the most informative datasets most organisations already collect but rarely use this way.

Skip level conversations, framed explicitly as listening rather than investigation, create a channel that bypasses the manager in question. Promotion and development patterns tell a further story: a team whose members are consistently not developing, not being stretched, and not being put forward for growth opportunities is a team being managed rather than led.

The most directly effective corrective remains feedback, sought deliberately and heard without defensiveness, from peers, mentors, or the team itself. [17] But for that feedback to travel, the organisation has to have built the conditions in which honesty carries no personal cost.

10. The Question Worth Sitting With

The manager who has read this far already suspects something, because curiosity about this topic does not arise in people who feel entirely comfortable with their leadership.

There is a temptation to read everything above as an argument for loosening standards or tolerating poor work. It is not. High standards and high trust are not in conflict; the mistake is treating your personal involvement as the mechanism by which standards are maintained, when what it actually does is prevent the team from ever internalising those standards themselves. A team that performs well because you are watching has not learned to perform well. A team that performs well because they understand what good looks like and have the autonomy to pursue it is an asset. The first version is a dependency. The second is a capability.

The goal of leadership is not to become indispensable. It is to become unnecessary for the ordinary decisions so that you are genuinely available for the extraordinary ones. The measure of your effectiveness is not how much your team depends on you today but how capable they are without you tomorrow.

Every controlling leader believes they are protecting quality. Every empowering leader accepts that people will occasionally fail, because the long term objective is not perfect execution today but building a team that no longer needs you for every decision. How much your team can do without you is the truest measure of how well you have led them.

References

1. The Macro Blind Spot of a Micromanager, The Best Leadership Newsletter
2. Your Boss Micromanages. Should You?, Rahmi Syahputri, Medium
3. Micromanagement Meaning and How to Deal With It, Coursera
4. The Ultimate Guide to Micromanagers, Gallup
5. How to Recognize Micromanaging and Stop Doing It, Wonderlic
6. When a Boss Is a Micromanager, They’ll Often Do These Things, YourTango
7. 19 Signs of Micromanagement and How to Stop It at Work, Deskbird
8. 8 Micromanaging Boss Characteristics That Endanger Your Business, Gail Golden Consulting
9. No Letting Go: The Psychology of the Micromanager, LinkedIn
10. What Is the Psychology Behind Micromanagement?, Melbado
11. Micromanagers Are Often Blind to Their Management Style, LinkedIn
12. 3 Big Signs That You May Be Micromanaging, BK Connection
13. The Hidden Costs: Psychological Effects of Micromanagement, Interobservers
14. The Psychological Effects of Micromanagement, OpenUp
15. The Psychological Effects of Micromanagement and 4 Ways to Fight It, Terryberry
16. Most Micromanagers Are Blind to Being Seen as One, manager.dev Newsletter
17. The Dark Side of Leadership: Introducing the Micromanager, Psychology Today