Library

Listen before you act

Your team already has a view of how things work, what’s broken and who really makes things happen. You can’t see it yet, and they won’t volunteer it until they trust you.

So start with questions, and then stay quiet long enough to hear the answers. What’s working well? What frustrates you? What would you change if it were up to you? What should I never do?

Resist the urge to fix things as you hear them. If you jump to solutions, people learn that sharing a problem means losing control of it. If you listen without judgement, they learn that it’s safe to tell you the truth. That safety is the most valuable thing you will build in these thirty days.

Learn how the work really happens

The org chart tells you who reports to whom. It doesn’t tell you where work gets stuck, who people actually go to for help, or which meeting everyone dreads.

Spend time with the work itself. Sit in on stand-ups, read recent incident notes, watch a release or a hand-off. Ask people to walk you through a recent piece of work from start to finish. You are looking for friction, not faults.

You will also discover what you don’t know. Say so. A manager who says “I don’t understand that yet, can you show me?” earns far more respect than one who nods and bluffs.

Agree what success looks like, with your manager and with your team

This is the step most new managers skip, and it hurts them later. Within your first few weeks, have an explicit conversation with the person you report to. What does good look like at 30, 60 and 90 days? Which problems are yours to solve, and which are not? How often do you want to talk, and about what?

Then turn it around. Ask each person you lead, individually, what they need from you. How do they like to receive feedback? How much direction do they want, and how much space? What does a good week look like for them? What would make you easier to work with? The answers will differ from person to person, and that is exactly the point.

Expectations that stay unspoken become disappointments, in both directions. Ask early, write the answers down, and revisit them.

Make one-to-ones the backbone

If you do one thing in your first month, make it a regular, protected one-to-one with each person in your team. Keep them. Don’t cancel them when you’re busy, because that’s exactly when they matter.

Keep them about the person, not just the task. Let them set the agenda. Ask what support they need and what’s getting in their way. Then follow through on the small things you promise, because trust is built far more by kept small promises than by big speeches.

Foundations aren’t one-off

A word of reassurance. Foundations aren’t something you build once and forget. Whenever you face a new team, a new challenge or a change in your role, you’ll find yourself back here, listening, learning and agreeing expectations. That’s not failure. It’s how experienced managers stay good.

Next time, in Part 2, we move into Practice: small, safe experiments with delegation, one-to-ones and difficult conversations, and how to get them slightly wrong without losing anyone’s trust.

Let the one-to-one grow up

In Part 1 you asked everyone the same few questions so that you could spot patterns. That was right for week one. You did not know these people yet, and a common script gave you something to compare.

But a script is scaffolding, not the building. If you are still asking everyone the same three questions in week six, they will notice, and they will start giving you the same three answers.

By now you know more than a script can hold. One person lights up when you ask about a half-built migration and goes quiet when you mention their career. Another says “fine” in a tone that isn’t. Someone has just come back from leave. You are no longer interviewing strangers. You are talking to colleagues, and your one-to-ones should start to show it.

The shift is from questions you ask everyone to attention you give to someone.

Prepare for the person, not the template

Before each one-to-one, spend two minutes on a single question: what do I know about this person now that I did not know a month ago, and what might they need today? Then choose your opening to fit.

These are openings, not scripts. Offer one, then follow where the person goes. Choosing a good question is not the same as steering the conversation, and they should still set the agenda.

A few habits make this easier:

• Keep short notes about the person as well as the actions: what they care about, what they have chosen to tell you. Use them to remember, never to probe.
• Let some one-to-ones be about nothing much. A walk or a coffee can do more than a tidy agenda.
• Treat a flat answer as information. If “fine” keeps coming back, change the question, not the person.
• Return to your original questions every couple of months as a check. The answers change, and so should what you do about them.

Delegate small, and choose with the person in mind

The same attention applies to delegation. Hand over one real piece of work a fortnight, and pick it for the individual. A stretch for the person who is hungry for one. Something safe for the person who is rebuilding confidence.

Agree the outcome, not the method. Agree when you will check in. Then stay out of it. It will come back done differently from how you would have done it, and if it is good enough, it is done.

Have the difficult conversation sooner than feels comfortable

Knowing people as people changes how you handle the hard moments. You can tell the difference between “cannot”, “will not” and “something else is going on”, and you will only find out which by asking.

So raise it early, while it is still small. Do it privately, in a one-to-one. Describe what you saw, not what you assume, then ask what they see. Practise on the small things so that the big ones are not your first attempt.

Expect to be a little clumsy. A clumsy but kind conversation held this week is worth far more than a polished one held next quarter.

Practice is meant to be imperfect

None of this is a technique you master and tick off. You will misjudge a person, pick a poor opening question, or delegate something too big too soon. That is what this stage is for. People forgive a manager who is trying to know them. They do not forgive one who never tries.

Next time, in Part 3, we move into Feedback: how to give it, how to ask for it, and why the most useful feedback you receive in these ninety days will probably be about you.

Feedback is a loop, not a verdict

New managers tend to treat feedback as an event: a performance conversation, a review, a verdict delivered from above. That is the wrong picture. Think of it as a loop. You notice something, you say what you noticed, you listen to what the other person sees, and you both adjust. Then it starts again.

A loop only works when it is small and frequent. Feedback saved for the annual review is not feedback. It is an ambush.

Give it sooner, smaller and kinder than feels natural

In Part 2 you practised the early, private, difficult conversation. Feedback is the same skill applied to everything else, including the good things.

A simple shape holds up under pressure: what I saw, what happened as a result, what I would like to see, and then a question. Keep the first part to observable facts. “The release notes went out without a review” is something you saw. “You were careless” is a verdict, and people stop listening to verdicts.

Notice that two of the five are praise. Aim for specific recognition at least as often as correction. “Great job” is pleasant and forgettable. “The way you split that migration into three safe steps meant we never had an outage” tells someone exactly what to do again.

Then check how it landed, using what you learned in Part 1. Some people want it straight and immediate. Some want a little time to think before they respond. Some want it written down. You asked. Remember what they said.

Ask for it, and start with feedback about you

Here is the part nobody warns you about: the most useful feedback you receive in these ninety days will probably be about you.

Your team already knows how you come across. They know whether you interrupt, whether you rescue too quickly, whether your “quick question” is ever quick. They will not volunteer it, because you influence their pay, their workload and their reputation. The gap in power makes honesty expensive, so you have to lower the price.

Try asking one specific, answerable question rather than “Any feedback for me?”:

• “What is one thing I do that makes your work harder?”
• “What is one thing I could stop doing?”
• “When did I last help you, and when did I last get in the way?”

Then apply the discipline from your own meetings: speak softly, and speak last. Ask the question, and wait through the silence. Somebody always fills it. If you jump in with an explanation, you teach everyone that honest answers get argued with.

When the answer comes, do four things:

• Thank them, without defending yourself.
• Ask one clarifying question so you are sure you understood.
• Do one thing about it, soon and visibly.
• Report back a few weeks later: “You told me I rescue too quickly. Here is what I have tried.”

That last step is the one that matters. Feedback requests that vanish into a void teach people not to bother next time.

If individual conversations feel too exposed for the team, try a lighter route. The One Word Game works as well for “how is working with me?” as it does for a retro. Everyone writes one word, nobody speaks, and you pick a word and ask the author to tell the story behind it. It is playful and non-threatening, and it lets quieter people be heard.

Get feedback from your own manager too

In Part 1 you agreed what good looks like at 30, 60 and 90 days. Day sixty is the checkpoint, and most managers forget to call it.

Book the conversation yourself. Bring your own assessment first: what has gone well, what has not, and what you are unsure about. Then ask three things. Where am I strong that I do not see? Where am I weaker than I think? What should I do differently over the next thirty days?

Sponsors, a note for you. Do not wait to be asked. A new manager who is not getting feedback will assume no news is good news, and it rarely is.

Look at the system, not just the people

Not all feedback is about individuals. Sometimes the right thing to say is that the process is wrong.

By now you have been watching how work flows. Which meetings, reports and checks help your team deliver, and which exist because nobody ever asked why? For each one, ask the question that matters: what problem is this solving? If nobody can answer quickly, you may have found some waste.

Be especially careful with numbers. A measure that helps the team see how they are doing is useful. The same measure used to rank people becomes a stick, and people will optimise for the number instead of the work. Use data to start a conversation, never to end one.

The feedback loop applies to your own habits too. If your team spends an hour a day feeding a tracking system you never open, that is a message about you, and you can fix it. Make sure they have what they need, then get out of the way.

When the feedback stings

Sooner or later you will hear something that stings. You will feel the urge to explain, justify or counter. That urge is normal and entirely human. It is also the moment that decides whether anyone ever tells you the truth again.

Have a stock reply ready: “Thank you. I need some time to think about that. Can we pick it up on Thursday?” It buys you a day, shows you took it seriously, and keeps the door open.

And remember that you are a person having a day. Managers have off days too. It is fine to say so, and it is fine to ask for time. Sharing that honestly does more for trust than a performance of calm.

Feedback never finishes

There is a pattern to these ninety days. You listened, you practised, and now you are being told how it went. Notice that none of it ends. Feedback feeds straight back into foundations: you ask new questions, you adjust expectations, you try again.

That is the cycle working, not a sign you are failing. The managers who stay good are the ones who keep asking.

In Part 4 we reach Mastery: what the first ninety days have really been building, why mastery looks like quiet consistency rather than heroics, and what to do when a new challenge sends you back to the start.

What the first ninety days have really been building

Look back over the series. In Foundations you listened, learned how the work really happens, and agreed what success looks like. In Practice you let the one-to-one grow up, delegated small, and had a difficult conversation sooner than felt comfortable. In Feedback you gave it, asked for it, and learned to sit still when it stung.

None of those were separate skills to tick off. Together they have been building one thing: trust. Your team trusts that you will listen. Your own manager trusts that you will ask. You trust yourself to get things slightly wrong and recover. That is the real foundation, and it is invisible, just as Part 1 promised.

Mastery looks like quiet consistency

Most people expect mastery to look like heroics: the brilliant intervention, the speech that turns a team around. In practice it looks much calmer. It is:

• the one-to-one that happens every week, including the busy ones
• the question you chose for this person, not the one you asked everybody
• the small piece of specific praise that went out on Tuesday, unprompted
• the pause before you reply when feedback stings
• the task handed over and left alone

You will not feel masterful doing these things. You will feel as though you are just doing the job. That is the point. Mastery is what is left when practices become habits, and habits stop taking effort.

Notice it, and celebrate it

New managers are harsh judges of themselves. They remember the meeting that went badly and forget the three that went well. So make progress visible on purpose.

Write down three things you do now that you could not do, or would not have done, ninety days ago. Be specific. “I ask what someone needs before I tell them what I think” is better than “I listen more.” Then tell someone: your own manager, a peer, a coach. Progress nobody acknowledges tends to fade, and acknowledgement is what keeps the habit alive.

When a new challenge sends you back to the start

Here is the honest part. Mastery of one situation does not carry across to every other. A new team, a restructure, a difficult stakeholder, a conversation you have never had before: any of these can leave you feeling like a beginner again.

That is not regression. It is the cycle turning. You find yourself back at Foundations: listening before acting, learning how this particular work happens, agreeing expectations. Only this time you know the route. You recognise the discomfort for what it is, you move through Practice and Feedback faster, and you trust the process because you have already been through it once.

So when the ground shifts, resist the urge to prove you already know. Ask the old questions again. Start small. Expect to be a little clumsy. Experienced managers are not people who never reset. They are people who reset without panic.

Choose your next ninety days

Mastery is not a finish line, so decide what comes next. Pick one practice you want to deepen, and one you have been avoiding. Perhaps it is delegating something bigger, or having the conversation you have been putting off, or asking for feedback from someone further up. Set a date to review how it went.

If you have a coach or a mentor, this is the moment to use them. The most useful questions at this stage are rarely “What should I do?” and more often “What am I not seeing?”

The cycle never really ends

There is a shape to these ninety days. You laid foundations, you practised, you received feedback, and you began to make it habit. Then something changes and you begin again, a little wiser.

That is not a sign that you have failed to master the role. It is what mastering the role looks like. The managers who stay good are the ones who keep listening, keep practising, keep asking how they are doing, and keep celebrating how far they have come.

Thank you for reading the series. If you are working through your own first ninety days, or supporting someone who is, I would be glad to hear how it goes.