PRINCE2 Beyond Process: The Human Side of Transformation

Lena: Hey everyone, welcome back to another personalized podcast from BeFreed-I'm Lena, and I'm absolutely thrilled to dive into today's conversation with my co-host Eli about something that's reshaping how we think about organizational transformation.

Eli: And I'm Eli! Lena, I have to say, I'm buzzing with excitement about this one. We're talking about PRINCE2 Foundation, but not in the way most people think about it. We're exploring how people, change management, stakeholders, and culture all come together to create truly successful transformations.

Lena: Exactly! It's fascinating how we often get caught up in the technical side of project management-the processes, the documentation, the governance-but what really determines success is the human element. How do we get people to actually embrace change?

Eli: You know, that's such a crucial point, and it reminds me of something I was reading in "The Practice of Adaptive Leadership." The authors talk about how most leadership failures don't happen because people are incompetent or have bad intentions. They happen because we treat every problem like a broken machine that needs fixing, when what's actually required is asking people to change how they think and what they value.

Lena: That's so true! And when you look at PRINCE2, it's brilliant at providing structure and control, but as I was diving into the material on PRINCE2 change management from Prosci, I realized there's this critical distinction we need to make. PRINCE2's change management is about managing technical changes through their five-step process, but organizational change management-that's about the people who need to adopt the solution.

Eli: Right! It's like having the most beautifully engineered car in the world, but if people don't know how to drive it or don't want to drive it, you're not going anywhere. The technical delivery is just one piece of the puzzle.

Lena: And that's where things get really interesting when we start thinking about organizational cultures. I was reading David Hinde's white paper on tailoring PRINCE2 to different cultures, and he makes this point that culture literally eats strategy for breakfast. You can have the most perfect PRINCE2 implementation, but if it doesn't fit your organizational culture, you're fighting an uphill battle.

Eli: You've hit the nail on the head there, Lena. And it connects beautifully with what Zachary Wong discusses in "The Eight Essential People Skills for Project Management." He argues that technical expertise alone won't make you successful-your ability to understand and influence human behavior determines your ultimate impact.

Lena: That's fascinating! What does that look like in practice?

Eli: Well, Wong introduces this concept called "The Wedge"-it's a three-level diagnostic framework where you have management at the top, work teams in the middle, and individual contributors at the base. When you're dealing with performance issues, you need to identify whether the problem exists at the individual, team, or management level. You can't just apply a one-size-fits-all PRINCE2 approach.

Lena: So you're saying that even within a structured methodology like PRINCE2, we need to be reading the human landscape differently depending on where the issue is coming from?

Eli: Exactly! And here's where it gets really interesting-Wong talks about this "ice cream cone" concept where everyone carries an invisible attitude indicator. The upper cone represents positivity, the lower cone negativity, and the topping represents feeling valued and accomplished. As project leaders, we need to keep people's "cones up" through recognition, empowerment, and making them feel valued.

Lena: I love that visual! It makes me think about how PRINCE2's role-based approach-with the Executive, Project Manager, Senior Users, and Senior Suppliers-could actually be leveraged to create those positive experiences. But only if we're thinking about the human dynamics, not just the governance structure.

Eli: Absolutely, and this is where the cultural aspect becomes so critical. When I was reading about tailoring PRINCE2 to organizational cultures, it struck me how different environments require completely different approaches. A large, process-driven corporate environment needs PRINCE2 applied very differently than a young, dynamic startup.

Lena: That makes so much sense. Can you give me an example of what that might look like?

Eli: Sure! Think about documentation requirements. In a traditional finance or engineering company, detailed documentation might be welcomed and expected-it provides security and clarity. But in a creative media environment, excessive documentation could be seen as bureaucratic overhead that stifles innovation. You'd need to tailor PRINCE2's documentation requirements accordingly.

Lena: Right, and that connects to something from "Change the Culture, Change the Game." Roger Connors and Tom Smith talk about how experiences shape beliefs, which drive actions and produce results. If your PRINCE2 implementation creates experiences that reinforce negative beliefs about bureaucracy or micromanagement, you're actually undermining your own success.

Eli: That's such a powerful insight! They introduce this concept of operating "Above the Line" versus "Below the Line." Above the Line means taking accountability through four steps: See It, Own It, Solve It, and Do It. When people feel empowered rather than controlled by processes, they naturally move above the line.

Lena: So the question becomes: how do we implement PRINCE2 in a way that creates "Above the Line" experiences rather than "Below the Line" resentment?

Eli: That's where adaptive leadership becomes crucial. The authors of "The Practice of Adaptive Leadership" make this distinction between technical problems and adaptive challenges. Technical problems have clear solutions-like fixing a broken system. But adaptive challenges require people to change their priorities, beliefs, and habits.

Lena: And most organizational transformations involve adaptive challenges, don't they?

Eli: Exactly! Think about implementing new technology. The technical part-installing software, configuring systems-that's straightforward. But getting physicians to change how they document patient care, or engineers to shift from individual work to collaborative processes? That's adaptive, and it requires a completely different approach.

Lena: This is making me think about PRINCE2's stage-based approach in a new light. Those stage boundaries aren't just control points for the Project Board-they could be opportunities to assess how well people are adapting to change, not just whether deliverables are on track.

Eli: Brilliant connection! And here's something fascinating from the adaptive leadership research-you need to maintain what they call "productive disequilibrium." Too comfortable, and no change happens. Too much pressure, and people panic and retreat. It's like a pressure cooker-you need enough heat to transform the ingredients without causing an explosion.

Lena: So as project managers using PRINCE2, we're not just managing scope and schedule-we're managing the emotional and psychological journey of change. That's a completely different skill set.

Eli: Which brings us to this crucial integration challenge. Prosci's research shows that organizations integrating change management with project management are 17% more likely to meet or exceed their objectives. But integration isn't just about running parallel workstreams-it's about fundamentally rethinking how we approach project delivery.

Lena: What does that integration look like in practice? How do you blend PRINCE2's structured approach with people-centered change management?

Eli: Well, one powerful model is Prosci's ADKAR framework-Awareness, Desire, Knowledge, Ability, and Reinforcement. These represent the five outcomes every individual must achieve for change to be successful. You can map these directly to PRINCE2 stages. Awareness and Desire should be addressed early in project initiation. Knowledge and Ability align with training and go-live milestones. Reinforcement happens during project closure and beyond.

Lena: That's such a practical way to think about it! Instead of treating change management as something that happens alongside PRINCE2, you're embedding it into the methodology itself.

Eli: Exactly! And this connects back to the cultural piece. In some cultures, you might need to spend more time building Awareness and Desire because hierarchy and consensus-building are important. In other cultures, you might be able to move quickly to Knowledge and Ability because people are comfortable with rapid change.

Lena: It's like PRINCE2 provides the skeleton, but culture and change management provide the muscle and nervous system that make it actually work.

Eli: That's a perfect analogy, Lena! And for everyone listening who's thinking about how to apply this in their own organizations, there are some really practical steps you can take. First, before you even start planning your PRINCE2 implementation, spend time understanding your organizational culture. What are the unwritten rules? What gets rewarded? What behaviors are actually tolerated versus what's officially stated?

Lena: And how do you assess that? It seems like culture is often invisible until you bump up against it.

Eli: Great question! One approach from "Change the Culture, Change the Game" is to look at the Results Pyramid-examine what results you're currently getting, trace back to the actions that create those results, then look at the beliefs driving those actions, and finally identify the experiences that shaped those beliefs. Your current culture is perfectly designed to deliver your current results.

Lena: So if you want different results from your PRINCE2 implementation, you need to create different experiences that will shape new beliefs and drive new actions. That's incredibly powerful for project managers to understand.

Eli: Absolutely! And here's another practical tip from the people skills research-use Wong's "three hats" framework. You need to balance your management hat, supervisor hat, and team member hat. When you're enforcing PRINCE2 processes, that's your management hat. When you're coordinating work, that's your supervisor hat. But don't forget your team member hat-showing genuine care for people as individuals.

Lena: I love that because it addresses something I think a lot of project managers struggle with-how do you maintain authority and structure while still being human and approachable? It's not about choosing one or the other; it's about knowing which hat to wear when.

Eli: Exactly! And for our listeners who are dealing with resistance to change, remember that resistance usually isn't about the change itself-it's about the losses the change represents. People might lose status, competence, predictability, or identity. If you can understand what people fear losing, you can design your PRINCE2 implementation to address those concerns.

Lena: So as we bring this conversation to a close, I'm struck by how this completely reframes what it means to be successful with PRINCE2. It's not just about following the processes correctly-it's about creating an environment where people can thrive during transformation.

Eli: That's beautifully put, Lena. And I think the key insight for everyone listening is that PRINCE2 is incredibly powerful, but its power is multiplied when you combine it with deep understanding of people and culture. The methodology gives you structure and control, but change management and people skills give you adoption and results.

Lena: Right, and whether you're working in a hierarchical corporate environment, a creative startup, or anywhere in between, the principles remain the same-you need to understand your people, respect your culture, and design experiences that help individuals successfully navigate change. PRINCE2 becomes the vehicle for that journey.

Eli: And here's something to think about as you go forward-every interaction you have as a project manager is either reinforcing the culture you want or the culture you're trying to change. Every email, every meeting, every decision is creating experiences that shape beliefs. That's both a tremendous responsibility and an incredible opportunity.

Lena: What a powerful way to think about it! You're not just delivering projects-you're shaping the future of how your organization works together. And on that note, we want to encourage everyone listening to stay curious, keep those questions coming, and remember that the most successful transformations happen when we honor both the technical and human sides of change.

Eli: Couldn't agree more! Until next time, keep building those bridges between structure and humanity, and keep making change work for everyone involved.