My role
Pitched the feature and led it from idea to launch, as one of WordCamp Asia 2025’s operations organizers
Team
Gravatar’s product team (a project lead, two engineers and a designer), the conference’s tech and comms teams, the company printing the badges and the registration volunteers
Timeline
Four months from the pitch in Oct 2024 to the launch at the event in Manila in Feb 2025
Outcome
A new Gravatar feature launched live to about 1,480 attendees, with about 2,820 badge scans and a setup any event can now reuse
~2,820
badge scans during the event
~1,480
attendees with a Gravatar code on their badge
4 months
from a pitch that wasn’t on anyone’s roadmap to a live launch
People came to network, and the event wasn’t built for it
WordCamp Asia 2025 brought about 1,480 people from the WordPress community to Manila, and I was one of its 77+ organizers, on the operations team. In the registration survey, networking came out as the biggest reason people were coming, and beyond putting them in the same rooms we weren’t doing much to help.
My day job was at Automattic, the company behind Gravatar, which already held contact details for a lot of people and needed more of them actually using it. So I pitched one launch that served both: a QR code on every badge that opens that person’s Gravatar profile. The software and the printed badges had to work on the same day, and the event itself was the launch, so there was no second try.
How I got it built and launched
The idea wasn’t on Gravatar’s roadmap, and I didn’t own that roadmap, so the ask had to be small enough for their team to say yes. I pitched it to our organizers first, then to Gravatar on 9 October 2024, offering our own tech team for the build.
I wrote the script that turned every attendee’s email into a one-way hash, which is how Gravatar looks up a profile, so each badge carried a working code and never an email address. Plenty of attendees had no account, so Gravatar’s team (a project lead, two engineers and a designer, with me as a stakeholder) built a “claim your profile” page for them, and it shipped on 6 January 2025.
Then I lined up everyone else: the organizers, the event producers, the local team, Gravatar and the company printing the badges, my first time coordinating this many groups outside Automattic. With the comms team I published a post on the event site showing attendees how to use their code, and I handed out custom NFC chips from Gravatar so anyone could share their profile with a tap.
Build on Gravatar instead of a plain QR code
Gravatar already held people’s contact details, and the same work could grow an Automattic product. The cost was that my event now depended on another team’s roadmap.
A claim page instead of temporary profiles
My pitch had suggested temporary profiles built from registration details. The claim page only had to exist where a profile was missing, so Gravatar could ship it in weeks, and the trade-off was that an unclaimed badge showed a claim page instead of that person’s details.
Fit the badge printer’s process instead of changing it
The production company generated its own QR codes, so Gravatar couldn’t make them. Instead of pushing for a process change close to the event, we added an event tag to every profile link, which also made the setup repeatable for any future event.
What happened
There were about 2,820 scans from about 1,480 attendees, roughly two per person. Matt Mullenweg had announced it internally as the first live event to try Gravatar’s new QR code generator and thanked me for helping make it happen, and Gravatar’s team cited the work in their internal updates.
On day 2 I noticed most attendees didn’t know they could scan each other’s badges, because the registration volunteers weren’t mentioning it. The event was the launch, so instead of saving it for the retrospective I retrained the volunteers during my shift, and it made an immediate difference. Once people understood it they loved it, and many had no idea they already had a Gravatar account.
Some of it didn’t work. Only a couple of sponsors scanned attendee badges, many of the NFC chips went unused, and I never got a figure for profiles claimed through the new page, the metric Gravatar’s team had set.
Our operations retrospective put Gravatar codes on badges straight into the “keep” column, and WordCamp Europe’s organizers showed some initial interest when I reached out. Gravatar has since published a public guide for event badges built on the same hash and event tag, with WordCamp Asia 2025 as its real-world example.
What I’d do differently
I’d start the attendee marketing much earlier, with several emails instead of one a week out, signs about scanning, and volunteers trained before the doors open. I’d also save the NFC chips for sponsors, speakers and organizers as special swag, build scanning into the sponsorship package with raffles and lead capture, and make the names and codes on the badges bigger.
