I love these types of questions! So it depends on the types of changes we want to make. Let’s use two changes as an example here: Orisa’s recent Fortify nerf (125 to 75) and something like Brig’s upcoming ultimate rework (I’m going to try to answer this without revealing too much about the change).
Say we wanted to just do a seemingly simple change like the Orisa Fortify nerf. It’d start with the balance team making a decision then informing other groups (for this usually our Producer/QA/Live Ops) that a change is coming and will require a hotfix. Then a designer would go into Orisa’s scripts, make the change, and submit. At that point QA and Live Ops are notified, QA tests the change to make sure it’s all good and Live Ops will then get the build process going. We usually see that hotfix occur the next day, so overall a small change like this takes about two days (critical changes can happen faster but hotfixes have a chance to introduce a small amount of instability).
Now for the Brig Rally changes, these are changes that do involve other teams. So we may start off with a similar origin point, design wants to make a change. This change could involve various art disciplines (such as vfx, modeling, etc.) or sound, so now it’s important to see where we can fit on their calendar. Design mocks up the change, shows it to art/sound so we can get an estimate on how big the ask is and then hopefully slots the change in for a future season. Since our other disciplines are working on so many things, such a change may not happen the next season or even the season after – it’s dependent on how big your ask is, how much lead time design is giving the affected teams, how much bandwidth those teams have, and ultimately how high of a priority the change is. That process can take anywhere from a month to 6 months, so we have to be forward looking and work together constantly in order to deliver new things to the community in a timely manner.