The Driving Principle for Product Decisions

3min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

We wanted to focus on the outcomes. And as you pointed out, that led to a lot of our product decisions. We were solving real why did we create the notion of schemes and like strong typing or denoting which fields were optional versus required? Itis because we felt the pain in previous products where if the schema changed, you were never notified. So all our decision making was like, how do we make this sustainable? HowDo we know when things break? How do we know if things are working?

What does it take to shape an early-stage security project into a product that solves real problems?

Understanding your customers is a key first step. Knowing the personas who can use your product and the leverage they can get out of it, it's what ultimately brings value to security teams and even other teams that can seize their benefits.

We had a great conversation with Joren McReynolds who is the VP of Engineering, IT and Security at Panther Labs. In today's episode he shares the experiences and lessons over the course of his journey at Facebook, Airbnb, and how they shaped his knowledge on what building a great product takes.

Topics discussed:

What led to the creation of osquery and why open source.
What the progression was to build that as an MVP.
Joren's approach to building the IR Team at Airbnb.
How different Airbnb's cloud-based environment was from Facebook's.
How Joren's past experience at Facebook influenced his work at Airbnb.
Joren’s thought process around implementing security monitoring.
What inspired StreamAlert.
3 pieces of actionable advice to security teams looking to excel in detection at scale.