November 5, 2020, 8:30 a.m. to 6 p.m. EDT | November 6, 2020 – February 7, 2021, On-Demand | Online Conference
Please login or join to subscribe to this thread
Interesting your question
Thanks for sharing
"Quando o mar bate na rocha..."
I think the best way is:
1. Identify functional managers who may affect or be impacted by the project
2. "Sell" the project idea to all these functional managers
(important: involve the project sponsor in this process)
3. Always keep functional managers informed of project implementation (using the most appropriate means to inform them)
It is very important for functional managers to support the project
Having the proper processes to ensure delivery of the technical submittals and approvals by the functional manager on time and no abuse to the power.
Job tasks to be well defined by the PM and FM at the beginning of the projects.
Some of the problems I used to see in this type of projects.
- Technical Requirements from the FM is not clear at the beginning of the project which might cause delay.
- Communication between FM and team members without coordination with PM.
In my case, what is usefull for me, is using SPIN Selling or Solution Selling method as a tool for stakeholder management.
I agree with Luis.
Business is people.
If you believe that, then you need to build positive relationships with functional managers BEFORE the going gets tough.
I've also found that when working with functional managers on a project for the first time, it helps to establish some working agreements or ground rules similar to what we'd do with a team. That way, there are no surprises...
I build relationships with the functional managers and involve them in project decisions if I think it will help build support. It wouldn't hurt to have them in your communication plan, and your human resources management plan.
Conflicts and clashes are signs of negative relationships, win-win and collaboration is the targeted outcome, best for the project and the involved parties.
That's why negotiations, conflict management, communications are key skills for a project manager and stakeholder analysis and engagement is so important. Emotional intelligence is required to understand them and influence them.
Some practical steps that worked for me:
- establish a good relationship with managers even before the project starts (eat drink talk)
- invite key managers to steering committees (when their peers help them)
- understand how you can help managers doing their job (e.g. building alliances)
- design the project orgchart so they are involved (and bound)
- involve other managers they are cautious with
Thanks for your feedback.
From my past experience and from sharing experiences with friends and colleagues working in corporations with such organizational structures, I verify that these conflicts are mostly regarding priorities, over-allocations and commitments due to nature of these organizations structures. And yes, in most cases, "quem se lixa é mexilhão"....
I agree and follow the steps you presented, which I believe engage most functional managers and avoid unnecessary risks to the project.
I agree with the need of having proper (and well oiled) processes, the focus on documenting the technical requirements and the tasks/responsabilities of each manager to avoid communication that sabotages or ampers both the project and the PM.
Did not know of the method and decided to google it a bit.
It resulted in me adding Neal Rackham's "SPIN Selling" book to my "Wish List" list. Thanks for your inputs and nice suggestion!
Please login or join to reply