More   Longer   Be*er  

More  

•  We  released  5  apps  in  our  first  18  months  (110  days  per  app)  

•  We  hosted  about  70  meetups,  two  CityCamps,  and  a  handful  of  other  mee@ngs  

•  We  can  get  more  done  

More  

•  In  2014:  – Faster  cycle  @mes    

•  From  110  days  to  30  for  easy  apps,  for  example  

– More  product  aJempts  •  Try  more  

– More  product  failure    •  Accept  more  risk,  more  difficulty  

– More  product  launches  •  Finish  more  

Longer  

•  We’ve  been  love-­‐’em-­‐and-­‐leave-­‐em  with  most  of  our  projects,  abandoned  on  launch  

•  So  we  don’t  iterate,  learning  from  users  •  So  we  don’t  build  social  and  community  elements  into  our  products  

•  So  we  miss  on  building  user  adop@on,  usage  per  user,  and  the  benefits  our  apps  might  deliver  

Longer  

In  2104:  •  Take  responsibility  for  products    past  first  launch  Growth  hacking  Community  development  Up@me  &  Recovery  Hos@ng  User  experience  Tech  support  

Customer  service  systems  Analy@cs  CI    User  feedback  and  bug  repor@ng  Privacy  

Revving  and  Release  Cycles  End  of  Life  Planning    

BeJer  

•  Our  Brigade  can  serve  our  volunteers  be*er  •  Too  many  people  never  show  up,    show  up  only  once,    drop  out  part  way  through  a  project,    or  never  come  back  for  a  second  project  

•  Not  enough  people  refer  their  colleagues  and  bring  them  to  hack  nights  

BeJer  

•  Conversion  Rates  through  the  Brigade  Member’s  Journey  – Turn  more  prospec@ve  volunteers  into  brigade  members  

– Deeper  engagement  First  

Leadership  Role  

First  Friend  

Recruited  First  Code  Check-­‐In  First  

Project  First  Mee@ng  Prospect  

BeJer  

•  We  can  help  brigade  members  extract  more  value  from  their  OO  experience  – Personal  goals:    

•  Accomplish  tangible  results  for  the  community  •  Affiliate  with  professionals  •  Acknowledged  for  contribu@ons  •  Learn  new  skills  •  Feel  like  an  Oaklander  

BeJer  

In  2014:    •  Cadres:    – Organize  around  professional  disciplines    

•  User  experience,  research,  design  •  Data  visualiza@on,  data  analysis,  data  science  •  DevOps,  produc@on  management  •  Partner  rela@onships,  business  analysis,  product  management  •  Growth  hacking,  community  management  

BeJer  

In  2014:    •  Establish  and  iterate  our  People  func@ons  – Recrui@ng  – Onboarding  

•  Every  newbie  Orientated  and  Connected  to  Cadre  &  Project  Teams  within  first  hour  of  first  visit  

– Reten@on  – Professional  Development  – Recogni@on  

BeJer  

In  2014:    •  Cadres:    – Deliver  value:    

•  Recrui@ng  •  Professional  development  and  educa@on  •  Common  standards,  tools,  prac@ces  across  projects  •  Member  con@nuity  between  projects  

– Cadres  connect  across  brigades  

More   Longer   Be*er