LanguageEnglish

World Cleanup Day / Global volunteer movement / 2018-2021

A global cleanup runs on invitations, not announcements.

World Cleanup Day asks people in more than 180 countries to show up on one date. I designed and developed the 2018 campaign and live event website, built the hosting around the annual traffic spike, and created an invitation generator that helped volunteers recruit their own friends with a photo, their own words, and the channels used in their region.

Visit World Cleanup DayAll case studies

countries

180+

Each country organised participation locally. The central product supported one shared day without becoming a global register.

invite seasons

2018→2021

The same generator carried a new date and new artwork every year.

The recruitment problem

Nobody can centrally organise a hundred and eighty countries.

A one-day global cleanup cannot be run from one office. Local leaders choose the sites, set the times, speak the language, and know who will actually turn up with a pair of gloves. The central website had to support that work without becoming its bottleneck.

World Cleanup Day had no global registration system. Each participating country ran its own registration. I designed the central campaign and live event website around that decentralised reality, then built a tool volunteers could use to recruit people directly.

The volunteer path

Understand the day. Make an invitation. Bring somebody with you.

  1. 01Find the shared date and local route

    The campaign and live event website explained the global day while local teams kept control of registration, sites, times, and practical details.

  2. 02Make the invitation personal

    The generator combined a photo, a personal sentence, and the year's World Cleanup Day artwork into one shareable image.

  3. 03Send it where friends already are

    The invitation could move through WhatsApp, Messenger, Viber, LINE, VK, SMS, or email, with download and copy-link fallbacks for the channels no API reaches.

The invitation

Give the invitation its own product.

The strongest recruiter for a cleanup is somebody the volunteer already knows. I gave that invitation its own flow. A volunteer picked a photo, wrote the sentence they would actually say, and received one image composed with the year's artwork and date. The interface did the design work without making every invitation feel the same.

  • Canvas composition combined the photo, personal sentence, artwork, and date
  • One shareable image replaced the need for a volunteer-facing design tool
  • The message stayed personal while the campaign identity stayed consistent

Phone constraints

The flow had to finish on the phone that started it.

The generator would fail as a recruiting tool if a large camera image stalled or an unsupported file broke the flow after somebody had written their message. I capped uploads, accepted common photo formats, and kept the output to one image that could move through ordinary mobile sharing.

  • Capped uploads kept the flow practical on phones
  • Common photo formats reduced avoidable failures
  • The completed image could be saved and shared outside the interface

Distribution

The share sheet has to match the country, not the head office.

The channel that matters in Indonesia may be different from the channel that matters in Honduras, Nigeria, or Estonia. Distribution followed the messaging habits of each region, with simple fallbacks for anything a platform API could not reach.

  • WhatsApp, Messenger, Viber, LINE, VK, SMS, and email were concrete destinations
  • Download and copy-link fallbacks covered channels no API reaches
  • Regional habits mattered more than one global sharing default

Infrastructure

Use boring hosting for the one date that matters.

Attention for World Cleanup Day arrives as a spike, not a stream. The editorial site ran on a provisioned WordPress stack with staging, deploys, and rollback as routine moves, while the interactive apps were deployed separately so a rush on one could not take down the other.

  • Staging and production built from the same provisioning playbooks
  • Rollback treated as a normal operation, not an emergency
  • Interactive apps isolated from the editorial site they promote

15 September 2018

The invite generator did its work in the weeks before the cleanup. On the day itself the site switched into live mode: a UTC clock, whichever country's broadcast was on air, a wall of posts arriving from the movement's own channels, and a map of the wave crossing the planet. Volunteers who had already finished their own cleanup could watch the rest of the world take its turn.

The homepage across the day, captured hour by hour: live video from the country currently cleaning, a social wall pulling posts from Facebook, Twitter, VK, and Tumblr, and the day's press releases underneath. Nobody re-published the page — it re-published itself as the wave moved.
The World Cleanup Day map on the day of the cleanup, with countries coloured to show which are about to clean, currently cleaning, and finished.
The green wave: every country coloured by where it stood in its own 10am-to-3pm window. Pink is next, yellow is cleaning now, green is finished. The state came from the schedule and the timezone, so the map never waited on somebody in Tallinn to update it.
Volunteers working on laptops behind a window in Tallinn during World Cleanup Day 2018, with World Cleanup Day stickers on the glass and wall.
The other half of the live site: volunteers in Tallinn on their own laptops, running twenty-four hours of coverage. That crew size is the real constraint behind every decision above — anything that needed constant manual attention would not have survived the day.

After the day

A movement's traffic arrives once a year. The rollover has to stay cheap.

Everything about the digital product was seasonal. Attention built towards one date, then the system went quiet until the next cleanup was announced. The yearly rollover of date, artwork, and copy had to be cheap enough that nobody dreaded it.

The invitation machine could return with a new visual identity and date instead of being rebuilt each year. The campaign site and the interactive generator were separated, so editorial changes and traffic on the tool did not have to become one operational risk.

  • Central swaps for the date, artwork, and campaign copy
  • The same generator reused from 2018 to 2021
  • The interactive generator isolated from the editorial website

HAAM’s role

I built the campaign website and the recruiting tool.

Product, interface, and operations

I designed and developed the 2018 campaign and live event website, built the invitation generator, and handled the hosting, deployment, and seasonal rollover through 2021. Registration stayed with participating countries. I did not build a global registration product. World Cleanup Day visual identity by Let's Do It World.

Next case study

An intergenerational project where the over-60s wrote the brief.

View Le Tre Meraviglie

How we learned

Research

Distributed participation

The service had to learn from how participation actually spreads.

Research connected country teams, languages, timezones, seasonal traffic, volunteer invitations, sharing behaviour, and the small central newsroom. The key insight was organisational: participation scales when local people can recruit and act without waiting for the centre to manually coordinate every step.

  • Volunteer journeys
  • Country operations
  • Localisation
  • Live-state analysis

Evidence trail

Why the interface is this way.

GLOBAL OPERATIONS DATA

Good interaction design should be traceable upstream. Depending on the project, that upstream work might be interviews, co-design, fieldwork, archive work, testing, analytics, or operations. Here is the shortest version of the chain from evidence to decision.

01

Evidence

180+ countries, 55 onboarding languages, 16 share destinations, annual traffic spikes, timezones, volunteer invitations, and a small live newsroom defined the environment.

02

Interpretation

A central team cannot manually coordinate every country or channel, so recruitment and live state need to distribute outward.

03

Design decision

Minimise registration, localise onboarding, let volunteers generate invitations, support regional sharing, and derive live states from schedules and timezones.

04

Result

Central infrastructure becomes decentralized participation, letting local volunteers recruit while the live site follows the cleanup wave automatically.

Help improve this website?

Optional analytics. Google Analytics and Clarity load only if allowed; form, email, and chat content are excluded.