IT News: September 2025

Overview of releases, incidents, and team plans for the month. This update matters for every department across the company, and we want to make sure the context, timing, and next steps are clear before anything changes in your day-to-day work.

What's changing

We have been preparing this change for several weeks together with the teams it affects most. The goal is to remove friction from a process that many of you rely on every day, while keeping the parts that already work well untouched.

Nothing happens overnight. The rollout is staged so that each team has time to adapt, ask questions, and give feedback. If you spot anything that looks off during the transition, you can reach the responsible team directly through the usual channels.

“We are not adding process for its own sake — we are removing the steps that slow people down and keeping the ones that protect quality.”

What you need to do

For most people the practical impact is small, but a few habits are worth adopting early so the transition feels smooth:

• Review the summary above and note the date the change takes effect.
• Update any saved links, templates, or bookmarks that point to the old flow.
• Share this article with teammates who handle related requests.
• Send questions to the responsible team rather than improvising a workaround.

Next steps

We will publish a short follow-up with answers to the most common questions once the first teams are onboarded. In the meantime, this article will stay up to date — check back if you need the latest version of the details.