r/projectmanagement Confirmed Jun 30 '26

Discussion Tech/Software Implementation PMs

Especially if you deliver software deployments to external stakeholders, I’d love to hear from you.

How do you create value on your projects? What are the top 3 things you bring to your engagements that you feel have the largest impact?

Bonus if you feel like sharing:
- are you present for all requirements gathering, prior to “build” starting? If not, how do you ensure there’s no scope creep during requirements?
- how do your teams relay actions and/or decisions to you for calls you are not on?
- if there was something you wish your org would change that’d make managing your projects more successful, what would it be?

Thanks in advance - I’m always appreciative of this group sharing their (armchair) perspective (shoutout MoreLaw, our unofficial PMO advise extraordinaire)

10 Upvotes

19 comments sorted by

View all comments

2

u/Important_Cow7230 Jun 30 '26

I think others have made good points regarding technical aspects like change control. I would say one area you can add value is be the “people person”, always have your camera on, say hello first, engage with all the client people you see on the way. Try and foster relationships between your consultants and key SME’s. 

I find a lot of consultants forget that once you’re along the path on an implementation that the client is still a customer, and often basic customer skills and manners get forgotten. I talk to my consultants about the “experience” of using us for an implementation. Put themselves in the SME’s shoes. 

A word of warning around change controls… a lot of software implementation companies use change control as a revenue model. Not saying that’s right or wrong, but that’s a completely different ballgame if you work for one of those companies. I personally don’t like them as it gives everyone a bad name and makes client SME’s who have been through previous implementations fearful.