Move organization to a '3'

jpb5013 commented 7 years ago

Required Information

Description

ProgCode has been measuring itself on a 1 to 10 maturity scale, currently measured at a two. This issue aims to provide concrete details for what is needed to move from a 2 to a 3. ...

Problem

It is difficult for volunteer staff to know the key areas to contribute toward, how they may contribute and the future direction for the organization. Additionally, there are a wide variety of issues right now in various states of completion, however they are disconnected and status is unknown. ...

Benefit

Having a defined action list will help people understand how they can drive significant impact to ProgCode, demonstrate key activities where people can get involved and help progress us toward our mission of getting money our of politics. ...

Plan

[ ] Review in #operations and during weekly operations call
[ ] Define key actions to complete
[ ] Create individual issue for each action
[ ] Create GitHub milestone with all associate actions
[ ] Define RACI for each issue

Actions

[ ] Finalize ProgCode Data Policy
[ ] Finalize ProgCode Bylaws
[ ] Develop community community onboarding training
[ ] Develop partner onboarding training
[ ] Have new person deliver community onboarding
[ ] Create onboarding recording
[ ] Finalize ProgCode funding plan
[ ] Define volunteer staff onboarding
[ ] Develop high level milestones for 4 - 10 maturity
[ ] Publish ProgCode Roadmap blog article
[ ] Begin development on key Roadmap actions
[ ] Create recurring calendar for operational actions
[ ] Define allowed/not allowed partisan/anti-partisan activities
[ ] Define ProgCode partner benefits
[ ] Submit non-profit status
[ ] Define supported issues beyond single payer healthcare and net neutrality
[ ] Create playbook based on Healthcare Blitz work
[ ] Create post about level 3 ...

Decision Making

Consent to continue by consent ...

Optional Information

Reference link(s)

...

PamelaJohn commented 7 years ago

This makes me so happy I could do a little jig!

stephenscapelliti commented 7 years ago

This is beautiful, Joe! Would "Finalize ProgCode funding plan" include the establishment of fundraising and revenue sources?

jpb5013 commented 7 years ago

Thanks, Stephen and Pamela! And yes indeed, Stephen, that's exactly what I had in mind.

On Jun 2, 2017 11:12 PM, "desmondjones" notifications@github.com wrote:

This is beautiful, Joe! Would "Finalize ProgCode funding plan" include the establishment of fundraising and revenue sources?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ProgressiveCoders/functions/issues/205#issuecomment-305946943, or mute the thread https://github.com/notifications/unsubscribe-auth/ALZmq0jOkCa1FRDL71qrBbXxTniKgCAVks5sAM8MgaJpZM4NunF3 .

jpb5013 commented 7 years ago

Per conversation with @tktino, when onboarding new partners need to understand up front what revenue structure they are (for/non-profit). Also any potential partisan affiliations. I added a checklist item for defining partner onboarding process.

patcon commented 7 years ago

:point_up: point of clarification: can someone add a ref link that discusses this scale? :)

PamelaJohn commented 6 years ago

@patcon Here's the issue re scale and sustainability with additional reference links below. https://github.com/ProgressiveCoders/functions/issues/212

ProgressiveCoders / functions