🔍 Is technical skill enough to lead complex projects today?

"Couldn’t agree more — strong relationships and clear, audience-appropriate communication are often the difference between a project that simply gets delivered and one that genuinely succeeds.

I really like your point about needing just enough technical knowledge to spot when something doesn’t add up, without getting pulled into the weeds. That balance allows project leaders to stay focused on the bigger picture while keeping delivery honest and transparent.

I’m curious — when you’re coaching or mentoring PMs, how do you help them find that sweet spot between technical awareness and over-involvement?"

"I completely agree — micromanagement not only wastes talent, it undermines trust. As you’ve said, projects are delivered by people, and the project manager’s role is to create the environment where those people can perform at their best.

I like your link to Sinek’s circle of trust — when teams feel safe, supported, and empowered, they’ll often deliver beyond expectations.

I’m curious — in your view, what’s the most effective action a project leader can take early in a project to establish that trust?"

"Well said — I really like the distinction you’ve made between project success and project management success. The triple constraints are important, but they don’t always tell the full story of a project’s value or impact.

Your point about people management is spot on too — when leaders focus on the long-term benefits and relationships a project creates, it often leads to better outcomes for both the organisation and stakeholders.

In your experience, what’s the most effective way to balance those immediate delivery pressures with the bigger-picture, long-term vision?"

"Completely agree — I think the term ‘soft skills’ can sometimes do these capabilities a disservice, because it makes them sound optional, when in reality they’re mission-critical for project success.

As you’ve highlighted, communication, interpersonal awareness, and problem-solving are what often make the difference between a project plan that works on paper and one that actually succeeds in practice.

I’m interested in your view — if you could choose just one of these skills for every project leader to master first, which would you say has the biggest impact?"

"Absolutely — the M.O.R.E. model is a great reminder that technical skills are just the foundation. It’s the higher layers — mindset, leadership, and the ability to navigate complexity — that often determine whether a project truly succeeds.

You’ve made me curious — in your view, which of those ‘other layers’ in the M.O.R.E. model tends to be the hardest for project leaders to master in practice?"

"I agree, it’s such an important observation — self-awareness is often underestimated, yet it underpins so many other leadership capabilities.

I really like how you framed it as understanding personal and professional agency — knowing both your influence and your limits. That ability to read the situation, adapt your approach, and decide when to push or hold back is often what separates a good project leader from a truly exceptional one.

In your experience, what’s been the most effective way to help project leaders develop that level of self-awareness — especially in fast-paced, high-pressure environments?"

"I love this perspective — especially the reminder that all projects have complexity baked in, and that we as project leaders are part of the bigger solution, not just the delivery mechanism.

Your point about partnering closely with business analysts really resonates. That collaboration is often where the bridge between strategic intent and practical delivery gets built — and without it, the project can lose alignment with business objectives quickly.

I’m curious — in your experience, what’s the most effective way to ensure that PM–BA partnership stays strong and productive throughout the entire project lifecycle?"

"That’s such a great observation — talent mapping at both a strategic and tactical level is something we don’t talk about enough in project leadership. I completely agree that it’s more than matching technical skills to roles; it’s about having the foresight to anticipate capability gaps and the agility to fill them, whether internally or through external networks.

I’m curious — in your experience, have you found more success in building that capability within existing teams or buying it in through external specialists? Or does it depend entirely on the project’s urgency and scope?"