Atlassian Strategy Collection explained: Focus, Talent, and where Align fits

The Atlassian Strategy Collection is three apps sold as one offering: Focus for strategic planning, Talent for workforce planning, and Align (formerly Jira Align) for enterprise portfolio execution. For most organizations the work starts with Focus and Talent, supported by Jira Plans, Jira Product Discovery, and Atlassian Analytics on the Jira side, because that path connects priorities, people, and Jira work without rebuilding Jira first.

What the Strategy Collection is

Atlassian launched the Strategy Collection in April 2025, bringing together Focus, a new app called Talent, and Jira Align, which Atlassian now calls Align. It is built for leaders of technology-driven enterprises, and the commercial terms reflect that.

• Sold as one offering. Focus, Talent, and Align cannot be bought separately. Seats are counted for the whole collection, not per app.
• Cloud only, with a Jira Premium floor. The collection needs an Atlassian Cloud entitlement, and Jira Cloud Premium is the minimum. Teams on Jira Free or Standard have to upgrade first.
• Annual, with no trial. There is no free trial, and contracts are billed annually.
• Included for Jira Align customers. Existing Jira Align customers can request Focus and Talent at no additional cost through their account team.

You do not have to implement all three apps. Atlassian says so in its licensing FAQ, and adds that Talent gives more value once your focus area hierarchy and focus areas exist. That ordering shapes everything below.

Focus: the plan in one place

Focus is the strategic planning app in the collection. Everything in it hangs off focus areas, the strategic priorities your company is working on. A product admin defines the hierarchy first: one to ten levels, each with a type name you choose, such as business unit, portfolio, or initiative. The hierarchy page starts blank, so someone has to decide how your company breaks down its priorities. Each focus area can have one parent and many sub-focus areas, and data rolls up through those relationships.

A focus area then collects four kinds of information:

• Goals. Goals, or objectives and key results if you use OKRs. A key result sits under an objective and is not connected to a focus area directly.
• Work. Epics and higher levels from Jira sites on Premium or Enterprise, up to 250 linked work items per focus area, archived ones included.
• Positions. The people allocated to the focus area in Talent, with labor cost when labor rates are set up.
• Funds. Budgets, cost and benefit items, monthly forecasts and actuals, and baselines. Atlassian is clear that Funds works alongside your ERP and general ledger, not in place of them.

Focus then raises insights on the focus areas you own or follow, such as an overdue target date, a goal not updated in 30 days, or more than 10 percent of linked positions unfilled. Rovo can summarize a focus area and help explain an insight, and insights only use data the reader has permission to view.

Talent: who is working on what

Talent is the workforce planning app. It answers the question a deck rarely can: which people are working on which priority, and where the gaps are.

Talent gets position, worker, and organization data from your HR system through a Teamwork Graph connector that an organization admin sets up in Atlassian Administration. There are two: Workday, and an HRIS S3 connector that reads CSV files from an Amazon S3 bucket. Talent uses one connector at a time and syncs every six hours. Positions are then allocated to focus areas, by managers in their own reporting line or by admins in bulk with a spreadsheet. Today a position can be allocated to one focus area. With labor rates configured in Talent, Focus shows labor cost by focus area.

The Jira side: Plans, Product Discovery, and Analytics

Focus and Talent answer what matters and who is on it. Three tools around Jira cover how the work gets planned, where it comes from, and how it is reported. None of them is part of the Strategy Collection, and their plan requirements differ.

• Jira Plans (formerly Advanced Roadmaps). Included with Jira Premium and Enterprise, so every Strategy Collection customer already has it. A plan combines work items from boards, spaces, and filters across many teams, shows dependencies and flags the ones that are off track, schedules against team capacity and velocity, and lets you compare scenarios without changing Jira until you commit. Team-managed spaces can be included.
• Jira Product Discovery. A separate subscription with its own Free, Standard, Premium, and Enterprise plans, billed per creator. Product teams capture ideas and insights, prioritize them in views such as a value against effort matrix, and share roadmaps. When an idea is ready, they create or link Jira epics from the idea and track delivery progress there.
• Atlassian Analytics. Available only to customers with a Cloud Enterprise plan for Jira, Jira Service Management, or Confluence, and not included in the collection. It queries the Atlassian Data Lake, which holds Focus, Talent, Goals, Jira, and Jira Product Discovery data, so you can build dashboards that blend them across apps and sites. Atlassian has started renaming the app Insights.

How the pieces connect

1. Jira to Focus. An app admin connects Jira Premium or Enterprise sites in Focus admin settings, and Focus treats epics and anything above them as work. You map each Jira status to a Focus status so the roll-up means the same thing on every site. Boards, teams, and planning cadence stay as they are.
2. Initiatives in Jira. Jira Premium and Enterprise let you add a level above epic, such as initiative, which Plans can use too. It gives Focus one clean thing to link per strategic bet. The change applies to every company-managed space on the site, can break existing parent and child links, and cannot be undone, so treat it as optional and plan it first.
3. Product Discovery to Jira. Prioritized ideas become Jira epics or link to existing ones, and Focus links those epics. Atlassian does not document a direct link from Focus to ideas, so the epic is the handoff. Ideas can also appear as a field in Jira Plans, and a Goals field ties ideas to the same goals you attach to focus areas.
4. Talent to Focus. Positions and, if you turn them on, labor rates.
5. Everything to Analytics. On Enterprise, a Data Lake connection brings in the apps you choose. Analytics does not apply row-level permissions from your apps, so people who can view a dashboard may see data they could not see in Jira or Focus. Scope the connection deliberately.
6. Align to Focus. If you run Align, Atlassian Support connects your Align site to Focus, and Align epics and above can be linked to focus areas.

Where Align fits

Align is the enterprise portfolio execution app in the collection. It plans and tracks work across portfolios, programs, and teams, supports scaled frameworks such as SAFe, LeSS, Scrum@Scale, and Disciplined Agile, and coordinates teams that keep working in Jira or Azure DevOps.

It is included, but it is not where most organizations should start. Focus and Talent, together with Jira Plans, Jira Product Discovery, and Atlassian Analytics, cover the portfolio jobs people usually look to Align for: priorities linked to delivery, cross-team plans and dependencies, capacity, staffing, idea intake, and executive reporting. That path is also easier to implement. Focus links the epics you already have, while the Align Jira connector expects programs and program increments to exist in Align first, maps each Jira space to a program and each board to a team, and asks for workflows that require nothing but a reason on a state change.

Align remains the right call for large organizations running a scaled framework with program increments across many teams, or with delivery split between Jira and Azure DevOps. Neither path matches the other feature for feature. Our guide Do you need Jira Align? maps each job to the tool that covers it and lists where Align is still the better fit.

Who it is for

Atlassian built the collection for leaders of technology-driven enterprises. Four groups get the most out of it:

• Executives and strategy leads who own the priorities and need one current view of progress, staffing, and spend.
• Portfolio and program offices who run the planning cycle and today assemble the status deck by hand.
• Finance and people leaders who need budgets and headcount tied to priorities, not only to cost centers.
• Jira and platform admins who own the hierarchy, connections, permissions, and data quality that make the roll-up true.

If you are on Jira Standard, or your priorities fit on one page that rarely changes, the collection is more than you need today.

Where to start

The common mistake is to start with the plumbing: restructure Jira around a framework, connect every site, link hundreds of epics, and hope a strategy emerges from the roll-up. It does not. We start with the plan leadership already has and work top down.

1. Put the deck into Focus. We agree the hierarchy with leadership, then load focus areas, owners, statuses, and target dates with the Focus spreadsheet import. It is a visible win, and it does not complicate the leadership meeting.
2. Get the people in. We connect Talent to your HR data and allocate positions to focus areas. Staffing against priorities is rarely tracked well anywhere else, so this view tends to land fast.
3. Connect goals, top down. Goals or OKRs go on the top focus areas first, then cascade, each with an owner and a target date.
4. Connect initiatives in Jira. We connect your Premium or Enterprise sites, map statuses, and link the epics and initiatives teams already use, one business area at a time. Jira Plans carries cross-team planning, dependencies, and capacity for the teams that plan together.
5. Add intake and reporting. Where you run Jira Product Discovery, ideas are prioritized there and become the epics Focus links. On Enterprise, Atlassian Analytics reports across Focus, Talent, and Jira. Funds comes in when finance is ready.
6. Decide on Align last. If many teams need to plan together in program increments, Align can be added and linked to Focus. If they do not, you already have the roll-up without it.

Steps one and two need no change to Jira, and they give leadership something real to react to before anyone touches a workflow. Atlas Bench, an Atlassian Platinum Solution Partner, runs this sequence as our Strategy Collection implementation. If inconsistent statuses or epics would make the roll-up misleading, read Jira standardization before capacity planning first.