Customers asked for custom metrics and drill-down report tables for a long time. Delivering them meant rewriting the grid and moving the screens to Angular. It was the biggest technical change in the interface.
The new reports had to sit next to old screens and still feel like one product, with no visible seam between legacy and new views. The product has a complex, variable structure. Basic customers need simple defaults. Enterprise customers work with huge data flows and many scenarios.
I designed the screens together with the developers who rewrote the grid, and I made decisions inside the limits of the technology. Several approaches were weighed against effort before anything went into production.
Add: 3 to 5 specific decisions, for example how many drill-down levels, how filters behave, how empty, loading and error states look, how the table scales for large data, how a user builds a custom metric.
Customers had requested these features for a long time, and the release was well received.
Add if you can say it: a qualitative sign of use, for example support questions about reports, feedback from customers or from the team.
When the data model is flexible, good defaults matter more than extra options. I design the simple path first and make the advanced one reachable without cluttering it.