Advocacy: Difference between revisions

610 bytes removed ,  19 February 2015
Added diagram of qual/quant flow
(Added diagram of qual/quant flow)
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==User Advocacy Mission==
==User Advocacy Mission==
The User Advocacy Team represents  the best interests of our users. It is the ultimate goal of User Advocacy to ensure  that we  as an organization do not fail our users. As a team, User Advocacy will  become the conduit for the true voice of the user to ensure that they are heard at all levels of the organization. User Advocacy distills information gained through user feedback. User Advocacy will translate, articulate, and  quantify these insights and disseminate them appropriately throughout the organization.  
UA is the conduit for the voice, desires, and needs of the user, ensuring that they are heard at all levels of the organization. We distill the data from various communication channels and turn these insights into actions. As a team, our goal is to ensure that we, Mozilla, never fail our users. The brand promise is our driving force. It is our mantra.


While User Advocacy is a stakeholder and ultimately influences all aspects of the Product Roadmap, User Advocacy owns the recoverability vertical. Through this vehicle we ensure that our users are always able to return  to a fully functional and familiar product no matter what issues they  may encounter in their journey.
==How we work==
[[File:Uaworkdiagram.png|Qualitative and Quantitative feedback flow]]


User Advocacy distills information gained through feedback from our users. User Advocacy strives to turn '''New''' into '''Known'''. Other groups such as User Support and our Product partners are able to take action based on these insights.
==Contact Information==
'''Desktop Lead/Manager - Matt Grimes'''<br>
'''Email:''' mgrimes@mozilla.com<br>
'''IRC:''' Matt_G<br>


==Responsibilities==
'''Desktop and Backend - Cheng Wang'''<br>
'''UA works proactively to ensure that our users have amazing products that work by monitoring pre-release versions of the project'''
'''Email:''' cww@mozilla.com<br>
'''UA works reactively to identify issues quickly and to prevent us from failing our users'''
'''IRC:''' Cww<br>
'''UA looks at the larger product picture to identify key areas of improvement'''
 
==Contact Information==


'''Mobile Lead - Tyler Downer'''<br>
'''Project Manager - Tyler Downer'''<br>
'''Email:''' tdowner@mozilla.com<br>
'''Email:''' tdowner@mozilla.com<br>
'''IRC:''' Tyler<br>
'''IRC:''' Tyler<br>


'''FF OS Lead and Special Projects - Cheng Wang'''<br>
'''Firefox OS and Quantitative Research - Ilana Segall'''<br>
'''Email:''' cww@mozilla.com<br>
'''Email:''' isegall@mozilla.com<br>
'''IRC:''' Cww<br>
'''IRC:''' ilana<br>
 
'''Firefox for Android and Backend - Rob Rayborn'''<br>
'''Email:''' rrayborn@mozilla.com<br>
'''IRC:''' rrayborn<br>


'''Desktop Lead - Matt Grimes'''<br>
'''Quantitative Research and Special Projects - Gregg Lind'''<br>
'''Email:''' mgrimes@mozilla.com<br>
'''Email:''' glind@mozilla.com<br>
'''IRC:''' Matt_G<br>
'''IRC:''' gregglind<br>
Confirmed users
447

edits