Events/Global Strategy 2011: Difference between revisions

 
(6 intermediate revisions by one other user not shown)
Line 6: Line 6:
Mozilla is engaged in a broad range of events that target many audiences and outcomes. Until now, there has not be a deliberate effort to develop an overarching events strategy and ensure that the energies invested in events are effective, impacting, and harmonious across the organization. To the extent there can be shared infrastructure, resources, and other assets across the organization, these should be explored and built.  
Mozilla is engaged in a broad range of events that target many audiences and outcomes. Until now, there has not be a deliberate effort to develop an overarching events strategy and ensure that the energies invested in events are effective, impacting, and harmonious across the organization. To the extent there can be shared infrastructure, resources, and other assets across the organization, these should be explored and built.  


Needs:
In an effort to describe possible shared tools and workflow improvements towards greater efficiency and impact, the following document is a '''DRAFT'''. It's a strawman to begin the conversation. There's much to revise and improve. Let's dig in!
 
===Framing Questions and Principles===
* How do we decide what events we attend/support?
* How do we decide what events we attend/support?
** United front to contributors
** United front to contributors
** Common toolset to measure against event requests
** Need common decision-tree to measure against event requests
** Define roles. A task force and defining responsibilities.
** Define roles. A task force and defined responsibilities.
** Common schedule (Internal for planning vs. External for marketing)
** Common schedule and calendar (consider internal for planning vs. external for marketing)
** Common practices around sponsorship
** Common practices around sponsorship
** Participant coordination. Knowing who's attending what, how to max time there.
** Participant coordination. Knowing who's attending what, how to max time there.
In an effort to describe possible shared tools and workflow improvements towards greater efficiency and impact, the following document is a '''DRAFT'''. It's a strawman to begin the conversation. There's much to revise and improve. Let's dig in!


===Shared Goals===
===Shared Goals===
Line 23: Line 23:
* Leverage and '''extend our reach''' internationally and beyond targeted geographies and domains
* Leverage and '''extend our reach''' internationally and beyond targeted geographies and domains
* '''Improve web tools''' and products and increase their usage
* '''Improve web tools''' and products and increase their usage
* '''Teaching people''' about open technologies so that when designers and developers pick technologies, the open ones are top of mind.


===Event Matrix===
===Event Matrix===
Line 55: Line 56:
|-
|-
|}
|}
Questions/Suggestions:
* Settle on terms for audience types. Difference in usage of "users", "contributors", etc.
* This matrix is focused on our events. Need one for events we sponsor. Weights in size/audience, etc and determines priority.
* Which group is responsible for each category?
* Who identifies as Mozillian? Sometimes the community doesn't realize they have capacity / already doing something active.
* How Mozilla delivers involvement for events that we attend / sponsor
* How to determine priorities based on size, audiences
* Category / strategy for meetups during larger events (i.e. a Mozilla gathering within another conf)


===Shared Infrastructure===
===Shared Infrastructure===
* Calendars
* Calendars
** Christian has prototype
* Wikis
* Wikis
** https://wiki.mozilla.org/Events
* [[ReMo/Tools_and_Resources|Request forms]]
* [[ReMo/Tools_and_Resources|Request forms]]
** Speaker (we have one through press team)
** Conference sponsorship
** Travel sponsorship to speak/represent on behalf of Mozilla
* Communication channels
* Communication channels
* Mozilla Spaces
* Mozilla Spaces
* Event agreements, making sure they respect our values and our users
* Feedback mechanisms
** For event attendees and organizers (did you reach your goals, was it worth it, etc)
* Existing tools
** lanyrd: Call out who's self-identified Mozillians. Conversation planned with the company.
** speaker rate = rating for talks


===Shared Resources===
===Shared Resources===
* ReMo
* ReMo
* Program assets (slides, print materials, videos, etc). [[ReMo/Toolkit|ReMo]]
* Program assets (slides, print materials, videos, etc). [[ReMo/Toolkit|ReMo]]
* Videos of talks Mozillians have given
* Event toolkits
* Event toolkits
* Content Modules
* Content Modules
* Speaker Bureau
** Listing of people who can talk about different subjects. (Shannon)
* Budget?
* Budget?
** Costs: How much do events cost Mozilla? Not just sponsorship, but people hours, travel time, travel, etc.
** Organization-wide budget pool. (Should all be in "6300 Events & Sponsorship" bucket.)
* Badges or awards for participating and speaking at an event as incentive
 


===Shared Branding===
===Shared Branding===
Confirmed users
172

edits