Team Hackathon 2022: What a Remote Team Built in 48 Hours
By Rachel Wright, published April 18, 2023, last updated January 7, 2025. 3 min read. A first company-wide hackathon in late 2022 gave a fully remote team two days to step outside normal work, pair with colleagues they rarely work with, and turn ideas into demos. The format worked because it was light on ceremony and heavy on showing finished work.
Why run it
The event was framed around a simple operating value: keep shipping useful work even as the organisation grows and decisions get slower. A hackathon was a deliberate counterweight — a short, focused window to practise speed, creativity, and cross-team collaboration without abandoning quality.
How the two days were run
Planning started with a shared spreadsheet of ideas, so people arrived with options rather than a blank page. A kickoff call the day before set the tone. During the two days, most rituals stayed asynchronous to suit a distributed team: demos were recorded and voting happened online instead of in a single room. That produced 15 submissions, spanning early proofs of concept, internal process improvements, and features that reached users within the same week.
A practical checklist for your own hackathon
Use this checklist if you are planning a similar event:
- Collect ideas in advance in one visible place, with a clear owner for each.
- Keep the build window short and fixed, so scope stays honest.
- Hold one live kickoff, then make demos and voting asynchronous for time zones.
- Require a short demo for every entry, even for aspirational concepts.
- Separate three kinds of outcome when you review results: prototype, internal improvement, and shipped product change.
- Decide after the event which projects get continued time, and name that owner explicitly.
Five highlighted projects
Team DarkMode — Josh, Franco, Jan — added a native dark display option to the dashboard, switched on under Labs in Account Settings. It is a small surface change, but it shows how a hackathon can deliver a visible quality-of-life feature quickly.
DBT Docs — Baran and Nicola — built a site that automatically generates documentation for an internal analytics transformation project. The value is maintenance: docs that update with the underlying work are less likely to drift out of date.
Improved Metrics System — Mario — upgraded how key metrics are displayed so data can be kept for a longer period, making later analysis easier. The distinction matters: this was about retention and readability for analysis, not a new metric definition.
ETL Deliveries — Jesus, Tina, Fon — surfaced data export logs on the customer's dashboard. Customers could see export status more directly, and support staff had a shared view when troubleshooting.
Documentation Snippets on the Support Form — Sharif and Lauren — placed relevant documentation inside the support contact form itself, so customers could resolve issues without leaving the flow. Work continued after the initial release, which is a useful pattern: a hackathon prototype that earns follow-up time is different from a one-off demo.
What carried forward
The main lesson was not any single project. It was evidence that focused time, mixed teams, and a bias toward showing work could restore momentum. The team carried that energy into the following year, which it dubbed the year of shipping.