intercom.help Open in urlscan Pro
54.87.14.112  Public Scan

Form analysis
1 forms found in the DOM

/atlas-by-atlassian/en/

<form action="/atlas-by-atlassian/en/" autocomplete="off">
  <div class="flex w-full flex-col">
    <div class="relative flex w-full sm:w-search-bar"><input type="text" autocomplete="off"
        class="peer w-full rounded-search-bar border border-black-alpha-8 bg-white-alpha-20 p-4 ps-12 font-secondary text-lg text-header-color shadow-search-bar outline-none transition ease-linear placeholder:text-header-color hover:bg-white-alpha-27 hover:shadow-search-bar-hover focus:border-transparent focus:bg-white focus:text-black-10 focus:shadow-search-bar-focused placeholder:focus:text-black-45"
        placeholder="Search for articles..." name="q" value="">
      <div class="pointer-events-none absolute inset-y-0 start-0 flex items-center fill-header-color ps-5 peer-focus-visible:fill-black-45"><svg width="22" height="21" viewBox="0 0 22 21" xmlns="http://www.w3.org/2000/svg" class="fill-inherit">
          <path fill-rule="evenodd" clip-rule="evenodd"
            d="M3.27485 8.7001C3.27485 5.42781 5.92757 2.7751 9.19985 2.7751C12.4721 2.7751 15.1249 5.42781 15.1249 8.7001C15.1249 11.9724 12.4721 14.6251 9.19985 14.6251C5.92757 14.6251 3.27485 11.9724 3.27485 8.7001ZM9.19985 0.225098C4.51924 0.225098 0.724854 4.01948 0.724854 8.7001C0.724854 13.3807 4.51924 17.1751 9.19985 17.1751C11.0802 17.1751 12.8176 16.5627 14.2234 15.5265L19.0981 20.4013C19.5961 20.8992 20.4033 20.8992 20.9013 20.4013C21.3992 19.9033 21.3992 19.0961 20.9013 18.5981L16.0264 13.7233C17.0625 12.3176 17.6749 10.5804 17.6749 8.7001C17.6749 4.01948 13.8805 0.225098 9.19985 0.225098Z">
          </path>
        </svg></div>
    </div>
  </div>
</form>

Text Content

Go to Atlas
English;
English
Go to Atlas
English;
English

All Collections

∞ The Loop

Introducing The Loop communication framework
Introducing The Loop communication framework

A framework for healthy and effective communication across teams

Written by Daniella Latham
Updated over a week ago

The Loop is a framework for healthy and effective communication across teams. We
use it at Atlassian, and it can be applied to any organization, whichever tools
they use.



Watch the video or dive into more ⤵️






WHY WE SAW A NEED FOR THE LOOP

For all the effort that has gone into creating Agile rituals for intra-team
comms, and design thinking rituals for customer comms, it’s shocking how little
thought has gone into designing a better system of communication across
teams–until now.





Team-to-team communication is not taught, not valued, and often gets a bad rap
as “status reporting.” Does any of this sound familiar?





We don't need another redundant meeting on our calendars. And we certainly don't
need yet another color-coded, cluster of a spreadsheet to update that no one
reads. What we need is a system of communication designed specifically for the
world of modern work we all find ourselves in right now. So, we created one.




A FRAMEWORK FOR HEALTHY & EFFECTIVE COMMUNICATION ACROSS TEAMS

We named it the Loop because after adopting it ourselves, our own teams felt
more “in the loop” with work happening across the company without feeling
overwhelmed, enabling us all to feel more connected and move work forward more
effectively.




THE LOOP'S FOUR BELIEFS

The Loop is based on four core beliefs about what makes for healthy and
effective teamwork. It’s these beliefs that underpin Atlas and how it works:

 1. Common vocabulary over common tooling

 2. Open up your work in progress

 3. Curate, don't automate

 4. Show that you're paying attention




BELIEF #1: COMMON VOCABULARY OVER COMMON TOOLING

A couple of years ago, we looked at the status of projects across Atlassian and
saw dozens of projects had marked themselves as green–on track.





Then we dug a little deeper and realized that each of the project’s
interpretations of “on track” was completely different. One project didn’t have
a committed team yet, another was waiting for legal approval, and one was
actually complete.



That’s no longer one of our biggest issues at Atlassian (trust me we still have
plenty), because every team, every department, every intern, and every exec has
a common vocabulary to share the status of their projects.



Learn how to practice this belief with Atlas




BELIEF #2: OPEN UP YOUR WORK IN PROGRESS

The only way cross-functional collaboration works is if you open up work that’s
not yet done. As a former management consultant, I've been scared in the past to
share imperfect drafts. Today though I'm a perfectionist in full recovery.





When you open up your work in progress you can reap the benefits of getting
feedback early and often if set expectations with stakeholders about the stage
your teams’ work is in.



Learn how to practice this belief with Atlas




BELIEF #3: CURATE, DON'T AUTOMATE

Effective cross-functional communication needs curation, more than it needs
automation. We're all constantly drowning in a never-ending stream of chat
messages, e-mails, and an abyss of unread notifications. And no matter how much
smarter our apps get, there’s still just too much content to consume.





At Atlassian, teams have started holding themselves accountable for limiting
what they communicate, just like crafting that perfect Tweet, we force ourselves
to be more deliberate about what we share, with who, and when. Curation is
making us much better communicators than automation ever will.



Learn how to practice this belief with Atlas




BELIEF #4: SHOW THAT YOU'RE PAYING ATTENTION

There is no loop if communication is one-sided. We believe that showing that you
are paying attention is critical to keeping communication flowing among teams.





It’s the worst feeling in the world to belabour over writing a status report,
only to have no one acknowledge it. So, part of the Loop is creating rituals
that keep stakeholders engaged and teams motivated.



Learn how to practice this belief with Atlas
Did this answer your question?
😞😐😃
 * Learn more about Atlas
 * Join the Community