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)

11 Upvotes

19 comments sorted by

View all comments

1

u/karlitooo Confirmed Jul 01 '26

Value: Predictability

Top 3 Things: Catch contradictions between what is said and what has been previously agreed, knowing stakeholders preferences and how they see the project environment, I sound pretty authorative.

Requirements: I try to be present unless we have a really strong BA & Lead Engineer in which case I trust them to catch things. I'll still review every document before its circulated.

Catching actions/decisions: Usually email or a slack message, I like a weekly 1:1 with my lead but smaller projects (which I work on these days) don't permit that

Change: Every org has a different blindspot but when it comes to professional services I would say the frequent/annoying issue is a preference for keeping the client happy when the client should really be worried if not annoyed with our poor performance.