You just got the promotion, now what?

Your peers are genuinely happy for you. You feel ready.

And then, sometime in your first week, it hits you: no one actually taught you how to do this job.

That’s not a knock on your company. Most organizations promote people into management because they were excellent at their previous role. Not because anyone assessed or trained whether they’d be good at managing people. It’s a skills mismatch built into how most companies grow, not a failure by anyone involved. The skill that got you promoted (being a strong individual contributor) is not the skill the new job actually requires (helping other people be strong individual contributors).

If that gap feels a little disorienting, it should. This post is the training most new managers never get: four principles, and — more importantly — the business logic behind each one, so you can apply the thinking even when the situation in front of you doesn’t match the example.

Get to Know Your People Before You Touch Anything

Before you change a single process, sit down with everyone on your new team — one on one, somewhere uninterrupted — and ask them two things: what they’re actually working on day to day, and what they want out of their future.

Here’s the logic: whether it’s written into anyone’s job description or not, most employees experience their manager as the person who manages their career. If you don’t explicitly set that expectation, they’ll assume it silently anyway — and an unspoken assumption is much harder to work with than a stated one. You don’t have to own their career. It’s theirs. But you’re in a position to mentor them, advise them, and advocate for them — and you can only do that well if you know where they’re trying to go.

A simple way to start the conversation: What does success look like for you in six months? In a year? Then work backward together into a plan with real steps and a timeline.

Set Expectations — For Them and For You

Tell your team plainly: you want to meet for 30 minutes a week for the first few months. Not a status update — a chance for you to keep learning what their job actually involves beyond the job description, and for them to bring you their own goals and a plan to get there.

The logic: new managers who skip this tend to land in one of two bad spots — invisible (nobody knows what you’re doing or thinking) or a bottleneck (everything routes through you with no rhythm to it). A short, clearly-purposed weekly cadence solves both, and it’s a small enough ask that it doesn’t feel like a burden to anyone’s calendar.

Do the same thing upward with your own manager. Set the same expectations, ask for the same kind of check-in, and after a couple of months, run what you’re hearing from your team by your manager to confirm you’re calibrated. Modeling the behavior you’re asking your team to trust is its own kind of credibility.

Resist the Urge to Change Anything (Yet)

Even if you’ve worked in this department for years and know exactly what you’d do differently — don’t, not yet.

Here’s why this one matters more than it seems. Changing something right away, even quietly, sends an implicit message that the previous manager was doing it wrong. That’s rarely your intent, but it’s often how it lands.  With the team and with peers who’ve been doing things a certain way for a long time. People don’t usually resist change itself. They resist change they don’t understand.

Before you touch a workflow or process, get your manager’s buy-in, and build a simple explanation for your team and peers: why the change is happening, how it’ll be implemented, and what the benefit is. That’s the whole “marketing plan.” It doesn’t need to be complicated; it just needs to exist. Give people time to understand a change before you ask them to live with it. If people start resisting from day one, you’re in for a much longer road than the change was worth.

Turn “No” Into “Yes, If”

At some point in your first weeks, someone on your team will ask you for something. Do everything you reasonably can to say yes to that first ask. There’s nothing worse than a team member feeling genuinely good about a brand-new manager, only to have their very first request turned down.

But “say yes to everything” isn’t really the principle — and it’s not sustainable. The real principle is that when you can’t say yes outright, avoid a flat no. Say “yes, if” — yes, if we adjust the timeline, yes, if we change this one step, yes, if we scope it differently. A flat “no, we can’t do this” is one of the fastest ways to demoralize someone, and if they hear it enough times, they’ll stop bringing you suggestions altogether.

This is really a question of psychological safety. People keep offering ideas only as long as they believe those ideas get a real hearing. A conditional yes keeps that door open while still protecting the constraints you actually have to manage around.

But “yes, if” only works if the “if” is real and explained — not a polite way of saying no without saying it. When you can’t move forward on an idea as proposed, walk through the actual reasoning with the person: what constraint is in the way (budget, timeline, dependency on another team, risk, capacity), why that constraint exists, and what would need to change for the idea to work. The goal isn’t to justify your decision — it’s to give them the same information you’re using to think it through, so they can start to reason as you do.

Repeatable Skill

Done well, this does two things at once. It turns a single rejected idea into a repeatable skill. The next time they have a suggestion, they’ll have already thought through the idea. Whether it is a budget question, dependency, or a risk. They’ve thought it through before they even bring it to you. And it signals that the constraint is the obstacle, not their judgment. This is exactly what keeps people willing to keep proposing things. A team that understands why stops guessing at what you’ll approve. They will start building ideas that already account for the real limits — which means, over time, you hear fewer ideas that need a “no” at all.

None of this is instinctive, and almost none of it gets taught. If you’re a brand-new manager reading this, you’re not behind — you just haven’t been handed the map yet. This post is a start. There’s a lot more to the shift from doing the work to helping other people do their best work. That’s a conversation for another day.

See you at the after party,

Ringo “HRNasty” Nishioka

nasty: an unreal maneuver of incredible technique, something that is ridiculously good, tricky, and manipulative but with a result that can’t help but be admired, a phrase used to describe someone good at something. “He has a nasty forkball”.

Ongoing writing and context live on LinkedIn and Bluesky.

**Did this article change how you see career decisions?**

Get Career Reality Updates from the other side of the management table.

Ringo Nishioka writes about how executives and managers actually make decisions about your career inside organizations.