Your SlideShare is downloading. ×
H(app)athon project Committee bible (guidelines)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

H(app)athon project Committee bible (guidelines)

309
views

Published on

This deck outlines who does what on our Committee, our budget, goals, stakeholders and other information most relevant to the Committee that we still wanted to share with the public.

This deck outlines who does what on our Committee, our budget, goals, stakeholders and other information most relevant to the Committee that we still wanted to share with the public.


2 Comments
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total Views
309
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
2
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. What  We’re  About  Why  Are  We  Doing  This?                    Page  3  How  Do  We  Want  People  to  Play  with  Us?              Page  5  What’s  our  Voice?                      Page  7  What  do  we  Want  People  to  Do?                Page  9  Who  are  our  stakeholders?                Page  12  Challenges                        Page  17      Our  Goals                      Overall  Project  Goals                  Page  20    TacJcal  Project  Goals                  Page  22        Opera2ons                      CommiLee  Structure                  Page  23  Calendar/Deadlines                  Page  26  Budget                      Page  30  PR/MarkeJng/Crisis                  Page  34  Thank  You                      Page  36             H(app)thon  Project    Bible   2  
  • 2.         Why  are  we  doing  this?         H(app)thon  Project    Bible   3  
  • 3.       At  the  heart  of  our  work,  we  (The  CommiLee)  are  facilitators  for  others  –  to   share  our  experJse,  help  others  opJmize,  and  idenJfy  resources  when  we   don’t  have  answers.       We’re  here  to  help  people  join  and  benefit  from  our  Mission  of  uJlizing   emerging  technology  to  improve  human  well-­‐being  and  drive  posiJve  change.       H(app)thon  Project    Bible   4  
  • 4.         How  do  we  want  people  to  play  with  us?         H(app)thon  Project    Bible   5  
  • 5. We  want  people  to  share  what  brings  their  life  meaning  while  we  provide  resources  to  help  them  opJmize  their  well-­‐being.    We  want  people  to  share  the  insights  they’ve  learned  to  bring  holisJc  and  h(app)y  value  to  the  world.   H(app)thon  Project    Bible   6  
  • 6.         What’s  our  Voice?         H(app)thon  Project    Bible   7  
  • 7. The  Voice  of  the  H(app)athon  Project  is  passionate,  whimsical,  curious,  and  above  all,  inviJng.    We  never  tell  people  what  brings  their  life  well-­‐being,  “happiness”  or  meaning  –  we  ask  them  what  they  think  and  to  help  us  change  the  world,  for  good.     H(app)thon  Project    Bible   8  
  • 8.         What  do  we  want  people  to  do?         H(app)thon  Project    Bible   9  
  • 9. Our  first  call  to  acJon  (CTA)  is  for  people  to  sign  up  for  our  mHIS  survey.  The  results  of  the  survey  will  form  the  backbone  for  the  data  to  be  used  at  our  fist  hackathon(s).  It  is  the  community’s  involvement  that  validates  our  creaJng  a  globally  crowdsourced  Happiness  Indicator  and  App.     H(app)thon  Project    Bible   10  
  • 10. The  two  Cycles  of  our  work  (surveys/Hackathons)  are  created  strategically  so  community  parJcipants  can  first  discover  how  well-­‐being  is  measured  via  emerging/mobile  tools,  then  opJmize  throughout  their  involvement  in  our  work.    This  could  only  be  an  open-­‐source  Project  inasmuch  as  we  need  global  parJcipaJon.    Well-­‐being,  as  an  economic  and  happiness  Indicator,  is  culturally  driven  and  cannot  be  mandated  by  any  group  or  government.        Our  purpose  is  always  to  Inform  (point  to  experts  on/off  Commi4ee),  Introduce  (list  resources  on  our  Wiki/Site  for  people  to  op<mize)  and  Inspire  (engage  with  personable,  kick-­‐ass  content  that  earns  interest  and  trust).       H(app)thon  Project    Bible   11  
  • 11.         Who  are  our  Stakeholders?     H(app)thon  Project    Bible   12  
  • 12. The  “Happiness”  Experts  We’re  focused  on  “well-­‐being”  which  encompasses  much  more  than  emoJon  or  mood.  Our  messaging/markeJng  should  appeal  to  people  who  deal  with  the  economic  or  scienJfic  areas  that  include:    •  SubjecJve  well-­‐being  •  Economic  well-­‐being  •  The  physiology  of  happiness/well-­‐being  •  The  psychology  of  happiness/well-­‐being  •  The  study  of  meaning  (in  business  and  in  life)     H(app)thon  Project    Bible   13  
  • 13. The  Big  Data  Experts  Big  Data  encompasses  mulJple  areas  of  technology  and  issues.  Our  messaging/markeJng  should  appeal  to  people  who  deal  with  the  following  types  of  issues:    •  How  to  communicate  privacy/idenJty  issues  around  Big  Data  •  How  to  frame  data  sets/quesJons  to  obtain  maximum/relevant  insights  •  How  to  frame  insights  to  give  greatest  value  to  a/our  community  •  How  Big  Data  is  part  of  a  larger  cultural  phenomenon  than  technology   H(app)thon  Project    Bible   14  
  • 14. Internet  of  Things/Emerging  &  Mobile  Tech  Community  IOT  is  criJcal  for  our  work  as  devices  are  now  measuring  and  recording  our  acJons  via  mobile  and  other  technology.  Our  messaging/markeJng  should  appeal  to  people  who  deal  with  the  following  types  of  issues:    •  How  sensors  collect  data  –  acJve,  passive,  where  and  how  •  Interoperability  of  sensors/tech  –  how  will  everything  work  together?    •  Cultural  ramificaJons  of  data-­‐driven  design  •  How  IOT  is  part  of  a  larger  cultural  phenomenon  than  technology   H(app)thon  Project    Bible   15  
  • 15. The  Policy  or  Governance  Community  This  is  the  most  sensiJve  area  of  our  work  –  how  do  we  communicate  the  sensiJvity  around  data  collecJon/usage  to  the  general  public,  and  then  frame  our  results  in  a  way  non-­‐tech  focused  officials  can  best  uJlize?    •  Groups  like  The  Sunlight  FoundaJon  would  be  an  excellent  partner  •  Doc  Searles  and  his  work,  re:  data  privacy  should  be  reflected  •  Our  second  cycle  of  work  (survey/hackathons)  will  invite  policy  or   governance  experts  to  join  our  work  so  we  can  ask  them  these  quesJons   H(app)thon  Project    Bible   16  
  • 16.         Challenges       H(app)thon  Project    Bible   17  
  • 17. Breaking  down  silos.    When  people  ask  us,  “why  should  you  be  the  ones  doing  this?”  our  answer  is,  “why-­‐did  you  want  to  help?”  For  all  of  our  stakeholder  groups,  there  may  be  disagreements  on  methodology  of  research  or  theory.        Our  moJvaJon  is  always  to  invite  all  groups  focused  on  areas  of  our  work  into  the  conversaJon  and  then  let  our  community  weigh  in  to  decide  how  to  iterate  our  technology  and  ideas.  A  great  deal  of  our  value  will  come  from  introducing  our  key  stakeholder  groups  to  each  other  to  move  our  vision  from  an  idea  to  reality.     H(app)thon  Project    Bible   18  
  • 18.         Our  Goals       H(app)thon  Project    Bible   19  
  • 19.       Overall  Project  Goals     Inform/Op2mize  –  Like  it  says  in  our  Vision  deck,  “our  product  is  our  process.”   There  are  hundreds  of  organizaJons  collecJng  data  about  well-­‐being,  building  apps   or  launching  studies  about  posiJve  psychology.    These  people  or  organizaJons  are   never  our  compeJtors  in  any  way  –  they’re  collaborators  if  their  pursuit  is  to  help   others  opJmize  and  find  well-­‐being.       H(app)thon  Project    Bible   20  
  • 20. Overall  Project  Goals           Build  an  App  that  acts  as  a  ‘Mood  Ring  for  the  Planet’–  While  we’ve  launched  the   idea  of  our  Project,  our  first  public  events  happen  March  20th.    This  is  the  place  where   we’ll  launch  our  Survey.  The  results  of  the  Survey  will  also  be  used  to  form  the  Data   we’ll  use  at  our  first  hackathon(s).    The  culminaJon  of  our  two  cycles  (this  first  one  in   March  and  one  other)  will  be  the  release  of  a  free  App  on  March  20,  2014  at  a  large-­‐ scale  conference  in  NYC.       While  specifics  of  the  App  will  be  formed  by  Hackers  and  guided  by  the  CommiLee,   its  basic  funcJon  will  be  to  help  a  user  idenJfy  areas  of  well-­‐being  to  be  opJmized,   see  how  they  can  help  others  nearby  or  around  the  world,  and  gauge  the  health/well-­‐ being  of  the  planet’s  well-­‐being  via  real-­‐Jme  data  visualizaJons.       H(app)thon  Project    Bible   21  
  • 21.     Tac2cal  Project  Goals       •  At  least  25,000  subscribers  to  our  mHIS  Surveys  (aggregate)  by  3/20/2014.   •  $250-­‐400  worth  of  sponsorship  to  cover  enJre  budget.   •  Twenty-­‐five    countries  parJcipaJng  in  our  work  in  some  way.     •  Ten  or  more  organizaJons  directly  related  to  policy  involved  in  our  work.     •  At  least  10,000  downloads  of  our  App  by  the  end  of  2014.     •  Coverage  via  top  media  outlets  that  helps  readers/viewers  learn/opJmize.   •  Enough  posiJve  momentum  to  conJnue  the  Project.   •  Enough  posiJve  momentum  to  make  our  final  Conference  an  annual  event   •  Become  the  “TED”  of  well-­‐being/emerging  media         H(app)thon  Project    Bible   22  
  • 22.         CommiTee  Structure       H(app)thon  Project    Bible   23  
  • 23. Oversight  CommiTee       •  John  C.  Havens  (Founder,  Chair)       •  Sean  Bohan  (OperaJons  Lead,  Data/Privacy  Sub-­‐CommiLee  Chair)   •  Kat  Houghton  (Tech  Lead,  Research  Sub-­‐CommiLee  Chair)   •  Stewart  Townsend/Carlos  Somohano  (Big  Data  Sub  CommiLee  and  Global  CoordinaJon  Chairs)   •  Alexis  Adair  (Wiki  Master/BaseCamp  and  Internal  DocumentaJon  CoordinaJon     Structure   •  JCH  leads  overall  Project,  Vision.    Coordinates  with  Oversight  CommiLee  and  Sub-­‐CommiLee  Chairs   •  SubCommiLee  Chairs  responsible  for  seong  meeJngs,  coordinaJng  tasks,  and  maintaining  calendar/objecJves   •  Global  OperaJons:     •  Sean  to  help  JCH  coordinate  SubCommiLee  meeJngs,  sponsorship,  Hackathons     •  Kat  to  coordinate  all  technical  aspects  of  Project  and  drive  Research  operaJons  for  surveys   •  Kat  to  work  with  Sean,  Carlos  and  Stewart,  re:  coordinaJon  of  survey  data  for  hackathons   •  Global  CoordinaJon:     •  Stewart/Carlos  to  coordinate  with  JCH  on  process/approvals  for  new  Happathon/Hackathons  (TBD)   •  Sponsorship  or  other  Monies:     •  See  Budget  secJon   H(app)thon  Project    Bible   24  
  • 24.     Sub-­‐CommiTees       •  Research.  Kat  Houghton,  Chair.   •  Members  -­‐      Jon  Hall,  Margie  Morris,  Mary  Czerwinski,  Laura  Musikanski,  Neal  Lathia,  Kalev    Leetaru,  Adam   Laughlin,  Stewart  Townsend,  Carlos  Somohano,  JP  Rangaswami,  Susannah  Fox,  Alexis  Adair     •  Big  Data  (QuanJfied  Self/Internet  of  Things)  Stewart  Townsend,  Carlos  Somohano,  Chairs.       •  Members  –  Sean  Bohan,  Ernesto  Ramirez,  Kalev  Leetaru,  Adam  Laughlin,  Neal  Lathia,  KonstanJn  Augemberg     •  Data/Privacy.    Sean  Bohan,  Chair.   •  Members  –  ScoL  L.  David,  John  Clippinger       •  Marke2ng.  John  C.  Havens,  Chair.     •  Members  –  David  Richeson,  Amber  Melhouse,  JaNae  Duane,  Stan  Stalnaker,  Tim  Leberecht,  Eiji  Han  Shimizu,   William  Hoffman,  Kim  WhiLemore.     •  Financial  Oversight.    Chair,  TBD.   •  3/20/2014  Conference.    Chair,  TBD.     H(app)thon  Project    Bible   25  
  • 25.         Calendar/Deadlines       H(app)thon  Project    Bible   26  
  • 26.     Cycle  One       •  12/28/2012  –  PROJECT  LAUNCH.  Press  release,  Mashable  arJcle,  temporary  site  launched.   •  1/21/2013  –  MHIS  COPY  COMPLETED.  Final  quesJons/answers  ready  for  ilumivu  app.   •  1/22/2013  –  3/20  Eventbrite  URL’s  completed,  invitaJons  begin  to  get  sent.   •  1/21/2013  –  PARTICIPANT  OPT-­‐IN  LANGUAGE  DRAFTED.  Opt-­‐in  language  for  approvals.   •  2/22/2013  –  mHIS  DRAFT  COMPLETED.  WriLen  copy  approved  by  research/Big  Data  Teams.     •  3/4//2013  –  mHIS  COMMITTEE  TESTING.    Up  to  two-­‐week  trial  to  work  out  bugs.     •  3/20/2013  –  HAPPATHON  EVENTS  TAKE  PLACE.  NYC,  London,  Tokyo.     •  3/20/2013  -­‐    mHIS  Survey  released  at  3/20  Events   •  3/20/2013  –  Partners  to  post  survey  app/link  release  link  to  build  parJcipaJon   H(app)thon  Project    Bible   27  
  • 27.     Cycle  Two     •  TBD           H(app)thon  Project    Bible   28  
  • 28.         Budget       H(app)thon  Project    Bible   30  
  • 29.     $350,000  (USD)*       •  $10,000  –  upfront  fees  for  website/designer,  LLC  formaJon,  press  release   •  $40,000  –  total  fees  for  London/NYC  happathons  on  3/20  (food,  venue,  insurance)   •  $100,000  –  total  fees  for  hackathons  in  Cycles  one  and  two  (at  least  one  hack/cycle)   •  $50,000  –  tech  fees  (staff,  development)  for  creaJon  of  H(app)athon  App  (released  2014)   •  $100,000  –  total  fees  for  large-­‐scale  conference  on  3/20/2014   •  Food,  venue,  insurance,  promoJon,  on-­‐site  staffing,  potenJal  fees/travel  for  speakers,  more  TBD   •  $50,000  –  staffing  fees  (JCH,  community  manager,  others  TBD)     *All  fees  are  rounded  up  to  represent  our  ‘dream  budget’  and  provide  buffer  for  unforseen  expenses         H(app)thon  Project    Bible   31  
  • 30.     Financial  Oversight       •  Happathon,  LLC  –  Covers  basic  org  needs  –  legal,  sponsors  can  write  checks,  etc.   •  CommiLee  needs  a  CFO  type  for  budget  so  JCH/Members  have  oversight.   •  Specifics  TBD  and  voted  on,  but  monies  collected  for  Happathon  project  in  general:     •  Pay  previously  agreed  upon  budgetary  costs/fees   •  Where  overages  occur,  monies  put  into  main  Happathon  budget  for  future   •  ExcepJon  is  when  approved  CommiLee  Franchisee  secures  sponsorship   •  Overages  in  this  case  –  50%  go  to  main  Happathon  budget,  50%  to  Franchisee     •  For  monies  collected  over  total  budget  of  $350,000:   •  50%  goes  to  Happathon  budget  for  2015  Conference,  25%  towards  a  Happathon  fund   (prizes  at  future  events),  25%  for  CommiLee  Party/Offsite  Event       H(app)thon  Project    Bible   32  
  • 31.         PR/Marke2ng/Crisis       H(app)thon  Project    Bible   33  
  • 32.     PR/Marke2ng/Crisis       •  The  MarkeJng  CommiLee  will  create  a  MarkeJng  Plan  for  the  Project  TBD.     •  PR  Wise,  we  will  be  seeing  in-­‐kind  PR  help  to  help  secure  media  placements  and  guide  our   overall  messaging.     •  Crisis  –  In  the  case  of  any  messaging  or  other  Crisis,  John  C.  Havens  should  be  contacted   immediately  as  primary  spokesperson  for  the  Project.     H(app)thon  Project    Bible   34  
  • 33.         Thank  You.         H(app)thon  Project    Bible   35  
  • 34.     This  CommiTee  is  telling  the  world  how  to  be  H(app)y.       Thank  you.         H(app)thon  Project    Bible   34