← Reading listTHE UNDERDOGS: ORIGINAL WORKPLACE FILM
Text

DEEPER STUDY / Apple / 2019

The Underdogs: original workplace film

organise multiple product capabilities around one recognisable collaborative task.

TechnologyUnited States5 min read
Published by SNS Media Tech

AI-assisted research and analysis for the SNS Creative Fieldbook

Sources reviewed 6 November 2026

The original campaign creators did not write or endorse this analysis.

Original campaign credits: Agency: Apple; Smuggler.
Recognition: No award claim is made in this study.
Launch / edition: 2019. Award years: No award claim.

The problem. The idea. The experience.

Editorial reading of the challenge: how to organise multiple product capabilities around one recognisable collaborative task.

How the idea came to life

Apple released The Underdogs in April 2019, following a small team preparing a round pizza-box prototype for an important meeting. MacRumors’ contemporary report identifies the work situation and the Apple devices and features shown. The History of Advertising Trust preserves the film and credits Apple, director Mark Molloy and production company Smuggler. This case treats later films with the same team as extensions of one series.

How it reached people

Online film

Read the data in context.

The numbers below describe different kinds of outcomes. Their date, scope and reporting source are part of the result.

Execution and timing verified; no isolated business or behavioural effect established.

Read the campaign story

Apple released The Underdogs in April 2019, following a small team preparing a round pizza-box prototype for an important meeting. MacRumors’ contemporary report identifies the work situation and the Apple devices and features shown. The History of Advertising Trust preserves the film and credits Apple, director Mark Molloy and production company Smuggler. This case treats later films with the same team as extensions of one series.

The story used a deadline to organise many product interactions into one shared task. The team moved between communication, design and presentation rather than stopping for a separate advertisement for each device. Features appeared when the characters needed them. The pizza box supplied a concrete object around which viewers could follow progress, disagreements and small successes without specialist knowledge of the fictional business.

Editorial reading: Workflow storytelling can explain an ecosystem more clearly than a list of compatible products. Each handoff has a reason, and the audience sees how individual actions contribute to an outcome. The characters provide emotional continuity while the task supplies structure. The strongest connection is between a recognisable work problem and the particular tool used at that moment.

The film remains a scripted demonstration, not a productivity study. It does not establish how quickly an actual team would complete the project, what training it would need or what other software might be required. A modern adaptation should show material compatibility and access requirements clearly. Humour about deadline pressure should not turn chronic overwork into an expectation for real employees.

A small software business can map a genuine task from start to finish and choose three moments where its product helps. Film a modest, consented demonstration or use an openly fictional team. Test whether viewers understand the sequence and the dependencies, including what remains outside the product. Compare task comprehension with a conventional feature list rather than measuring entertainment alone.

The sources verify the release and visible capabilities, not an isolated business effect. The archive’s award year is distinct from the 2019 launch. The transferable lesson is to make product breadth understandable through a coherent job, while keeping the story honest about limits. A team narrative can demonstrate coordination without promising that technology eliminates all friction or guarantees a successful presentation.

Follow the workflow

Features need a reason to appear.

Show dependencies honestly

A story should not hide access or compatibility needs.

Measure comprehension

Enjoying the characters is not understanding the tools.

A small test for another brief

Editorial reading of the challenge: how to organise multiple product capabilities around one recognisable collaborative task.

Accurate workflow and dependency recall.

Stop if the story implies unmeasured productivity or normalises harmful overwork.

  • Map a real task and its dependencies.
  • Show three relevant product moments.
  • Test sequence understanding against a feature list.

Sources & further reading.

These are educational analyses of external campaigns, not SNS client projects. Source-backed campaign details, editorial interpretation and proposed tests are distinguished. Brand and campaign-entry reports are not independent causal audits.