Keep the lesson for the next incident
Record the list shape that mattered
Document row count, fields, filters, sort, nested controls, viewport, and the operation that exposed the cost. Explain which interval grew and which measurements support it. Include both the healthy smaller case and the boundary case so future comparisons do not lose scale context.
Make the growth assumption visible
Add a focused review item or repeatable fixture for the representative boundary. Define what must remain usable, including loading, sorting, selection, focus, or pagination. Assign a responsible owner for interpreting growth evidence instead of treating one fixed row count as a lasting promise.
Revisit after schema or workflow changes
Re-run the case when fields, joins, sort options, row controls, or account growth change. Compare server, payload, DOM, and interaction costs again. If the workflow becomes page based or virtualized, create new correctness checks for continuity, keyboard movement, and recoverable loading.
What to carry forward
The learning record should keep the scale boundary, list shape, operation contract, and recurrence trigger together. It is useful when future work can reproduce the cost with representative data and can tell whether a change improves a layer while preserving the list's actual decisions.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow