Project Management Central

Please login or join to subscribe to this thread
Failed practices/approaches - Lessons Learned
Network:522



I strongly believe we can learn more from failures much faster . so please let us know what went wrong and what you learned from your recent and past projects.

Hope this will topic will really help all of us by not making the same mistake and your answers will be save good amount of time for all of us.

For example -
Failed approach - We try playing safe/smart by not sharing the critical information/issues/risks and and we end up seeing the impact and loose our credibility. Solution - Rather we raise the issue/risk as early as possible and build credibility and trust with key stakeholders and avoid the risk.
Sort By:
Network:2046



Hi Sandeep, I strongly agree with you that we learn from our failures and just as much, we learn from those areas where we “fall short of hitting the mark” i.e. those areas where we need improvement. I’ve written an article called “Strategic Lessons Learned From a Battle-Hardened Project Manager” that was put up yesterday on the Knowledge Shelf. It’s a bit long, but it puts forward things I’ve learned that I don’t’ want to forget and those things I want to pass along to others
.
Specific though to your question, here’s my contribution:

Failed Approach – The team puts together a document presenting their understanding of the functional requirements to the customer. They do this in “written form only” and chaos follows with more time being spent clarifying the content then was spent analyzing and putting the content together in the first place – credibility impacted.

Solution – Recognize that reflecting a project teams understanding of a requirement “without visualization” accomplishes little and will likely stall the project and affect the teams credibility.

A lesson learned decades ago and one that was seared into my being.
...
1 reply by Sandeep Kumar MK
May 18, 2018 10:57 AM
Sandeep Kumar MK
...
Thank your George for sharing your experience. Excellent!
Network:522



May 18, 2018 10:29 AM
Replying to George Freeman
...
Hi Sandeep, I strongly agree with you that we learn from our failures and just as much, we learn from those areas where we “fall short of hitting the mark” i.e. those areas where we need improvement. I’ve written an article called “Strategic Lessons Learned From a Battle-Hardened Project Manager” that was put up yesterday on the Knowledge Shelf. It’s a bit long, but it puts forward things I’ve learned that I don’t’ want to forget and those things I want to pass along to others
.
Specific though to your question, here’s my contribution:

Failed Approach – The team puts together a document presenting their understanding of the functional requirements to the customer. They do this in “written form only” and chaos follows with more time being spent clarifying the content then was spent analyzing and putting the content together in the first place – credibility impacted.

Solution – Recognize that reflecting a project teams understanding of a requirement “without visualization” accomplishes little and will likely stall the project and affect the teams credibility.

A lesson learned decades ago and one that was seared into my being.
Thank your George for sharing your experience. Excellent!

Please login or join to reply

Content ID:
ADVERTISEMENTS

"A closed mind is like a closed book; just a block of wood."

- Chinese Proverb

ADVERTISEMENT

Sponsors