- Articulate our root questions (what was the purpose of the survey, what questions is it intended to answer?
- Satisfaction of our customers
- How to fine-tune our offering to be more valuabe? To be more appealing?
- How to convert from survey results into answer to question survey was inteded to address
- Results analyzed and documented
- results examined
- Results visualized if appropriate
- obvious patterns, anomolies identified
- Answers to purpose questions determined
- Based on survey results, summarize new findings that aren't directly related to original questions
- Conclusions drafted
- What does this mean to TPG?
- What is TPG thinking about changing as a result of this report?
- Results published
- TPG mailing list
- WMF
- mediawiki?
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | ggellerman | T139549 [EPIC] Roll out Light Engagement survey | |||
| Resolved | ggellerman | T141136 Report on Light Engagement survey pilot, round 1 |
Event Timeline
Comment Actions
@ggellerman: I think the "what we learned about the survey itself" should also be part of a "report on" task, rather than part of the "revise the survey" task. Do you think this task (T141136) should be expanded to include that other report, or should I create a new subtask of the epic specifically for that report?
Comment Actions
@ksmith
I agree that "what we learned about the survey itself" should be part of the "report." I also think that it could be its own task so as not to complicate the 'assigned to" field.
Comment Actions
Created T145134: Report on Light Engagement survey pilot, pt 1, what we learned about the survey itself for the other report.
Comment Actions
Customer feedback summarized:
https://docs.google.com/document/d/1fhvGWtkfvY-7RspPzk-ZiqMpF5tnQM1ReJLCTUoB-xw/edit
Sent to TPG for comments 2016-09-12