Atlassian CEO has confirmed that the company's IT team now reports to HR, according to comments reported by Information Age. The reorganization places the internal technology function — traditionally a standalone or finance-adjacent department — under the leadership of the people organization, a structural choice few large employers have made explicit.

The headline fact matters because it signals how one prominent technology employer now frames the relationship between workplace infrastructure and workforce management. Atlassian, the Australian software company behind products such as Jira and Confluence, has previously attracted attention for its distributed-work policies and team-based operating model. Moving IT into HR extends that logic to the org chart itself: the systems employees use to work and the systems used to manage employees now sit under one reporting line.

For HR leaders, the announcement raises a set of capability and governance questions rather than a single verdict on whether the model works. Atlassian's CEO has offered a rationale — the Information Age report carries his explanation under the headline "Atlassian's CEO on why his IT team now reports to HR" — and the reasoning will likely resonate with people executives who have spent the past several years arguing that employee experience is inseparable from the tools that deliver it.

The move touches several people-process decisions directly. Internal mobility, onboarding, hardware provisioning and access management all span the HR–IT boundary. When IT reports to HR, accountability for those handoffs consolidates: the department that owns the employee lifecycle also owns the infrastructure supporting it. That can shorten decision cycles for tooling changes and give CHROs direct control over the digital workplace budget.

It also concentrates risk. IT carries obligations — data security, access controls, regulatory compliance — that sit awkwardly under a function historically measured on engagement, retention and talent outcomes. Whether Atlassian's HR leadership has absorbed those obligations, or whether technical compliance remains a dotted-line responsibility elsewhere in the company, is the question other employers will need to answer before copying the structure.

The organizational-design precedent deserves attention either way. Most large companies still run IT under a CIO who reports to the CEO or CFO, with HR as a peer function. Collaboration happens through shared projects: HRIS implementations, identity management, hybrid-work tooling. Atlassian's choice collapses that boundary. It treats the technology employee experience as a people function deliverable rather than a technical one delivered on HR's behalf.

CEOs weighing a similar move can draw several testable questions from the announcement. Does the CIO role survive, and with what mandate? Which budget lines move, and how are shared services — security operations, infrastructure, vendor contracts — carved out? How will the change affect recruiting for technical talent who may read an HR reporting line as a downgrade in organizational status?

The reporting detail is also a signal for HR technology vendors. When the buyer of workplace tools and the buyer of people tools become the same executive, product categories blur. Vendors that sell employee-facing infrastructure now pitch a CHRO audience alongside — or instead of — a CIO audience. Adoption questions follow: does consolidated ownership accelerate deployment, or does it slow technical due diligence?

Atlassian has a track record of structural experimentation, and the company tends to publish its internal playbooks. HR leaders watching this space can reasonably expect more operational detail from the company as the reorganization matures — and the real test will be whether employee experience metrics and IT service performance both hold under the new reporting line.