I would rather build in community. You always have the problem that you don't know your customer very well in the beginning...so adding a lot of "noise" in public..is bad, compared to a real closed community environment.
I would rather build in community. You always have the problem that you don't know your customer very well in the beginning...so adding a lot of "noise" in public..is bad, compared to a real closed community environment.
I totally get where you're coming from, but I think there's actually a lot of value in building in public. It allows for transparency and feedback from a wider audience, which can be really valuable for improving your product.
Agree Daisy. Building in a community definitely seems more strategic, engaging directly with potential users and customers. It fosters a more meaningful connection.
Building in community is essential, but building in public requires rapid development capabilities, enabling you to iterate quickly on your product. Otherwise, you risk being surpassed by imitators.
Obviously not totally mutually exclusive (YMMV), but if I have to choose one, as a community builder, I have seen some genuinely remarkable insights bubble up from community feedback