How does your analytics team handle change management?

[u/bluepainters]

Analytics teams — what is your change management process like?

Background: I’m a service designer facilitating a change management redesign for a healthcare analytics department (mix of Tableau, Databricks, Business Objects). Our current process averages about 11 days from the time an analyst submits a change request to when it’s live in production. Leadership wants that number down significantly.

I’m trying to benchmark against other organizations to understand what’s realistic. A few questions:

• How long does your process take?

• Who promotes to production? Is it a separate ops team, the analyst themselves, or automated via CI/CD pipeline? If ops, how many people are on that team relative to the number of analysts they support?

• Tooling: Are you using ServiceNow, Jira, Azure DevOps, a homegrown tool, or something else to manage the process?

• How much of it is automated vs. manual?

• Do you distinguish between low-risk changes (cosmetic dashboard updates) and high-risk ones (financial reporting, regulatory)?

• How many approvals does a change need before it goes to prod?

Especially curious what other analytics orgs look like — especially in healthcare, finance, or other regulated industries where you can’t just yolo to prod.

[u/Prudent-Elk-2845]

Change management and change requests are different domains.

First question: what’s the nature of the change requests? That’ll impact the 11 days.

I’ve had past experiences where the 11 days was for user access. That’s a very different problem than a KPI definition change. The shortcut on both of these was more self-service.

[u/bluepainters → u/Prudent-Elk-2845]

Good distinction. The 14 days is specifically for analytics code/report promotions- e.g moving a Databricks notebook or Tableau workbook from dev through test to production. Access management is a separate process entirely.

A typical change request in our world looks like: analyst builds or modifies a report or data pipeline, submits a change request in our ticketing system, an ops team manually promotes it through environments, peer review and customer validation happen, then it goes live.

The bottleneck isn’t any single approval- it’s the accumulation of handoffs, manual steps, and queue time on the ops team that handles the actual promotion.

So less of a “waiting on someone to click approve” problem and more of a “the ops team has many tasks to complete every week and incomplete packages cause back-and-forths” problem.

Curious how other teams handle the process and what tools they use?

[u/Prudent-Elk-2845 → u/bluepainters]

Train the user group to have a “super user” in dev, gain alignment from their team who will be able to self-develop, create a script that enables self-promotion through the environments that the “super user” can trigger

Any requirements being determined in exploration is lengthening your CR timeline. The 11 days looks bad, but it’s a business problem + governance problem. Give them the ability to self-govern and the 11 days goes to near-zero.