DIRECTIVE 135 / FEEDBACK

SKIP THE DEBRIEF

Finish the project. Begin the next one before anyone can learn from it.

Cancel post-project reviews to protect delivery time. Keep the same teams, tools, and assumptions regardless of what went wrong. When the next project repeats the failure, demand a more detailed recovery plan.

THE MECHANISM

Learning opportunities sacrificed to relentless delivery cycles.

Primary: FEEDBACKGROWTHMEANING
RATIONALE
Debriefing creates visible non-production time and may surface process changes that require ownership.
SUCCESS INDICATOR
Teams repeat familiar methods with increasing efficiency and recurring surprises with admirable consistency.
COMMON FAILURE
Creating deliberate opportunities for team reflexivity: reviewing objectives, strategies and processes and adapting them when evidence suggests the current way of working is insufficient.
THE UNFORTUNATE PART

Evidence, with limitations.

Claim

Team reflexivity is associated with team performance, but the benefit is contingent on team characteristics and context rather than automatic.

Evidence

A 2024 meta-analysis found team reflexivity facilitated performance overall while identifying team size and tenure as boundary conditions and participation and psychological safety as important antecedents.

Scientific boundary: Team reflexivity is associated with performance in many settings, but meeting structure and task characteristics moderate benefits.

Sources

These references offer context, not a completed review or a test of this instruction.