Kinaxis recently walked through its Q3 2026 product roadmap, and the direction of travel is unmistakable: more AI woven into the platform, more automation in how workflows get built, and a continued push to move core authoring capabilities onto Maestro Web. For any organisation running Kinaxis Maestro, this matters, not because the roadmap is unusual, but because of what it represents. The platform keeps getting more capable, release after release. The question that rarely gets asked in the same breath is whether the people using it are getting more capable alongside it.
What's actually changing
A few themes stand out from the session.
AI and automation are moving from add-on to infrastructure. Kinaxis is expanding AI capabilities across the platform, with AI-assisted workflow and script authoring on the way. The new Adaptive Semantic Graph initiative is designed to give AI agents better business context, so the insights and suggestions they generate are more grounded in how a specific supply chain actually operates. Longer term, the roadmap points toward AI-generated insights feeding directly into workflow execution: automation that doesn't just flag a decision but starts to help make it.
The migration to Maestro Web continues. Hierarchy management and Task Flow authoring, previously tied to the legacy Java client, are now available directly in the web interface. This isn't a cosmetic update. It's a steady reduction in dependency on legacy tooling, and it changes what "knowing the system" looks like for planners and administrators who built their muscle memory on the old client.
Data Fabric and Databricks integration deepen. New capabilities allow data publishing from Maestro to Databricks and ingestion of ERP data into Maestro using Databricks Open Sharing. This lays groundwork for more scalable analytics and self-service data management, but only for teams already set up to make use of it.
Inventory optimisation gets faster and more granular. Advanced Inventory Optimization now supports customer-specific service levels and part-site service time definitions, alongside meaningful performance improvements that reduce optimisation runtimes on large planning networks.
Administration and environment usability improve too, with new theming and branding options across development, test and production environments, and expanding monitoring support within Maestro Web.
Why capability alone doesn't move the needle
Every one of these updates is genuinely useful. None of them is automatically adopted.
A new scripting engine only saves time if the people writing scripts trust it enough to use it instead of falling back on what they already know. AI-generated workflow suggestions only improve decision-making if planners understand what the AI is basing them on, and know when to override them. Data Fabric only becomes a foundation for self-service analytics if the teams around it have actually been brought into how it works, not just told that it exists.
This is the pattern behind almost every platform rollout we've seen: the technology arrives on schedule, the training happens, go-live is declared a success, and then, six months later, half the new functionality is quietly sitting unused while everyone reverts to the workarounds they trust. Not because the platform failed. Because readiness was treated as a milestone instead of an ongoing state.
What "ready" actually looks like
Being ready for a roadmap like this one isn't about attending a webinar or reading a release note. It's a team that understands why the new capability exists, has had the chance to build confidence with it under low-stakes conditions, and has someone close by who can answer the awkward question without making them feel behind.
That's the layer that determines whether a feature like AI-assisted script authoring becomes part of how a team actually works, or becomes one more thing sitting unused in the corner of the platform. Capability and adoption move on separate timelines. Closing the gap between them is the work.
Go-Live is where most focus. Adoption is where we thrive.