CASE 114 / Slack / 2014
So Yeah, We Tried Slack…
A sceptical creative team became the demonstration of why a new collaboration tool was worth trying.
AI-assisted research and analysis for the SNS Creative Fieldbook; published by SNS Media Tech. No named human reviewer is claimed.
Sources reviewed 2026-11-05
Campaign credits belong to the original creators. They did not write or endorse this analysis.
Credits: Sandwich for Slack. The credited production company is also the customer depicted.
Recognition: No award claimed in this brief.
Launch / edition: 2014. Award years: No award claim.
The problem. The idea. The experience.
Sandwich says it initially rejected Slack founder Stewart Butterfield’s invitation because its existing tools seemed sufficient. The communication problem was therefore not simply explaining features. It was helping people understand why another application might improve an arrangement they already tolerated.
How the idea came to life
The agency tried Slack, then filmed its own experience in its office with staff playing themselves. Documentary-style scenes and humour linked features to real workplace interactions. Butterfield also reenacted his original approach, making the making-of-the-ad story part of the product story.
How it reached people
The original 2014 online film was a self-contained explanation suitable for sharing with colleagues. Sandwich’s retrospective says people later told it they used the film to persuade management to try Slack. Slack’s own 2020 article confirms the 2014 collaboration; its later work-from-home sequel is not counted here.
Supporting sources: Primary creator case study → Primary brand article by the creator →
Read the data in context.
The numbers below describe different kinds of outcomes. Their date, scope and reporting source are part of the result.
The sources establish the film and its continuing use as a sales-conversation aid, but provide no audited campaign conversion, revenue or productivity lift. Reports that viewers forwarded it to management are creator-reported anecdotes, not a measured rate of adoption.
The creative mechanism.
A customer’s change of mind provides a relatable narrative for evaluating unfamiliar software
Start with a reasonable objection
The opening resistance gives the viewer a position they can recognise without being made to feel foolish. Identify the legitimate reason someone stays with the status quo, such as retraining costs or fragmented adoption. A useful story earns the change of mind rather than presenting hesitation as ignorance.
Demonstrate a changed interaction
A feature matters when it changes what two people can do together. Write scenes around finding an answer, handing over work or including the right colleague. This makes the benefit concrete without requiring every viewer to study a dense interface tour or remember a long feature list.
Let testimony retain its context
A production company using the tool is a specific customer, not a representative sample of every enterprise. Explain team size, workflow and relevant constraints when adapting this approach. A believable bounded story can be more useful than an unsupported promise that every organisation will obtain the same result.
Equip the internal advocate
Business software often needs several people to agree. A short, understandable story can help an enthusiastic employee explain the proposal to someone who missed the first demonstration. Pair emotional recognition with practical next steps, including migration effort, permissions and a realistic trial plan.
The intended behavior loop
- 01Recognise a familiar coordination problem
- 02See a similar team change its approach
- 03Share the explanation internally
- 04Evaluate a limited team trial
Growth job: Explain the product → reduce switching resistance → support a team trial. This is an interpretation of the mechanism, not an audited attribution model.
A direction to take into the room.
Original editorial interpretation and proposed adaptation. This is a proposed adaptation, not historical campaign execution or a forecast.
The transferable principle
Use a genuine customer’s initial objection and specific changed workflow to explain why a trial might be worthwhile.
Keep these boundaries
Do not script false testimonials, expose private work or imply that one team’s experience predicts universal productivity gains.
Turn the lesson into a test.
Illustrative adaptation, not a historical campaign fact
A small-team experiment
A small SaaS company films an approved customer explaining one coordination problem before and after a limited trial.
Build the test
- Agree on the exact claim, participant consent and any commercial relationship before recording.
- Show one recreated workflow with synthetic data and let the customer describe remaining limitations.
- Give viewers a short trial checklist covering ownership, access and a decision date.
Measure the right thing
Compare product comprehension and qualified trial requests with the existing feature-led explainer; ask the customer to approve factual accuracy.
Know when to stop
Stop if the customer cannot substantiate the improvement, confidential data appears or the edit changes the meaning of their testimony.
How this reading fits your brief
Start with the useful part.
Best for: Explain the product → reduce switching resistance → support a team trial
What to adapt: Use a genuine customer’s initial objection and specific changed workflow to explain why a trial might be worthwhile.
Prerequisites: Willing real customer; Consent and claim review; Simple filming and editing; Synthetic workflow data.
Smaller-team route: A small SaaS company films an approved customer explaining one coordination problem before and after a limited trial. Constraint: Do not script false testimonials, expose private work or imply that one team’s experience predicts universal productivity gains.
Budget: Unknown; no verified historical campaign budget in the cited sources. No cost-fit claim is made.
Trade-offs and evidence: Read the limits below before choosing a test. There is no guaranteed reach, sales lift or ROAS.
Questions for your next brief
- What is the strongest reasonable argument against switching?
- What could a colleague forward without adding a long explanation?
Sources & further reading.
Brand and award-entry results are attributed claims, not independent causal audits. Source links open the original third-party pages.
- Sandwich: Slack →Primary creator case study · Supports: Initial scepticism, actual use, documentary-style production, staff casting and reported internal-sharing anecdotes.
- Slack: Sandwich in a Lunchbox →Primary brand article by the creator · Supports: Confirms original collaboration in 2014 and distinguishes it from the 2020 work-from-home film.
Independent educational analysis of external campaigns. These are not SNS client projects, endorsements or claims of involvement. Campaign facts and reported outcomes are attributed to their sources. Explanations, adaptations and test plans are original analysis and hypotheses, not proven causal findings.