Thank you for spending AI Week with us. We’re thrilled by the reaction and we all enjoyed replying to your questions. Thanks for engaging.

Historically, non-technical stakeholders would’ve had most of their data questions answered either through pre-built dashboards or by asking their Data team (or equivalent). Self-serve analytics tools went a step further by offering safe, governed datasets built by Data teams which let non-technical users dig into data without having to worry about how it joins together, how metrics like “revenue” are defined, and so on.

Continuous integration and continuous delivery (CI/CD) have dramatically changed how we ship software. But once code reaches production, the operational work is still surprisingly manual. Engineers continually monitor systems, investigate unexpected behavior, and decide which issues require action. And that is where the next opportunity for AI-driven automation lies. For example, in today's CI/CD workflows, someone refreshes the pipeline page to see whether the queue has moved.

AI is set to transform our technology landscape. For many of us working in software, it already has — developers are now writing more code, building more features, and deploying more applications, faster. For the teams supporting IT and software services that means more applications to support, across a greater breadth of technologies, and with more complexity (that is probably less well understood by the developers who created it). Your operational tooling needs to keep pace.

Getting your dashboards in the right hands is vital for many teams. This typically means that someone has to remember to check them, and that rarely happens consistently. Stakeholders miss weekly updates, managers ask for reports that already exist, and your carefully-built dashboards sit unread while people wait for someone to send them a screenshot. Scheduled sharing is the frictionless feature that solves this issue.

You’re about to click "Merge" on a PR, but you feel more anxious about it than you used to. Why?