If you’re lucky, you know what it will take to get your next promotion. Maybe you need to work on communicating your analyses at the C-level instead of primarily to functional managers. Maybe you need to finish a complex project like a predictive churn model. But there is lot of work in every analytics role that just has to be done, even if it doesn’t seem to help you get from where you are to where you want to be. You have ad-hoc requests coming in, you want to test out a new tool that looks like it will really improve productivity, and you spend an awful lot of time in cross-functional meetings just trying to stay plugged into what is going on around the company.

Tanya Reilly created the term glue work to capture “the less glamorous - and often less-promotable - work that needs to happen to make a team successful.” Glue work is valuable - without it, projects fall apart - tasks get dropped, teams miscommunicate, and it is just harder to get things done. However, there is a difference between valuable and valued. If there’s nothing in your job description or career ladder that addresses this work, when it comes to promo time, it can be hard to get credit for the time you spend on these tasks. If glue work makes the team function more smoothly and effectively, but it is not valued, then that is a problem.

Ultimately, team management should be responsible for aligning valuable and valued in their team’s work. Unfortunately, there’s often a disconnect. If you’re a manager, there’s a lot you can do to help that situation. But even if you aren’t (yet), you can take tangible steps to set yourself up for success (and hopefully a promotion). Let’s dig into it.

What Does Glue Work Look Like in Analytics?

Analytics has become much more technical in recent years, and Reilly’s descriptions of glue work resonate in some ways. But analytics is by its nature more collaborative and cross-functional than engineering, and I think that yields some meaningful differences.

Engineering is a well-defined discipline, with established norms and practices - whereas in analytics we’re in the midst of a period of transition where the dominant tools, processes, and expectations are shifting. We’re adopting some of the best practices of engineering, but it’s a work in progress. Most of us don’t have (and maybe don’t want) a product manager to sort through competing stakeholder requests and determine priorities - we work closely with our stakeholders and do that ourselves. Our teams often include folks with a pretty wide range of technical skills. There is a lot of variation in the work we do, and fewer clear rules on progression.

Engineers also generally report into other engineers all the way up the org chart, so there is reasonable alignment on what success looks like for an individual contributor. On the other hand, an analyst may report into a manager who understands the nuances of their technical and non-technical contributions, but the next level manager could be an engineer, a finance leader, a marketer, or anywhere in between. As a result, there isn’t always good alignment on what the most important parts of Analytics work are. Your manager almost certainly has to defend your promotion at that level, and may be actively competing for promotion slots - so clarity and visibility of what is promotable becomes even more important.

From the small sample of teams I’ve been on, there may be as much variance between analytics teams as there is between analytics and engineering. But defining what glue looks like on your team is the first step to combatting it.

A Few Examples

The short answer is, what is promotable varies depending on what is (and isn’t) in your job description or on your career ladder. Glue work might include any of the following:

Sometimes within analytics teams, it’s work that crosses job descriptions. It can be:

And sometimes, technical data folks report into or have to pitch their promotion recommendations to a less technical leader. In that case, highly technical work can actually become glue work, including:

Why It Matters

All the work listed above is important and valuable. And all of it belongs in an analytics team. It really shouldn’t be glue work - it is the work. The alternative is wasting time on analyses that aren’t aligned with business priorities, team members getting stuck, accumulating technical debt, losing trust from stakeholders, and maintaining painful manual processes. I lead analytics teams, and I want my team to be rewarded for glue work so we can all be more successful - and spend more time on work that will make the company more successful.

But it also matters a lot because the distribution of glue work is not equitable. Women are more likely to volunteer for non-promotable tasks at work (much like they do at home, but that is another story). Representation of women in analytics varies across specialties - women and men are close to equally represented among analysts, but less than a quarter of data scientists and engineers are women. Only 24% of analytics leaders are women. Tackling glue work is a real, tangible way we can help women advance and to work toward more equitable gender representation in analytics leadership.

If you don’t have any women on your analytics team, well, think about that the next time you’re hiring. But in male-only groups, the same men tend to volunteer time after time for non-promotable tasks. So regardless of the gender makeup of your team, a small number of people on your team are probably doing this work without being rewarded for it.

The Meta-Story

Arguably, analytics itself is glue within many companies. In most companies, the analytics team is not responsible for a revenue target. The team may not own any OKRs. The impact of analytics is subtler. Good analysts are multipliers, enabling the company to identify and focus on areas where changes can have the most impact. We don’t build features, we don’t close deals, but we shape the processes, tools, and cultures that enable companies to be smarter and faster across the board.

Yet, there is often confusion about what analysts are - they just write reports, right? Data science has the opposite problem - folks on the outside think it’s really exciting, but the reality is that it’s exciting occasionally, and boring a lot. In either role, when you tell someone that the “simple” request they asked for is really multiple days or weeks of work because the data isn’t yet available, isn’t well-defined, or needs significant transformation work, their eyes may glaze over.

These disconnects represent a misunderstanding between the company as a whole and the analytics team about what is valuable, and what is valued. Clearly identifying and communicating why different types of work is valued within the analytics team sets the stage to more clearly communicate the value of the analytics team itself to the rest of the company.

So What Do We Do About It?

The problem of glue work is fixable. If your team is doing work that helps improve the likelihood of success on projects, that work needs to be explicitly valued.


If you are in a position to drive systematic change in your organization, you can help align valued and valuable:


Maybe you are not in a position to change the system - yet. So what can you do to make it more likely that you’ll get promoted (and eventually be able to make those changes yourself)?

Glue work puts the health of the team ahead of individual accomplishments. It is core to the success of individual projects, but also to maximizing the impact of the analytics team overall. Explicitly valuing glue work and not relying on volunteers to do it helps team remain sucessful while leveling the playing field and improving gender equity.

I would love to hear what glue work looks like on your analytics team, and what you’ve done to address it. Send me an email or come have a chat in our slack channel!