The document outlines proposals for strengthening the YNPN network through three projects: developing shared standards, creating a data center, and setting up chapter input and decision-making structures. It discusses the goals and processes for each project. For the shared standards project, it proposes developing a set of standards to define what it means to be a YNPN chapter and determine the necessary supports. For the data center project, it discusses creating a system to collect and aggregate chapter-level data. And for the chapter input project, it proposes creating a Chapter Congress representative body and processes for greater network connectivity and joint decision-making. Feedback from chapters is requested on the proposals to further refine them.
2. Big Ideas:
• Shared membership status
across the network
•Institutional memberships for
national organizations
•An all-member conference
•More shared technology such
as a CRM
•Funding and support for
chapters that pilot programs to
scale nationally
3. Big Ideas:
•More active, organized
involvement in the advocacy
and policy arena
• Training Institutes
throughout the year for
chapter leaders and members
• Fiscal sponsorship via YNPN
National
•Group purchasing
opportunities
4. YNPN 3.0 is
about
strengthening
our network
infrastructure.
5. YNPN 3.0 is
about
deepening
relationships
across the
network.
6. YNPN 3.0 is
about better
access to the
network for a
broader range
of people.
8. Project #1: Developing
Shared Standards
Developing a set of shared standards will
allow us to name the essence of what it
means to be a chapter in our network
and determine what supports and
systems of accountability we’ll need to
uphold these standards.
9. Project #2: Creating a Data
Center
Together, we’ll come up with a system
for collecting and aggregating chapter
level data that will create a cohesive
story about YNPN, our chapters, our
membership, and our collective impact.
10. Project #3: Setting up
chapter input & decision-
making structures
This project will focus on creating a
system of feedback and joint decision
making for YNPN National and YNPN
chapters that will create a stronger
network that effectively engages the
talent and perspective of all leaders.
12. Feedback:
•Today – fill out the survey post-webinar
•July 10 - 20th = chapter reps and leaders
submit feedback (via YNPN 3.0 blog)
•July 27th - the proposals are revised
•August 4th - present at conference
13. Megrd
Ese e
Sheph
Shared Standar
ds
Charise
Trish
Data Center
rd Chapt
Kim
S hephe er Inp
u t/ D e
cision
s
14.
15.
16.
17.
18.
19.
20. Questions to think about:
•What has the 3.0/Congress process itself
been like for your chapter?
•What’s really excites you about what
you’re hearing?
•What concerns you about what you’re
hearing?
22. Data Center Survey Results
Goal: To understand chapter data management & collection
practices
Completed by 20 YNPN Chapters
Focused on three core areas:
28. Current Data Center Collection &
Practices
6. Who on the board collects & manages data?
29. Data Sharing Across Chapters,
National & Sector
7. Who should have access to the following types of data?
Collecting YNPN Other Partners upon
Chapter National Chapters Request
Name 100% 52.2% 21.7% 17.4%
Age 90.5% 100% 47.6% 66.7%
Race 94.7% 100% 47.4% 57.9%
Ethnicity 95% 100% 45% 55%
Gender 95.2% 100% 47.6% 47.6%
Profession 95.7% 95.7% 60.9% 65.2%
Issue area 95% 95% 55% 65%
Job function 95.5% 95.5% 50% 50%
Aspirations for being a
part of YNPN 95.5% 81.8% 40.9% 27.3%
Email Address 100% 36.4% 9.1% 9.1%
Twitter Handle 100% 30.0% 10% 10%
30. Data Sharing Across Chapters,
National & Sector
8. For what purposes should national be using data?
32. Next Steps
Form data working group to develop initiatives based on chapter feedback
from survey (Summer 2012)
Set priorities for:
Data collection & management best practices at chapter and national
level (Fall/Winter 2012)
Shared data management system and templates (Fall/Winter 2012)
Implement data collection & management structure for YNPN (2013)
34. TASKFORCE
• Review current network standards for
chapters and create a new slate of standards
for the network (July 2012)
• Understand key challenges and benchmarks
for each level - Novice, Emerging, Affiliate
• Revisions of first draft of new standards
completed by August 2012
35. NOVICE CHAPTERS
CHALLENGES OLD BENCHMARKS
- Board development (moving - 200 members on listserv
from a steering committee to a
formalized board)
- 3 programming events by end
of first year in operation
- Membership
recruitment/retention
- 1 person from leadership
team attend Leaders
- Securing space for events/board Conference
meetings
36. EMERGING CHAPTERS
CHALLENGES OLD BENCHMARKS
- Membership - 400 members on listserv
recruitment/retention
- Cycled through one board
- Board development recruitment process
- Strategic planning - Fiscal/strategic planning
process for chapter
- Paid membership
discussions/processes - 3 yrs old
37. AFFILIATE CHAPTERS
CHALLENGES OLD BENCHMARKS
- 501c3 status - 800 members on listserv
- Securing position as a leader/ - Cycled through 2 board
go-to organization in recruitment process
community
- Host Leaders Conference
- Fiduciary responsibilities
- Annual membership drive
38.
39. NOVICE/SPRING CHAPTERS
• Board of Directors
o range from 4 - 20 people
o Chair, Co-Chair (optional), Treasurer (optional), Secretary
• By-laws for chapter
• A clear mission statement
o a clear target audience (nonprofit professionals)
o a vision statement is optional and up to each chapter to decide on
• 4 events per year (broken down into quarters)
• A defined membership list/communication channel to communicate with members
o member profile
• A virtual home for the chapter (online presence)
o LinkedIn
o Twitter
o Facebook Group
o Website
• A logo for chapter
40. EMERGING CHAPTERS
• Age requirement (3 - 5 yrs) - for sustainability
• Sustainability plan
o
range from 1 - 5 years
o
sponsorship/partnership
o
format can be flexible
• Engaged Membership
o
paid and non-paid breakdown
• A signature annual event
41. ESTABLISHED/AFFILIATE CHAPTERS
• Settled on fiscal sponsor/501c3 status for chapter
• A robust fiscal/budgetary process/template
o
budgets (actual, programming)
o
over a specific timeframe
o
chapter bank account
• 5+ years
• Formalized board and alumni board roles
• Professional programming slate
43. YNPN CHAPTERS
• Annual report chapter
• Mentor another
o availability/capacity
o 1-to-1 mentor model or
o case studies/stories
• Partner of chapter org that is invested in the success and
growth
with 1 local
o within 1 year of operation
• Innovative spirit to nonprofit sector
o commitment
• National liaison contact
44. PROCESS FOR GRADUATING TO NEW
LEVEL
1. Review of chapters done annually, at the end of the calendar
year
2. YNPN Chapters committee responsible for implementing review
process
a. Review template
b. Grading scale (i.e. point system?)
3. Disputes of chapter level will be taken to Chapter Congress
4. Chapters can slide up and down the levels scale depending on
performance
5. Announcement of new chapter level/grade published to listserv
and on National's website
45. PROPOSED IMPLEMENTATION TIMELINE
- July 2012: Proposal submitted to YNPN (Chapter Congress),
edits/comments to proposal documented
- August 2012: Proposal revision discussed at YNPN Leaders
Conference and final proposal adopted
o Every chapter must vote to approve new standards
o Majority wins; challenges/concerns from dissenting chapters taken into
consideration
- September - November 2012: Chapters re-assigned to new
levels, YNPN Chapters develop review template
- January 2013: New shared standards in place and operational
• Review of new standards done December 2013
47. The Congress
• Decision-making body comprised of
representatives from Affiliate, Emerging and
Novice Chapters
• Purpose to propose, discuss and vote on
issues related to the network
• Provides greater connectivity and replaces
chapter liaisons
48. Membership
Chapter Congress
Start-up
Affiliate, Emerging, Novice Chapters Chapters
• Every Chapter has one delegate/one vote
• Start up chapters invited to attend, but not
voting members
• Delegates selected by chapters to serve one
year terms; no term limits
49. Meetings
• Meet twice each quarter
• Proposals can not be introduced and voted on
in the same meeting to allow time for
delegate to seek chapter input
50. Topics for Congress
• Can discuss any number of concerns or opportunities
• For each topic below, the Congress makes the corresponding
type of decisions
Topic Approach
Connection between National and Chapters Centralized
Funding Decentralized
Membership Models Collaborative
Board Structure Collaborative
Advocacy Collaborative
Communication Collaborative
Partnership Collaborative
51. Proposed Timeline
• July 2012: Proposal submitted to YNPN 3.0
working group and thus, the network
• August 2012: Proposal revised discussed at YNPN
Congress
• September 2012: Vote called network wide on
the proposal
• October – December 2012: Further details
discussed by chapter delegates
• January 2013: First Chapter Congress convenes
52. Adoption Process
• A majority of chapters must adopt the
proposal (method for adoption at their
discretion)
• If passed, all chapters must delegate
representative
53. Review Process
• Chapter Congress and National Board check-in
on progress and make adjustments in June,
2013
54. What has the process itself been
like for your chapter?
55. Of everything we just talked
about, what’s one thing that
really excites you?
56. Of everything we just talked
about, what’s one thing that
really concerns you?
YNPN 3.0 is about getting us to the place where we can actually take on those big ideas.
What are your chapters saying? Which are you most excited about?
I’ve been doing a little bit of travelling for the past few months and ever chapter that I met with, I would say to them, “we’re going to put the call out for chapter leaders to join these task forces that are going to develop systems and protocol that we’ll want chapters to adopt, what would that process need to look like in order for you to feel as though you had input along the way and could make an informed decision about whether or not to adopt a proposal when it was set up.” We heard time and time again that you needed representation right from the beginning. So the best way that we could think to do this was with a chapter congress. We’re calling it beta because one of the actual projects that the congress will take on is figuring out what a more permanent decision for chapter input and decision making should be, but we think this is a good structure to get us going. (Even in the most decentralized processes, there has to be a process for figuring out the process. This is that process.) For those of you who haven’t had a chance to go to the rep submission form, there’s a place there where reps can talk about what interests them about the chapter congress. The responses are all a bit different but there are definitely two themes emerging and they’re right on - 1) people see that YNPN as a national network is on the cusp of big things and they want to be a part of it, 2) Their chapter has put in place some really solid programs, structures or even principles and they want to share that with the network. That’s what’s so great about this chapter congress - it’s this perfect reflection of how our model has played out nationally - we create a basic structure for people to connect with and they - all of you - will bring ideas and skills far greater than anything we could have come up with on our own. Also, to be clear - there’s actual work to be done. The whole point of this is that we need to come up with actual systems that will be implemented and we need not only the ideas but the capacity you bring to develop those proposals. So we structured the chapter congress with that in mind
Other tools used include: Google Docs Google survey Old listserv iMods
Mini annual report concerns around sharing data across national and with partners; privacy and security concerns
3 Images: 1) Map with spots in CA, DC, NY, Denver, Chicago; 2) Map with more spots + dotted lines; 3) Map with more spots solid lines Talking points: Start with housekeeping Really important to mute yourselves in the meantime Also want to let you know that this conversation’s going to start pretty big picture but I promise you, we’ll get to the details, so just hang in there. Along the way, you can use your chat box on the right there to let us know when you want to know more about something or even if you’re really excited by something you here. If we’re not able to address it on this call, at least we’ll have it captured so we can follow up with you. Want to start by thanking all of you for giving me the opportunity to serve in this position First I want to thank the YNPN National board I also want you to know that we hear you re: the basic tools you need to run your chapters I see it on the list serv and When all of you RSVP’d, several of you asked about really important, really practical things that you need to run your chapter day to day – are we looking at a shared content management system, are we planning to revisit a shared 501c3 structure. More than likely this conversation won’t reach that level of detail but we will be responding to those questions that came up via the blog so that not only will we be responding to the particular folks who raised those questions but everyone can be aware of our plans in those areas.