By Bridget Suthersan, Data Analysis Manager at Amnesty International UK and member of the Data Collective.
As a person working in a data team in a charity, how often do you get to the end of the week and feel like you’ve just spent your time fire fighting and responding to last minute urgent data requests?
In other words, how often do you feel like you’re not being proactive, only reacting to the needs of other teams?
Data teams do need to be responsive to the needs of other teams. Problems arise, though, when data teams cross the line and become overly reactive. It’s really hard to define the line between responsiveness and reactivity, but generally, you might see a reactive data team:
- Dealing with lots of last-minute requests, often with unrealistic timelines or expectations attached;
- Working with key stakeholders or teams who have a poor understanding of the data team’s processes, skills, and workloads;
- Finding themselves overlooked when other teams are implementing key processes or policies that impact them;
- Having a poor understanding of other team’s strategic priorities and their role in helping them achieve them.
A reactive data team is not seen as true collaborators or business partners. Members of the team may feel that they have limited control over how they spend their time and are buffeted from task to task and request to request.
From a stakeholder perspective, there are also key drawbacks: most importantly, a reactive data team is often too busy to consistently supply timely or detailed information to support data-driven decision making. Data requests then necessarily become concise, condensed, and limited. There is no capacity to get answers for all but the most immediate questions.
Why do some teams find themselves working in this way? Many data teams do have members with the skills to conduct more detailed, in-depth analyses that could contribute real value to strategic decision-making and which many stakeholders would undoubtedly welcome.
Perhaps it is because, once established, it can be very difficult to break out of the reactivity paradigm. From the data side, spending your days fulfilling one data request after another means you are not building up a good understanding of the priorities of other teams. Meanwhile, the full capabilities of data teams remain overlooked or even invisible to key stakeholders as they rarely call on data teams to provide in-depth analysis.
Moving away from reactivity
Moving away from reactivity is about building up a shared understanding of data tasks, how long they take, and their contribution to the strategic objectives of other teams. This will invariably look different for different organisations, and different teams, but below are a few ideas:
- Talk strategy: Take every opportunity to talk to other teams about their strategic priorities, and the role that they see the data team playing in helping them achieve them.
- Document key projects: Other teams may ask for work without knowing much about your other priorities or tasks. Keep a full list of the major projects that you are working on, and regularly share with other teams. If possible or appropriate, involve them in helping you balance competing priorities
- Probe motivations and make suggestions: If it is unclear, take the time to understand why a stakeholder is asking for the data. If appropriate, make suggestions: ‘Have you thought about doing it this way? Can I ask, why have you decided on this course of action?’
- Talk in time, not only tasks: One of the inherent complexities of data work is the fact that a timeline can be easily derailed by issues that are only identified once you get into the details: missing data, unclear documentation, etc. Informing stakeholders how long a task has taken you, along with the key steps you have taken to complete it, can help to build up an understanding of the nature of data work.
- Embed a member of your team with other stakeholder teams: Have yourself, or some of your team, follow the data request to understand and get better insight into the full or strategic use of the data
- If possible, provide tools and reports for other teams to obtain routine data requests themselves: This will free time for you to contribute to more strategic tasks
- Produce deep dives and share results with other stakeholders: This will demonstrate to other departments the higher-value work that you could do to help them strategically
The above are just a few ideas – shifting a data team from working reactively to proactively requires a multi-pronged approach. Building up the relationships, trust, skills, and processes necessary to work more proactively is likely to take time and persistence. But breaking out of the reactivity paradigm is ultimately to the benefit of everyone – data team and stakeholders alike.
