Menu

2,512 product ideas, most of them killed: designing a kill-reason dataset (free 100-row sample)
📰

2,512 product ideas, most of them killed: designing a kill-reason dataset (free 100-row sample)

DEV Community: datascience·Sebastian Bardach·3 days ago
#NBlQ7g10
#devtodatascience#science#devto#dev#rows
Reading 0:00
15s threshold

For a month I ran an automated screen over ideas for small software and digital products: SaaS, web templates, books, downloads, content channels, e-commerce. 2,512 ideas went in. Most of them failed, and that turned out to be the useful part, because every failure was stored with the rule that stopped it.

I published a free 100-row sample of that table under CC BY 4.0: screened-product-ideas on Hugging Face . This post is about the schema, the three design choices that made it worth querying, and a few lines of Python to read it.

The columns

column what it holds

id , title , field , created the idea and when it was generated

stage , status , verdict how far it got (S1, S2, …) and how it ended: parked, killed, still open

screen_total , screen_line the score at the field screen and the pass line it had to beat

desk_total , c1 … c10 the deeper ten-criterion scores, only for ideas that got that far

weakest_criterion , fatal_codes which criterion sank it

kill_codes one or more coded reasons, separated…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.