The question that keeps slowing down a conversation with Engineering is a useful starting point for choosing a technical book. APIs covers integrations, Software Architecture explains systems and dependencies, and SQL deals with analysing product data.
This guide compares The Product Shelf’s own technical catalogue. Each recommendation relates a book to the work it covers, so that a reader can choose a starting point and see where two subjects overlap.
Which problem are you trying to solve?
| Book | Start here when you need to… | Main topics |
|---|---|---|
| APIs | Understand integrations and discuss what happens when systems exchange data. | REST, endpoints, authentication, webhooks and errors. |
| Software Architecture | Follow a feature across the systems that need to change. | Frontend, backend, databases, dependencies and scalability. |
| SQL | Investigate a product question beyond the dashboard. | Queries, filters, JOINs, aggregations, funnels and cohorts. |
| Product Metrics | Choose evidence for a product decision. | KPIs, funnels, retention and user behaviour. |
| Logs, Kibana and Observability | Investigate what happened during an incident. | Logs, metrics, traces and searches in Kibana. |
| CI/CD and Releases | Discuss how and when a change reaches users. | Pipelines, environments, deployments, releases and rollback. |
| Testing, Bugs and QA | Assess test results and prioritise defects before a release. | Test types, severity, priority, acceptance criteria and quality risks. |
| Technical Debt | Compare technical improvements with new features. | Debt assessment, refactoring, prioritisation and business cases. |
| Security | Discuss access, sensitive information and product risks. | Authentication, authorisation, encryption and vulnerabilities. |
APIs or Software Architecture: which should you read first?
Choose APIs if you need to understand a partner integration, a webhook or an API error. Choose Software Architecture if your question is broader: which systems are involved, where data lives, or why a change affects several teams.
Our suggested sequence is APIs followed by Software Architecture: a concrete exchange between two systems provides a starting point for examining the wider design. Readers currently working on dependencies or system boundaries can begin with architecture.
SQL or Product Metrics?
SQL helps you obtain and examine data. Product Metrics helps you decide what to measure and how to interpret it. If you know your question but cannot get the data, begin with SQL. If you have many dashboards but cannot tell which metric should guide a decision, begin with Product Metrics.
For example, asking how many customers returned within 30 days requires definitions as well as a query: which customers, what counts as returning, and which dates belong in the analysis? Reading the two topics together helps you connect the calculation to the decision.
Testing, CI/CD or Observability?
These books cover different parts of delivery. Testing focuses on the evidence and defects you assess before deciding to release. CI/CD explains the path through pipelines, environments, deployment and release. Observability helps you investigate behaviour in a running product.
If a release meeting is your immediate difficulty, start with Testing. If the deployment process is unclear, start with CI/CD. If the team is already investigating an incident, start with Logs, Kibana and Observability.
When should you choose Technical Debt, Security or Cloud?
Choose Technical Debt when technical work competes with new features and you need to understand the consequences of postponing it. Choose Security when the decisions concern access, permissions, data protection or vulnerabilities.
For infrastructure, availability and cost discussions, the Spanish catalogue also includes Cloud e infraestructura para Product Managers (Spanish edition). Check the edition language on each product page before buying.
Build a reading path around one real decision
- Write down one question from your current product: an integration, a metric, an incident or a release.
- Choose the book closest to that question and read its product page for the scope and edition.
- Use what you learn to prepare questions for Engineering or your data team.
- Add a second topic when the next decision calls for it.
For a first look at the topics, read our guides to software architecture, SQL for product analytics and CI/CD and releases. You can also browse the technical book catalogue.