Chapter 21. Product Engineering Strategy
In my career, the majority of the strategy work I’ve done has been in nonexecutive roles, things like Uber’s service migration (Document 16-1). Joining Calm was my first executive role, where I was able to not only propose but also mandate strategy.
Like almost all startups, the engineering team was scattered when I joined. Was our most important work creating more scalable infrastructure? Was our greatest risk the failure to adopt leading programming languages? How could we rescue the stuck service decomposition initiative?
These strategies are where the Calm engineering team and I aligned after numerous rounds of iteration, debate, and inevitably some disagreement. As strategies, they’re both basic and also unambiguous about our values, and I believe it’s a reasonably good starting point for any low scalability-complexity consumer product.
Reading These Documents
The documents in this chapter are rewritten from memory to capture the strategies we pursued during my time at Calm. They are:
- Document 21-1: “We’re a Product Engineering Company!”: Engineering Strategy at Calm
This document outlines Calm’s strategy for focusing on product engineering work, explicitly not focusing on infrastructure-style foundational work, and the rationale behind that approach.
- Document 21-2: How to Resource Engineering-Driven Projects at Calm
This document summarizes Calm’s approach to investing in Engineering priorities when the prior prevailing belief within ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access