Decide where the work belongs
Rank the blocked list operation
Name the action that fails to remain usable: opening the list, finding a row, sorting, bulk selecting, or moving to another page. Separate a slow view from an operation that prevents completion. Give weight to repeated daily interactions and actions with no practical workaround.
Measure reach and growth pressure
Group observations by row count, account size, route, filter, and viewport. Compare current sizes with the size at which the delay first appears. A problem nearing many accounts deserves earlier capacity than a boundary reached only by a test fixture with no comparable production shape.
Choose the smallest useful queue slice
Select investigate now, schedule pagination or rendering work, or collect a representative larger list. State the evidence that changes the choice, such as a row-count trend or a reproduction of sorting cost. Keep a proposed architecture separate from the immediate slice needed to unblock work.
What to carry forward
Produce a queue decision that names the affected operation, confirmed row-count reach, growth pressure, and evidence gap. The item is ready when the next engineer can start with one representative list and understand why this slowdown outranks other performance work.
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