Keep the lesson for the next incident
Compare the hidden causes
Align page, role, project, filters, data presence, processing state, lifecycle, copy, and next action across episodes. Identify causes repeatedly collapsed into one message.
Preserve the decision language
Document the plain-language question each empty state answers: nothing exists, nothing matches, setup is pending, or this scope is unavailable. Keep links tied to that decision.
Define recurrence recognition
Set a review trigger for query, policy, setup, lifecycle, or copy changes that can create a new empty branch. Name the matrix rows and owner needed before trusting the state.
What to carry forward
The lesson should add one explicit empty-state distinction and a recurrence rule for changes that affect it. Treat clarity as provisional until later filters, roles, and setup states still lead to truthful decisions. Keep an empty-state decision matrix tied to query, lifecycle, setup, and scope changes, and review it whenever a page gains a new filter or data source. The matrix should include a concrete example for every message so future copy changes can be checked against the underlying cause.
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