A promotion can change your authority in a day. Your habits rarely change that quickly.
That gap explains a common management problem. Someone becomes responsible for a team because they were reliable, technically capable, commercially strong or unusually good at getting difficult work done. The new title gives them permission to allocate work, set priorities and make decisions. It does not automatically teach them how to create clarity for other people, listen before deciding, earn trust, handle disagreement or adapt their approach without making the team feel directionless.
Jim Salvucci makes this distinction explicit in his Genius Talk conversation. He separates the formal position of a boss from the practiced skill of leadership. In his view, moving into management does not prove that someone knows how to lead. Leadership still has to be studied, practiced and improved through feedback.
Jonathan Bennett approaches the same transition from another angle. He describes leaders who keep applying the habits that made them effective as individual contributors. They push harder, work faster and become more involved. At team scale, those habits can turn into micromanagement and burnout.
The job has changed. Performance now depends partly on work you cannot do yourself.
That changes what deserves your attention.
The first shift is from personal output to team conditions
Individual contributors can often compensate for a weak process with personal effort. They stay late, solve the problem themselves, chase the missing information or redo a task that does not meet the standard.
A manager has access to the same escape route, which is why it is so tempting.
The trouble appears when personal rescue becomes the management system. The team learns that difficult decisions will eventually move upward. Important knowledge stays in the manager’s head. Standards become whatever the manager notices in the moment. People wait for approval because that is safer than exercising judgment.
Bennett’s warning about individual-contributor habits matters here. Working harder can increase your own output. It does not necessarily increase the capability of the people around you. Once responsibility expands, the leader has to improve the conditions in which other people make decisions and deliver work.
Wesley Dove adds a useful practical lens. His work links everyday leadership behavior with outcomes such as recruitment, retention and culture. Those relationships are part of his leadership framework rather than universal quantified effects, but the underlying point is concrete: culture is influenced by what supervisors, managers and owners repeatedly do.
Dove also distinguishes between taking care of people personally and developing leaders who can do the same for others. That moves leadership away from the idea of one unusually capable person at the center. A strong team cannot depend on one person being present for every judgment call.
A useful question for a new manager is therefore: What currently works only because I am personally involved?
The answer reveals where the old job is still hiding inside the new one.
Self-awareness becomes an operating skill
Salvucci places self-awareness near the beginning of leadership because it includes more than knowing your intentions. It also includes understanding how other people experience your behavior.
That distinction is easy to underestimate.
A manager may intend to be thorough while the team experiences constant second-guessing. The manager may intend to be available while repeated unscheduled check-ins feel like surveillance. A leader may believe they are encouraging debate while people learn that disagreeing creates a long, exhausting defense of every point.
Intent matters, but teams respond to behavior.
This is why self-awareness has to include observable evidence. What happens after you speak? Who stops contributing when pressure rises? Which decisions keep coming back to you? Do people ask for clarification early, or do they wait until a problem is already expensive? Do team members tell you when they think a plan is weak?
Leadership feedback is useful when it helps answer questions like these.
The goal is not to become endlessly self-conscious. It is to notice the gap between the leader you believe you are and the working environment your behavior creates.
Dove’s emphasis on daily behavior supports the same idea. Mission, values and leadership training have limited force if the day-to-day experience teaches a different lesson. A leader who says that initiative matters but corrects every small deviation is teaching caution. A leader who says people should raise issues early but reacts defensively to bad news is teaching delay.
Culture listens closely to reactions.
Listening is a form of diagnosis
Daniel Murray’s work on empathy gives leadership a sharper use for listening.
He defines empathy around understanding another person’s perspective rather than simply agreeing with it. His professional background in analytical fields led him to a recurring problem: plans that looked sound on paper could fail because the people expected to act on them had not been understood.
One of his examples involves actuaries communicating with a sales team. More data did not solve the problem. Murray says the information had to be translated into the relationships, customer stories and meaning that mattered to the salespeople.
The management lesson is broader than the example. When someone resists a plan, misses a deadline or argues for a different approach, the first explanation available to the manager may be incomplete.
Murray’s phrase “consciously curious” is useful because it describes a deliberate interruption of assumption. Slow the conclusion down. Ask what the person is seeing. Find out what constraint, incentive or interpretation is shaping the response.
Understanding does not require agreement with every explanation.
A manager can understand why someone objects and still make the same decision. A leader can understand why a deadline was missed and still hold the person accountable. Perspective-taking improves the quality of the diagnosis; it does not remove the need to decide.
That matters because premature certainty is expensive in people problems. If the manager misdiagnoses a capability problem as an attitude problem, the response will be wrong. If the issue is unclear priorities and the manager treats it as low motivation, a motivational speech adds noise rather than clarity.
Listening earns its place in leadership when it improves the next decision.
Clear expectations reduce the need for constant intervention
Many management problems become personal because the operating expectations were never made explicit.
Kevin Eikenberry makes this especially visible in remote teams. He argues for an agreed communication cadence instead of leaders contacting people unpredictably whenever something comes to mind. Team members should know what communication is expected, through which channels and with what frequency.
The principle travels beyond remote work.
People need to know what good work means, which decisions they own, when the manager expects an update, what should be escalated and how priorities will be resolved when everything seems urgent.
Without that clarity, the manager often compensates by checking more.
More checking can create the appearance of control while leaving the underlying ambiguity untouched.
Salvucci’s emphasis on mission and shared values adds another layer. Expectations should connect to a larger direction. When people understand what the organization is trying to accomplish and what it values, they have more context for decisions that cannot be reduced to a checklist.
The combination matters.
Goals without working rules leave people to guess how to coordinate. Rules without a meaningful destination can produce compliance without judgment. Leaders need enough stability that people know what they are aiming at and enough operating clarity that they can move without waiting for permission at every step.
A practical expectations conversation can cover five questions:
- What outcome are we responsible for?
- What does good work look like here?
- Which decisions can you make without me?
- What information do I need, and when?
- What should happen when the situation no longer fits the plan?
These questions turn management from ongoing interruption into a clearer agreement about how work will run.
Trust grows through predictability and useful boundaries
Trust is often discussed as a feeling. For a manager, it also has a procedural side.
Can people predict how you will respond when something goes wrong?
Do they know whether a concern will be heard before it is judged?
Will the same standard apply when the work is under pressure?
Can someone say, “I do not know,” without pretending until the uncertainty becomes a bigger problem?
Eikenberry’s remote-leadership advice adds a human boundary to this. He distinguishes between personal connection and private information. Leaders can create real relationships without pushing people to disclose parts of their lives they would rather keep private.
That is a useful correction to the idea that trust requires forced intimacy.
The leader’s task is to create enough relationship for people to work together honestly, while respecting the fact that different people have different comfort levels.
Murray’s perspective-taking fits here too. Understanding a person’s point of view can make a difficult conversation more accurate. It can also make accountability more specific. Instead of treating resistance as a character flaw, the leader can address the actual disagreement, expectation or constraint.
Trust becomes stronger when candor has a fair process around it.
That does not mean every conversation ends pleasantly. It means people can understand the basis of the decision, the standard being applied and the next step expected of them.
Accountability becomes clearer when the standard is visible
A new manager can easily confuse authority with accountability.
Authority says the manager has the right to make a decision. Accountability asks whether people understand what they are responsible for, what standard applies and what happens when the work falls short.
The distinction matters because positional authority can produce short-term compliance without improving judgment. If the only reason a task gets corrected is that the manager insisted, the team has learned who has power. It may not have learned how to recognize the same issue next time.
Salvucci’s emphasis on mission, values and observable behavior gives accountability a stronger base. A leader can point back to the agreed purpose and expected behavior instead of treating each correction as a fresh personal preference.
Murray’s perspective-taking adds another safeguard. Before assuming someone ignored a standard, find out whether the standard was understood in the same way. A missed expectation can come from disagreement, capability, competing priorities, incomplete context or simple ambiguity. Those causes require different responses.
This makes a difficult conversation more precise.
The leader can explain the gap between the agreed outcome and what happened, ask how the other person understood the situation, identify the cause and agree on what changes next. When the cause is a capability gap, the answer may involve support or practice. When the issue is a decision the person knowingly made, the conversation can focus directly on responsibility. When the manager’s own instruction was vague, accountability includes correcting the management system.
That last case is important. Leaders weaken trust when every failure is interpreted downward and every ambiguity is ignored upward.
Dove’s focus on everyday leadership behavior reinforces the point. The team watches whether standards are applied consistently and whether leaders hold themselves inside the same culture they expect from everyone else. If a value applies only when it is convenient, people learn that the value is optional.
Clear accountability therefore has two parts: people know what they own, and leaders make their own contribution to the outcome discussable.
That combination is more durable than relying on rank whenever something goes wrong.
Adapt the method while keeping the destination steady
One of the hardest parts of management is deciding when consistency helps and when it becomes rigidity.
Eikenberry offers a useful trigger: when the answer is “it depends,” ask what it depends on. The phrase can prompt a leader to examine context instead of repeating the response that happens to feel familiar.
He also argues that goals and values can serve as a stabilizing force while the leader remains flexible in approach.
That resolves an apparent contradiction in people management.
Different people may need different levels of context, different communication rhythms or different kinds of support. A new team member may need more frequent alignment than an experienced colleague. One person may think best through a live discussion; another may produce a stronger answer after reading the problem first. A situation involving a new risk may deserve more manager involvement than routine work.
Variation in method does not require variation in standards.
The leader can hold the same destination, quality threshold and values while changing how they help different people reach them.
This is also where careless “treat everyone the same” management can fail. Equal respect does not require identical supervision. The work should be fair and understandable, while the route to effective performance can reflect the person and the context.
The opposite failure is over-adaptation. If every expectation changes with every individual preference, the team loses a shared operating model. People cannot coordinate when the rules are permanently negotiable.
The better question is: What must stay stable for the team to trust the system, and what can flex so people can do their best work?
That is a leadership judgment, not a formula.
Stop proving your value by being the answer to everything
Promotion can create an identity problem for high performers.
The activities that used to prove competence may now be the activities the leader needs to do less often.
The expert was rewarded for having the answer. The manager may need to ask a better question.
The individual contributor was rewarded for solving the issue quickly. The manager may need to let someone else work through the problem.
The specialist could optimize a piece of work. The leader has to consider whether that piece still matters in the larger system.
Bennett’s account of leaders becoming louder, faster and more controlling as responsibility grows captures the trap. A larger role cannot be handled simply by increasing the intensity of the old one.
Dove’s distinction between personally caring for a team and developing other leaders offers the alternative. Leadership capacity expands when judgment, context and responsibility expand beyond the person with the title.
Delegation in this sense is more than distributing tasks. It means transferring enough context and decision space for another person to own an outcome.
That transfer will sometimes produce a different method than the leader would have chosen. If the outcome, standard and boundary are clear, difference is not automatically a defect.
For a new manager, that can be uncomfortable. It is also one of the clearest signs that the job has changed.
A leadership practice plan for the role shift
The Genius Talk perspectives suggest a practical development sequence for someone moving from strong individual performance into responsibility for people.
1. Audit where authority has changed but behavior has not
List the work you still solve personally.
Look for decisions that always return to you, meetings where you dominate the answer, tasks you routinely redo and problems the team waits for you to notice.
Choose one area where your involvement is preventing someone else from building judgment.
2. Ask for behavioral feedback, not a personality verdict
Use Salvucci’s self-awareness principle in concrete form.
Ask trusted colleagues questions such as: When do I make it harder to raise a concern? Where am I unclear? What do I keep taking back after delegating? When do I help the team most?
Specific situations are more useful than being told you are “supportive” or “demanding.”
3. Replace assumption with curiosity in one recurring conversation
Use Murray’s approach when a pattern frustrates you.
Before explaining, diagnosing or correcting, ask enough questions to understand how the other person sees the situation. Then decide what still needs to change.
The aim is a better diagnosis, not agreement for its own sake.
4. Create explicit operating expectations
Borrow from Eikenberry’s cadence principle.
Agree on communication frequency, channels, escalation points, decision rights and what a useful update contains. If the team is repeatedly surprised by your check-ins, the cadence is probably still living in your head.
5. Separate stable standards from flexible support
Write down what cannot change: goals, ethical boundaries, quality requirements, decision principles or values.
Then identify what can change by person or context: level of detail, coaching frequency, communication format or path to the outcome.
This gives adaptation a boundary.
6. Develop someone else’s judgment deliberately
Choose a decision you would normally make.
Give the person the context, desired outcome, constraints and authority to make it. Review the reasoning afterward rather than silently replacing the answer with your own.
That is how delegation becomes development.
7. Review the environment your behavior is creating
At the end of each week, look for evidence.
Are problems surfacing earlier?
Are people clearer about what they own?
Are decisions moving without unnecessary approval?
Are disagreements becoming easier to discuss?
Are you spending more time on direction and fewer hours rescuing work that should not need rescue?
Leadership improvement becomes more useful when it can be observed in the way the team operates.
The title is the beginning of the learning curve
The interviews behind this synthesis converge on a demanding idea: formal responsibility and leadership capability are separate things.
Salvucci emphasizes practice and self-awareness. Murray adds perspective-taking as a way to understand the people inside a plan. Eikenberry shows why expectations and communication cadence need to be intentional. Bennett exposes the limit of scaling individual-contributor habits. Dove brings the focus back to repeated behavior and the development of leadership beyond one person.
Together, those ideas change the question a new manager needs to ask.
The question is no longer, “How do I keep proving that I can do the work?”
It becomes, “What do people need from my leadership so they can do strong work without depending on me for every move?”
That is the real role shift from boss to leader.
It is also why the transition takes practice. The new manager has to replace reflexes that once produced personal success with habits that create clarity, judgment and responsibility across other people. The work becomes less visible in any single task, but more visible in how the team operates when the manager is not supplying every answer.
A useful sign of progress is that the team becomes more capable without becoming less clear about direction. People know what they own, know when to involve the leader and can explain the standards behind their decisions. That is a better leadership signal than a manager who remains indispensable to every important move.