8 Signs You're Ready for a Leadership Role at Work

The ranking criterion is simple: how much each sign predicts whether you survive the first ninety days in the role, weighted by how hard it is to build after you are promoted. Things you can only practise safely while you are still an individual contributor rank higher. Things you can learn on the job, with a manager coaching you, rank lower.

That ordering comes from how the job actually changes. Once you have the title, your calendar fills with other people's problems, and the quiet practice time disappears. Giving your first piece of hard feedback is much easier when it isn't also a formal performance conversation with a record attached.

Two honest caveats before you read on.

First, "leadership role" means different things at different employers. At a 30-person company it may mean running a team of three with no budget authority. In a large matrixed organisation it may mean managing managers, or leading a function with no direct reports at all. Ask for the actual job description and the competency framework before you decide you match it.

Second, the downside is real and people rarely say it out loud. You stop doing the craft work you were promoted for and start doing calendar work, hiring work, and conflict work. Your output becomes other people's output, which is slower and harder to feel good about. Some people move into management, dislike it, and move back — which is normal and not a failure, but is easier to do early than three years in. Pay also doesn't always jump straight away: leadership pay is usually a base salary plus a bonus or incentive tied to team or company results, set against an internal band, and in some structures a senior individual contributor sits in the same band as a first-line manager. Ask HR how the bands work at your employer, and check the BLS Occupational Outlook Handbook for the broader picture in your occupation and state.

One more thing that varies: the rules around hiring, discipline and termination differ by state and by country, and your employer's HR policy sits on top of them. Treat your HR business partner as the person to ask, not a guide like this one.

Time ranges assume you are doing this alongside a full workload. The spread depends mostly on how often the opportunity comes round — a team that plans weekly gives you ten times the reps of a team that plans twice a year.

1. People bring you problems before they escalate

This is the strongest signal because it can't be self-reported. Colleagues route questions to you when they trust that you will do something and won't make them look bad. If that is already happening, you are doing the informal half of the job.

To build it, block a recurring 30-minute slot each week, tell three or four people it exists, and close the loop on everything raised in it within a week. The habit takes about three to six months to become visible; it is faster on a co-located team and slower if most contact is asynchronous.

On a resume, this shows up as scope, not sentiment: "first point of contact for [process] across [number] teams." In an interview, tell the story in sequence.

Interview answer

"[Colleague] came to me when [issue] was still small. I checked whether it was a one-off, found it had happened twice before, and brought a short written fix to [manager] instead of escalating the incident. We changed [process] and it stopped recurring."

2. You own an outcome you cannot deliver alone

Leadership is delivering through people who don't report to you. The test is whether you have ever been accountable for something where your own effort was not enough.

Build it by volunteering to run one cross-team project end to end: a written scope, named owners, dates, and a weekly update you send yourself. One project per quarter is a realistic pace. If you want formal recognition for this, the Project Management Institute's PMP is the common route — PMI requires a minimum amount of unique, non-overlapping professional project management experience, with different thresholds depending on whether you hold a secondary degree, a four-year degree, or a degree from a GAC-accredited program (Project Management Institute, undated). PMI also requires documented contact hours of formal project management education unless you are an active CAPM holder, in which case that requirement is waived (Project Management Institute, undated), and the experience must be accrued within a set number of consecutive years before you apply (Project Management Institute, undated). Check PMI's current handbook for the exact thresholds before you plan around them.

Show it as a line with a deliverable and a date, not a list of meetings attended.

3. You give feedback that changes behaviour

Most first-time managers underestimate this one and then avoid it for months. The sign is not that you are comfortable criticising people; it is that your feedback is specific enough to act on and lands without blowing up the relationship.

Practise with one piece of feedback a week, written down first in three parts: the situation, the behaviour, the impact. Two to four months of this makes the conversation routine. Ask for it as well — a manager who has never had their own feedback challenged tends to deliver it badly.

Interview answer

"[Teammate] was shipping work that missed [requirement]. I showed them two specific examples, explained what it cost [downstream team], and agreed we'd check the next three together. By the third, the checks weren't needed."

4. You plan other people's work, not just your own

Planning for yourself is estimating. Planning for a team is sequencing: dependencies, handoffs, who is out next month, what gets dropped when something slips.

Build it by taking over your team's sprint board or quarterly planning document and running the sequencing conversation. Two to six months, depending on how often your team plans. Keep the version where you were wrong — being able to say what you misjudged and what you changed is more convincing than a clean record.

On a resume: "planned and sequenced [team]'s quarterly roadmap across [number] workstreams."

5. You stay useful in conflict

This is where new managers most often come unstuck, and it is the hardest sign to fake. The question is whether you can sit in a disagreement between two people who both have a point and get to a decision without either of them feeling steamrolled.

Build it by facilitating one contested decision a month — a technical trade-off, a priority clash between teams — and writing a short decision record afterwards saying what was decided, by whom, and what was rejected. Expect six to twelve months before this feels normal.

If the conflict involves people issues rather than work issues, the formal route is HR credentialing. SHRM notes that SHRM-CP candidates do not need an HR title, a degree, or previous HR experience to apply (Society for Human Resource Management, 2024-11-26), which makes it accessible from outside the function; SHRM-SCP eligibility, by contrast, requires a history of strategic-level HR or HR-related duties, or holding SHRM-CP while working in or moving into a strategic-level role (Society for Human Resource Management, 2024-11-26).

6. You have made someone else productive

Onboarding, training and mentoring are the closest thing to a rehearsal for the job. If someone has become competent partly because of you, you have evidence that your judgement transfers.

Ask your manager to let you own the next new hire or intern's first 30 days, against a written plan: what they should be able to do unsupervised by day 10, day 20, day 30. One cycle takes four to eight weeks. Do it twice and you will notice how much of your first plan was wishful.

In an interview, name what the person could do at the end that they couldn't do at the start.

7. You decide with incomplete information and own the outcome

Managers rarely get the full picture. The sign is that you can make a call at seventy percent confidence, say out loud that it might be wrong, and not relitigate it every week.

Build it with a decision log: for each call, write what you knew, what you chose, what you expected, and revisit it in a month. Six months gives you enough closed loops to speak about it credibly. The honest version of this sign includes a decision that went badly and what you did about it.

Interview answer

"We had to choose [option A] or [option B] without knowing [unknown]. I chose [option A] because [reason], told the team what would make me reverse it, and set a check at [date]. It turned out to be wrong on [point], so we switched and lost about [time] rather than a quarter."

8. You can explain the work in business terms

You will be asked to justify headcount, defend a deadline, or explain a delay to people who do not understand the detail. If you can only describe the work in your team's internal vocabulary, those conversations go badly.

Rewrite your team's weekly status update around three things: what changed for the customer or the business, what it cost in time or money, and what risk is now higher or lower. Four to eight weeks of doing this will change how you talk about your own work too.

On a resume, this is the difference between "migrated [system]" and "migrated [system], cutting [manual process] from [X] hours a week."

Work on two signs at a time, not eight. Pick the ones your current role actually gives you reps at.

Then do three concrete things:

1. Ask your manager for the written competency framework or promotion criteria for the leadership level you want, and mark which rows you already have evidence for.
2. Book a 30-minute conversation with someone one level above you who was promoted in the last two years, and ask what surprised them in month one.
3. Write your evidence down as you go — project, date, who was involved, what changed. Reconstructing it eighteen months later is much harder than keeping a running file.

If your employer has no written criteria at all, that is useful information: ask your HR business partner what the bands and titles actually are, because an unwritten ladder usually means promotion depends on one person's opinion.