How to Manage People When You Have Never Been a Manager

You don't need a management theory, you need five habits

Becoming a manager for the first time can feel like you should have read a stack of books before you're allowed to do it properly. In practice, most of what makes management work well in a small team comes down to a handful of consistent habits, done reliably, rather than any particular theory or leadership style. Consistency matters far more than sophistication here.

The five habits worth building first are: a regular one-to-one with each person, clearly stated expectations for their role, feedback given close to the moment it's earned, a fair process when something goes wrong, and simply noticing when someone needs support before it becomes a crisis. None of these require formal training to start; they require deciding to do them and then actually doing them every time, even when it's inconvenient.

This is not a claim that management is simple — people and situations are genuinely varied and sometimes difficult. It is a claim that the basics, done consistently, solve the large majority of problems that first-time managers run into, and that the harder situations become much more manageable once the basics are already in place.

Setting up the one-to-one

A regular one-to-one is the single most useful habit you can build as a new manager, because it creates a reliable space for things to surface before they become urgent, and it gives the other person a consistent channel to raise concerns without needing to make a special request to talk to you.

Keep it short, regular and protected — thirty minutes, fortnightly is a workable starting cadence for a small team, and it should almost never be cancelled, because cancelling repeatedly signals that it isn't actually a priority. Structure it so their topics come first, then progress on current work, then any feedback either way, then a short list of agreed actions before you finish.

1. Their agenda first: what's on their mind, blockers, questions
2. Progress: what's moved forward since last time, what hasn't
3. Feedback: from you to them, and genuinely invite it from them to you
4. Development: anything they want to grow into or learn
5. Actions: a short written note of what's agreed before you both leave

A one-to-one that only ever covers task status is a status meeting wearing a one-to-one's name — leave real space for what isn't on the task list.

Setting expectations that actually land

A huge share of what looks like underperformance in small teams is actually a mismatch between what the manager expected and what was ever actually communicated. If an expectation exists only in your head, it will not be met reliably, however obvious it seems to you — the person cannot meet a standard they were never told.

State expectations specifically and in writing where possible: what does good look like for this role, what are the non-negotiables, what's the standard for communication and reliability, and how will progress be reviewed. Revisit these at the one-to-one, not just once at the start of employment, because roles and priorities shift and the written expectation needs to shift with them.

• What does 'doing this job well' actually look like, described concretely, not in general terms
• What are the non-negotiables — things that must always happen, regardless of workload
• What's the expected standard for communication: response times, when to flag problems, when to escalate
• How and when will progress be reviewed, and by what measure
• What support or resources are available if something is genuinely blocking them

Giving feedback close to the moment

Feedback saved up for a formal review, weeks or months after the event, is far less useful than feedback given close to when it happened, because the details are fresher and the person still has a chance to apply the lesson to the very next similar situation. Waiting for a scheduled review to raise something small also risks it growing into a bigger issue than it needed to be.

For positive feedback, be specific about what was done well and why it mattered, rather than a general 'good job' that doesn't tell the person what to repeat. For corrective feedback, describe the specific behaviour or outcome, the impact it had, and what you'd like to see instead — keep it about the work, not the person's character, and give it privately unless the positive version is genuinely public praise.

A simple structure that works for most everyday feedback: what I noticed, why it matters, what I'd like next time. This keeps the conversation factual and forward-looking rather than accusatory, and it's short enough to use in the moment rather than saving it up.

Recognising the early signs of a genuine performance problem

Before assuming a performance issue is about the person, work through the more common explanations first: unclear expectations, insufficient training, unclear authority to make the decisions the role requires, or a genuine external blocker like a broken tool or an unclear brief from you. Most apparent performance problems trace back to one of these rather than to capability or effort.

If, after addressing those and giving a fair and reasonable period, the standard still isn't being met, it's time for a direct, honest conversation, held privately, that names the specific gap between what's expected and what's happening, and asks for their view on what's causing it. This conversation should happen well before anything becomes formal, and should be documented in a simple note even at this informal stage.

When to move from informal to formal, and how

If informal conversations and a fair opportunity to improve haven't resolved the issue, or if the matter is serious enough to require a formal process from the outset — such as a conduct issue — you are moving into territory where getting the process right matters legally as well as practically. This is not the place to improvise based on instinct or on what feels fair in the moment.

Acas provides clear, free guidance on managing performance and disciplinary processes, including the steps that should be followed to keep things fair, and GOV.UK sets out the relevant employment-rights framework. As a small-team operator without formal HR training, this is exactly the situation where you should be following that guidance directly rather than relying on general advice, and taking independent advice if the situation is serious or you are unsure.

I am not a lawyer or HR professional, and anything that could lead to a formal warning or dismissal should be checked against current Acas and GOV.UK guidance, or with a qualified adviser, before you act.

Noticing when someone needs support, not correction

Not every dip in performance is a discipline issue. Genuine personal difficulty, health problems or work-related stress can all show up looking like underperformance, and treating them as a discipline matter from the outset can make things considerably worse and is potentially unfair. A regular one-to-one is often where these things surface first, if you've built enough trust for someone to actually raise them.

If you suspect stress or wellbeing is a factor, the HSE provides practical guidance for employers on managing work-related stress, including how to have supportive conversations and what reasonable adjustments might look like. Approaching the conversation with genuine curiosity about what's going on, rather than an assumption of low effort, usually gets you to the truth faster and preserves the relationship either way.

Your first month as a manager: a practical starting checklist

If you're stepping into managing people for the first time, resist the urge to overhaul everything at once. A small number of habits, started properly and kept up, will do more good in the first month than any amount of reading about management styles.

• Schedule a recurring one-to-one with each person and protect the time
• Write down, in one page per role, what 'doing this job well' actually looks like
• Give at least one piece of specific, timely feedback (positive or corrective) each week rather than saving it up
• Ask directly, at least once, what's currently getting in the person's way
• Read the Acas overview of managing performance so you know the shape of a fair process before you ever need it
• Be honest with your team that you're new to this and open to their feedback on how you're doing it

What good management does not require

It's worth being explicit about what first-time managers often assume is necessary but isn't. You do not need to have all the answers, to never change your mind, or to maintain a strict professional distance from a team you may have previously worked alongside as a peer. What matters is consistency, fairness, and a genuine effort to understand what's actually happening for each person, rather than projecting confidence you don't feel.

It's also worth saying plainly that you will get some of this wrong in your first months, particularly around feedback timing or expectation-setting, and that this is a normal part of learning the role rather than a sign you're unsuited to it. How you recover from a misstep — acknowledging it honestly and adjusting — tends to build more trust with a small team than never making one in the first place.