ProjectBridge

ProjectBridge is a platform design for project-based learning at community colleges. It grew out of the same institutional experience that motivates the research: watching students struggle to find meaningful project opportunities, build teams across disciplines, and document work in ways that translate to portfolios and careers.

The original prototype (StemBridge) was built for Foothill College. I conducted a full product evaluation and redesign, producing a strategy document that covers platform architecture, data models, accountability systems, AI integration, faculty adoption, and a phased scaling strategy from one classroom to a multi-college network.

What the redesign demonstrates

Systems thinking grounded in research. The accountability features (weekly check-ins, milestone tracking, the 30-Day Pulse Check) are designed around what the help-seeking and persistence literature suggests works: gentle positive pressure, visible progress, and normalized iteration. The "Build Journal" feature is directly inspired by the portfolio evidence model that P1 and P3 aim to validate.

Data modeling for learning analytics. The redesign includes complete PostgreSQL data models for users, projects, milestones, updates, collaborator requests, and wanted ads — each designed to capture the kinds of behavioral signals (update frequency, team composition, milestone completion patterns) that the learning analytics work in P1 could eventually analyze.

Equity-centered design. The platform integrates directly with existing learning communities (MESA, Puente, Umoja, ETI) rather than creating a separate silo. The "Collaborator Marketplace" is designed to surface cross-disciplinary connections — the same structural bridges that the research argues are systematically undersupplied at community colleges.

Scaling strategy. The phased approach — one classroom, one college, multi-college, platform network — mirrors the research strategy of establishing findings locally before generalizing. Each phase has specific success metrics tied to the platform's equity goals.

Key design artifacts

The full redesign document includes: candid evaluation of the original prototype (five dimensions, rated honestly), proposed product vision and design principles, complete page architecture (12 pages, each mapped to a user need), six data models with field-level specifications, accountability feature designs, AI integration strategy (using the Anthropic API, starting with low-risk documentation tools), faculty adoption playbook, and a 20-week phased product roadmap.


Connection to the Research

ProjectBridge is not a research project, but it is deeply informed by the research program. The accountability features operationalize ideas from the persistence literature. The data models are designed to capture signals the learning analytics work would analyze. The faculty adoption strategy reflects what the qualitative research on institutional change suggests about how educational tools actually get used.

Including this work here serves a specific purpose: it demonstrates that the research agenda isn't purely theoretical. The structural equity questions I'm studying have direct implications for how we design educational tools, and I'm interested in closing that loop — using research to inform design, and using design contexts to generate research questions.

Last updated: April 2026