INTRO - I Think I Just Became the Boss - How to Start Managing People, Delegate, Give Feedback, and Stop Trying to Do Everything YourselfINTROYesterday, you were the person people called when something needed to get done. You knew the systems, the clients, the process, the shortcuts, the hidden traps, and the exact spreadsheet tab everyone else somehow avoided. Today, you walk into a meeting and discover that people are no longer asking you to fix the problem. They are waiting for you to decide who fixes it, by when, with what priority, and what happens if they do not.
That is usually the moment it hits you.
You are not just doing the work anymore.
You are responsible for people doing the work.
Congratulations. I think you just became the boss.
There is rarely a ceremonial moment. Nobody hands you a small velvet box containing managerial wisdom. No one gathers the team, dims the lights, and says, "From this day forward, you shall understand delegation." More often, the promotion arrives in an email, a calendar invite, a quick conversation, or a sentence from someone senior who says something like, "You already know the team, so the transition should be easy."
It will not be easy.
It may be perfectly manageable, but those are not the same thing.
The first surprise is that the skills that got you promoted are not the same skills that will make you good at managing. You may have earned the role because you were reliable, competent, fast, calm under pressure, or the person who could rescue a project after everyone else had quietly begun discussing whether changing industries was still an option. That is useful. It is also dangerous, because your instinct will be to keep doing exactly what made you successful.
Someone is struggling with a report? You can fix it.
A client issue is getting messy? You can step in.
A deadline is slipping? You can take the difficult part yourself.
The presentation is not good enough? Fine, send it over. You will "just tidy it up."
Three hours later, you have redesigned half the deck, rewritten the recommendations, answered six messages for other people, and somehow added three new tasks to your own list. Meanwhile, the person whose work you rescued has learned an important lesson: when things get difficult, the boss eventually takes over.
This is how a very capable person accidentally builds a helpless team.
The trap feels especially reasonable because taking over often works in the short term. You are experienced. You can do the task faster. You may genuinely produce a better result today. The problem is that management is not only about today's result. It is about whether the team can produce good results next week, next month, and on the Friday you are off work and have made the radical decision not to spend your afternoon answering "quick questions" from a supermarket parking lot.
That requires a different definition of usefulness.
As an individual contributor, usefulness is often visible. You make something, solve something, analyze something, sell something, deliver something. There is a satisfying before and after. The problem existed. You touched it. Now it is smaller, cleaner, finished, shipped, approved, or at least moved into a folder called FINAL_v6_REAL_FINAL.
Management is less polite.
Some of your best work will produce no obvious artifact. You will spend thirty minutes helping someone think through a decision, and the visible result will be that they do not need you the next time. You will clarify responsibilities between two people, and the benefit will be a conflict that never happens. You will explain a standard properly, and the reward will be a document you do not have to rewrite on Thursday night.
That can feel strangely unproductive at first.
You may finish a day with fewer completed tasks than before and wonder whether you are doing enough. Then you notice that three people moved forward because of decisions you made, one stopped waiting for permission, another finally understood what "good" looks like, and a problem was surfaced early instead of exploding six days later in a meeting with twelve people and one extremely tense silence.
That is work too.
In fact, it is now a large part of your work.
The second surprise is that managing people means dealing with people. This sounds obvious until you actually have to do it. People do not behave like tasks in a project tracker. You cannot mark one "blocked," assign another to Tuesday, and put a third into a folder called "motivation issues" for later.
One person wants more responsibility but does not yet have the judgment for it. Another is excellent but overloaded. Someone else is reliable, quiet, and slowly becoming invisible because the loudest people get more attention. One employee needs clear instructions. Another becomes frustrated if you explain what they already know. One person wants feedback immediately. Another hears the sentence "Can we talk for five minutes?" and mentally begins updating their resume.
And then there are former peers.
People you complained with.
People who know what you said about the old process.
People who may have applied for the same promotion.
People who used to send you messages that began with, "Can you believe what management has done now?"
You are management now.
Enjoy that.
You will also discover that being responsible does not mean knowing everything. A team member may know more than you about the client, the tool, the technical process, the numbers, or the tiny operational detail currently holding the entire project hostage. The temptation is to pretend otherwise because leadership and certainty are often presented as close relatives.
They are not.
A useful manager does not need to be the smartest person in every room. A useful manager needs to know what must be decided, who has the relevant knowledge, what matters, what is still uncertain, and when the team has enough information to move.
Sometimes the most competent sentence you can say is, "I don't know yet. Let's work out how to find out."
The third surprise is that many management problems arrive disguised as personality problems. "She is difficult." "He is not proactive." "They do not communicate." "Nobody takes ownership."
Sometimes that description is accurate.
Often it means something much less dramatic.
The expectation was unclear.
Two people thought they owned the same decision.
Nobody knew what "urgent" meant.
A deadline was assumed rather than agreed.
An employee was told to be independent but criticized whenever they made a decision the boss would have made differently.
A manager wanted people to "take more ownership" while requiring approval for every move larger than choosing a font size.
Organizations are full of problems that look emotional from a distance and turn out to be procedural when you get closer.
This book is about getting closer.
Not so you can become a management philosopher who says things like "leadership is a journey" while staring thoughtfully out of a glass meeting-room wall. You have work to do. The point is to become better at the ordinary, awkward, repeatable things that actually shape a team: setting expectations, deciding priorities, delegating without dumping work, giving feedback before frustration turns into folklore, handling conflict without becoming the official translator between adults, and noticing when you have quietly made yourself the bottleneck.
You will need to learn how to say no without turning into a dictator, how to support people without doing their jobs for them, and how to give someone room without abandoning them and calling it empowerment.
You will need to make decisions when the information is incomplete.
You will sometimes need to tell someone that the work is not good enough.
You will sometimes need to hear that your own management is not good enough.
That last one is particularly inconvenient.
There will be days when you do this well. You will leave a conversation thinking, "That was actually useful." Someone will solve a problem without you. A difficult discussion will be more straightforward than expected. A person you coached will handle something better than you would have handled it yourself.
There will also be days when you explain something badly, give the wrong answer, delay a conversation you should have had earlier, or say, "Fine, I'll just do it," and realize halfway through the task that you have once again become your team's highest-paid emergency substitute.
That does not mean you failed at management.
It means management is a skill, not a personality transplant.
You do not need to become a guru, a motivational speaker, an amateur therapist, or the kind of person who puts the word "leader" into every second sentence. You need practical habits that work when you are tired, busy, uncertain, under pressure, and dealing with people who are also tired, busy, uncertain, and under pressure.
The goal is not to become indispensable.
Quite the opposite.
A strong team should need your judgment, direction, support, and leadership. It should not need your personal involvement in every task, email, decision, spreadsheet, argument, and mildly confusing Tuesday.
If everything has to pass through you, you are not leading a team.
You are operating a human toll booth.
And there are already enough queues at work.
Chapter 1 - This Is Not the Same Job Anymore - I Think I Just Became the Boss - How to Start Managing People, Delegate, Give Feedback, and Stop Trying to Do Everything YourselfChapter 1 - This Is Not the Same Job AnymoreYour first Monday as a manager may look suspiciously normal. Same laptop. Same coffee. Same inbox. Same person in Finance who can turn a yes-or-no question into a twelve-line answer beginning with "It depends." For the first half hour, you may even convince yourself that not much has changed. Then, at 9:14, someone messages: "Can you help me decide what to do with this client?" At 9:22, another person asks whether they can move a deadline. At 9:37, your own manager wants to know why the team's numbers slipped last week. At 9:46, someone says, "We need a decision from you." It is still before ten, and you already miss the peaceful old days when your biggest problem was a file that refused to open.
This is the first major adjustment: the job did not simply get bigger. It changed shape.
Before becoming a manager, most of your value was probably tied to what you personally produced. You wrote, analyzed, sold, fixed, presented, negotiated, designed, organized, or solved. Work arrived, you did it, and at some point there was a satisfying moment when you could say, "Done." The result might have been a report, a client win, a repaired process, a finished project, or at least a file you could save somewhere and never look at again until someone mysteriously asked for it six months later.
Management is less tidy.
A large part of your value now comes through other people's work. Sometimes your best contribution is making a decision. Sometimes it is clarifying what matters. Sometimes it is noticing that two people are solving the same problem in opposite directions. Sometimes it is asking a question that prevents three days of wasted effort. And sometimes your greatest achievement of the afternoon is doing absolutely nothing because the person in front of you is perfectly capable of handling the issue without being rescued.
That last one can feel deeply unnatural.
Especially if competence is what got you promoted.
You may have spent years building a reputation as the person who can sort things out. People trust you because when something goes wrong, you get involved and the situation improves. That is a useful reputation. It is also how many new managers accidentally become the busiest person in the building.
A team member brings you a messy spreadsheet.
You fix it.
Someone struggles with a difficult email.
You rewrite it.
A presentation looks weak.
You take it home and "polish it."
Someone is behind schedule.
You absorb part of the work.
Each individual decision makes sense. You are helping. You are protecting the result. You are being responsible.
After a few months, your team is performing reasonably well, and you are answering email at 10:48 p.m. while eating something over the sink because sitting down now feels like a luxury associated with childhood.
The problem is not that you worked hard.
The problem is that you kept using the operating system of an individual contributor in a role that now requires something else.
If you want to see whether this is happening, look at the last five working days and ask three uncomfortable questions about each major task: Did this genuinely require me? Could someone else have done it with the right preparation? Did my involvement make the team more capable next time, or did it simply make this problem disappear today?
Those questions expose a lot.
You may discover that you are still producing a weekly report because you have always produced it, even though someone else could take it over. You may be attending a recurring meeting because your name has been on the invitation since a previous role and nobody has ever dared disturb the ancient administrative ecosystem. You may be making small decisions simply because people are used to asking you.
This does not mean you should suddenly stop doing all operational work and spend your days walking around saying, "I need to stay strategic." That is the opposite mistake. A manager who used to do everything can sometimes swing dramatically toward doing nothing visible at all, as if promotion involved being medically advised to avoid direct contact with tasks.
That is not leadership either.
Many managers, especially in smaller teams, still do hands-on work. The issue is whether the work you keep is deliberate or inherited. There is a major difference between "I am handling this because it is genuinely part of my role" and "I am handling this because nobody ever changed the habit."
Start by dividing your work into three broad groups.
The first group is work that truly requires your level of responsibility: decisions that belong to you, sensitive conversations, priorities, major trade-offs, escalation, and issues where the team needs leadership rather than another pair of hands.
The second group is work that someone else could perform, but not yet without preparation. This is where teaching, handover, context, and gradual transfer matter.
The third group is work you should probably stop owning altogether.
That third category can be surprisingly emotional.
It often contains things you are good at.
You may be the fastest person at building the monthly report. You may know the client best. You may be excellent at solving technical issues. Giving those things up can feel less like efficient management and more like voluntarily surrendering your favorite tools to someone who does not hold them correctly.
This is where many new managers discover a very important distinction: being the best person to do something is not the same as being the right person to keep doing it forever.
Imagine that one of your team members prepares a slide deck for an important internal meeting. It is decent, but not how you would do it. The story is slightly clumsy. Two slides are too busy. One chart is uglier than necessary but not, strictly speaking, illegal.
Your old instinct says: open the file and fix it.
You can make it better in twenty minutes.
And you probably can.
But what happens next month?
Another draft arrives.
You fix that too.
Eventually the employee learns a very rational workflow: produce something acceptable, send it to the manager, wait for the premium version to return.
You, meanwhile, begin to believe that nobody in the team can produce a good deck without you.
Both of you helped create the evidence.
A better approach takes longer the first time. Sit down with the person and ask what the audience needs to understand. Point out where the message becomes unclear. Explain what a strong first slide should accomplish. Let them rebuild it. Review again if needed.
You might spend forty minutes teaching something you could have fixed in twenty.
That can feel inefficient.
It is only inefficient if you plan to manage the team for the next forty minutes.
Management requires a longer time horizon.
The same applies to decisions. If people come to you with every small question, your instinct may be to answer because answering is fast. But speed today can create dependency tomorrow. Sometimes a better response is, "What do you think we should do?" or "What options have you considered?"
Do not turn every basic question into a philosophical retreat.
If someone asks where the updated pricing file is stored, you do not need to lean back and say, "Where do you believe knowledge truly lives?" Just tell them where the file is.
But when the question involves judgment, use it.
"Customer wants a small exception. Can I approve it?"
"What do you recommend?"
"I think yes, because it keeps us within margin and solves the issue today."
"Good. Do it."
That conversation takes slightly longer than "yes."
It also moves a little judgment out of your head and into theirs.
You want more of that.
Another part of the transition is learning that a productive day no longer always looks productive in the old way. You may spend an hour in a conversation that prevents a resignation, thirty minutes clarifying a broken process, and twenty minutes helping a junior employee make a decision they would previously have pushed upward. You end the day with fewer completed personal tasks, yet the team is in a better position.
If you judge yourself only by how much you personally produce, you will keep dragging yourself back into individual-contributor mode.
Try changing the questions you ask at the end of the day.
Instead of only "What did I finish?" ask: What became clearer because of me? Who became more capable? What recurring problem became less likely to return? What decision stopped people from waiting?
Those are management outputs too.
They are just annoyingly difficult to attach to an email.
The transition also requires accepting that sometimes other people will do things differently from you.
This sounds obvious until you witness it.
A team member organizes the client file in a different folder structure. Someone runs a meeting with more discussion than you would allow. Another person builds a process using a tool you would not have chosen.
Your entire nervous system may whisper, "Wrong."
Pause.
Is it actually wrong?
Or is it simply not yours?
This distinction will save you hundreds of unnecessary interventions.
There are absolutely moments when you must step in. The data is inaccurate. A client is at risk. The person has misunderstood the objective. There are legal, safety, ethical, or financial consequences. Standards matter.
But if the outcome is good and the difference is mostly style, consider leaving it alone.
A manager who corrects every personal preference eventually produces a team of adults waiting for approval on details they are fully capable of handling.
Then the manager complains that nobody shows initiative.
It is one of management's more elegant self-inflicted wounds.
The minimum version of this chapter is simple. Tomorrow, pick one task you normally take over because it is faster to do it yourself. Do not take it. Ask the person what they need to complete it themselves, agree on when you will check progress, and let them own the next move.
One task.
Not a dramatic transformation.
You are trying to break an automatic reflex, not announce the independence of a small country.
Plan B is for the situation where you genuinely cannot let go because the team is understaffed, inexperienced, or in the middle of a demanding period. Sometimes you really do need to carry more operational work. If that is the reality, do it consciously. Mark the tasks you have temporarily absorbed and attach an exit condition to each one.
"I will handle this report for the next two cycles while Maya learns the process."
"I am taking the client call this week because of the escalation, then ownership returns to Daniel."
Temporary work needs a way back out of your calendar.
Otherwise "for now" becomes permanent through the ancient business process known as nobody mentioning it again.
There is one more thing to accept early: you should not always be the busiest person on the team.
This can feel wrong if busyness has become your measure of value. You look around and someone has seven tasks, someone else has six, and you appear to have three. Part of your brain may say, "I should take something."
Maybe.
Or maybe your three tasks are deciding the quarter's priorities, resolving a cross-functional conflict, and hiring the person who will remove an entire bottleneck from the team.
Task count is not value.
Hours visibly spent typing are not leadership.
A manager who is constantly overwhelmed may be hardworking. They may also be holding onto far too much.
Your new job is not to prove that you can carry more than everyone else.
It is to make sure the right work gets done by the right people, with enough clarity and support that everything does not collapse back onto you.
Tomorrow, when someone brings you a task you know how to do better and faster, notice the reflex.
That little voice saying, "Give it to me."
You do not have to obey it.
Because the job changed.
You should too.
Chapter 2 - Yesterday We Were Colleagues - I Think I Just Became the Boss - How to Start Managing People, Delegate, Give Feedback, and Stop Trying to Do Everything YourselfChapter 2 - Yesterday We Were ColleaguesOn Friday afternoon, you are sitting with a coworker complaining about a pointless approval process. It takes six signatures to spend an amount of money that would barely cover lunch for the people signing it. You both agree this is ridiculous. You laugh. Someone says something mildly unwise about senior management. Nobody takes minutes.
On Monday morning, you are announced as the new manager.
At 9:12, the same coworker walks up and asks, "So... do I send my vacation request to you now?"
There is a pause.
A small one.
But both of you feel it.
Something changed.
Internal promotion comes with an unusual social puzzle. You already know the people. You know who hates early meetings, who needs three reminders, who secretly keeps every old version of every document, and who starts every difficult email with "Just to clarify," which is never a sign that anything is about to become clearer.
This knowledge is useful.
It is also dangerous, because familiarity can trick you into pretending the relationship has not changed.
It has.
You can still like people. You can joke. You can have lunch together. You do not need to begin addressing former colleagues by surname or suddenly send emails that end with "Regards, Management."
But now you make decisions that affect their workload, priorities, development, time off, performance evaluation, and sometimes pay or promotion recommendations depending on your role. You may know them socially, but your professional responsibility is different.
Ignoring that difference does not preserve the old relationship.
It usually makes the new one confusing.
The first bad strategy is trying to prove that nothing has changed.
You say things like, "I'm still the same person," which is probably true. Unfortunately, you are now the same person with different authority.
A former colleague misses a deadline.
Before, you might have rolled your eyes, helped fix it, and complained together afterward.
Now you have to address it.
Two people want the same week off, and the team cannot cover both absences.
You have to decide.
Someone you are close to wants a high-profile assignment, but another person is better suited.
You have to choose.
Your job now contains moments where keeping everyone comfortable is impossible.
That is not betrayal.
It is responsibility.
The opposite strategy is equally strange: becoming aggressively managerial overnight.
Some people get promoted and immediately develop Corporate Voice.
On Friday: "Yeah, send it over when you get a chance."
On Monday: "Please ensure this deliverable is submitted no later than 14:00."
Same human.
Different wildlife documentary.
The sudden formality is usually not arrogance. It is fear. You are trying to signal that the role is real. Maybe you worry that former peers will not take you seriously unless you create visible distance. So you become colder, stricter, and strangely fascinated by phrases nobody says outside conference rooms.
You do not need a personality replacement.
You need clarity.
One of the best things you can do early is acknowledge the transition directly with the team. Not with a speech worthy of a presidential inauguration. A few normal sentences will do.
"We already know each other, and I am not going to pretend we all became different people over the weekend. My responsibility has changed, though. There will be times when I need to make decisions, set expectations, or give feedback in a way I did not before. I want the rules to be clear and consistent, and I also want you to tell me if something I am doing is making the transition harder."
That may feel slightly awkward.
Good.
Awkward and honest is usually better than smooth and confusing.
The people you were closest to may need an individual conversation. Again, not a ceremonial ending to friendship. You are not gathering them at sunset to say, "From this day onward, we can no longer discuss sandwiches."
But there may be practical boundaries worth naming.
Perhaps you used to share informal commentary about management decisions. That changes when you now have access to information you cannot pass along casually. Maybe one person was used to hearing news from you early because you were friends. Now that creates favoritism, or at least the appearance of it. Maybe you used to complain together about a process you are now responsible for enforcing.
These situations are much easier if you admit the tension rather than act as though nobody notices.
Suppose a former close colleague asks, "So what did they say in the leadership meeting about the restructuring?"
You know.
The information is not public.
Previously, you might have said, "Do not tell anyone, but..."
Now you cannot.
You say, "I know a bit more, but I can't share it before the official communication."
Your friend may be disappointed.
That is fine.
Disappointment is not a management emergency.
Do not compensate by giving them another piece of confidential information so they still feel special.
The moment you create an unofficial inner circle around the boss, the rest of the team will notice. Maybe not instantly. But people are extremely good at detecting who knows things early, who gets extra context, who seems to have private access, and who can walk into your office without knocking while everyone else schedules time.
Soon, one harmless coffee starts looking like a cabinet meeting.
The solution is not pretending you like everyone equally. You probably do not. You are a person. Some colleagues are naturally easier to talk to. Some share your sense of humor. Some would not be your first choice for a six-hour car journey unless the alternative was walking.
Fairness does not require identical personal chemistry.
It requires professional decisions based on relevant reasons.
A useful rule is this: for any meaningful people decision, you should be able to explain the reason without mentioning how well you get along with the person.
Why did Jordan get the project?
Because they have the relevant experience and need exposure to the next level of responsibility.
Why did Priya get the training?
Because it directly supports a skill needed in her role.
Why did Chris not get Friday off?
Because two earlier requests were already approved and minimum coverage would otherwise fail.
Those are reasons.
"Because I trust him more" might be valid, but if you cannot explain what that trust is based on, inspect it carefully.
"Because we just understand each other" is generally not a strong staffing model.
Former peers may also test boundaries, sometimes deliberately and sometimes because old habits have not caught up with the org chart.
"Come on, just approve it."
"Do I really need to do this part?"
"Can't you just let this one slide? You know how it is."
This is where managers often panic because they do not want to look like someone who got promoted on Friday and became a tyrant by breakfast Monday.
You do not need to become harsh.
You need to become consistent.
"I get why you're asking, but I need to apply the same rule I would for anyone else."
Or:
"I can look for another option, but I can't skip the process just because we know each other."
Say it normally.
Do not suddenly sit straighter and speak like the keeper of constitutional order.
You are setting a boundary, not announcing martial law.
You may hear, "You never cared about this before."
That can be true.
The answer is not to deny history.
"You're right. I looked at this differently before because I had a different role. Now I am responsible for how the decision affects the whole team."
That is a much stronger response than pretending you always believed in the rule with religious devotion.
Your former peers may also expect you to be more relaxed with their performance because you know them.
This is another place where delayed action becomes expensive.
A friend starts missing deadlines.
You give them extra room.
They miss another.
You think, "I know they're usually good."
Another one slips.
Now you are annoyed, but you have also spent six weeks teaching them that the deadline is flexible.
When you finally speak up, they are genuinely surprised.
That is partly on you.
Address issues early and specifically, especially with people you know well.
"Two deadlines moved this month without warning. I need you to flag the risk before the deadline, not after. What's getting in the way?"
Notice what you are not saying.
"You've changed."
"You're taking advantage of me."
"You always do this."
You are managing the work, not rewriting the history of the friendship.
If they respond, "But you know I always get things done," stay with the current issue.
"I know you are capable. I am talking about how these last two deadlines were handled."
That keeps the conversation clean.
There is a mirror-image problem too: becoming harder on friends because you are terrified of looking biased.
This can feel morally admirable.
It is still unfair.
If you give everyone else three days to fix an issue but give your friend twenty-four hours because you want to prove there is no favoritism, you are not neutral. You are simply practicing reverse favoritism with very serious facial expressions.
The standard should come from the situation.
Not from your anxiety about how the situation looks.
When decisions are important, decide the criteria before the names. If you are assigning a high-visibility project, define what the project needs first. If you are approving limited training slots, decide what makes someone a strong candidate. If several people want the same scarce opportunity, determine the rule before choosing.
This protects both you and the team from vague reasoning.
It also helps if someone challenges the decision.
"Why did Sam get it?"
"Because the project needs someone who has already led a cross-functional launch, and Sam has done that twice."
Clear.
You may still have disagreement.
Clarity is not a machine for generating universal happiness.
The social side of internal promotion gets especially uncomfortable if someone else wanted your job.
They may be professional about it.
They may also be hurt, skeptical, distant, or mildly allergic to your new title.
Do not force a cheerful reset.
You do not need to say, "I hope there are no hard feelings," because there may be hard feelings and they are allowed to exist.
A better conversation is practical.
"I know you were interested in the role, and I respect that. I want us to work well together in this structure. If you still want to grow toward management, I am also happy to talk honestly about what experience would help you."
Then stop trying to make the emotional weather sunny by lunchtime.
They may need time.
Your job is to be fair, not magically lovable.
There may also be situations where a friendship outside work continues. There is no universal rule that promotion requires immediate social exile. If you used to have dinner, go running, or complain about your terrible fantasy football team together, you do not have to move house.
But the closer the relationship, the more disciplined you need to be about professional boundaries.
Confidential information stays confidential.
Work decisions need defensible reasons.
Private closeness cannot create public advantage.
And you need enough self-awareness to notice when you are avoiding a difficult conversation because it would make dinner awkward.
Sometimes the minimum version is enough. In your first weeks, do two things. First, tell the team clearly that your responsibility has changed and that you intend to use consistent work-related criteria. Second, have a short private conversation with the one or two people where the transition is most likely to be awkward.
Ten minutes can prevent months of weirdness.
Plan B is for when the relationship has already become strained.
A former peer says, "You've changed since becoming manager."
Do not immediately defend yourself.
Ask, "What specifically feels different?"
They may say you are more distant. Maybe that is necessary in some areas and unnecessary in others. They may say you no longer ask for their opinion. Perhaps you are overcorrecting to avoid favoritism. They may say your tone is more formal. Maybe you have accidentally developed Management Accent.
Listen first.
Then separate what must change because of the role from what you can improve as a person.
"I cannot share some information as freely as I used to. That part is different now. But if I have become colder in normal day-to-day conversations, that is not something I want. I can work on that."
This is a mature response.
Much better than "I haven't changed at all," when everybody has noticed that you now say "Let's circle back."
Another Plan B applies when a former friend keeps using the old relationship to push boundaries after you have addressed it. At that point, the issue is no longer just adjustment. Make the expectation explicit.
"I value our relationship, but at work I need us to operate within the same standards as everyone else. This has come up more than once, so I want to be clear that I am not going to make exceptions based on our friendship."
Uncomfortable?
Probably.
Useful?
Very.
The transition from peer to manager becomes easier when you stop trying to preserve every part of the old relationship exactly as it was. You cannot.
Some things will stay.
Some things will become more formal.
Some friendships will adapt.
Some may cool down.
That is not automatically failure.
You are building a different professional relationship around the same people.
The important part is predictability. People need to know that they can disagree with you, receive feedback from you, ask questions, and be treated according to work-related reasons rather than private history.
Being liked is pleasant.
Being trusted is more useful.
And trust does not mean everyone always gets what they want.
It means they understand that you will not suddenly change the rules depending on who is asking.
Tomorrow, think of the relationship in your team that has become least clear since your promotion. Have one normal conversation about what changed and what did not.
Do not make it dramatic.
You are still allowed to laugh together.
One of you just approves the vacation now.
