7 Steps to Run a Project Without Project Management Training!
Have you ever been called into your boss’s office, praised for doing a great job, and then suddenly told, “We want you to run a project”?
On the outside, you say, “Absolutely.”
On the inside, you’re thinking, Wait… I’m not a project manager. I have no idea how to run a project.
If that sounds familiar, you’re not alone.
A lot of capable people get asked to lead projects because they are organized, reliable, and good at getting things done. But running a project is about much more than managing a task list. You’re also managing people, expectations, decisions, deadlines, competing priorities, and unexpected changes.
And when no one has actually taught you how to do that, even a smart, capable person can feel overwhelmed.
The good news? You do not need to figure it all out at once.
Below are seven practical steps you can take when you’ve been asked to run a project but nobody trained you how.
Key Takeaways
- Don’t try to keep everything in your head…capture it in one place.
- Identify the sponsor or senior person who owns the project.
- Clarify the actual goal before you start building the plan.
- Define what’s in scope and what’s out of scope to avoid scope creep.
- Break the work into smaller, manageable pieces.
- Create visibility so the whole team can stay aligned.
- Ask for guidance early, before small problems become big ones.
1. Don’t Try to Keep Everything in Your Head
When you’re learning how to run a project, it’s easy to think you should be able to remember every deadline, conversation, decision, and follow-up.
But that approach becomes overwhelming quickly.
Instead, start by putting everything you know in one place. And not in an email.
Capture:
- What you’re being asked to deliver
- Deadlines already mentioned
- Who is involved
- What decisions still need to be made
- What questions are still unanswered
You do not need to have everything figured out yet. The goal is simply to capture what you know, what you don’t know, and what you need to find out.
That information becomes the foundation of your Project Charter. It’s the heartbeat of the project. It helps define why the project is happening, what it needs to achieve, the key deliverables, the priorities, the constraints, and the people involved.
If you’re not sure where to start, a beginner’s planning checklist can help you clarify and document the right things before kickoff.
Before you kick off your project, grab our free checklist that walks you through what to clarify, prepare, and document before your kickoff meeting: https://www.slayprojectmanagement.com/checklist
2. Find Out Which Senior Person Owns the Project
One of the first things to understand is that you are not doing this alone.
There is usually a senior person who wants the project to succeed. In project management, that person is often called the sponsor.
Your sponsor is not there to run the project for you. But they should help you understand the bigger picture:
- Why the project matters
- Who needs to be involved
- What’s happening behind the scenes
- Where you may need support or decisions
Without a clear sponsor, it’s very easy to get stuck chasing answers or making decisions that are not yours to make.
So confirm who your sponsor is and book time with them. Once you know who can give you direction, the next step is understanding what the project is actually supposed to achieve.
3. Clarify the Goal Before Building the Plan
Before you jump into tasks, get clear on what the project is actually supposed to solve or achieve.
Ask questions like:
- What problem are we solving?
- What outcome do we want?
- Why does this project matter?
- How does it support organizational goals?
- How will success be measured?
Sometimes the original request is much less clear than it first sounds.
For example, “improve the onboarding process” could mean:
- reducing training time
- creating better materials
- helping new employees become productive faster
Those are very different goals, and they would lead to very different project plans.
Once the goal is clear, talk about governance — who can make decisions, what needs sponsor approval, and how updates will be shared. Then capture it all in your Project Charter so you have a clear objective and a clear decision path.
Related: How to Write a Project Charter
4. Define What’s In and What’s Out
This step is critical.
A lot of projects struggle because people understand the big goal, but not the boundaries of the work.
Defining what’s in and what’s out helps you:
- uncover hidden details
- build the right Work Breakdown Structure
- protect the project from scope creep
- identify what might be missing early on
Scope creep happens when new requests keep getting added and the project slowly becomes bigger than anyone originally agreed to. That doesn’t mean scope can never change. It means change should be intentional.
That’s where change control comes in. If something new is requested, review the impact and decide whether it should be added before the team starts doing extra work.
Also, asking what’s in and what’s out can reveal important missing pieces:
- Do you need more resources?
- Are key people missing?
- Are assumptions untested?
- Are risks hiding in the details?
The clearer the scope, the easier it is to build the right plan and keep the work on track.
Related: How To Define Project Scope In Project Management
5. Break the Work Into Manageable Pieces
Once you know the scope, do not try to plan the entire project all at once.
That’s a fast way to get overwhelmed.
Instead, break the work into smaller pieces:
- Identify the main deliverables
- Break each deliverable into smaller tasks
- Assign ownership
- Set deadlines
- Identify dependencies
For example, if the project is to improve onboarding, one deliverable might be updated training materials. To complete that deliverable, you might need to:
- review the current materials
- gather feedback
- draft updates
- get final approval
This is where a Work Breakdown Structure (WBS) helps. It gives you a simple way to organize the project so nothing important gets missed.
Once the work is broken down, move it into an action plan. That way everyone knows what needs to happen, who owns it, and when it’s due.
The goal is not to map every tiny detail on day one. The goal is to make the work clear and manageable.
6. Create Visibility and Follow-Up
Once the work is broken down, put the action plan somewhere the whole team can access it.
Everyone should be able to see:
- what needs to be done
- who is responsible
- when it is due
- whether anything is delayed or stuck
Make sure the team knows how to use it. Ask people to update their own tasks and add notes when something changes. That way, you are not constantly chasing people down to figure out what is happening.
Your action plan should become one of the main tools you use to run the project. Use it in team meetings to guide the conversation and keep everyone focused.
When a deadline changes or a decision affects the plan, update it so everyone is working from the same information.
This creates accountability without making you feel like you need to micromanage everyone.
7. Ask for Guidance Before Things Go Sideways
When nobody has trained you how to run a project, it’s easy to feel like you should figure everything out on your own.
But asking for help is part of leading well.
Some situations are not straightforward:
- an executive pushes back
- a team member keeps missing commitments
- the project gets stuck because no one wants to decide
Don’t wait until a small issue becomes a big problem.
Talk to someone with project experience while there is still time to work through it. Explain what’s happening and what you’ve already tried. Then ask for help thinking through the next step.
That person might be your sponsor, your manager, or an experienced project lead.
Learning how to run a project is not just about documents and process. It is also about handling people problems and unexpected situations with confidence.
Related: Project Derailed? Get Projects Back on Track
Final Thoughts
If you’ve been asked to lead a project and no one trained you, don’t panic.
You do not need to know everything right away. You just need a simple structure to follow.
Start by capturing what you know. Find your sponsor. Clarify the goal. Define scope. Break the work into manageable pieces. Create visibility. And ask for help early.
That’s how you build confidence and reduce chaos — one step at a time.
FAQ
What should I do first if I’ve been asked to run a project?
Start by writing down everything you know in one place. Don’t rely on memory or scattered emails.
Who is the sponsor in a project?
The sponsor is the senior person who owns the project, supports it, and can help you make decisions when needed.
Why is defining scope so important?
Because it helps you understand exactly what is included and what isn’t, which prevents scope creep and confusion later.
What is a Work Breakdown Structure?
A WBS is a way of breaking a project into major pieces and then into smaller tasks so the work is easier to manage.
What if I feel overwhelmed by the project?
Focus on one step at a time and ask for guidance early. You do not have to figure everything out alone.
