1 / 15

Lessons Learned from the RI DataHUB Data Story Process The Good, the Bad, and the Ugly

Learn about the process of creating a Data Story with a large cross-sector team, the benefits, challenges, and valuable insights gained. Understand the importance of stakeholder engagement and iterative data exploration to produce impactful stories.

benglish
Download Presentation

Lessons Learned from the RI DataHUB Data Story Process The Good, the Bad, and the Ugly

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lessons Learned from the RI DataHUB Data Story ProcessThe Good, the Bad, and the Ugly Rebecca LeeOctober 2014 @ ProvPlan

  2. What is a RI DataHUB “Data Story”? A PRODUCT….CREATED FROM A TEAM PROCESS

  3. Data Story Team • Team Leader • Facilitator • Data Analysts • Copywriter • Graphic Designer • Key Stakeholders: • Reps from Data Partners • Content Experts • Program Directors • Community Partners • Etc. TEAM CAN BE LARGE OR SMALL, DEPENDING ON GOALS. TIMING OF ENGAGEMENT MAY VARY.

  4. Why Stakeholders? • Gain expertise and context • Increase data literacy • Create shared understanding • Cultivate ambassadors for story • Built-in user testing • Make new friends!

  5. Typical Large Team Process FIRST, A FUNDER/CONVENER IDENTIFIES A TOPIC. Unhealthy Housing Juvenile Justice Out-of-School Time Workforce Development Postsecondary Access Educational Transitions Chronic Absenteeism Civic Engagement Adult Education

  6. Convene a Cross-Sector Team Higher Ed. Community Partners K-12 Work-force Group Diversity Considerations: • Content expertise • Comfort with data • Prior experience • Logistics • Politics

  7. The Team Picks an “Essential Question” • BE CLEAR THIS IS A DRAFT! • MANAGE EXPECTATIONS. • OK TO START BROAD, NARROW LATER.

  8. Explore Data Together, Write Story Explore data. Refine essential question. Write story. This is ITERATIVE and will take TIME.

  9. Vet Story. Expand Stakeholders. Timing depends on what you’re willing to change.

  10. Publish and Disseminate. Plan for rollout while the team is still captive.

  11. Some Lessons Learned. • Facilitators are really helpful. • Data exploration with novices is hard. • Consistent participation is key. • Adjust use of collaboration tools according to team skills.

  12. The Good. “I Learned a lot about education policy and how administration works” “What data we have/don’t have is surprising!” “Not everyone sees things the same way. Dropouts to K-12 are new entrants to workforce to DLT.” This process made clear the need to understand each other across agencies – more of this! ‘Kids are all of ours’” “I was surprised how hard it can be to represent data in graphics.” “I learned about the data and the process around it; learned to trust”

  13. The Bad and the Ugly. • Expensive! • Too long to be “timely”. • Not all questions are fit for stories. • Building data literacy is hard.

  14. Summary Creating “Data Stories” with a large cross-sector team can be a really effective way to build relationships, break down barriers, increase capacity, and produce a better product. However, they cost lots of time and money, so being clear about the goals for the story is essential.

  15. Thank You! http://www.ridatahub.org

More Related