Strategy, discovery, metrics, growth, pricing, design, delivery and leadership. Each entry says when it is the right one to pick up.
Schneier describes the surveillance that falls out of ordinary technology use, covering both government collection and the commercial data economy that supplies it.
Written for the people who work with data scientists rather than for the people who will build the models. It teaches the fundamental concepts, including how a business problem maps onto a data mining task, why overfitting happens …
Lin's interview preparation book, built around named frameworks for the common question types. CIRCLES for product design, DIGS for behavioural questions, AARM for metrics, and structures for estimation and strategy questions.
Newport defines deep work as cognitively demanding activity performed without distraction, and argues it is becoming both rarer and more valuable at the same time.
Hansen wrote this after several thousand customer interviews conducted while bootstrapping a software business, and it is the most practical book available on the mechanics of the conversation itself.
Kholmatova approaches a design system as a shared language rather than as a component library, and organises the book around defining that language before building anything.
Kleppmann covers the foundations beneath data systems. Part one covers reliability, scalability and maintainability, data models and query languages, storage engines and encoding.
Huyen treats machine learning as a production systems problem, covering everything around the model rather than the modelling itself. The book moves from framing a business problem as a machine learning problem and deciding …
The authors argue that every hard conversation is really three conversations happening at once, one about what happened, one about feelings, and one about identity.
Gottesdiener and Gorman set out a structured conversation for deciding what to build, run across three planning horizons, which are the whole product, the next release and the current iteration.
Krug's short book on web usability, organised around the idea that a page should be self evident and a user should never have to work out what something is. Covers scanning rather than reading, conventions worth keeping, navigation and the home page, and the trunk test for orientation.
A book about product leadership rather than product work. Cagan and Jones argue that the difference between strong and weak product organisations lies in the manager's job of coaching and staffing, and they spend most of the book on those two duties.
Perri names the pattern where organisations measure success in features shipped rather than problems solved, then works through what replaces it. You get a product role defined by outcomes, a strategy framework she calls the …
Cutler's collected writing on the feature factory pattern, where teams ship features on a schedule with no feedback loop to outcomes. Covers the signals that you are in one, including no discovery, success measured at delivery, and constant context switching.
A condensed statement of the Kanban Method, distilled from Anderson's longer blue book into about eighty pages. It sets out the values, the change management principles and the service delivery principles, then the general …