22 February 2021
Balloon: giving every team a first question to ask
How I built Flight Plans, a library of expert-written templates, plus the marketing site and component library around it.
getballoon.com today. Image: Balloon.
At Balloon from July 2020 to August 2021.
I joined Balloon in July 2020, after almost six years at a software factory. There I worked on several client projects at the same time, each with its own stack and its own rules. At Balloon I wanted the opposite: one product, a small team, and enough time to get the details right.
Balloon is a tool for teams to share ideas without groupthink. You start a "flight" with a question, people answer without knowing who wrote what, and the ideas get judged on their own. I used it myself while I worked there. English is not my first language and I can get nervous speaking up in meetings, so I liked being able to take my time and write.
The problem: an empty flight
A finished flight: anonymous ideas, ranked by the team. Image: Balloon.
The product worked well once a team was using it. The hard part was the first flight. A manager signs up, opens the app, and gets an empty box asking for a question. What do you ask your team? How do you phrase it so people actually answer honestly?
That blank state was costing us. People didn't know where to start, so a lot of them didn't.
Flight Plans
So between December 2020 and February 2021 we built Flight Plans: a library of ready-to-launch templates, written by people who know a lot about teams. Each template had a name, a short description, the questions to ask, the insights you could expect, and a quote from its author. A template carried everything a flight needed, so a manager could go from "I don't know what to ask" to a running flight in a couple of clicks.
The Flight Templates library on getballoon.com today. Image: Balloon.
The authors were the fun part. Matt Mullenweg wrote about distributed work. Amy Edmondson, Adam Grant and Daniel Pink were there. So were Arianna Huffington and a long list of founders, investors and people leaders. Templates had names like "Evaluating Feedback Mechanisms", "Reducing Team Anxiety" or "Transforming DEI for Remote Work", grouped into series and categories.
Some of the Flight Plan authors. Image: Balloon.
I built the frontend for the library, in the app and on the marketing site: the template pages, author pages, series and categories, on top of the new plans, series and authors endpoints the API team added in December 2020. On getballoon.com every template got its own statically generated page, so each one could be found from a search engine and not only from inside the app.
A template page: author, quote, categories, description and suggested questions. Image: Balloon.
The library grew to more than 130 templates. It helped push sales up by 35%, and it played a part in closing a contract with a global luxury beauty brand. It turned out the thing many customers were paying for was not only the anonymity, it was knowing what to ask.
getballoon.com
From late 2020, I owned getballoon.com, a Nuxt static site hosted on S3. I spent a lot of time on the less visible work there: SEO, browser compatibility and performance. Leads and product visibility went up 45%.
I also reworked all the typography styles on the site. Once that was done, I pushed to write them down in a proper style guide, because otherwise the next person would start drifting again in a month.
Globo UI
In fall 2020 I started Globo UI, our Vue component library, documented in Storybook, so the app and the marketing site could share the same pieces. It was my first time building a component library and my first time with the Composition API, and if I'm honest, at the start I felt a bit lost. I lost a few days just getting SVG icons to load when the library was imported into another project. But it paid off: we stopped rebuilding the same buttons and cards on every surface, and new pages shipped faster.
What I took with me
Being on a small team focused on one product meant every person mattered, and I found that a big motivator. I learned a lot from PR reviews and pair programming, and I also learned to ask for what I needed: regular feedback, architecture diagrams for the API and the app, and docs for whoever joined next.
That last part followed me everywhere. At every job since, one of the first things I do is write down how things work, for future me or for someone new.