Research

Every feature begins with listening.

SchoolBoardHQ is being built on published, peer-reviewed research about school board service — not just our own assumptions. Before we ran a single survey of our own, we read what the academic literature already says about board governance, technology use, training, and public trust.

This page is that literature, cited honestly — including the two areas where almost no one has studied school boards specifically yet.

Take the Interest Survey

Vote on Product Ideas

Our Research Philosophy

We don't assume. We ask.

Listen First

We begin by understanding the challenges, priorities, and experiences of school board members before proposing solutions.

Validate Assumptions

Ideas are tested through surveys, interviews, and product feedback before significant development investments are made.

Build Transparently

Whenever possible, we share what we are learning, how decisions are being made, and what remains uncertain.

Improve Continuously

Research continues after launch to ensure the platform evolves alongside the changing needs of public education governance.

What We Already Know

The literature already answers some of this.

Before launching studies of our own, we reviewed the existing peer-reviewed and academic research on school board governance. Four domains turned up real, checkable evidence. Two did not — and we're not going to pretend otherwise.

Research Methods

From conversation to continuous improvement.

Each stage in our research process is designed to answer specific questions. Together they form a pipeline that moves from deep understanding to validated product decisions.

1
Interviews
One-on-one conversations with school board members to understand daily experiences, challenges, and priorities in depth.
Question answered:
What does board service actually feel like, and which problems are most urgent?
2
Surveys
Structured questionnaires distributed to board members across the country to identify patterns and validate hypotheses at scale.
Question answered:
How widespread are specific challenges, and what do board members across different contexts prioritize?
3
Feature Validation
Direct input from board members on specific product ideas, prototypes, and feature concepts before development begins.
Question answered:
Which proposed solutions are most valuable, and which assumptions are incorrect?
4
Prototype Testing
Structured evaluation of early product versions with a small group of participants to identify usability issues and improvement opportunities.
Question answered:
Does this work as intended in a real board service context, and what needs to change?
5
Beta Programs
Expanded access to new features and tools for a trusted cohort of board members who provide ongoing feedback during development.
Question answered:
How does this perform across different board sizes, contexts, and geographies?
6
Usage Analytics
Identifiable product analytics are product events linked to an account identifier in Supabase or a PostHog distinct ID when PostHog capture is enabled, so we can understand feature usage, verification state, and feature-flag cohorts. We use aggregate statistics and de-identified reporting to inform future improvements without publishing individual account activity. Internal Supabase product analytics are on for authenticated users. Third-party analytics and pixels require the runtime enable flag plus an analytics-consent grant; Global Privacy Control on web overrides any prior grant for consent-gated tracking.
Question answered:
Where do board members spend their time, and where do they encounter difficulty?
7
Continuous Improvement
An ongoing cycle of feedback, iteration, and evaluation that persists long after initial launch to ensure the platform evolves appropriately.
Question answered:
As governance evolves and board member needs change, how should the platform adapt?

Literature Review Snapshot

What a real review turned up.

These numbers describe the national literature-review pass, not a participant panel. Washington-specific findings are presented separately in the domain evidence. Direct interviews and surveys with board members haven't started yet.

Sources reviewed

Claims extracted

Claims checked

Claims confirmed

Claims rejected

Domains flagged as gaps

What the literature says, cited

These findings come from published, peer-reviewed studies — not from SchoolBoardHQ's own board-member research. Percentages from our own research stay offline until sample sizes and methodology are ready to publish.

"Board-superintendent relationships fall into four recurring patterns — role contestation, confusion, collaboration, and dependence."

Sutherland, 2023, Educational Administration Quarterly

"Trustees rely on online news and research articles roughly twice as much as social media when making decisions."

Kay & Carruthers, 2017, Canadian Journal of Learning and Technology

"More participatory, deliberative school board meetings increase public trust and willingness to attend future meetings."

Collins, 2021, American Political Science Review

What We Study

Six domains. One purpose.

Our research spans the full context of school board service, not just the software that supports it. Each domain below is tagged with what the literature review actually found.

Governance

Decision-making processes, board effectiveness, meeting preparation, strategic planning, and policy oversight.

8 sources

Technology

Current tools, workflow challenges, interoperability, and opportunities for improvement in how boards use technology.

1 study

Community

Peer connection, mentorship, collaboration, and knowledge sharing among board members across districts.

Research gap

Trust, transparency, responsible use, governance implications, and practical applications that support rather than replace human judgment.

Research gap

Professional Development

Learning needs across different stages of board service, from newly elected members to experienced board leaders.

1 study

Public Trust

Transparency, ethics, communication, public engagement, and accountability in local governance.

2 studies

How We Protect Participants

Research built on trust.

Participation in our research is voluntary and protected. We take seriously the responsibility that comes with collecting feedback from public servants.

Privacy

Survey responses are stored securely and never sold or shared with third parties. Identifying information — such as name and district — is only collected when you explicitly provide it and is never required for participation.

Anonymous research participation is supported when a form does not request contact details. Product analytics are different: Identifiable product analytics are product events linked to an account identifier in Supabase or a PostHog distinct ID when PostHog capture is enabled, so we can understand feature usage, verification state, and feature-flag cohorts.

When we share findings, we use de-identified reporting or aggregate statistics, never individual responses. Internal Supabase product analytics are on for authenticated users. Third-party analytics and pixels require the runtime enable flag plus an analytics-consent grant; Global Privacy Control on web overrides any prior grant for consent-gated tracking. Identifiable product analytics follow the account-deletion and de-identification workflow; aggregate statistics that no longer identify a person or account may be retained indefinitely. Participants may withdraw from research at any time without consequence.

Research Integrity

We are committed to accurately representing what participants tell us. Findings are not selectively interpreted to support predetermined narratives. When data is ambiguous or sample sizes are too small to draw conclusions, we say so.

Participant feedback guides decisions — it does not simply validate them. Where research contradicts an assumption we held, we update the direction of the platform accordingly.

Analytics language used across policies

Identifiable product analytics

Identifiable product analytics are product events linked to an account identifier in Supabase or a PostHog distinct ID when PostHog capture is enabled, so we can understand feature usage, verification state, and feature-flag cohorts.

De-identified reporting

De-identified reporting removes direct identifiers before analysis or publication, but is not described as anonymous unless re-identification is no longer reasonably possible.

Aggregate statistics

Aggregate statistics combine many responses or events into group-level counts, rates, or trends and are published only when they cannot identify an individual participant or account.

Looking Ahead

Each stage informed by the last.

No stage is locked in. Each phase is informed by new evidence and participant feedback from the previous one. The pace is determined by what we learn, not by a fixed schedule.

Research
Understanding the landscape through surveys, interviews, and ongoing listening.
Validation
Testing ideas with school board members before committing to development.
Prototype
Building and refining early versions based on validated concepts.
State Beta
Current Phase
Washington State Beta — verified peers connecting across districts.
Pilot Programs
Expanding access to additional states and governance contexts.
Regional Expansion
Scaling the platform as research insights guide growth.
National Community
A connected community of school board members across every state.

Help shape the future of school board governance.

Whether you are a current board member, superintendent, governance professional, or education organization, your perspective can help ensure the platform reflects the realities of board service.

Take the Interest Survey

Vote on Product Ideas

Join the Research Community

Every feature begins with listening.

This page is that literature, cited honestly — including the two areas where almost no one has studied school boards specifically yet.