Could you elaborate on how this could help with UX goals?

We're currently looking into whether we're actually able to understand zine's value for users. We have the per-section CTR measure, and it looks like we'll be able to get an understanding of the level of personalization, but there are still open questions. This is one tool we may want to use.

Here's a doc on this topic: https://docs.google.com/document/d/1KPnGh-53SoAb0A_pBXmbG8Y0HJ7qPBqbRgz7pRMwaxE/edit

we should be careful not develop such features in an ad-hoc manner.
I chatted with the Google News team a while back, and they have lots of valuable advice on how to collect feedback you can actually react on.
They specifically warned us from asking too broadly for feedback as it's really hard to tell what the user meant. Is the topic right but not the timing? Is the topic wrong?
If we want to go that route, they advised to collect precise reasons and we would have to expose the reason why we suggested the card first (like the reason they have in the GSA). [this requires server and client changes] Then, the question is what do we do with that feedback and if we use it to improve the product (which the user would assume), provide ways for the user to inspect and possibly correct their feedback.
That's the point where we also need to think about how much of this functionality we really want to have inside our product and if we can draw a boundary and resort to other properties.

Don't get me wrong, I believe user feedback is very important, but we need to carefully design this and look at the whole product and how we relate to other Google products as well.

Another point worth raising: We are planning to add a feature toggle where users can turn off remote suggestions. So users who are not interested would just turn it off.

One important feedback we probably should allow to give more easily is reporting inappropriate content that Chrome should not suggest at all.

Thanks for these notes Tim. We agree that this should be very carefully designed, and we're looking forward to the discussion tomorrow to flesh it out.

Helen is putting together a proposal at the moment so we can avoid exactly this issue - we've looked at Google Now's approach and do want to be much more targeted in our questions.

Were you able to ask Now for any additional documentation of what they did and what their findings were? That would be a useful reference.


//One important feedback we probably should allow to give more easily is reporting inappropriate content that Chrome should not suggest at all.

This feels like a separate feature. Shall we file a bug to track it?

// provide ways for the user to inspect and possibly correct their feedback.

This seems like much more complexity than we want to have. Let's talk more on Wednesday.

I don't see a milestone target -> setting priority to P3 for now until we have clarity. 

@nepper - following up on this piece. Are we just waiting on our meeting with Helen to decide if we'll move forward with this?

I think we've de-prioritized this work for now. Won't fix.