What I Wish I Knew About Project Risks When I Started

Risk management is one of those things that sounds bigger than it is.

Especially when you’re just starting out.

The moment someone mentions “risk register” or “qualitative analysis,” your mind might start blowing.

You start thinking of reports, meetings, maybe even Excel sheets you don’t want to look at. And for a second, you feel like skipping it altogether and just hoping nothing goes wrong.

But here’s the truth… And it took a while for me to understand that.

Risk management is about paying attention. It’s about asking, “What might go wrong?” before you’re already dealing with a mess.

And the best part? You don’t need to be an expert to start doing it well.

You just need a few simple habits. A bit of awareness. And the willingness to write things down before they surprise you.

This post is for you if:

You’re a project manager just getting started
You’ve heard of risk management but never really used it
You’ve been told to make a “risk log” and had no idea where to begin
You want a calm, clear way to bring this into your work

Let’s break it down together. No pressure. No heavy theory. Just real, useful ways to understand and apply this stuff in your projects.

What Risk Really Means in a Project

I know it sounds obvious, but let’s say it out loud anyway.

A risk is something that might happen. That’s it.

It hasn’t happened yet. You’re not in trouble.

It’s just a possibility, something floating in the future that could affect your project.

Now, there are two kinds of risks:

Negative risks are the ones we think about most. Things that could go wrong. Delays. Budget overruns. Scope creep. Supplier issues. You name it.
Positive risks are things that could go better than expected. Maybe a vendor delivers early. Maybe a feature works better than planned. These are called “opportunities,” but let’s not complicate it for now.

The most common question I get from new PMs is this: What’s the difference between a risk and an issue?

Easy answer:

A risk might happen.
An issue is already happening.

If your developer might be out next week, that’s a risk.

If they’re already out and the sprint is affected, that’s now an issue.

Treating everything like an issue is exhausting. But treating everything like a risk lets you think ahead while things are still calm.

Let me give you a simple example.

On one of my first projects, we had a dependency on a third-party system.

We needed access from their team by a specific date, or we couldn’t test on time.

That access hadn’t failed yet, but something made an architect think it could.

So I added this to my notes:

“Risk: access to third-party test environment might be delayed.”

I flagged it in a weekly meeting. We followed up early. We got the access a bit late, but we were ready. Because we saw it coming.

That’s what risk management is. Not a big drama. Just a calm habit of noticing things early.

Now that you know what a risk really is, let’s talk about something nobody explains well: why we avoid talking about them.

And why does that create more problems later?

Why New PMs Avoid Risk Conversations (And Why That’s a Problem)

Let’s be honest. Most people don’t love talking about risks.

And if you’re a new project manager, it can feel even harder.

You don’t want to sound negative. You don’t want to make people uncomfortable. You definitely don’t want to be the one who brings up “what could go wrong” when everyone’s trying to stay optimistic.

I get that. I’ve been there.

But avoiding risk conversations doesn’t make the risks disappear. It just makes them harder to deal with later, when they’ve already turned into real problems.

Here’s what I’ve seen happen over and over.

A new PM wants to show they’re strong. They want to look in control. So they focus on delivery. They push the team forward. But they don’t raise potential risks, because it feels like they’d be admitting doubt or weakness.

Then something happens. A deadline slips. A dependency fails. A key person goes on sick leave at the worst possible time. And suddenly, the question in the room is: “Why didn’t we talk about this earlier?”

That’s not a good feeling.

So let’s name what’s really going on.

You’re Not Being Negative by Naming Risks

This one’s big. Somewhere along the way, a lot of people got the idea that talking about risks is like being the person who always sees the worst in things.

But that’s not what this is. This isn’t about fear. It’s about responsibility.

Calling out a risk doesn’t make you paranoid. It makes you prepared.

It tells your team, “I’m thinking ahead.” It tells your stakeholders, “I care enough to be real.” And it tells yourself, “I’m not just reacting, I’m leading.”

That’s not negative. That’s the job.

People Respect PMs Who Think Ahead

Here’s a little truth from experience.

The PMs who last are not the ones who rush toward every goal like nothing could possibly go wrong.

The ones who last are the ones who know things might go wrong and plan for it.

When you talk about risk in a thoughtful way, people notice.

You don’t need to be dramatic. You don’t need to be loud. You just need to be steady.

When you say things like,

“There’s a small risk with this timeline, and I’m keeping an eye on it,” you’re not causing panic. You’re creating confidence.

It shows you’re paying attention. It shows you care. And people start coming to you when they notice something, too, because they know you’ll listen.

A Risk Management Framework for Dummies

PMI has a detailed process for risk management, and it’s good. It works.

But if you’re new to project management, or even just managing your first serious project, it can feel like a lot.

What helped me was boiling it down into something simple. Something I could remember even when I was tired or the project was getting messy.

I’ve used this five-step approach many times. It’s clean, human, and it fits any kind of project. You can use it with a full team or just for yourself.

Let me walk you through it.

Step 1: Spot the Risk

This is about awareness. Just noticing what could go wrong. No need to overthink it.

Look at your project and ask:

What are we depending on that might fail?
What do we not control?
What could delay us, block us, or surprise us?

You don’t need to solve it yet. Just write it down.

Talk to your team. People working closely with the problem often see risks before anyone else. And they’ll usually tell you, if you’re open enough to ask.

If something caused problems before, it’s worth considering again. Patterns repeat more often than we admit.

Step 2: Write It Down

This sounds basic, but it’s the part most people skip.

You don’t have to call it a “risk register.” You can call it your “uh-oh list” if that feels better. The point is to make it visible.

Use a simple format:

Risk
Likelihood (low, medium, high)
Impact (low, medium, high)
Plan (what we’ll do if it happens)

When you write risks down, you make them easier to track. You also show your team that you’re thinking about more than just the next task.

People feel safer when they know someone is looking out for them.

Step 3: Think Through the Impact

Now you’ve got a list. It’s time to look at what’s actually worth worrying about.

Not all risks are equal. Some are just noise. Others can throw your whole plan off track.

Ask yourself:

If this risk happened, how bad would it be?
Would it affect the timeline, budget, or trust?
Can we handle it easily, or would it hurt?

You don’t need to build a mathematical formula. Just use your judgment. If a risk feels both likely and painful, that’s the one to focus on.

PMI calls this “qualitative risk analysis.” But all you need is common sense and a bit of honesty.

Step 4: Make a Plan

For each serious risk, come up with a simple action.

Something you’ll do now or later to reduce the pain if it shows up.

Some ideas:

Add buffer time
Ask for a backup resource
Document the steps early
Schedule a checkpoint sooner
Escalate before it becomes urgent

You can also decide to accept some risks. That’s okay.

Not every risk needs a plan. But if you do accept one, make that choice clearly. Say it out loud, write it down, and move forward.

What matters is that it’s not a blind spot anymore.

Step 5: Keep It Alive

Risk logs don’t help if they just sit in an Excel sheet.

Every week, take two minutes to glance at your list. Ask:

Did any risks happen?
Are there new ones?
Does anything need updating?

If you’re leading a team, review it together once in a while. Keep it light. Keep it real.

And when someone raises a new risk? Thank them.

You’re building a team that thinks ahead, and that’s a rare thing.

It doesn’t require training. It doesn’t need tools. You can do it on a sticky note or in a spreadsheet. What matters is that you do it.

And when you do it often, it becomes part of how you lead.

Not because PMI says so. But because your projects start feeling less like a guessing game and more like a plan with a pulse.

Totally Normal Beginner Mistakes

I’ve never met a project manager who got risk management right from the start.

Most of us learn by messing things up a little first.

And you know what? That’s fine. These small mistakes are part of the work.

They’re signals that you’re paying attention and getting better.

Let me walk you through a few of the most common ones I see, and sometimes still catch myself making.

Mistake 1: Only Noticing Risks When It’s Too Late

This one is classic. You’re so focused on getting things done that you don’t stop to ask, “What might stop us?”

Then something happens. A dependency fails. A decision gets blocked. And suddenly you’re reacting, scrambling, and wondering why nobody saw it coming.

The fix? Make risk part of your weekly rhythm. You don’t need to turn it into a project. You just need to stay curious.

Ask yourself, “What could go wrong?” before the problem arrives.

Mistake 2: Creating a Risk Register Nobody Reads

I’ve seen beautiful risk logs. Color-coded. Sorted. So detailed, they looked like they were built for an exam.

But nobody used them.
Not the team.
Not the sponsor.
Not even the person who built it.

A risk register only works if it’s alive.

If it lives inside the project, not next to it.

Keep it simple. Keep it visible. And bring it into your regular check-ins, even if it’s just one sentence.

Something like, “We’re watching two risks this week, but no changes since last time.”

That one sentence can go a long way.

Mistake 3: Treating Risk Like a Task Instead of a Habit

A lot of people treat risk management like a one-time thing.

You fill out a log at the start of the project, maybe tick a box in a process checklist, and move on.

But risks don’t stop showing up just because your document is done.

Treat risk management like brushing your teeth.

Small, regular actions that prevent bigger problems later.

And the more you do it, the less scary it feels.

Conclusion: You Don’t Need to Predict Everything. You Just Need to Pay Attention.

Risk management is about staying awake. Looking around once in a while. Asking yourself and your team what could change, and how you’ll handle it if it does.

That’s what good project managers do. Not because someone told them to. But because they care enough to lead with their eyes open.

So if you’ve made it this far and you’re thinking, “Okay, I want to try this.”
Start small.

Pick one project. Make a simple list of three risks. Talk about them in your next meeting. Ask your team what they’re worried about. Add their ideas to the list.

You’ll feel the shift almost immediately. Less guessing. More clarity. And a little more peace of mind.

And if something does go wrong, which it will, from time to time, you’ll be ready.
Not surprised. Just ready.

Let’s keep learning. One clear step at a time.

Do you want to deep dive into content that will transform your career, management, and leadership?

Check the premium content below, helping people grow in their careers, become great leaders, and manage work and life better:

Meller Notes: My weekly newsletter for career, management, and book lessons.
Project Management Compass: Premium content on Project Management
You Visible: A clear path to building your professional presence and branding.
YouTube Channel: To a deeper connection on career, management, and leadership.

I am incredibly grateful that you have taken the time to read this post.

I was hoping you could support my work by sharing my content with your network using the sharing buttons below.

Want to show your support and appreciation tangibly?

Creating these posts takes time, effort, and lots of coffee, but it’s totally worth it!

If you’d like to show some support and help keep me energized for the next one, buying me a virtual coffee is a simple (and friendly!) way to do it.

Do you want to check previous Book Notes?

Do you want to check previous Articles?