Founders

Product

Video and longer casts are both examples of stuff people ask for and then don't use very often. 

Ultimately both were worth adding, but stated vs. revealed preference strikes again.

as a builder, how do you think about prioritizing features?

thinking about this cast from @dwr.eth

as a builder, how do you think about prioritizing features?

thinking about this cast from @dwr.eth 

https://warpcast.com/dwr.eth/0x46e747da

sometimes features are table stakes & necessary simply to avoid the "doesn't have" wen ur a new product entering an existing market.

beyond that, i always asked teams to focus on value and function then design the feature set

Sometimes competitive-parity is a necessary evil.

+ I don’t know that usage stats for something like long casts is a good indicator of value. Not every cast needs to be an essay, but knowing it’s possible is… nice?

There’s definitely an art to balancing all the different inputs… what people say, what they actually need, short term vs long term, maintenance, optics, etc. 

Probably no right answer beyond first principles thinking and aiming to stay a step ahead of both users and competition.