Year: 2025
Type: article
Abstract: When developing a dashboard or report, it's always best to start out simple and specific," recommends Paula Baingana, associate director of analytics at the University of St. Thomas (St.Paul, MN)."Start with the smallest viable product.Does it answer one question?If that is useful, then you can go ahead and request a new filter or an extra field."To create a practical tool, Baingana suggests establishing an iterative organic process.If a dashboard starts out too complicated, it becomes difficult to weave all the components together."This makes it harder for developers to maintain and update," Baingana explains, "and it increases the need for specialized training to onboard new users.Pruning useless or obsolete components regularly is another helpful process that helps keep it clean and user-friendly."
Source: The major gifts report
DOI: 10.1002/mgr.32582
Author: Kerry Nenn
Institution: University of St. Thomas - Minnesota
Language: English
Subfield: Management Information Systems
Domain: Social Sciences
Open Access status: bronze
OpenAlex ID: W4409282228