Somewhere along the way, teams decided the best way to manage projects was:
send an email → wait → follow up → follow up on the follow-up → Then schedule a meeting about the follow-up

At this point, the project isn’t delayed, it’s emotionally exhausted

This event is for teams ready to stop treating communication as the work, and start actually running the work.

Let’s begin with the bold idea that projects can run without email chains

How to Run Projects with Atlassian (Without Sending a Single Email)

This is not about “using Jira better.”
This is about escaping the black hole of status updates.

We’re talking:

• Turning Jira into a system people don’t avoid

• Using Confluence for decisions, not digital dust collection

• Making Jira Service Management actually manage something

• Replacing half your meetings with Loom (and no one complaining)

End result? Work moves. People breathe. Emails… become optional

Now that work is (finally) moving, let’s talk about the part that quietly breaks everything, notifications

Notifications in Jira Service Management, From Chaos to Control

Notifications are either:

• So quiet nothing happens

• Or so loud people mute everything and disappear

There is no in-between. Or… is there?

We’ll break down:

• Why default notifications feel personally offensive

• How automation can turn noise into signal

• When you stop configuring and just bring in an app to save yourself

Because “I didn’t get notified” and “I got too many notifications” shouldn’t both be true at the same time.

And just when everything sounds clean and structured, reality enters the chat.

Panel Discussion: Unfiltered Atlassian | What Actually Works

We’ll wrap things up with a candid panel featuring our speakers and the founders of Optimizory, an Atlassian Marketplace partner who’ve seen it all.

Expect:

• Honest takes on how teams actually use Atlassian tools

• What breaks at scale (spoiler: a lot of things)

• When to customize vs when to stop overengineering

• And probably a few opinions you won’t hear in official docs

If any part of this sounded uncomfortably familiar, you should probably attend