Starting projects at incident.io
We've found a way of kicking off projects at incident.io which helps us ship in a fast and focussed way.
Lisa Karlin Curtis
Designing your incident severity levels
Learn what incident severities levels are, what to consider when designing them, and the levels we recommend you use.
Stephen Whitworth
Customer Success at an early-stage B2B SaaS company
A killer Customer Success function is critical to the success of any SaaS company. Find out how we’ve developed strong customer feedback loops to fuel our product development and built user insights to improve feature adoption.
Esther Delignat
The three pillars of great incident response
There’s no one-size-fits-all incident response process, but the same three pillars form the core of any good process: clarity, transparency and calm.
Lisa Karlin Curtis
Use your words: the importance of clear writing in product development
Good copy can be the difference between a decent product and a great one. Our engineer Sophie explains how copywriting is a central part of product development - and at startups, it's often an engineer's job.
Sophie Koonin
Our engineering interview process
Interviews can seem mysterious, but they don't need to be! We're sharing each interview we do, why we do it, who you'll speak to, how we run it and tips on how to prepare.
Pete Hamilton
The startup guide to sensible incident management
A simple guide to help you bootstrap great incident management practices at your startup.
Chris Evans
No capes: the perils of being a hero-engineer
When I first started out as an engineer I really leant in to being a hero-engineer; here's the advice I wish I'd listened to earlier. you want to avoid.
Isaac Seymour
A modern data stack for startups
Data should be a commodity, and accessible to everyone in a company. We've picked a data stack for tools that make this possible- here's what we use, how it's configured, and why we picked it.
Lawrence Jones