October 13, 2026 · Project Retrospectives
Retrospective: Why Acceptance Took Half a Year
The system was live for months while acceptance stalled. The causes were documents, process and communication, not software.
An enterprise blog · Lanzhou · since 2019
What we learn, written down in public
October 13, 2026 · Project Retrospectives
The system was live for months while acceptance stalled. The causes were documents, process and communication, not software.
October 1, 2026 · Project Retrospectives
The hard part of integration is not the interface, but getting two departments to agree on what a field means.
September 19, 2026 · Project Retrospectives
Ads ran normally after launch but enquiries stayed low. The review found trust and form friction were the blockers.
September 7, 2026 · Project Retrospectives
Users arrived on launch day and so did the problems. We now include post-launch operations in scope.
August 26, 2026 · Project Retrospectives
In multi-party projects the most expensive cost is waiting and arguing, not development.
August 14, 2026 · Project Retrospectives
The dashboard looked great and leadership applauded. Three months later its open rate was close to zero.
August 2, 2026 · Project Retrospectives
At half the usual budget, the way to protect quality is to cut scope rather than foundations.
August 1, 2026 · Project Retrospectives
A retrospective is not a blame meeting and should not be a process performance. It only needs to solve one problem: how to do a little better next time.
July 21, 2026 · Project Retrospectives
To hit a client's opening date we cut testing from three weeks to one, then spent six weeks fixing production.