An experienced project manager takes the floor and says calmly: “The project is successful if we deliver on time and within budget. And especially if the customer is willing to pay the invoices for all the additional work.”

I'm delivering a workshop to a medium-sized Dynamics 365 implementation partner. We're in the middle of a discussion about what project success actually is. And what this organization can do to deliver more successful projects.

I sense some hesitation in the group.

And it's quiet for a moment.

Until someone raises their hand and asks me: "Guus, are we as partner really the one who can determine whether the project is successful? After all, it's about the customer and achieving their objectives, isn't it?"

This situation occurs regularly when I deliver my Project Excellence workshop to ERP and CRM partners. And it always starts a very valuable discussion about what ERP projects are really about.

Unfortunately for the buyers, many implementation partners and their suppliers still primarily pursue their own success. Revenue, margin, growth and individual bonuses far too often take precedence over actually helping the client organization move forward.

With a lot of frustration, poor projects, failures, lawsuits and churn as a logical consequence.

👉 So how do you define Project Success?

And does that definition lead to more successful projects?
Or rather to more hassle, churn and legal cases?

Consider organising this workshop with your team if you're ready to redefine Project Success.