You don't need to lead a companywide initiative to prove that you can lead. Most management careers begin with smaller opportunities that are easy to overlook.
Four ways to start:
- Volunteer to run the weekly team meeting for a month.
- Take over the project plan nobody else wants to own.
- Document the one process that still only lives in your head.
- Help your team get ready for the next big presentation.
None of those come with extra pay or a new title, but they put you in the room doing the work managers do every day: clarifying expectations, organizing information, following up when something's incomplete. That's most of what the job actually is, not busywork around the edges of management.
What actually matters is learning to create progress through other people, not stacking up impressive sounding assignments. That takes more than enthusiasm, it takes structure: a goal, a deadline, and someone who owns each piece.
Agree on the finish line first. Before you take on a project, make sure everyone agrees on the goal, the deadline, and who owns what. If it's ambiguous, write down your own understanding of it and get the group to confirm that instead of assuming everyone's picturing the same finish line.
"I'd like to take this on. Here's what I think done looks like, let me know if that matches what you had in mind before I start."
Don't let confusion sit. Once it's underway, don't let confusion sit. If you notice two people working off different assumptions about scope, say so at the next check in rather than waiting for the deadline to expose it the hard way.
Ask what worked. When it wraps, actually ask what worked and what didn't: was the timeline realistic, was ownership clear, did the communication plan help or just add meetings. Skip that step and the next project repeats the same mistakes.
"Quick retro before we move on: what actually worked here, what would we do differently, and is there anything we should fix before the next one?"
A small project can demonstrate that you know how to:
Before the work. Define a goal, break work into manageable steps, assign ownership, identify risks.
During. Coordinate different priorities, communicate expectations, follow up without micromanaging, resolve disagreements.
After. Recognize contributions, learn from the outcome.
Look for friction. Don't wait for someone to hand you a perfect leadership opportunity. Look for friction in the normal flow of work. A recurring meeting with no clear outcome, a process that causes repeated errors, or a project with unclear ownership may be an opportunity to practice leadership. Start small enough that you can succeed, but choose work that involves other people.
Run things. Organizing a team meeting, creating a project timeline, preparing a team presentation, managing a shared deadline, taking responsibility for a recurring team report.
Teach and document. Training a new employee, documenting a recurring process, creating a checklist, creating an onboarding guide, organizing a retrospective after a project.
Connect and decide. Coordinating a cross functional task, leading a brainstorming session, helping resolve a workflow problem, coordinating a customer response, facilitating a decision between competing options.
Don't volunteer for everything. Choose opportunities that are visible, useful and realistic alongside your existing responsibilities. A poorly managed extra assignment can hurt your reputation more than it helps.
Use this when you are asked to coordinate a project.
Project goal: What are we trying to accomplish?
Business reason: Why does this matter, and what problem will it solve?
Deadline: When must the work be completed?
Responsibilities: Who owns each task?
Dependencies: What must happen before another task can begin?
Risks: What could delay the work or reduce its quality?
Communication plan: How often will we check in, and where will updates be shared?
Decision process: Who makes decisions if the group cannot agree?
Definition of success: How will we know the project worked?
Send a short update using this structure. It makes your coordination visible without creating unnecessary meetings.
Completed:
In progress:
Next steps:
Risks or blockers:
Decisions needed:
Owners and dates:
Ask these when the project ends.
What outcome did we achieve?
What worked well?
Where did confusion or delay occur?
What should we repeat?
What should we change?
What did I learn about coordinating people?
What recommendation should we carry into the next project?
A project that only requires you to work independently may demonstrate competence, but a project involving several people gives you more opportunities to demonstrate leadership.
This week: find one meeting or process with no clear owner and send the volunteering script from above.