Firefox 4 is coming out with an expanded beta program. This affects support in 3 key ways:
- 1 Supporting the users
- 2 How will we run this?
- 3 How many people do we need?
- 4 How to involve the community in this effort?
- 5 Can we use the beta to pilot the community <=> QA interaction?
- 6 What are the feedback channels we should be monitoring (Feedback button)
- 7 Who should be monitoring them?
- 8 What do we want to get out of it?
- 9 How should the study be designed
- 10 Which other groups would benefit from this information and how should we communicate it with them?
Supporting the users
The goal is to expand from 1.3M users on the beta channel to 2-4 M users, with 30-40% of the users on the beta being "mainstream" rather than techie. These users are going to need help with their problems and concerns especially because: 1) The software is in beta and not release quality. 2) Mainstream users are less likely to accept changes and may get discouraged and switch back.
In order to do this, we need to figure out how to support these users:
How will we run this?
How many people do we need?
Can we get marketing to help build a support community
Should we do a special schwag outreach to kick start this community?
Brainstorming and planning doc: Support/Firefox 4 User Support Plan
Collecting user feedback/questions and passing off to devs
SUMO is listed as a feedback channel for this project and we should be responsible and proactive about making sure that we do our part in passing common issues along.
How to involve the community in this effort?
Can we use the beta to pilot the community <=> QA interaction?
Brainstorming and planning doc: Support/Firefox 4 feedback reporting plan
Using the feedback from all channels to improve SUMO before release
There are going to be lots of feedback channels as part of this project and we should use the data from them to inform what needs to be done to get the KB and SUMO ready for release.
Who should be monitoring them?
Brainstorming and planning doc: Support/Firefox 4 feedback incorporation plan
Test pilot user learning study
There will be a study that will be run through Test pilot that will help us better understand the ways Firefox users adapt to the new UI as well as how they learn.
What do we want to get out of it?
How should the study be designed
Which other groups would benefit from this information and how should we communicate it with them?
Brainstorming and planning doc: Support/Firefox 4 Longitudinal user study
- Late June: First betas release for FF4
- July/August: Big push to mainstream users
- Late October/November: FF4 final release.