Skip to content
Kaarne Superstore⌕
Small Business Life

Run a Website Project Retrospective Without Ranking the Blame

Follow one requirement across the project instead of counting comments by person. The missing confirmation may be more revealing than the busiest thread.

Two teammates inspect a paper timeline with repeated speech bubbles and a small bridge across a gap.

The website has launched, and the retrospective begins with who left the most comments. That may produce a memorable chart while explaining little about why decisions returned or work waited. Review the transitions between information, decisions and implementation instead of ranking the people who spoke.

Choose one project-process question

In this fictional example, an agency delivered a service website after several repeated review rounds. The retrospective asks: “Why did the enquiry requirement return after the team believed it was settled?” This is a question about a project’s decision flow. It is different from reviewing whether a particular design treatment was good or whether one rejected draft taught the designer something useful.

Choose a bounded sequence with enough records to inspect. Avoid opening every disappointment from the entire relationship at once. Invite the people who supplied the facts, made the decision and implemented the resulting work. Tell them that the intended output is one change to try on the next project, with a way to see whether it was used.

Prepare a small evidence timeline

Gather the relevant review invitation, original requirement, decision note, implementation handoff and later reopening. Keep only the material necessary to understand the sequence. Remove unrelated personal detail from the discussion pack. Distinguish a dated record from someone’s recollection, and invite corrections where the chronology is uncertain.

For the example, the timeline might contain five events: marketing requested an enquiry field; the team recorded it as agreed; the developer implemented it; operations later explained that the information was unavailable to new customers; the field was revised. These are fictional events to illustrate the method, not findings from an audited project.

Examine each handoff with the same questions

Ask what the sender believed they were handing over, what the receiver understood, and which evidence supported that understanding. At the decision point, ask who was expected to confirm the operational requirement. At implementation, ask whether an unresolved assumption was visible. At reopening, ask what new information arrived and where it could reasonably have been requested earlier.

Keep the language descriptive. “The decision note did not identify an operations confirmation” points to an inspectable gap. “Marketing never thinks about operations” turns one sequence into a judgement about people. If participants disagree, preserve the competing accounts and identify the record or missing fact that would help, rather than voting on whose memory wins.

Separate a process gap from a necessary reconsideration

A reopened discussion is not automatically waste. A service rule may genuinely change after a decision. New evidence may show that a reasonable earlier choice needs revision. Ask whether the reopening followed a new fact, an unclear decision, a missing contributor, an incomplete implementation or another identifiable circumstance.

For the fictional enquiry field, the group might discover that the review brief asked marketing to check tone but never asked operations to verify the information needed at intake. That remains a hypothesis until the actual project evidence supports it. The facilitator should not arrive with a favourite diagnosis and rearrange every event to confirm it.

Design one small process experiment

Turn the supported explanation into a specific trial. For the next project, the team could add an “operational fact confirmation” line to the enquiry review brief, naming the contributor and the exact question before implementation. Assign someone to prepare that brief and someone to check that the line received an answer.

Define an observation point. At the next implementation handoff, inspect whether the confirmation is present and whether any relevant question remains unresolved. At the next retrospective, ask whether the step helped or introduced an unnecessary obstacle. Do not promise that one extra line will eliminate all repeated reviews or quantify a saving without evidence.

Close with an experiment card

Write four lines: the transition that caused difficulty; the change to try; the owner and next project; the evidence to examine afterwards. Keep the original timeline accessible to the relevant team so the experiment has a reason attached. Thank contributors for correcting the account, and record any important disagreement still open.

The result should help the next team act differently at a known moment. A list of who commented most cannot tell them that. A precise handoff experiment can.

Review where a discussion lost its context or returned after being marked complete. Those moments can guide your next process improvement without judging people by comment counts.

Continue with The Useful Agenda for a Website Review Meeting and Who Can Settle Conflicting Website Feedback?.

0

Discussion 0

What did this article make you think about?

Join the conversation

Your email address will not be published. Required fields are marked *

Saved articles

Saved in this browser.