Steps to managing and prioritizing data requests
As an early data hire at a fast-growing company, one of the first things that you’ll likely encounter is a backlog of questions from employees. This backlog, alongside all the other tasks associated with reporting, maintaining data and creating new pipelines can feel extremely overwhelming. These long lists of tasks and questions prevent many data teams from being proactive about analysis. Without a proper process in place that allows analysts to enable self-service, managing data requests proactively can feel like a never-ending battle against a current. Additionally, data teams that constantly need to answer the same question are not creating processes that help them manage the scale and complexity that companies experience as they grow.

Below are some of our tips on how to manage the data requests backlog. We believe that great data teams should be proactive. They should adopt tools and processes that ensure that the data team never has to answer the same question twice. We hope this step by step list is helpful to all data teams that want to improve their efficiency and reduce their workload in the future:

1. Set expectations about the data requests workflow with reasonable timelines

The first step of setting expectations around a team is communicating the way that your team is working to the stakeholders in the company. We suggest adopting an Agile workflow with weekly or bi-weekly sprints. Although your Scrum team may be small at first, setting expectations about when certain requests will be answered with the sprint methodology can be helpful. With scrum, a product is built in a series of iterations called sprints that break down big, complex projects into bite-sized pieces.

2. Define your requests workflow

Data requests are questions that employees have about data that exists in the organization or about new data that isn't being collected yet. Traditionally, data teams will take data requests through an intake form or a Slack channel where employees can ask for the request. Some of the requests are unique and difficult questions, which require the full attention of the data team. On the other hand, some data requests are repetitive and low priority, which doesn’t require much effort from the data team.

3. Create a requests template

We’ve created a data requests template for teams that are looking for a better way to manage inbound questions. Below is the template. Feel free to copy the template and use it in your team's workflow. Here's our template:

What is the business question you are trying to answer?

What is the impact of this question and how will it help the company?

Who will be using this data?

What time frames are crucial here? (Example: Monthly, weekly, daily)

What is the visualization you are trying to create?

What interactions/drill-downs are required? (Ie. the type of use, revenue amount etc.)

Are there any other details we should know about this data request?

4. Automate repetitive data requests

Data teams that take the next step with their data requests process can start to think proactively about data requests. Customer support teams have been deflecting inbound questions for years using tools like Intercoms knowledge base and Ada automated customer support chatbots. Smart data teams realize that they can do the same. Data teams can automate and deflect common questions with tools that allow them to document data requests in the same place teammates are looking for answers.

5. Measure the data requests workflow

Lastly, you can’t improve anything you don’t measure. Taking the time to measure what your users are asking, which tables are used the most, and who is the most influential user in your organization is a great way to automate more common questions.

If you found this useful, you can find the full article here: https://www.secoda.co/blog/how-to-manage-and-prioritize-data-requests