‹ BackHN Continuity

Thread

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

161 points · 54 comments · ChrisArchitect

  1. swader999 · · focus · HN ↗
    The one I get constantly is we want "custom reporting". Well what the hell is that really? Why, why, why do you need that? Then I just build a new feature they will actually use and defer "custom reporting" for another month.
    1. tytho · · focus · HN ↗
      I worked with a guy who specialized in custom reporting tools and pipelines. He said that a majority of the time people are asking for custom reporting tools, it’s because the app’s built-in tools for sorting/filtering/aggregating data aren’t answering the questions they are asking.

      Now whenever someone brings that up, I ask “What question are they wanting the answer to?”. It usually leads to either a new feature or just clarifying where that question can be answered. Looks like you’ve caught onto that same school of thought.

      Sometimes people just want to feed data into their own warehouse so they can query data across different pieces of software, or they are too stubborn to get to the bottom of what question they’re trying to answer.

      1. Pxtl · · focus · HN ↗
        My experience is always "we have a standard SQL server datamart. We just need to put a good reporting tool on that. You're a business analyst and product manager, go analyze some products."

        "But can't you just make something exactly like we imagine? We're already paying you and buying stuff is paperwork".

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.