###Priorities for growth

* **improve first contact experience**
* **integrate with Kits Initiative**

###Priorities for depth:

* **develop better structure to become an organizer**
  * Organizer Summit
* **make a strong translation model for our "communities of practice"**
  * includes distributing resources
* **include social process throughout online and offline**
  * community asset mapping workshops, dialogue education facilitation, modes of communication beyond email groups, OpenHour, guides and distance learning, offline logbooks, etc

###Scaling engagement: a model

####First contact

* map of **first contacts** --> pathways: http://publiclab.org/wiki/first-encounters
  * folks find out about Public Lab through: our kits, our web presence and social media, press coverage, heard about from a person, Kickstarter campaign, evangelism(?)
* ISSUE: website **front page**
  * too much information, lacks community presence/identity, not synthesized

####Welcome moment

* **Looking for how I "fit in"**
  * lead with values
  * culturally, is the first "welcome" over dinner or by typing into a technical discussion?
  * identifying the "need" to engage -- begin with what is already known locally -- asset mapping exercise -- needs to be systematized. This can combat the perception problem of tools seen as speculative not results-oriented. 
  * attracting diversity in the context that many active members have leisure time, are high capacity and degreed
* **"When do I see myself as a part of Public Lab?" --> Hello Moment**
  * _see First contribution below_
* **who's responsibility is welcoming / orienting new members?**
  * Welcome Working Group has scaling issues
  * everyone / no one?
* **option to speak to **types** of stakeholders:** 
  * [reference from Sugar Labs](http://wiki.sugarlabs.org/go/Sugar_Labs/Getting_Involved), 
  * and Scott's metaphor below: 

[![scotts-metaphor-boat_kite.jpg](https://i.publiclab.org/system/images/photos/000/004/297/medium/scotts-metaphor-boat_kite.jpg)](https://i.publiclab.org/system/images/photos/000/004/297/original/scotts-metaphor-boat_kite.jpg)

####First contribution / activity

* **publiclab.org/signup** --> profile page
* **posting a research note**
* **going to an event / meeting someone in person**
* **Ask a question / answer a question** forums
  * serves as a venue for matchmaking
  * develops a Most Wanted List to prioritize R&D

####Building peer-to-peer bonds

* **mailing list discussions**
  * prompts upon joining to say "I am interested in [...], I can help with [...], bio, location
* **comments on research notes**
* **website:** 
  * further integration of lists and website (future)
  * regionalization of website / feeling of place
  * listening to interests and areas
  * tours of places through mapknitter
* **collaborative editing on wikis / pads**
* **regularly scheduled meetups**
  * not just tech, but also goal setting, asset mapping, strategizing, learning 
  * on research sites
* **cross-group and cross-region exchanges**
* **voice channels: [openhour](http://publiclab.org/wiki/openhour)**
* **ISSUE: social bonds should not result in clubhouse effect**

####Becoming an organizer

* **update / demystify nomination process:**
  * change nomination process to focus on profile pages
  * self-nomination for folks instantly seeking a higher level of engagement
  * options for community organizers who may be offline / won't join email list
* **attracting new organizers:**
  * targeting outreach, diversity
* **resources for organizers**
  * buddy system with experienced organizer
  * event "guides"
  * receive all foldable kits
  * speaking opportunities on OpenHour
  * Organizers Summit (day before annual Barnraising)
* **benefits / expectations**
  * regional focus to nurture new members, partner orgs, and research sites
  * staying engaged monthly
  * annual survey for re-up
  * fundraising support
  * Fellows Program

####Developing organizer-supported chapters