Atlassian dropped from Australia's Best Tech Employer list while Canva rises: the AI transformation playbook that decides which Aussie tech brand survives 2026
Atlassian and Canva are running the same AI restructure. The employee surveys say one is landing as growth, the other as restructure. The change management is the variable.

Two Australian tech employer rankings landed in early May 2026. The Best Workplaces in Tech 2026 list, based on nearly 25,000 employee surveys across 50 Australian companies, dropped Atlassian entirely. Atlassian had been ranked 3rd in 2025. The LinkedIn Top Companies list named Canva as #6 for career growth in Australia. Macquarie Cloud Services took #1 small company for the second year running.
In the same window, Bloomberg ran a long-form feature describing Canva's "risky AI transformation": going all-in on internal AI tooling across product, design and operations. Atlassian is doing functionally the same thing: deeply integrating AI into the product, reorganising teams around AI-native workflows, and asking every employee to operate differently.
Same playbook. Opposite employee response. That gap is the story.
The AI is not the variable
The natural read of the rankings is "Atlassian is bad, Canva is good." That read is wrong.
Both companies are running deep AI transformations. Both are integrating AI into core products. Both are restructuring teams. Both are demanding new skills. Both are betting the future of the business on AI-native workflows.
The technical work is similar. The cultural work is not.
The employee surveys show the difference. Atlassian's employees are reading the transformation as "I am being restructured." Canva's employees are reading the same transformation as "I am growing into this." The objective facts are similar. The subjective experience is night and day.
The change management gap
Canva is being explicit. Every team has been briefed on: which roles are being expanded as AI scales, which roles are being redefined, and which roles are being deprioritised. The narrative inside the company is "here is the company we are becoming, and here is your seat in it." Even employees whose roles are being deprioritised know where they sit in the plan.
Atlassian's narrative, based on the survey signal, is missing the explicit version. Employees know AI is changing the company. They do not know what it means for their specific role. The story they fill in for themselves is the worst-case version. That is what shows up in the rankings.
This is the change management gap. It is not about communication frequency. Both companies communicate often. It is about specificity. The Canva narrative names roles, teams and outcomes. The Atlassian narrative talks about transformation without naming who specifically wins or loses.
Why this matters for Sydney agencies
Every Sydney agency owner with more than 10 staff is running an AI transformation right now. The transformation has the same shape as the Atlassian and Canva ones: new tools, new workflows, new expectations.
The question is whether the team is reading the transformation as growth or as restructure.
If you have:
- Hired a head of AI in the last 12 months
- Rolled out new internal tools without naming which roles they replace
- Asked the team to "use AI more" without specifying what success looks like
- Restructured a team or service line and called it "evolution" without saying who wins and loses
Then you are running the Atlassian play, not the Canva play. The team knows the transformation is real. They do not know where they sit in it. The story they fill in is the worst one.
The narrative reset every agency owner needs to run
Five elements separate a Canva-shape AI narrative from an Atlassian-shape one.
One: Name the new operating model explicitly. Not "we are becoming AI-first." Specifically: "Here are the five teams we have. Here is what each one does in 12 months. Here is what each team stops doing." Specificity beats slogan every time.
Two: Name the roles that are growing. Identify the specific roles that gain scope as AI scales: usually senior judgement, client-facing strategic work, and quality assurance. Make these growth paths visible to the team.
Three: Name the roles that are being redefined. Be honest about the roles where the work is changing materially. Not "everyone will use AI more." Specifically: "The work this person used to do is now done by AI. The work this person now does is different. Here is the training pathway."
Four: Name the roles that are being deprioritised. The hardest part. If a role no longer fits the operating model, the responsible move is to say so: early, with notice, and with help into the next thing. The team knows when something is being deprioritised. Pretending otherwise erodes trust.
Five: Connect the transformation to a revenue narrative the team can see. Canva's employees know what winning looks like for the company. Atlassian's employees are not as sure. When the team can see the revenue line the transformation is supposed to grow, they read the change as growth. When they cannot, they read it as cost-cutting in disguise.
The audit every agency owner should run this week
Run an anonymous one-question survey to the team: "How would you describe the AI changes happening in the agency right now: career growth, lateral move, restructure, or other?"
If the dominant response is "career growth," you are running the Canva play. Keep going.
If the dominant response is "restructure" or "other," you are running the Atlassian play. The fix is not more tools. The fix is the narrative reset above. Until the narrative is explicit and role-specific, the team will read every new tool as another step toward their replacement.
This is the part most agency owners underrate. The AI transformation is happening in the agency whether the narrative is clean or not. The variable is whether the team comes with you or starts looking for the door. Atlassian and Canva just gave Australia a free A/B test on which approach works.
The Sydney agencies that come out of 2026 strongest are the ones who run the Canva play deliberately, this quarter, before the team writes the worst-case version of the story for themselves.
