September 28 & 29, 2020 | Virtual
Please login or join to subscribe to this thread
Tough situation. If they'd listen I'd explain the steps, the process, asking for their help, but promising i'd stay out of their way. I've been in this position a bit. What I did was I stopped using PM terminology, take away any threat, and began with simply setting down and collecting a narrative. Once i had something I refined it, asking if I had it correct... until I had a plan. They owned it, it was their narrative, their understanding. From that I could plan and support them. I asked if I could make a call or clear the way for them. Eventually they began to turn it over to me. It was painful. I can't say i enjoyed it but it got everything moving. Good luck.
Suggest you consider risk-driven project management. You can do it their way however here are the risk associated with this methodology. Start wit a risk management plan including a detailed risk identification, consequence and mitigation measures spreadsheet. Explain what needs to be done to mitigate the risks and enhance probability of success. I'm sure the C-Suit and division leaders understand the concept of risk.If they are okay with the exposure then you set your plan based on their direction.
This is a dictatorship, not leadership. In scenarios like this, you can try and introduce Agile and the concept of servant leadership while showing the real added value of doing this.
Its a tough situation, no questions about that, but arguing and confronting won't help in this situation.
Definitely a tough situation. What I do in this situation is rough out what a plan would look like at a high level, and based on that, show them the disconnect from reality. That helps to illustrate the need for more comprehensive planning better than just explaining it.
For example, I might show that we have a supplier who needs 100 days to fabricate hardware, 6 months of design work is needed before we send a purchase order to the supplier, and knowing just that we should have started 3 months ago. Now what?
How you manage it from there could use an agile framework, but the first challenge is convincing people that you need a plan rather than just letting things follow the path of least resistance.
Erikka, you have clearly articulated both the sides. Offcourse agile is the way to go. Uphold the art of not getting things done, focus on the highest priority item that would please and help you gain confidence among the CxOs.
As you said there is a transition taking place, I assume the core is at stack.. it eventually would run through to every branch and every end point.
Cascade the importance to people and emphasis on vision to keep up the motivation.. I hope this is interim by the way :)
Erikka, I think in this challenging environment Leadership really need to be inclusive and go in with a participation approach.
The goals is set at 14 and you definitely want to try and achieve that as a team, no doubt. But does the team have a say in which 14 projects have the best chances of success if initiated?
Maybe what you are referring to as 'plan' is what I'm referring to as inclusive/participation.
I think it's really vital to get at least some requirements from them that you can work on and develop. Without eliciting these initial requirements from them, would be challenging to deliver on something they'll buy-in to.
Agile is NOT a silver bullet to slay senior management dysfunctions. All an adaptive approach might do is show the impact of those dysfunctions faster.
Unfortunately, unless you are in a position where you can influence senior leadership's thinking to be more strategic (i.e. decide what they will NOT do so that they can plan the vital few initiatives that they do wish to have implemented) this sounds like a death spiral to me.
Dear Erikka: If this is a real scenario, it's not easy. If you are going to stay with this company, you have to continually present financial and other reasons for doing things the right way. Doing things the right way will bring about the best overall results.
The situation is simple to face when you understand the basement about why we are hired as project managers. Projects are started to create a solution. Solution to what? To a business need/wish/desire/want. That business need/wish/desire/want create a problem situation then a solution must be created. But, what is a need?. An unbeatable situation from which every human being wants to leave as fast as possible. That´s because everybody say "just do it" and when you say them times almost always are not accepted. So, first thing to undertands is you will always get need/wish/desire/want that you have to translate to requirements to create the solution (in the PMI and other organizations business analyst is on charge of that). You never get requirements (something that will help you to create the solution). On the other side, a plan is always there. Explicit, implicit, in the PMI way, whatever. With that on hand you can take different roads. But you always have to think in terms of the solution to the problems your clients expressed, just in case a problem exists because problem is the gap between the perceived reality and the desire reality.
Please login or join to reply