Strategic Drift Gets a Smoke Detector: What's New in Atlassian Strategy Collection

Archived

October 13, 2026
Atlassian
AI
Rovo
Jira
Two railway tracks splitting apart through a green forest, a picture of strategy and execution quietly heading in different directions. Photo by Sergej (@skstrannik) on Unsplash.

Most strategy changes are announced in a meeting and abandoned in a spreadsheet. Leadership agrees on a new priority on Tuesday. The slide deck is updated by Friday. Three months later, the budget, the hiring plan, and forty Jira boards are still executing last quarter's strategy with admirable commitment.

Atlassian calls that gap strategic drift, and on October 8, 2026, as part of its Team '26 Europe announcements, it published a set of Atlassian Strategy Collection updates built to catch drift while it is still cheap to correct. The headline features are early warnings, AI spend visibility, scenario planning, and status updates that draft themselves. The fine print is that five of the six capabilities are in open beta, and every one of them depends on data most organizations have not connected yet.

What Atlassian announced, and the release state of each piece

Strategy Collection is Atlassian's strategic portfolio management solution. It bundles three apps: Focus for strategic planning, Talent for human and AI capital management, and Jira Align for enterprise portfolio execution. If the Collections packaging is new to you, our practical guide to Atlassian Collections explains what sits in each bundle and what can no longer be bought on its own.

According to Atlassian's announcement, the October release adds:

  • Strategic Intelligence in Focus (open beta). Flags priorities that are off track, at risk, or inactive across connected portfolio data, with a personalized "For You" page for each leader.
  • Atlassian MCP for Focus, Talent, and Jira Align (generally available). Uses the Model Context Protocol to connect the three apps to Rovo and to external AI tools, including Claude Desktop. Leaders can ask plain-language questions about the portfolio, build small custom apps on Strategy Collection and Teamwork Graph data, and take actions such as posting weekly updates.
  • Human and AI Capital Management in Talent (open beta). Shows AI usage and spend next to the teams and initiatives it supports, and flags budget overruns.
  • Workforce Skills in Talent (open beta). Shows where specialized skills live and where the gaps are, for reallocating people toward new priorities.
  • Strategic Planning in Focus (open beta). Compares funding and headcount scenarios side by side using Jira delivery work, available capacity, and actual costs.
  • Agentic updates (open beta). Drafts progress updates from connected Goals, Projects, and Focus data. Teams refine and approve each update before it goes out.

One generally available capability, five in open beta. If your internal memo to leadership says "now available," make sure it says which one.

Why the intent, investment, and outcomes framing matters

Atlassian frames drift as a disconnect between three things: intent (the priorities leadership chose), investment (where people, budget, and AI resources are actually deployed), and outcomes (what changed in the real world). That framing is the most useful part of the announcement, because it explains why drift is so hard to see. The information usually exists. Goals live in slides, budgets in spreadsheets, and delivery in Jira. It simply never sits in the same place at the same time, so the quarterly review turns into an autopsy instead of a course correction.

We made a similar argument about building Jira dashboards executives actually use to steer: leaders rarely lack data. They lack a translation layer between the work and the decision. Strategy Collection is Atlassian's attempt to make that translation layer a product.

The AI angle sharpens the problem. Atlassian argues that AI widens drift because teams now execute faster, and faster in the wrong direction is still the wrong direction. The announcement includes a quote from Helen Lau, General Manager of Engineering Platform at Commonwealth Bank of Australia, who says agents already drive almost half of the bank's Atlassian interactions. That is one customer's figure, not an industry benchmark. It does illustrate the point: a growing share of the "work in progress" was never in the all-hands meeting where the strategy changed.

The part people will skip: AI spend becomes a portfolio line item

Human and AI Capital Management is the capability I expect finance teams to care about first. It places AI consumption next to the initiatives that consume it, which turns "is AI paying off?" from a quarterly finance exercise into a portfolio question.

The timing is not a coincidence. As we covered in our breakdown of Atlassian usage-based pricing, Atlassian is moving Rovo credits and Automation steps onto metered allowances in December 2026. Once AI usage carries a real invoice, someone will ask which initiative it was for. Talent is Atlassian's answer to that question.

The catch is attribution. AI spend can only be connected to an initiative if the work, the team, and the usage are already mapped to that initiative. Without that mapping, the feature will faithfully report a large number with no owner.

What Strategy Collection will not fix on its own

The prerequisites are real. Atlassian's Strategy Collection page states that the collection requires Jira Cloud Premium as a minimum, is sold through Atlassian sales rather than self-serve, and that Focus, Talent, and Jira Align are not available as standalone licenses. Existing Jira Align customers add Focus and Talent through their Atlassian account team.

Inactive often means unlinked. Strategic Intelligence can only flag a priority as inactive if work is linked to it. If half your active epics are not connected to a focus area, the early warning system will cheerfully warn you about your linking discipline. The capacity and cost data Jira now holds natively, which we covered in our look at Jira capacity planning and formula fields, only improves Strategic Planning scenarios if teams actually maintain it.

Self-drafting updates still need an owner. Agentic updates remove the blank-page problem from status reporting. They do not remove accountability. Atlassian built in a refine-and-approve step, and that step should stay mandatory. A status update that writes itself can also be confidently wrong.

Connecting external AI tools is a permissions decision. Generally available Atlassian MCP access means portfolio data, including budgets and workforce skills, can be queried from Rovo and external AI clients. Those tools act with the access the user already has. Before turning this on, read our audit of how Atlassian agents enforce your permissions exactly as written, then check who can see Talent and Focus data today.

Who should care, and who can wait

  • Enterprises already on Jira Align or Focus should test the open beta capabilities now, starting with Strategic Intelligence, because the data is already partly connected.
  • Organizations on Jira Cloud Premium running portfolio management in slides and spreadsheets should evaluate Strategy Collection, with a realistic plan for the linking work it requires.
  • Smaller organizations and single-product teams can probably wait. Jira's native plans, goals, and dashboards may already cover what you need, and a portfolio tool will not resolve a portfolio you do not have.

What to do before the betas grow up

  1. Write down current intent. One list of active priorities, each with a named owner, kept in one place.
  2. Measure your linking. Check what share of active epics and initiatives connects to a priority. If the answer is low, fix that before switching on Strategic Intelligence.
  3. Tag investment. Make sure teams, cost centers, and AI usage owners map to initiatives, so spend has somewhere to land.
  4. Assign approvers for agentic updates before the first draft appears.
  5. Review Focus and Talent permissions before connecting external AI tools through Atlassian MCP.
  6. Pick one drift question to answer within 30 days. For example: which funded initiatives had no delivery activity last month?

The Avaratak Take

The most consequential item in this release is the only generally available one. Atlassian MCP makes the portfolio queryable by executives who will never open Focus. A chief financial officer can ask an AI assistant which priorities are off track and get an answer drawn from live delivery data. That is genuinely useful. It also raises the stakes on data hygiene, because the answer will be delivered with total confidence whether or not the linking behind it is any good.

Where I expect customers to overreact is in buying Strategy Collection to fix an alignment problem that is really a decision problem. A tool can show you that three teams are still funding an abandoned bet. It cannot make a leadership team agree to stop funding it. Drift is visible long before it is corrected, and the gap between those two moments is organizational, not technical.

My recommendation is to treat each open beta capability as a pilot with a defined question and a deadline. The test is simple: does the tool surface drift earlier than your quarterly review would have? If it does, it has earned its place. If it does not, you have bought a nicer slide deck.

Common questions about the Strategy Collection update

Is Strategic Intelligence in Focus generally available?

No. Atlassian's October 8, 2026 announcement lists Strategic Intelligence in Focus as open beta. The Atlassian MCP connection for Focus, Talent, and Jira Align is the generally available capability in this release.

What do I need before I can buy Strategy Collection?

Atlassian states that Strategy Collection requires Jira Cloud Premium as a minimum and is purchased through Atlassian sales. Focus, Talent, and Jira Align are sold together only as part of the collection.

Does Strategy Collection replace Jira Align?

No. Jira Align is one of the three apps in the collection, alongside Focus and Talent. Existing Jira Align customers can add Focus and Talent through their Atlassian account team.

Strategy keeps shifting, which is the whole point of having one. If you are working out whether Strategy Collection fits your environment, or what linking work it would take to make the early warnings trustworthy, Avaratak's senior Atlassian consultants are happy to help separate the useful part from the shiny part. Book a discovery conversation whenever it is useful.

Related reading

Share this post:
Get new posts by email
Check your inbox. We sent a confirmation link, and nothing else arrives until you click it.
That didn't go through. Try again in a moment, or email blog@avaratak.com and we'll add you.
One email per new post. Confirm from your inbox. Unsubscribe any time.