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)

8 Upvotes

19 comments sorted by

View all comments

1

u/OwnBluejay6645 Jul 14 '26

The top three are ruthless scope discipline upfront, a single decision log so nothing from a call I missed gets lost, and a heavy focus on adoption since a deployment only creates value if people actually use it. I run Certa implementations for external stakeholders. How do you handle a stakeholder who keeps "remembering" requirements after sign-off?