- The default state of the table (sort order, sort column)
- Whether to remember sorting preferences between uses of the table.
- Whether to invest in making sort controls on mobile more discoverable
- Whether to cache frequent sorting options for speed and usability
- Whether to replace pagination, with a endless scroll option
High level, the PM, developer, and designer want to improve the user experience for this table.
To answer these questions the team needs to collect a lot of granular event data like:
- column sorts (with column text, direction, etc.)
- pagination actions (with page #, results per page, next, back)
- clicks on list items (with index, identifier, etc.)
- number of list items displayed
- ...along with information about the user and their device.
...and then be able to query that data, visualize the data, and answer their questions.
Note: Assume that none of this event tracking exists, and you need to start collecting the data. If you have an analytics solution enabled for your product, assume that solution is being used. If you have a "record everything" solution in place, note that the questions involve tracked properties (e.g. sort direction).
