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

pedalpete•4 minutes ago

Part of the question may be how do you change the users expectations.

If you are building a product the user already knows, that might not be difficult.

We work in the sleep space, where everyone expects a hypnogram and a sleep score. Even though these things don't actually tell you anything real. They are of little value to most people, but that is the expectation.

jongjong•2 minutes ago

I would say that 'what not to build' is the second most important decision.

The most important decision is what limitations and constraints you are prepared to accept. There are always limitations and constraints but they are rarely identified up-front.

The most difficult, hard-to-revert decisions are those related to hard constraints imposed by the systems and/or data you have to rely on. Maybe it's not physically possible to obtain the data you need to solve your problem you want for the price you need for your solution to be viable. Maybe you need to be able to process large files which may take many hours to complete. Or your input data grows father than you can process on a single CPU core.

djtriptych•31 minutes ago

Or as I like to say “the best way to launch is to cut features”.

As an engineering leader you’ve got to advocate for it against product/design all the time.

pedalpete•6 minutes ago

The better way is to never have those features in your pipeline already.

swader999•about 2 hours ago

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.

tytho•about 1 hour ago

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.

Zarathustra30•5 minutes ago

I thought "custom reporting" was code for "our in-house dev team is slow".

pelagicAustral•about 2 hours ago

I see this all the time... custom reporting, reports... I have seen this so many times in so many places and I wonder why the fuck are people asking about it. Most of the time they have little clue of what they want reported, or how they want the data to look like. Nearly 100% of the time what they mean by reporting is "join all the tables that have a foreign key, force join all the ones that do not have a foreign key by using a union against some arbitrary value picked at most-likely-to-be-the-right-one and dump everything on an "excel spreadsheet". This is the golden standard most people go by.

pier25•about 1 hour ago

Give them an API with the data so they can get create their own reports. Maybe even charge them per hour to create the custom reports.

SP3269•about 2 hours ago

It’s hard decision, but it has to be made.

I’m not building space elevator.

andsoitis•about 3 hours ago

Yes. Don't succumb to featuritis. Destroy the barnacles.

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

⚡ Community Insights

Discussion (11 Comments)Read Original on HackerNews