How should we use AI to write?
AI is a helpful tool but, without guardrails, its writing can fall flat. We joke about AI tells like em-dash overuse and “it’s not X, it’s Y,” but issues with over-reliance on AI writing go deeper.
- Externally: We’re all already inundated with increasingly AI-generated text. And if you’ve ever received an email clearly written by AI, you’ve likely felt how it erodes trust in the sender.
- Internally: AI-generated content feeds our knowledge graph. Think of it like a constant xerox copy of a photograph—with each copy of a copy, the quality degrades. When the content is generic and unvetted, it solves for no one.
On Atlassian’s Brand team, these areas are top of mind. We want to move fast with AI but still put out content that is useful, fun to read, and trustworthy. Our mission has always been to unleash the potential of teams, and we believe a key part of that is putting out content that represents our best, most actionable, and most unique thinking.
In April, we brought together a group of writers across Atlassian to discuss if, where, and how AI should show up in the writing process. We then pressure-tested those guidelines with our entire Marketing function.
In the spirit of “Open company, no bullshit,” we decided to publish them here as well.
This is an ongoing journey. Rather than a rigid set of rules, these guidelines outline what we aspire towards. We hope they’re useful for your team, too.
disclaimer
As AI capabilities evolve, these guidelines will, too. We’re committed to revisiting them every three months or as AI capabilities change to keep future-forward thinking in balance with rigorous quality control.
- First pulled together: April 1, 2026
- Last updated: June 24, 2026
Core principles
- Humans lead all writing and ideation. AI can help validate, edit, and refine, but a human should always write the first and final drafts in their own voice.
- Everything we publish needs to have a human byline. That human is publicly accountable for the content, including anything AI-influenced.
- Give AI the proper context. When using AI to edit or refine, always specify the text’s audience, purpose, and tone to avoid generic feedback.
- Fact check, fact check, fact check. Anything AI says or suggests must be verified by the accountable human before implementing—including any factual information, data, or quotes.
- Don’t publish anything you wouldn’t read yourself. If you don’t find the piece genuinely helpful or resonant, our audience probably won’t either.
- Guard against AI erasure. AI defaults to the audiences most represented in its training data, over-representing some perspectives and potentially flattening others. When reviewing AI writing suggestions, pay as much attention to what it removes as what it adds.
Applying these principles at Atlassian
Great uses of AI
Encouraged use cases (with human ownership):
- Identify gaps or weak spots in a draft (“Where is this argument unclear or unsupported?”).
- Stress-test messaging (“What objections might a skeptical reader raise?”).
- Group verified customer research themes into structured takeaways.
- Turn detailed human bullet notes, research findings, or a strong outline into a structured first pass.
- Narrowing down multiple ideas into one strong contender.
Proceed with caution
These uses require careful editing and judgment:
- Drafting additional collateral (social posts, newsletter blurbs, pull quotes).
- Rewriting for voice or tone.
- SEO support – suggesting keywords, meta descriptions, or header structure.
- Light competitive positioning exploration.
- Aligning content with narrative pillars.
Do NOT use AI
These uses are prohibited:
- Generating statistics (quantitative or qualitative), customer testimonials, or case studies.
- Inventing product claims or performance results.
- Drafting content without defined Atlassian context or POV.
- Determining the core argument or differentiated thesis.
- Treating AI as the final authority on fact-checking.
acknowledgements
A special thank you to Martha Fishburne for driving this project and to Arseny Tseytlin, Sid Chaturvedi, Kesha Thillainayagam, Jane Thier, and Katelyn Miner for contributing.


