Product Management 11 min read

How Designers Can Master Effective Project Post‑Mortems

This article explains what a post‑mortem (复盘) is, why it matters for designers, outlines a four‑stage framework, explores different review types, offers practical tips for running productive sessions, and suggests tools and habits to turn reflections into lasting growth.

58UXD
58UXD
58UXD
How Designers Can Master Effective Project Post‑Mortems

Introduction

A post‑mortem (复盘) is the process of reconstructing a project and discussing its outcomes to extract lessons. It can be approached actively or passively, and its impact varies greatly depending on the participants’ mindset.

Why Post‑mortems Matter for Designers

Designers benefit from post‑mortems in three main ways: personal skill growth, self‑assessment of design value, and building trust within the team.

Skill growth: By reviewing the whole project and hearing others’ perspectives, designers accelerate insight and deepen understanding of business context.

Design‑value assessment: Feedback from other roles helps quantify the contribution of design and makes the process more scientific.

Trust building: Explaining design reasoning during the review strengthens the team’s confidence in design decisions.

Four Basic Stages of a Post‑mortem

Every review follows these steps:

Goal review: Re‑establish a SMART‑based project goal that all members understand.

Result evaluation: Objectively compare actual outcomes with the goal, noting positive and negative deviations.

Cause analysis: Identify root causes of gaps using tools such as the “5 Whys”, fishbone diagram, or other brainstorming methods.

Experience summary: Distill learnings, consider applicability to future projects, and define actionable to‑dos.

Different Review Purposes

Depending on the objective, a post‑mortem may focus on data‑driven insights, process challenges, or design‑value evaluation. Data‑centric reviews help infer design strategy, while process reviews address communication, workflow, and empathy improvements.

Key Practices for Effective Reviews

Open mindset: Avoid blame and encourage multi‑perspective discussion.

Beyond reporting: Prevent the session from becoming a simple status recap.

Resist premature conclusions: Explore objective and subjective factors before deciding.

Facilitator role: The host should keep the discussion neutral, stay on topic, and ensure everyone contributes.

Building a Sustainable Review Habit

Integrate post‑mortems into regular workflows, combine deep and shallow reviews, and archive findings in a shared knowledge base to prevent repeated mistakes.

Appendix: Common Review Tools

5 Whys – repeatedly ask “why” to reach root causes.

Fishbone diagram – categorize and visualize causes.

Team‑listing – individual preparation followed by group sharing.

World Café – rotating small‑group discussions for diverse ideas.

Talking stick – a physical cue to let only the holder speak.

Six Thinking Hats – assign colored hats to focus on specific perspectives.

Reference: Qiu Zhaoliang, Post‑mortem+ : Turning Experience into Capability .

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

process improvementteam learningproject reviewdesign postmortemdesigner growth
58UXD
Written by

58UXD

58.com User Experience Design Center

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.