What are your thoughts about Building in Public?
Alan Shteynberg
2 replies
My partner and I were discussing what true transparency in business means, and we ultimately came to the same conclusion; give people full build access of our to-do list that we manage as a dashboard on the backend. I'm still a little on the fence, but technically there isn't anything to hide nor do we keep any sensitive information such as identity or financial identifiers in this to-do dashboard.
What do you guys think? Would you follow along in this Google Sheet Dashboard to see how we progress over time?
Thanks!
Replies
Richard Gao@richard_gao2
Evoke
The only arguments for not doing it are competition and it being a waste of time.
I'll address them both.
For the first one, it's honestly not an issue unless it's already later on in your business and you're just leaking all your secrets. No one pays attention to the small fish until they become large.
As for the second, build in public takes a few seconds in terms of posting your progress online. It's really not a big loss of time, so even if it was not that effective, nothing of huge value would be lost.
I've been building evoke-app.com in public long before we released, and I'd say a large part of how we were so successful on PH was because we built in public
Share
Took the words right out of my mouth @richard_gao2. I'll likely give the folks what they want in that case, and continue the build and soft launch in public. Thanks!