Project Management

Please login or join to subscribe to this thread

What are the Characteristics of the Worst Project You've Ever Had to Manage?

linkedin twitter facebook  
avatar
Debra Oglesby Atlanta, Ga, United States
For me, it was the largest cross functional project of my career. It was extremely complicated. We lacked the tools, processes and people to execute successfully. However, with sheer determination, a few bumps and bruises, we prevailed...eventually. To me, it almost always points back to leadership and whether you are being supported and protected.

Go to Amazon and check out my new e-book "Your Leadership Sucks! Its Not the Project Manager" to find out more about my experience and the Lessons Learned I offer to various roles in Leadership.

We're in this together!
Sort By:
avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
A project where the investors, city hall, architects, public, most stakeholders, and the Asian financial crisis of 2008 were all against the project. No wonder it failed!
...
1 reply by Debra Oglesby
May 09, 2018 8:43 AM
Debra Oglesby
...
Wow, Sante. I thought my list of disruptors was bad...thanks for sharing that. When we share our stories, the commonalities become so apparent.
avatar
Kevin Drake Perth, Western Australia, Australia
I had a project in Oman, The client and the sponsor was against it, guess what is the results!
...
1 reply by Debra Oglesby
May 09, 2018 8:44 AM
Debra Oglesby
...
Yep. That's what I'd call Project hell. Been there! Thanks Kevin.
avatar
Drake Settsu Project Manager / Blogger Hi, United States
A project where the team required so much microscopic management. Yes microscopic management, that's how bad it was.They needed their hands held continuously due to their managers lack of experience and guidance.
...
1 reply by Debra Oglesby
May 09, 2018 8:49 AM
Debra Oglesby
...
Ouch! Yes, Drake. Been there too. In my case the offending team's leadership would dig in to identify discrepancies about other teams when her own team didn't have their day to day roles and responsibilities firmed up. The project we were executing brought out ALL of her team's deficiencies and forced them to face and update their roles and processes in order to properly execute the project. It was EPIC and yes, pointed back to her lack of inexperience in that particular department. Thanks for sharing!
avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
Disruptive team-member(s) and toxic behavior - then implicitly 'supported' by leadership due to either tenor or feared implication of loss.
...
1 reply by Debra Oglesby
May 09, 2018 8:59 AM
Debra Oglesby
...
Wow, Andrew. So, your feedback brings to mind a project where I had to convince a leader that he needed a tool in order to prepare for an effort. He consistently acted as a disruptor. He would not get his team trained, he would blame IT for holding him up (when there were clear paths to avoid delays), he would accuse me of siding with IT...saying I was trying to force a tool vendor on him. Well, ultimately, I believe he was just unhappy b/c, he left in the middle of this same effort. To me, there's always a human condition behind the way people behave.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Debra -

Most of the really bad projects I have worked on were the result of unrealistic constraints imposed on the team - whether that was schedule, cost, resources or quality.

Where I could, I pushed back. On some, I walked away after formal communication of my concerns fell on deaf ears - usually these were contract roles. On others, I went down with the sinking ship...

Kiron
...
1 reply by Debra Oglesby
May 09, 2018 9:19 AM
Debra Oglesby
...
Kiron, my favorite part of your response is that you walked away after formal communication! I like your style and wished that I had learned that early on. I have actually felt like I was near a nervous breakdown trying to manage the chaos of UNREALISTIC CONSTRAINTS within projects before. It took me some time to learn your approach. And, now my attitude is like, never again! Hats off to you for setting a standard to follow!
avatar
Debra Oglesby PM III| WorldPay Inc Acworth, Ga, United States
May 08, 2018 9:48 PM
Replying to Sante Delle-Vergini, PhD
...
A project where the investors, city hall, architects, public, most stakeholders, and the Asian financial crisis of 2008 were all against the project. No wonder it failed!
Wow, Sante. I thought my list of disruptors was bad...thanks for sharing that. When we share our stories, the commonalities become so apparent.
avatar
Debra Oglesby PM III| WorldPay Inc Acworth, Ga, United States
May 09, 2018 4:47 AM
Replying to Kevin Drake
...
I had a project in Oman, The client and the sponsor was against it, guess what is the results!
Yep. That's what I'd call Project hell. Been there! Thanks Kevin.
avatar
Debra Oglesby PM III| WorldPay Inc Acworth, Ga, United States
May 09, 2018 6:03 AM
Replying to Drake Settsu
...
A project where the team required so much microscopic management. Yes microscopic management, that's how bad it was.They needed their hands held continuously due to their managers lack of experience and guidance.
Ouch! Yes, Drake. Been there too. In my case the offending team's leadership would dig in to identify discrepancies about other teams when her own team didn't have their day to day roles and responsibilities firmed up. The project we were executing brought out ALL of her team's deficiencies and forced them to face and update their roles and processes in order to properly execute the project. It was EPIC and yes, pointed back to her lack of inexperience in that particular department. Thanks for sharing!
avatar
Debra Oglesby PM III| WorldPay Inc Acworth, Ga, United States
May 09, 2018 6:36 AM
Replying to Drew Craig
...
Disruptive team-member(s) and toxic behavior - then implicitly 'supported' by leadership due to either tenor or feared implication of loss.
Wow, Andrew. So, your feedback brings to mind a project where I had to convince a leader that he needed a tool in order to prepare for an effort. He consistently acted as a disruptor. He would not get his team trained, he would blame IT for holding him up (when there were clear paths to avoid delays), he would accuse me of siding with IT...saying I was trying to force a tool vendor on him. Well, ultimately, I believe he was just unhappy b/c, he left in the middle of this same effort. To me, there's always a human condition behind the way people behave.
avatar
Debra Oglesby PM III| WorldPay Inc Acworth, Ga, United States
May 09, 2018 7:59 AM
Replying to Kiron Bondale
...
Debra -

Most of the really bad projects I have worked on were the result of unrealistic constraints imposed on the team - whether that was schedule, cost, resources or quality.

Where I could, I pushed back. On some, I walked away after formal communication of my concerns fell on deaf ears - usually these were contract roles. On others, I went down with the sinking ship...

Kiron
Kiron, my favorite part of your response is that you walked away after formal communication! I like your style and wished that I had learned that early on. I have actually felt like I was near a nervous breakdown trying to manage the chaos of UNREALISTIC CONSTRAINTS within projects before. It took me some time to learn your approach. And, now my attitude is like, never again! Hats off to you for setting a standard to follow!

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Impartial observers from other planets would consider ours an utterly bizarre enclave if it were populated by birds, defined as flying animals, that nevertheless rarely or never actually flew. They would also be perplexed if they encountered in our seas, lakes, rivers and ponds, creatures defined as swimmers that never did any swimming. But they would be even more surprised to encounter a species defined as a thinking animal if, in fact, the creature very rarely indulged in actual thinking."

- Steve Allen

ADVERTISEMENT

Sponsors