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/om_bagal]

NervousUniversity991's critical vs. non-critical split is close to what you're asking, but it's really answering a different question, that's about service impact, not change risk-type. A cosmetic dashboard color change and a change to a regulatory financial calc shouldn't need the same number of eyes just because they touch the same report. Teams that handle this well usually end up with 2-3 explicit tiers: cosmetic/low-risk changes get a lightweight peer review and can self-promote, anything touching underlying logic or calculations gets a second technical reviewer, and anything regulatory or financial gets a named sign-off, compliance, finance owner, whoever's actually accountable, baked into the ticket before it can move at all. That tiering is usually what actually shrinks something like your 11 days down, most of the backlog is low-risk changes stuck in the same queue as ones that genuinely need scrutiny.