The Weekly 30 Minutes That Sets the Tone for Everything Else
In the overview post, the second principle was to set a simple cadence: 30 minutes a week with each person on your team for the first few months, and the same thing up the chain with your own manager.
It sounds small. It is small — that’s part of the point. But what you do with those 30 minutes, and why you do it, is where most new managers either build real trust or quietly waste an opportunity.
Why a Meeting This Small Matters This Much
New managers tend to make one of two mistakes with 1-on-1s. Either they skip them, assuming things are fine unless someone says otherwise — or they turn them into status updates, spending the whole 30 minutes reciting what’s already visible in a project tracker somewhere.
Both mistakes come from the same misunderstanding: treating the meeting as a way to stay informed, instead of a way for the relationship to develop. If the only thing happening in that room is a status report, you haven’t built anything that wasn’t already sitting in an email or a dashboard.
The version that works is different in purpose, not just in tone. The two questions from your first conversation — what their day-to-day actually looks like, and where they want to go — don’t go away. They become the running agenda. Each week, you keep learning what someone’s job involves beyond the job description, and you give them space to bring you their goals and how they’re progressing toward them.
The Mistake Experienced Leaders Don’t Make
There’s a third mistake, and it’s the one that most clearly separates new managers from senior managers and executives.
New managers put a recurring 1-on-1 on the calendar and assume everyone understands what it’s for. Experienced leaders don’t assume. They set the expectation out loud. Senior leaders explain why the meeting exists, what it’s for and what it isn’t, and why a consistent format matters. They make clear that it’s the employee’s time: a place to talk about their work, their goals, and their progress, not a weekly audit.
Most importantly, they explain what’s in it for the employee. When a manager is current on someone’s work, they can answer questions from their own leadership accurately, without having to go find out. And when an opportunity comes up, whether that’s a stretch project, a promotion, or a visible assignment, they can advocate with real examples of that person’s work instead of general impressions.
Experienced leaders say this plainly: “If I don’t know what you’re working on, I can’t speak up for you. No information, no advocacy.”
That changes how the employee sees the meeting. It stops being a check-in they sit through and becomes something that works in their favor.
That explanation isn’t a formality. Without it, the meeting has no north star. Your report doesn’t know whether to bring updates, problems, or nothing at all, so they bring whatever feels safest. Over time, a meeting without a clear purpose gets spent on whatever is loudest that week. Or it quietly falls off the calendar because neither of you can say what you’d lose if it did.
Setting the expectation up front gives both of you something to hold the meeting to. It also tells your report something important on day one: this meeting is about them, and you meant it.
One more warning: the fastest way to undo all of this is to treat the 1-on-1 as the first thing to move when your calendar fills up. Every reschedule tells your report where they rank against everything else on your plate. Hold it, even if it’s 15 minutes instead of 30. Consistency is the message.
Why This Also Protects Your Team’s Future, Not Just Yours
In the first post of this series, I mentioned that most employees see their manager as the person advocating for them in rooms they’re not in. When you set the meeting expectation, you told your report that’s what the time is for. Here’s what it looks like when you follow through.
Think about what happens when a Director or VP is deciding who gets a stretch project, a promotion, or a seat on something visible. They’re relying on you, the manager, to make the case. If your weekly check-ins have been real — if you actually know what someone’s working toward and what they’ve been doing to get there — you can walk into that conversation and market them specifically and credibly. If those check-ins have been thin or skipped, you have nothing to offer beyond a vague sense that they’re “doing fine,” and vague doesn’t win anyone a seat at the table.
This theme is explored in more depth in Behind Closed Doors: Careers. But the short version for a new manager: the weekly 30 minutes isn’t just a courtesy to your report. It’s what makes you able to defend them and put their name forward when it counts. Skip it, and you’re not just under-informed — you’re unable to advocate for the people counting on you to do exactly that.
Why Weekly, and Why It Should Stay Weekly
The first few months are where weekly is non-negotiable. Early on, you don’t yet know what you don’t know — about the work, about the team’s rhythms, about which of your assumptions from the outside were wrong. A tighter cadence lets you catch misunderstandings quickly, before they compound. It also lets your team calibrate to you faster: they learn what kind of manager you’re going to be based on how you show up in these early conversations, long before you’ve made any big decisions they can judge you by.
After that, some people will suggest moving to every other week. My recommendation is to keep it weekly, and to explain why. The meeting isn’t for your convenience. It’s what keeps you current enough to do your job on their behalf. When your Director asks about a project, you can explain and defend it accurately, not with last month’s version. When an opportunity comes up behind closed doors, you know what that person has been working on and where they want to go, and you can put their name forward on the spot. Every other week, you’re working from older information. And opportunities don’t wait for your next check-in.
If the calendar is the issue, shorten the meeting before you space it out. Fifteen minutes every week keeps you more current than thirty minutes every other week.
The Part Most New Managers Skip: Doing This Upward, Too
Here’s the piece that’s easy to overlook: you should be asking for the same thing from your own manager.
The logic runs in both directions. Just as your team doesn’t automatically know what you expect of them, you don’t automatically know what your manager expects of you — especially in this new role, where the job looks different from the one you were just promoted out of. A regular check-in upward gives you the same benefit you’re trying to give your team: a chance to calibrate early, before a misread expectation turns into a real problem.
And the advocacy logic applies here too. Your manager explains and defends your team’s work to their own leadership, and puts your name forward when opportunities come up that you’ll never hear about. A weekly check-in keeps them current enough to do that well. It isn’t for your benefit in the room. It’s for your benefit in the rooms you’re not in.
One more reason this matters is specific to the first few months. After you’ve run weekly check-ins with your team for a couple of months, you’ll have a real, grounded sense of what your team needs and expects from you — not a guess, but something built from actual conversations. That’s exactly the moment to bring it to your own manager and confirm you’re both reading the situation the same way. You’re not asking permission to do your job. You’re checking your calibration against someone with a wider view of the organization than you currently have.
Managers who skip this step tend to find out they were misaligned only when it’s already visible — in a missed expectation, a surprised reaction, a decision that lands wrong. A short, regular upward check-in catches that early, while it’s still just a conversation and not a problem.
What This Sets Up
This principle doesn’t stand alone — it’s what makes the next one possible. Eight weeks of consistent check-ins is a track record. When you eventually introduce a change, your team won’t judge it in isolation. They’ll be judging it against everything they’ve seen from you in those meetings: whether you listened, whether you followed through, whether what you said in the room matched what happened outside it. A new manager with that track record is proposing a change. A new manager without one is imposing it.
The 30 minutes isn’t really about the 30 minutes. It’s the mechanism that builds trust early enough to matter later.
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.



Leave a Reply