Lessons learned report
Project or event: Customer portal, release 3
Dates: 10 January to 16 April 2027
Review led by: Lucia Romero
Date of the review: 30 April 2027
Who took part: Lucia Romero, Jin Park, Priya Nair, Henrik Larsen, Mei Chen
The aim of this review is to learn, not to blame. We look at what happened and how our way of working can improve.
1. What we set out to do
Launch the portal with online payments by 5 April, for EUR 90,000.
2. What happened
Launched on 16 April, 11 days late, at EUR 96,500. Online payments work and 40 percent of clients use them in the first 2 weeks.
3. What went well
Daily short meetings kept everyone informed
The test team found problems early
Clients joined the demos and gave useful feedback
4. What did not go well
The payment test system was slow and unreliable
Changes were agreed by chat and not written down
Help texts were written too late
5. Why it happened
We did not test the bank connection before we planned the work.
There was no clear way to approve changes.
6. Lessons
Test every outside connection in the first month.
All changes go through a written change request.
7. Actions
Add a connection test to the project checklist: Lucia Romero, 14 May
Write the change process: Priya Nair, 21 May
We will check these actions at the next team meeting and record when each is done.
Shared with: All project managers, the management team