Why I Went Back to Study Project Management After Years of Managing Projects

After years of working with projects, I decided to go back and study project management.

It sounds slightly backwards.

Usually, we imagine the process happening in the opposite direction.

You study something.

You get certified.

You start applying what you learned.

You gain experience.

My journey was different.

For years, I was already doing the work: coordinating people, managing timelines, monitoring progress, solving problems, dealing with pressure and taking responsibility for outcomes.

I learned project management by managing projects.

And for a long time, that worked.

Until I realized that experience alone could also become a limitation.

I Learned by Doing First

My experience with projects started in public institutions.

At the beginning, I wasn't thinking about methodologies or project management frameworks.

I wasn't asking myself whether something aligned with a particular theoretical model.

I was thinking about a much simpler question:

What needs to happen to get this done?

That meant coordinating activities, following deadlines, communicating with different stakeholders, identifying problems and finding ways around them.

Over time, the responsibilities increased.

So did the complexity.

I moved from supporting projects to taking greater responsibility for their delivery and eventually managing multiple initiatives.

Much of what I learned came from experience.

Something goes wrong.

You solve it.

A deadline is at risk.

You adjust.

People disagree.

You find a way forward.

A process doesn't work.

You redesign it.

Do that enough times and you develop instincts that no textbook can fully replicate.

But there is another side to learning almost exclusively through experience.

Experience Teaches You What Worked Where You've Been

For much of my career, I worked inside structured institutional environments.

Those environments had their own procedures, regulations, hierarchies, constraints and ways of getting things done.

I became good at operating within those systems.

But when I decided to make a significant career transition, I had to ask myself a difficult question:

How much of what I know is transferable outside the environments in which I learned it?

That question changed how I looked at my experience.

I knew how to manage projects.

But much of that knowledge was practical and intuitive.

I could often tell what needed to happen next because I had encountered similar situations before.

What I had never done systematically was formalize why I approached projects the way I did.

That distinction started to matter.

Because if I wanted to operate effectively across different organizations and industries, relying entirely on patterns learned in one environment was no longer enough.

Knowing How and Understanding Why Are Different Things

Experience is incredibly valuable.

But experience can also create blind spots.

If something has worked repeatedly, we naturally begin to assume that it is the right way to do things.

Sometimes it is.

Sometimes it simply worked because of the environment we were operating in.

Structured learning forces you to examine those assumptions.

It gives names and frameworks to things you may already be doing intuitively.

It exposes gaps you didn't know you had.

And sometimes it challenges habits that years of experience have made feel obvious.

That is why I decided to go back to the fundamentals and study project management formally.

I chose PRINCE2 7, with the initial goal of completing the Foundation level and then progressing to Practitioner.

Not because I was starting from zero.

Quite the opposite.

I wanted to take the practical experience I had accumulated over the years and put a structured framework around it.

Going Back to the Fundamentals Is Not Going Backwards

I think this is something professionals sometimes struggle with.

Once you have accumulated years of experience, going back to study the fundamentals can feel unnecessary.

Maybe even uncomfortable.

You are supposed to already know this.

But experience and structured knowledge solve different problems.

Experience teaches you what happens in reality.

It teaches you how people behave under pressure.

It teaches you that plans change.

It teaches you that stakeholders don't always agree, that priorities move and that the technically correct solution isn't always the practically achievable one.

Structured learning gives you something else.

It gives you a common language.

It gives you frameworks that can travel with you between organizations.

It allows you to compare your instincts with established approaches instead of assuming that the way you've always worked is the only way.

The two are not competitors.

They reinforce each other.

The More Experienced You Become, the Easier It Is to Stop Questioning Yourself

There is another reason I think returning to structured learning matters.

Experience creates confidence.

Usually, that's a good thing.

But enough experience can also create intellectual comfort.

You have solved similar problems before.

You know what usually works.

People start asking you for answers rather than expecting you to ask questions.

And slowly, it becomes easier to rely on what you already know.

That is dangerous.

Especially now.

Technology is changing.

Organizations are changing.

Entire industries are changing.

The skills that made someone effective ten years ago won't automatically make that person effective ten years from now.

So I've become increasingly convinced that professional development shouldn't stop when you become experienced.

In some ways, that is exactly when it becomes more important.

The objective isn't to replace experience with theory.

It is to prevent experience from becoming a closed system.

Certifications Are Tools, Not Destinations

I also don't believe that earning a certification automatically makes someone a good project manager.

A certificate cannot teach judgment.

It cannot replace years of dealing with real people, real deadlines and real consequences.

And passing an exam doesn't suddenly make someone capable of leading a complex project.

But that isn't the point.

For me, studying PRINCE2 is about adding structure to experience.

It's about identifying what I already understand, discovering what I don't and developing a project management language that isn't tied to one organization or one institutional environment.

The certification is evidence that I studied the framework.

The real value is what I can do with that knowledge afterwards.

Experience Should Be a Foundation, Not a Boundary

The biggest lesson I've taken from this process has little to do with any specific project management methodology.

It is about professional growth.

The longer you work in a field, the easier it becomes to define yourself by what you already know.

But what got you here doesn't necessarily determine where you can go next.

My experience gave me a strong foundation.

Going back to structured learning is about making that foundation more transferable.

Because if I rely only on experience, I risk limiting my thinking to the environments I've already experienced.

If I combine that experience with structured knowledge, new frameworks and continuous learning, I expand the range of environments in which I can operate.

And that is ultimately why, after years of managing projects, I went back to study project management.

Not because I needed to start again.

Because I wanted to be able to go further.

contact@romagcompany.com

© ROMAG Company 2026

Privacy policy

Terms and conditions

CONNECT

EXPLORE

About

Journal

Services

Projects

Operated by GEORGESCU ADRIAN-NICOLAE PFA

CUI: 52838515 CIF: RO53355080

Romania