Websites/Mozilla.org/Roadmap 2011/Q2: Difference between revisions

Revision as of 21:35, 14 June 2011

Goals

(because goals are awesome! huzzah!)

Communicate Brand Positioning
Promote Developer Awesomeness
Establish Accessibility Excellence
Create Ideation Process
Measure User Experience
Measure Brand Awareness
Develop an Outstanding Mobile Experience
Adapt to Rapid Product Release Cycles

Rough list of Q2 goals (will finalize with Web Team feedback):

Communicate Brand Positioning

Engagement Owner(s): John, Chrissie

WebDev Partner(s): Fred, James

Rebranding Project - Team Wiki
- Planning
- Phase 1: Rebrand Mozilla Europe
- Phase 2: Rebrand Mozilla Messaging
- Phase 3: Rebrand Mozilla.com
- Future Phase: Site Unification Project
Improve conversion on Firefox landing page by 2% with detailed plan for ongoing A/B testing & measurement
- Project tracking bug
Measure & establish baseline of brand awareness on Firefox (US) Product Site & develop a detailed plan for testing & measurement that includes:
- User testing/interviews (as discussed with Blake this is more effective than running surveys given resources)
- Eye tracking research/testing (Brian Krausz of Gazehawk Eye Tracking]
- Implementing ongoing brand awareness survey on /fx (first run page) (Bug 660996 - delayed until Q2 due to Metrics resources)

Promote Developer Awesomeness

Engagement Owner(s): Laura

WebDev Partner(s): James, Raymond

3 mini HTML5 projects (404 error page, Snippets, and Firefox-focused landing page*)
Producing automated tests
- Finalize Raymond's tests & get them running on Hudson
Git transition (James)
- Work with localizers to warn them of switch
- Work with IT on switching live site to git
- Use Git & GitHub (more on infrastructure)
Dynamic content project(s) (James)
- Leveraging Playdoh where appropriate to reduce engagement team's dependency on webdev for making copy changes
- List of pages Engagement would like to edit on a ongoing basis

Chrissie = owner

Establish Search Excellence & Standards Compliance

Engagement Owner(s): Chrissie & Laura

WebDev Partner(s): TBD

Create XML sitemap for search engines & institute a regular & automated update schedule
Implement SEO/tag strategy (includes 404 page to assist with & improve lost lead user experiences, title tags, & descriptive alt text). Reach goal: increase natural search traffic by 5%. Wiki.

Bugs:

Update moz.com "Mobile" pages: 642432
Update H1, H2, H3 tags/copy: 663925
Update title tags and meta descriptions Bug 657387

Note: All of the above will be part of a checklist of excellence.

Measure User Experience

Engagement Owner(s): Chrissie & Laura

WebDev Partner(s): TBD

Establish creative/ideation process that leads as a companion partner into webdev process (Chrissie)
- Conduct design & user research (eye tracking, user testing, brand awareness) for existing & new projects
Centralize a web metrics dashboard for reporting on user engagement success (Bug 664294)
- Improve user (Mozilla team member) experience around understanding, interpreting, and accessing analytics (details)

Develop Outstanding Mobile Experience

Engagement Owner(s): Chrissie, Laura

WebDev Partner(s): Jason Grlicky

Develop a concise mobile experience around content for the Firefox product site (mozilla.com/org)
- Conduct user & design research phase & produce discovery & recommendations brief (includes a survey & report of what mobile users are looking for when they come to the website - e.g. they may not be looking for a mobile download) [Bug 656453]
- Conduct a content inventory/audit of all mobile content (what content exists that is only available for /m users - why do we have that content, can that content be replaced with a single content experience that works for desktop & mobile users, which would reduce overall content maintenance)[content inventory here on second tab]
- Streamline entire content experience across Firefox product site (mozilla.com/org) to produce a single content experience that works for both desktop & mobile users (eliminating redundant, long-winded, vague, and puff copy). Create best-practices for content creation for Firefox product site that ensures prevailing copy creates an awesome experience for mobile users)
- Establish creative/ideation process as a companion into the new webdev process
Increase conversion to download for mobile clients
- Support FX5 mobile release project(s)
- Make mobile more actionable [Bug 659451]
- Learn more about the Android app store experience/process & identify areas for improvement

Adapt to Rapid Product Release Cycles

Engagement Owner(s): Laura & Chrissie

WebDev Partner(s): James Long & Steven Garrity (silverorange)

Successfully launch FX5 desktop & mobile on the website on time
Successfully launch Rapid Release site changes on Mozilla.com. [Bugs]

Team Onsite (Results)

A 3-day working onsite in Mountain View to gather as a team and tackle projects and planning.

Notes on our sessions can be found here.

@@ Line 5: / Line 5: @@
 #Communicate Brand Positioning
 #Promote Developer Awesomeness
 #Establish Accessibility Excellence
 #Create Ideation Process
 #Measure User Experience
 #Measure Brand Awareness
 #Develop an Outstanding Mobile Experience
 #Adapt to Rapid Product Release Cycles
@@ Line 18: / Line 18: @@
 Engagement Owner(s): John, Chrissie
 WebDev Partner(s): Fred, James
 *[https://wiki.mozilla.org/Mozilla.com/2011-Rebranding-Project Rebranding Project - Team Wiki]<br>
 **[https://wiki.mozilla.org/Mozilla.com/2011-Rebranding-Project#Planning Planning]
@@ Line 30: / Line 31: @@
 **User testing/interviews (as discussed with Blake this is more effective than running surveys given resources)
 **Eye tracking research/testing (Brian Krausz of [http://www.gazehawk.com/ Gazehawk Eye Tracking]]
-**Implementing ongoing brand awareness survey on /fx (first run page) (Bug 660996)<br>
+**Implementing ongoing brand awareness survey on /fx (first run page) (Bug 660996 - delayed until Q2 due to Metrics resources)<br>
 == Promote Developer Awesomeness  ==
@@ Line 70: / Line 71: @@
 <br>
 ''Note: All of the above will be part of a [https://wiki.mozilla.org/Websites/Processes checklist of excellence].''
 == Measure User Experience  ==
@@ Line 80: / Line 81: @@
 *Establish creative/ideation process that leads as a companion partner into [https://wiki.mozilla.org/Websites/Processes webdev process] ''(Chrissie) ''
 **Conduct design &amp; user research (eye tracking, user testing, brand awareness) for existing &amp; new projects<br>
-*Centralize a web metrics dashboard for reporting on user engagement success ''(Laura)''
+*Centralize a web metrics dashboard for reporting on user engagement success (Bug&nbsp;[https://bugzilla.mozilla.org/show_bug.cgi?id=664294 664294])
 **Improve user (Mozilla team member) experience around understanding, interpreting, and accessing analytics ([https://wiki.mozilla.org/Engagement/Analytics/Webtrends#4.2F20.2F2011 details)]<br>
@@ Line 91: / Line 92: @@
 *Develop a concise mobile experience around content for the Firefox product site (mozilla.com/org)
 **Conduct user &amp; design research phase &amp; produce discovery &amp; recommendations brief (includes a survey &amp; report of what mobile users are looking for when they come to the website - e.g. they may not be looking for a mobile download) [Bug [https://bugzilla.mozilla.org/show_bug.cgi?id=656453 656453]]<br>
 **Conduct a content inventory/audit of all mobile content (what content exists that is only available for /m users - why do we have that content, can that content be replaced with a single content experience that works for desktop &amp; mobile users, which would reduce overall content maintenance)[[http://bit.ly/k3yvcw content inventory here on second tab]]<br>
 **Streamline entire content experience across Firefox product site (mozilla.com/org) to produce a single content experience that works for both desktop &amp; mobile users (eliminating redundant, long-winded, vague, and puff copy). Create best-practices for content creation for Firefox product site that ensures prevailing copy creates an awesome experience for mobile users)
 **Establish creative/ideation process as a companion into the [https://wiki.mozilla.org/Websites/Processes new webdev process]
 *Increase conversion to download for mobile clients
 **Support FX5 mobile release project(s)
 **Make mobile more actionable [Bug [https://bugzilla.mozilla.org/show_bug.cgi?id=659491 659451]]
 **Learn more about the Android app store experience/process &amp; identify areas for improvement
@@ Line 108: / Line 109: @@
 *Successfully launch Rapid Release site changes on Mozilla.com. [[http://bit.ly/m0H8bh Bugs]] <br>
-== Team Onsite (Results) ==
+== Team Onsite (Results)  ==
 A 3-day working onsite in Mountain View to gather as a team and tackle projects and planning. <br>
 Notes on our sessions can be found [https://wiki.mozilla.org/Mozilla.org/Roadmap_2011/Q2WebsiteOnsite <span style="text-decoration: underline;">here</span>].