Using feedback loops and lessons learned is crucial for organisational and project maturity. These mechanisms formalise continuous improvement by ensuring that knowledge gained from past experiences is captured, analysed, and integrated into future planning.

 Feedback Loops: The Engine of Improvement

A feedback loop is a closed system where the outputs of a process are returned as inputs to that process, affecting its future operation. Effective communication relies on making these loops explicit and structured.

1. Establish Clear Collection Points

The loop begins with consistently gathering data from the point of communication or action.

• During Execution (Real-Time Feedback):

  • Pulse Surveys: Quick, anonymous check-ins to gauge team morale or understanding during a long project.

  • Check-ins/Stand-ups: Asking specific questions like, “What is currently blocking you?” or “What’s the riskiest element right now?”

  • Observational Data: Tracking metrics like email response times, adoption rates of a new process, or compliance statistics.

• After Execution (Post-Mortem/Retrospectives):

  • Structured meetings designed to analyze a project or campaign after completion.

2. Analyze and Synthesize the Data

Once collected, the raw data needs to be converted into actionable insights.

• Categorization: Group feedback into themes (e.g., clarity of instruction, availability of resources, timeline accuracy, technical blockers).

• Root Cause Analysis: Use techniques like the 5 Whys to move beyond symptoms and identify the foundational cause of successes or failures.

• Quantification: Determine the frequency and severity of issues. For example, “80% of negative feedback concerned the complexity of the reporting form.”

3. Close the Loop (The Critical Step)

The loop is only complete when the insights are communicated and acted upon.

• Communicate Findings: Share the lessons learned back with the people who provided the feedback. This demonstrates that their input was valued and strengthens psychological safety.

• Integrate into Process: Update policies, communication templates, training manuals, or project charters based on the findings. This formalizes the change and prevents the same mistake from recurring.

Lessons Learned: Formalizing Knowledge

“Lessons learned” is the resulting knowledge gained from the feedback process that is documented and archived for future projects.

1. Documenting the Lesson

A documented lesson must be actionable, not just descriptive. Every entry should contain four components:

2. Creating a Knowledge Repository

Lessons learned should be easily accessible, searchable, and mandatory to consult at the start of any new project.

• Centralized System: Store documentation in a common, stable platform (e.g., SharePoint, wiki, or dedicated database).

• Mandatory Review: Make it a required step in the Project Initiation Phase to review relevant historical lessons learned. For instance, before writing a new risk plan, teams must search for past project risks.

3. Institutionalizing the Culture

The greatest challenge is making the process a habit, not an optional step.

• Allocate Time: Officially schedule time for retrospectives and documentation in the project plan.

• Link to Performance: Recognize and reward teams and individuals who contribute high-quality, actionable lessons learned, reinforcing the value of continuous improvement.