proomt

Search

Search posts, papers, and topics

All posts

Hacker News front pageLiam Nugent5 min readintermediate

The most important product decision is what you don't build

Summary

This post argues that the most critical product decision is often what not to build, citing "document hubs" and "notification centers" as common pitfalls. It highlights how seemingly simple features can balloon into complex, costly, and poor user experiences, advocating for ruthless focus and illustrating long-term running costs.

  • Avoid generic "document hubs" or "notification centers" as they often lead to complex, costly, and poor user experiences.
  • Illustrate long-term running costs, not just build costs, to convince stakeholders against unnecessary features.
  • Address specific user needs with targeted solutions rather than building one-size-fits-all platforms.
  • Recognize the cognitive bias towards additive changes and actively seek subtractive improvements.

Product managers and engineering leaders should read this to understand the hidden costs of feature creep and the strategic value of disciplined product subtraction for long-term success and maintainability.

7/10

Related reading

  1. The pursuit of excellence does not need justification

    Opinion piece arguing that engineers should pursue excellence without needing to justify it, using anecdotes about a fast terminal emulator and a WordPress menu cache to illustrate how over‑engineering can yield unexpected downstream benefits, while also acknowledging the practical need for “good enough” decisions.

    Bjørn Johansenbjornjohansen.com2 min
  2. I am often wrong

    The author shares a six‑step iterative framework for tackling product problems—understand data, fill gaps, define problem, craft a simple approach, set a goal, and act urgently—emphasizing that being wrong is a useful feedback loop. The piece is a personal opinion on product management practice.

    Hacker News front pageborischerny.com2 minHN319220
  3. CSS-Tricks could be a co-op

    The author argues that CSS-Tricks, a critical web development resource, has struggled under corporate ownership because it wasn't a core strategic priority. They propose a co-op model as a more sustainable alternative to preserve such valuable knowledge infrastructure, prioritizing cultivation over profit.

    Lobstersericwbailey.website2 minHN2lobste.rs41
  4. EP226: API Concepts Every Software Engineer Should Know

    This article outlines essential API design considerations, covering HTTP fundamentals, architectural styles like REST and GraphQL, and critical aspects such as naming, versioning, security, and reliability. It serves as a high-level checklist for engineers designing or consuming APIs.

    ByteByteGobytebytego.com5 min