WFP’s analytics team started with what they call a “server reboot,” focusing on content management within their Tableau Server environment. As a result of rapid growth—about 12 times the size within 24 months—there was an abundance of published dashboards on their Tableau Server, with very little organization, impacting discoverability. This also led to unnecessary work, since people were recreating dashboards and data sources that already served a specific purpose.
“We found that some people were publishing multiple versions of the same data source, so we wanted to consolidate and bring some order to the chaos,” shared Prianka.
The team set out to create a sandbox environment so administrators could monitor server content and end users could have more clarity about what are ready-to-use products. This meant tracking high-profile content that could then be certified for widespread use or flagged for potential deletion if the content was stale.
Tableau Blueprint helped the team bring structure to some of the questions they were getting from employees around data access—for example, “where is the data I need?” or “why can’t I access this data source?” Blueprint’s governance framework helped them identify gaps in their data strategy, particularly around data quality and content management. They now understand the steps they needed to take to ensure data is fresh and trusted, as well as used responsibly across the organization. It also came in a good moment, since WFP is launching a new data strategy this November that will allow the organization to increase the amount of data available for analysis.
“In this moment, we’re making data a more powerful asset within the organization, bringing our data to a new level internally,” shared Prianka. “Previously we thought of each track linearly, but Blueprint changed our perspective—that they need to run in parallel.”
As part of these strategic discussions, they found clarity around roles and responsibilities, particularly around server management and governance. They also found that they needed additional headcount to support their plan and to help advocate for best practices moving forward.
“Blueprint helped us to identify the need for a new headcount to head up governance and help with the robust server configuration change we needed, including training our users and administrators on how to publish and certify data sources. The lack of knowledge on this has been generating a huge number of avoidable tickets and really impacting our daily work,” explained Prianka.