Case study · Education data + public systems

Student belonging: from survey data to district insight.

At DCPS, I worked with Panorama survey data and the people planning school culture programs. My role connected analysis with Culture Institute support and student-adult leadership.

DCPS Central OfficePanorama survey dataSummer 2025Public overview

Belonging is a lived experience and a system signal.

District survey data can surface patterns that individual anecdotes cannot, but the numbers still need context. The work connected Panorama survey analysis with conversations about culture, equity, student voice, and how adults and students share responsibility for school climate.

Education Data & Innovation Intern, DCPS Central Office.

I analyzed Panorama survey data, supported Culture Institute design and logistics, and helped develop shared student-adult leadership structures with the district team.

Analysis was one part of a larger decision process.

More than thirty thousand survey responses move through analysis of belonging and culture patterns into stakeholder planning contextEnlarge image
Public evidence mapAn overview of my workflow, prepared for this portfolio. District findings remain confidential.

Move carefully from response to recommendation.

A survey number only becomes useful once someone can trace it back to a real planning question, which meant working through four stages before anything reached a stakeholder.

Frame

Start with the planning question

Clarify which belonging and culture decisions the analysis should help stakeholders discuss.

Analyze

Look for patterns, not isolated numbers

Review survey results for themes and differences that warrant closer contextual interpretation.

Interpret

Connect data with student experience

Use student voice and human-centered thinking to keep meaning attached to the metrics.

Support

Translate into findings people can use

Help make the evidence usable in Culture Institute and shared-leadership conversations.

The value was analytical and relational.

Reading the data well was half the job; the other half was making sure it reached people in a form they could actually use.

Pattern recognition

Used survey evidence to surface belonging themes relevant to district planning.

Data storytelling

Translated analysis into language that could support conversation outside an analytics team.

Program support

Contributed to Culture Institute design and logistics alongside the analytical work.

Shared leadership

Supported structures intended to strengthen collaboration between students and adults.

What I can share.

  • This overview shares my role and method. Student information, school-level findings, internal dashboards, and district recommendations remain private.
  • The 30K+ response count describes the scale of the survey work, not a survey I independently designed or administered.

A durable interest in public-sector decision support.

I left DCPS more interested in what happens after an analysis is finished: who reads it, what they need to decide, and whether students recognize their own experiences in the conversation.