Impossible Alone: Make Collaboration Visible Through a Shared Making Process

Read the campaign story

Impossible Alone launched around Atlassian’s Team 23 conference in April 2023. Contemporary reporting describes a brand film and three projects: Giving Trees, Earworm Eraser and Dreamkeeper. Their respective forms were a donation interaction, an audio piece and an AI-assisted image experience. Droga5 and specialist partners collaborated with Atlassian. The related projects count as one campaign, distinct from the company’s separate Team Playbook resource.

The reported business problem was recognition of the parent company behind familiar work-management products. This study treats the projects as demonstrations of collaborative making, not proof that software caused their results. In particular, it does not validate claims about changing intrusive tunes, reproducing dreams or producing charitable impact. The former campaign URL now redirects to the company homepage, so historical descriptions are not presented as currently available experiences.

Editorial interpretation: collaboration is difficult to advertise because the most important work often occurs between visible outputs. A shared project can expose complementary roles and give the audience something concrete to discuss. That makes the partnership itself part of the message. The connection remains incomplete unless the campaign explains how the advertiser contributes, rather than merely placing its name beside the finished result.

Editorial interpretation: playful interpretations of an impossible task can attract attention without establishing that the literal problem has been solved. A visualisation is not an exact record of an experience, and a symbolic interaction is not evidence of a social outcome. The useful lesson is to distinguish imaginative framing, functional output and substantiated result. Treating those as separate layers allows a campaign to be inventive without asking its audience to mistake metaphor for verification.

Reveal the handoffs that make the output possible

Map which participant contributes which capability and where their work connects. A team story becomes more informative when it shows a meaningful dependency, not just a row of partner logos. For a small organisation, an annotated process sketch can explain the relationship before a costly demonstration is built. Ask viewers what each contributor added and what would be missing without them. If they cannot answer, the collaboration may be visible as a credit list but absent from the actual communication idea.

Specify what the demonstration establishes

Write a modest claim about what can be directly inspected in the experience. Separate that from an interpretation and from any outcome that would require independent evaluation. A surprising interaction can show that an artifact exists or that a process connects; it does not automatically prove effectiveness, accuracy or benefit. Give reviewers a chance to state what they think has been demonstrated. Correct any stronger inference through the core presentation rather than relying on a qualification that contradicts the most memorable part of the experience.

Build a clear bridge back to the brand

A memorable project may become better known than the organisation that enabled it. Explain the advertiser’s relevant role in ordinary language, without claiming ownership of every contributor’s work. Connect the project with the audience’s actual question about the offer. Avoid asking people to infer a software benefit merely because a team used technology somewhere in the process. A useful next step might explain one shared task or show a bounded workflow. The brand connection should make the experience more understandable, not interrupt it with a disconnected sales message.

A small test for another brief

Proposed adaptation: an adult community-design group could make a fictional paper exhibition guide by combining a writer’s information structure, an illustrator’s original diagrams and a reviewer’s accessibility notes. Show one version as a finished guide and another with annotated handoffs. Compare understanding of collaboration and the organising service’s role. No donations, personal dreams, audio treatment, AI upload or live service is involved.

Ask participants to identify the handoffs and describe what the prototype demonstrates. Separate recognition of teamwork from claims about software productivity, psychological effects, charitable results or a guarantee that collaboration always succeeds.

Stop if the concept makes an unsupported health or accuracy claim, collects sensitive personal experiences or attributes the whole result to a sponsor without explaining other contributors.

• Give each role a specific fictional input and output.
• Credit contributions without implying endorsement.
• Keep a readable plain-text route to the same explanation.