# data[].attributes.body
would like to see more plug and play. . .here is the formula. . . we have relationships here. . .etc.
Powerful and thoughtful feedback.: "roundtables perpetuate the old power dynamic and stifle the new model of funding that includes respect and conversation." I am hearing this sentiment more and more. This should be evaluated and looked into for redesign.

# data[].attributes.body
Time. Perhaps lack of the bigger picture around how this is so important for regional not-for-profits and how they impact the community. More visibility on individual growth opportunities--training, new knowledge.

# data[].attributes.body
Although each region is part of a state-wide effort, the key for me is that we are in our region and we must make it work for us.

# data[].attributes.headline
The survey questions are very broad, and do not separate the various aspects of the event. So, respondents are answering based on a specific aspect of the event, or overall, but we really don't know what they are responding on specifically.

# data[].attributes.subject
The survey questions are very broad, and do not separate the various aspects of the event. So, respondents are answering based on a specific aspect of the event, or overall, but we really don't know what they are responding on specifically.

# data[].attributes.body
I'm wondering if people read the question and in stead of seeing "flexibility" and "structure" as broad subjects, they are skipping directly to roundtables and whether or not they should be a staple component of the event

# data[].attributes.body
People might be associating this specifically with Roundtables, or specific aspects of the conference. Not specific to different elements.

# data[].attributes.headline
I think it's a difference between Content and Structure. Local steering committee should have flexibility to design the content based on regional uniqueness and needs, but rely on CRC to put together the Structure of, for example, the workshops organization...

# data[].attributes.subject
I think it's a difference between Content and Structure. Local steering committee should have flexibility to design the content based on regional uniqueness and needs, but rely on CRC to put together the Structure of, for example, the workshops organization...

# data[].attributes.body
State-wide RPD Conference

# data[].attributes.body
Explaining the rationale for the different components/structure and why it is recommended as an activity for the conference, and then giving the steering committee flexibility to decide if the activity and rationale applies to their region.

# data[].attributes.body
logo for each area. Instead of spending so much time creating one for each event

# data[].attributes.body
Host community should be figured out further in advance than one year and specific expectations of the host community and their participation on the steering committee that will make the event more successful.

# data[].attributes.body
Give Steering Committee option for 100% out-of-the box conference or 75% same/25% new elements. Based on the make up the committee, they need to decide what they have the energy/time to execute.

# data[].attributes.body
Time and distance. Virtual participation can help this.

# data[].attributes.body
Time.  Being on eh committee is time consuming.

# data[].attributes.body
When you're not in the host community, understanding the what's in it for me can be hard for potential committee members

# data[].attributes.body
Most committee members are one person (or less) shops. No time to devote days to it. Some roles are SIGNIFICANTLY larger than others.

# data[].attributes.body
I think the flexibility comes from the issues of individual regions. The statewide aspect is from the structure and sharing between conferences.

# data[].attributes.body
Ask each Steering Committee "what makes this region unique" and see if that can built into an additional/new element

# data[].attributes.body
Could this be that people were answering based on the current idea/understanding of RPD and not from a place of some of the changes that could be incorporated?

# data[].attributes.body
Start with reviewing feedback from previous conference and apply feedback to see if there were weak points that could be improved/ditched

# data[].attributes.body
I think the challenge/opportunity here is about the feeling of having to reinvent the wheel. Build on past success and structures.

# data[].attributes.headline
I believe the flexibility has been great because we get to structure the event the way want to.  It just becomes a lot of work.  Finding a medium. 

# data[].attributes.subject
I believe the flexibility has been great because we get to structure the event the way want to.  It just becomes a lot of work.  Finding a medium. 

# data[].attributes.body
Setting guidelines or goals for success of the conference. Understanding that the conference is a combination of workshops, networking and keynotes.

# data[].attributes.body
Steering Committees like not having a blank slate for a conference, because of limited time and resources to do something BRAND new

# data[].attributes.headline
A template with flexibility to add the local flavor.

# data[].attributes.subject
A template with flexibility to add the local flavor.

# data[].attributes.body
provide a framework for making it work for our community--we're not all the same.

# data[].attributes.headline
Having a framework for the conference is more efficient.  Not having to re-invent the wheel.  It is also good to have the consistency all around the state and I am sure it makes it easier for CRC to administer.

# data[].attributes.subject
Having a framework for the conference is more efficient.  Not having to re-invent the wheel.  It is also good to have the consistency all around the state and I am sure it makes it easier for CRC to administer.

# data[].attributes.body
Each region, however, is different and there may become different dynamics that should be honored.

# data[].attributes.body
I'm surprised. Perhaps many more structure? Want to draw on others' experience?

I wonder what funders feel about this? Do they want more common structure?

# data[].attributes.body
Maybe people who favor limited flexibility were not as experienced with RPD.  But then when addressing local issues, they really wanted more flexibility?