๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Jean-Denis Greze ๐Ÿ’ก
@jgreze
Co-Founder and CEO at (@TownAI). Ex-CTO @Plaid. Investor at @ASDFVentures. Everything is satire.
๊ฐ€์ž… January 2011
616 ํŒ”๋กœ์ž‰ ์ค‘    6.2K ํŒฌ
We had about 40 power users at a Town event a couple of weeks ago and got a lot of product feedback. One person pointed out that during onboarding Town will say something like, โ€œIโ€™m going to create a routine.โ€ Normal people trying Town for the first time donโ€™t know what a routine is. Town should probably just say, โ€œDo you want me to do this every day?โ€ That's easy. You hear feedback like that and you fix it. Not all feedback is like that. My feeling is you should listen to all of it. You obviously can't implement all of it, but you can keep it in your head. Sometimes you find something you can build that solves a lot of the feedback at once. And then sometimes you hear the thing that everyone wants and you're still not convinced you should build it. Because if you go too far in that direction, the product kind of loses its soul. There's a Simpsons episode where Homer's brother decides Homer is the average American, so he should build the car Homer wants. He lets Homer design it and the car is a total monstrosity. That's kind of the problem. You have to listen, because if you don't listen you're going to build the wrong thing too. But at some point you still need intuition and taste about what makes the product simple and what will speak to lots of people. And if it works, people say you're a product genius because you made weird choices. If it doesn't work, they say you weren't. It's art more than science.
๋” ๋ณด๊ธฐ