7 Principles for Cross-Functional Product Development Excellence at Teachable

Part One: The Principles

Photo by Tim Marshall on Unsplash

Want to join our team? We’re hiring for several different positions.

The Problem

The Solution

7 Product Engineering Operating Principles

Photo by Baim Hanif on Unsplash
Photo by Form on Unsplash

NOTE: We do make it very clear that this doesn’t mean we’re a cult or family. Building trust requires a sense of vulnerability and openness, but we’re a place of business. Everyone gets to choose the level of “their full self” they bring to their teams. As long as their behavior creates space for trust to emerge.

Photo by Dave Phillips on Unsplash
Photo by The Digital Marketing Collaboration on Unsplash
Photo by Gary Sandoz on Unsplash

NOTE: We’ve had a lot of internal conversations around the balance between principles #3 (quality) and #5 (experimentation). This is not a hard binary with the right answer, but generally we understand #3 to be the overall long-term state of the product (high quality) vs. #5 pertaining to being willing to jeopardize quality temporarily with appropriate groups of people in the interest of learning. #5 is not an open pass to hack stuff together, ship and forget.

Photo by Neil Thomas on Unsplash

Important caveat: This doesn’t mean “just do whatever customers ask you to build.” We need to go beyond that and understand what their real needs are and solve them in a way that truly makes our product better for them — now and in the future.

Photo by Krista Mangulsone on Unsplash

Now What?