November 12, 2020 · 1 min read
Documentation is critical if you want to save time and avoid making the same mistakes twice.
Check out how our team structures tech specs, tackles bugs, and runs A/B tests.
A bug is an error, flaw or fault in the Air experience. To standardize how bugs are reported, this document provides instructions on the appropriate course of action.
Bug Squashing Process
This document breaks down the process by which a bug is resolved by the on-call lead.
Front End Tasks Template
For use of front-end developers, this form is filled out by the individual proposing a new feature. Documenting your general approach allows members of your team to provide the necessary support.
Back End Tech Spec
For use of back-end developers, this form is filled out by the individual proposing a new feature. Documenting your general approach allows other members of your team to provide the necessary support.
How to Run an A/B Test
This document, and accompanying video, provides step-by-step instructions on running A/B tests in Google Optimize. A/B testing allows you to make careful changes to your user experience (UX) while collecting data on the results.
Product Development Guide
A comprehensive overview of how we approach product developement at Air. Roadmap planning, kickoffs, design sprints, planning, demos, and retrospectives.
Go back to all categories ↓
Imitation is the sincerest form of flattery. 65+ Notion docs for early stage startups.