How Spotify Design increases transparency with a tracking doc.

Our program tracker increases transparency at Spotify, provides space for asynchronous updates, and keeps the team accountable.
Spotify exists to give opportunities—to a million creative artists building sustainable livelihoods from their art and to billions of fans enjoying and taking inspiration from that art.

To do that successfully, Spotify program managers coordinate initiatives that move the product and our users forward, both on company- and org-wide levels. Within Spotify Design, every program is supported by a series of workstreams, milestones, and tasks that are owned by individual members of the Design organization.

We found ourselves tracking the layers of cross-functional work inconsistently, across various tools. And we wanted to cut through the noise. Our Design Ops team recognized a need for a single source of truth—a scalable solution transparent and intuitive enough to meet the needs of program managers
any stakeholders seeking information.

The problem: Death by a thousand copy-pastes

When I joined the team, we used an existing program tracker. And it worked for a while.

But with each new quarter or phase of the program, we were forced to rebuild the entire tracker, copying and pasting content from one doc to the next. Because tables weren’t linked, any updates to data needed to be made across every table in every track. Efforts to adapt and evolve a program were difficult—as was convincing others to actually use the tracker.

The solution: Spotify Design’s program tracker

We wanted a hub for new team members to learn about tools and values, for squads to review each other’s progress, and for management to view the program at macro- and micro-levels. A doc that fit into existing rituals and connected people to their work.

So we created a new program tracker—the one templated in this doc—with three specific goals:
Improving asynchronous updates.
Reinforcing cross-functional transparency.
Increasing adoptability.

Eliminating duplicate data.

Our new tracker was created from the ground-up. We began by identifying the information that we wanted to connect within the doc and building an admin section to house the connections. With content successfully mapped, tables within the doc communicated with one another, saving us time spent on manual updates.

While content mapping seems like a simple concept, this foundational step was revolutionary for us—and something we’ve carried into every doc since.

Creating room to work.

While the
provide a holistic view of progress within the doc, we also carved out smaller, more focused spaces. With
, we created space to capture, document, and house work away from the noise of other workstreams or updates. This allowed team members to add content to their own individual workstream pages, while any updates automatically bubble up to other pages in the doc, like

Simplifying adoption—and adaptation.

Our new tracker was great, but it wouldn’t be a complete success without buy-in from others. The doc’s structure needed to be intuitive enough for people with context (like the doc builder) and those without (like high-level stakeholders).

So, we templatized our doc to take the stress out of spinning up a new tracker. And with the use of Coda’s Packs, we brought our trackers into the other tools our team uses every day—like a Slack reminder to add an update to a doc.

Apply our learnings to your own doc.

Our new program tracker has become the source of truth for program managers across Design. With each tracker, we’re committed to creating a hub of information for that program and team—a place where anyone can get a snapshot of progress at any point in time. Perhaps more importantly,
the tracker has provided us with a consistent language and structure for tracking discussing programs with stakeholders.

And we’ve already started experimenting with the boundaries of our trackers. We’re adopting the workstream page framework as space for individual tasks. We’re mapping our workstreams to OKRs to gain even broader perspective of our programs. Even teams outside of design are introducing the template into their own projects.

Ready to adapt our program tracker for your team’s needs?

Get started by
copying this doc
. Here’s what you can expect to find in this template:

provides a high-level summary about our team,
, and more. This page serves a variety of audiences at Spotify:
New hires
- Onboarding instructions and general information about the team ensures the new hire has all the knowledge they need to contribute to the team
Other teams
- For non-design teams at Spotify, the various pages in the overview gives them an idea of what our team is all about
Senior management
- Management can get a snapshot of what our team is working on, and they can dig deep into a specific program, workstream, or task if they want to
goes one step below the surface, providing workstream-related
and and team-related updates on
Individuals will spend most of their time within the
subpages. Here you’ll find a blank template and an example of an existing workstream. Keep the template to copy as your workstreams scale.
We’ve carved out dedicated space for all
relevant to the particular program you’re tracking. Again, you’ll find a blank template and an example notes. Make sure to keep the template to copy for each meeting.
drive the doc and are the base for your customization.

👉 Start exploring the doc with:

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.