Identify questions we want to answer for Pocket Listen, design telemetry

[mcomella]

Why/User Benefit/User Problem

We're going to have questions about how users use Pocket Listen. Sometimes the questions we want to answer about how users use a feature affect its design so we should identify those questions early in the design process. That time is now. :)

Filed a data science bug to initiate this: https://bugzilla.mozilla.org/show_bug.cgi?id=1535186

What / Requirements

• Meet with Product, data, eng & design to determine which questions we want to answer, feasibility to probe implementation, and any necessary changes to design
  • Consider meeting with Pocket data team to see if we should make Listen probes match mobile applications

Acceptance Criteria (how do I know when I’m done?)

[mcomella]

@athomasmoz FYI that I have filed a bug for this with the data science folks. Feel free to comment or close that issue if you don't think this is a good idea.

CC @devinreams In general, maybe we should get data involved in the process sooner – to help identify the questions we want to answer about user behavior – before we finish the design and especially before we've implemented the probes.