If you want to become a really good project manager, you need to learn how to actually manage projects — not just talk about them.
After more than eight years managing multimillion-dollar initiatives in banking, retail, security, and manufacturing, I’ve learned that most people overcomplicate project management.
The truth is: almost every successful project — no matter the industry — can be broken down into a few simple parts.
Today, I’ll show you a 5-step project management framework that you can use to confidently manage any project, even if you’ve never done it before.
🧠 Step 1: Get Crystal Clear on the Objective
Every project starts with a why.
Before diving into timelines, meetings, or budgets, ask yourself:
“What’s the real objective of this project?”
The objective defines why the project exists and what success looks like.
Example
When I was managing a project at Walmart, our goal was to replace paper price labels with digital electronic price tags across hundreds of stores.
The objective wasn’t “install hardware.” It was to automate pricing updates across all locations — saving time, cutting costs, and improving accuracy.
When you start with a clear objective, every decision and task after that becomes easier.
Without one, you’ll drown in details that don’t matter.
🧩 Step 2: Define the Scope
Once you understand the objective, the next question is:
“What exactly are we doing — and what are we not doing?”
That’s your scope. It defines the boundaries of your project.
If you skip this, you’ll fall into the trap every new PM faces: scope creep — when your project keeps expanding until it’s unmanageable.
Example
In that same Walmart project, I was responsible for deploying the tech stack inside new stores.
My scope included installing:
-
Self-checkout systems
-
Point-of-sale terminals
-
Routers and Wi-Fi infrastructure
-
Fresh produce scales
-
Online grocery equipment
It did not include replacing older tech from legacy stores.
Drawing that line early helped me stay focused, deliver on time, and avoid getting buried in “nice-to-have” requests.
🗓️ Step 3: Set the Timeline
Without a deadline, it’s not a project — it’s a hobby.
A good project manager defines when things need to happen.
If no one gives you a deadline, create one yourself. This triggers what’s known as Parkinson’s Law — “work expands to fill the time allotted.”
Give yourself six months, and it’ll take six months.
Give yourself thirty days, and you’ll find a way to get it done in thirty.
Pro Tip
Every project should have:
-
A start date
-
An end date
-
Milestones that mark progress along the way
These dates turn abstract goals into accountability.
💰 Step 4: Identify the Resources
Resources are the fuel that make your project move — money, people, and tools.
You might have the perfect plan, but if you don’t have the resources to execute, you’ll stall.
Example
In a tech deployment project, I was managing remotely.
I relied on an on-site IT partner who acted as my eyes and ears inside the store. That one person was a critical resource — without him, the project couldn’t have progressed.
Every project has three essential ingredients:
-
A defined timeline
-
A clear scope
-
Sufficient resources
If one of these is missing, you’re not managing a project — you’re guessing.
And remember: resource planning isn’t just about counting heads or dollars.
It’s about ensuring that the right people, with the right skills, are working at the right time.
⚠️ Step 5: Manage Risks, Issues, Dependencies, and Assumptions
Even the best-planned project can go sideways.
That’s why experienced project managers constantly monitor four key elements:
1. Risks
These are potential problems that might happen.
Example: During the Walmart rollout, one risk was hardware delays from China.
We mitigated it by ordering early and tracking shipments closely.
2. Issues
These are problems that are already happening.
In one project, we started without an on-site IT technician — a major issue.
Identifying it early allowed us to solve it fast before it derailed the project.
3. Dependencies
These are things outside your control that you rely on.
For example, we depended on an external vendor (Unisys) to handle electrical and network cabling.
Their schedule directly affected ours — so we tracked that dependency carefully.
4. Assumptions
These are beliefs you’re operating under — things you assume to be true.
For instance, we assumed vendor quotes wouldn’t change before purchase orders were approved.
If those prices changed, it would blow up the budget. So we regularly validated our assumptions throughout the project.
When you identify risks, issues, dependencies, and assumptions early, you stay in control — even when things don’t go as planned.
🧭 Putting It All Together
Here’s the complete Project Management Framework in one view:
| Step | Focus | Question to Ask |
|---|---|---|
| 1 | Objective | Why are we doing this? |
| 2 | Scope | What exactly are we doing (and not doing)? |
| 3 | Timeline | When does it need to be done? |
| 4 | Resources | Who and what do we need? |
| 5 | R.A.I.D. (Risks, Issues, Dependencies, Assumptions) | What could go wrong or impact success? |
When you approach every project using this framework, you’ll sound — and perform — like a true professional.
🚀 Final Thoughts
Managing projects isn’t about jargon or certificates.
It’s about clarity, communication, and control.
You don’t need a PMP to be a great project manager.
You need a process that keeps you grounded — and this 5-step framework will do exactly that.
If you’re serious about building a career as a six-figure project manager, this is just the beginning.
Inside The Eddie System™, I teach this framework hands-on using real project simulations — from retail rollouts to IT migrations — so you can build experience that actually gets you hired.
👉 Join the community at skool.com/tesl and start managing your first real project today.
Having the right templates makes applying any framework easier — Get 90+ PM templates in the PM Briefcase.
A framework is only as good as the practice you put behind it. Inside The Eddie System, you apply frameworks like this on 27+ real project simulations — and build a portfolio of PMO-grade deliverables in the process.
