Upgraded.today

Hands-on experience #10 from business projects: What has previously been tried to solve the problem, that failed?

Cover Image for Hands-on experience #10 from business projects: What has previously been tried to solve the problem, that failed?
Thor Mønsted
Thor Mønsted

What has previously been tried to solve the problem/situation/case, as described in the problem statement, that failed?

Like nothing else, this is so much about seeing historical "failures" as learnings !!

Armed with insights from past failures, project managers can chart a course that not only avoids the pitfalls of the past but also paves the way for innovative and effective solutions.

Understanding the landscape of past attempts to solve a problem / situation / case is a cornerstone of effective project management.

It provides a historical perspective, allowing project managers to identify patterns, root causes and potential blind spots that may have contributed to previous failures.

Steps that can help you get closer to historical events and adjust your project activities

1: Problem Statement recap

Begin by revisiting the problem statement with team members and people with historical experience in the organization and/or with the identified problem/issue.

Clearly articulate the problem, ensuring a shared understanding among team members. This step is crucial in aligning everyone on the focal point and avoiding misinterpretations that might have contributed to previous failures.

2. Historical Review

Examine project documentation and reports, and any available records of previous strategies. Identify what was attempted, the methodologies employed, the push-back from the organization or the customers, and the specific points where these strategies fell short.

3. Root Cause Analysis

Go deep into the root causes of previous failures. What were the underlying issues that led to the breakdown of earlier attempts?
Try to peel back the layers and uncover the fundamental reasons behind the shortcomings.

4. Stakeholder Feedback

Engage with key stakeholders, sponsors, line managers, subject matter experts, etc. who were involved in or affected by past efforts.
Collect as honest as possible feedback on what worked, what didn't and insights on potential blind spots or unclear agendas.

Stakeholder perspectives can offer nuanced insights into the human and interpersonal aspects that may have contributed to the failure.

5. SWOT Analysis

Conduct a comprehensive SWOT (Strengths, Weaknesses, Opportunities, Threats) analysis specifically focused on the previous attempts. Identify the strengths that were underutilized, weaknesses that proved detrimental, opportunities that were missed, and threats that were not adequately addressed.

6. Lessons Learned Documentation - SUPER important

Compile a robust "Lessons Learned" documentation. Synthesize the insights gained from the historical review, root cause analysis, stakeholder feedback and SWOT analysis into a comprehensive document.

This serves as a super important reference for the current project team, ensuring that the wisdom gained from past failures is not forgotten.

7. Strategy Refinement

Armed with a deep understanding of past failures/learnings, refine the current strategy. Identify key areas where adjustments can be made based on the lessons learned. This may involve re-evaluating the project plan, revisiting resource allocation or reassessing the feasibility of certain approaches.

____________________

Did this resource provide an answer or solution to your specific project/problem/situation?

If not, then describe the question here and receive an answer within 2-3 business days based on 15 years of hands-on experience


More Resources

Cover Image for Hands-on experience #11 from 15y in complex projects: Describe the stakeholders surrounding the problem

Hands-on experience #11 from 15y in complex projects: Describe the stakeholders surrounding the problem

Project success hinges not only on the clarity of the problem statement but also on the profound understanding of the stakeholders, organizational landscape and hierarchical structures surrounding the identified problem. There is a critical importance of looking into the (complex) web of relationships, perspectives and organizational structures - especially in larger established organization with a maybe conservative culture.

Cover Image for Hands-on experience #9 from business projects: Why is the problem actually a problem for the organization?

Hands-on experience #9 from business projects: Why is the problem actually a problem for the organization?

The problem statement is the cornerstone of any project and it serves as a compass guiding teams toward solutions. This resource will help work on the next important step: "Why is the problem, as defined in the problem statement for the project, actually a problem for the organization from a strategic or operational perspective?"

Thor Mønsted
Thor Mønsted