Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: This is our YC W2014 application. Can you give me feedback?

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 38 posts

Re: Ask HN: This is our YC W2014 application. Can you give me feedback?

#11

Post by 6thSigma »

sandeep45 wrote: post #7
6thSigma wrote: post #4

(I'm not involved with YC, so take this with a grain of salt.) I think the idea is really cool and I can see how useful it could be for companies, but do you have evidence that users actually give feedback via your method? I'm trying to look at this product from that side of the equation, and I could see me getting frustrated that clicking "Sign up with Google+" doesn't actually do that. If you have evidence showing…

6thSigma: Thanks for your feedback :). To answer your question, with our beta customers, we have shown the feedback overlay more than 1K times and have gotten a 60% feedback rate. We think this is because we ask the right person, the right question at the right time. Its the right person, because this person clicked on the feature, its the right question because the question is about the feature they clicked on and n…

If I were you, I'd get rid of the "right person, the right question at the right time" bit in the application and include "we have shown the feedback overlay more than 1K times and have gotten a 60% feedback rate."

Re: Ask HN: This is our YC W2014 application. Can you give me feedback?

#12

Post by sandeep45 »

bradpineau wrote: post #5

Great overall concept. I think it's something my company could use. One concern I'd have if using this product, is that often the customer says what they think they want, but don't actually need. So I'd expect there to be some decent "management" tools for working through all the feedback. Maybe some sort of internal scoring or feedback system within the company or something.

FeatureKicker provides both qualitative and quantitate feedback. Besides what the customer has said, you can also see things like how many time was the feature "viewed" and then how many times was it "clicked". How long was it open for, did they highlight things when reading etc. In our next version, we r planning on building something to better digest all this data so customers can take quick action.

Re: Ask HN: This is our YC W2014 application. Can you give me feedback?

#13

Post by arethuza »

I actually think this is a pretty good idea. However, could there be some way of having these "proposed" features turned off by default and giving users an option to turn them on? Otherwise, as people have commented, it might cause frustration as people try to use features that aren't implemented yet.

Could you have a view for end users so you can see all proposed new features? Sort of crowd-sourced product marketing...

Edit: What about letting end users suggest completely new features this way? (e.g. allowing them to draw on a screenshot of the page and say "I want a button here that does XYZ").

Re: Ask HN: This is our YC W2014 application. Can you give me feedback?

#14

Post by JRFuentes7 »

mrgreenfur wrote: post #10

Honestly, I think it's a cool widget! It doesn't sound nearly big enough to get a 10x return on VC though. How big is the market really? I watched your intro video and came away a bit underwhelmed: Can't someone just replace this with an analytics event of "clicked" and extrapolate that only people who want a feature are clicking on that feature? Have either of you worked on product teams before? Do you have feedback…

"Honestly, I think it's a cool widget! It doesn't sound nearly big enough to get a 10x return on VC though."

I hear ya... we worry about that sometimes. But then I think about what PG says re "it's our Altair." We gotta start somewhere.

How big is the market? There are 5M product managers in the US, according to LinkedIn. Assuming 13 PMs per company, there are many, many companies that should be using this.

I don't think you could or should replace our tech with a click event. I'll agree that 404 tests are a good start... but they lack qualitative data and a rules engine. I believe that's an inferior customer experience.

We've interviewed 100+ product teams at this point. We're getting good feedback -- especially re "getting data on existing features."

Re: Ask HN: This is our YC W2014 application. Can you give me feedback?

#15

Post by JRFuentes7 »

porter wrote: post #6

Here's some feedback on the last questions about something surprising you've found. Instead of putting something any middle schooler could find on google, you should but a unique insight instead. For example, what features (out of the many you claimed to have built), have had surprising results? Perhaps this could be something nobody thought would move the needle, but ended up as a breakout success. This would provid…

Very good thoughts, porter. We'll consider this more and edit our application. This is precisely the kind of feedback we're looking for here. :)

Re: Ask HN: This is our YC W2014 application. Can you give me feedback?

#16

Post by JRFuentes7 »

6thSigma wrote: post #11
sandeep45 wrote: post #7

Earlier quoted context omitted.

6thSigma: Thanks for your feedback :). To answer your question, with our beta customers, we have shown the feedback overlay more than 1K times and have gotten a 60% feedback rate. We think this is because we ask the right person, the right question at the right time. Its the right person, because this person clicked on the feature, its the right question because the question is about the feature they clicked on and n…

If I were you, I'd get rid of the "right person, the right question at the right time" bit in the application and include "we have shown the feedback overlay more than 1K times and have gotten a 60% feedback rate."

Cool. Can you go a bit deeper and tell us why? As in, why is that more compelling to you?

Re: Ask HN: This is our YC W2014 application. Can you give me feedback?

#18

Post by austenallred »

You asked me to give it to you straight.

Seems like a cool little widget, but I doubt the market for it would be big enough to be worth your time. It's a small enough of a problem that most people won't notice it, and if they do they could easily solve it themselves. People won't be looking for a solution, and it's not cool enough that people would share it just because.

As for your questions, your responses are way too long.

Re: Ask HN: This is our YC W2014 application. Can you give me feedback?

#19

Post by sandeep45 »

arethuza wrote: post #13

I actually think this is a pretty good idea. However, could there be some way of having these "proposed" features turned off by default and giving users an option to turn them on? Otherwise, as people have commented, it might cause frustration as people try to use features that aren't implemented yet. Could you have a view for end users so you can see all proposed new features? Sort of crowd-sourced product marketing…

Arethuza: Thanks for your feedback.

We have a rules engine, which can be used to really fine tune when and how the feature experiments are shown.

For example, you can setup so 1. feature experiments are only shown to a customer who has logged in at at least X times. 2. You can control so they don't see an experiment after it has been seen once by them. 3. You could say that if they have seen 1 feature experiment, then they shouldn't see another 1 for X days. 4. You could also only show to X percentage of your traffic. 5. And many more rules.

I like the idea of being able to crowd source ideas. It would be a great feature for me to "kick" and see what customers say :)

Re: Ask HN: This is our YC W2014 application. Can you give me feedback?

#20

Post by 6thSigma »

JRFuentes7 wrote: post #16
6thSigma wrote: post #11

Earlier quoted context omitted.

If I were you, I'd get rid of the "right person, the right question at the right time" bit in the application and include "we have shown the feedback overlay more than 1K times and have gotten a 60% feedback rate."

Cool. Can you go a bit deeper and tell us why? As in, why is that more compelling to you?

One is marketing speak showing why you think users would want to give feedback and the other is actual metrics showing a pretty high success rate of getting real feedback.
Post reply on HN