PROJECT • 2025

ClassCollab — Compatibility-Based Team Formation

ClassCollab hero
Role
UX Research, UX/UI Design
Skills
Secondary Research, Prototyping, Validation
Context
8 weeks • Solo
Focus
Team formation & fit
PROJECT INTRO

Forming compatible student teams for better outcomes

Students often struggle with mismatched project teams, which leads to unclear goals, uneven workloads, and poor collaboration. This project tackled that by creating a smarter team formation process that matches students based on shared goals, working styles, and availability—while supporting stronger course outcomes for instructors and institutions.

Using Lean UX, I ran secondary research, built rapid prototypes, and validated ideas with users over multiple iterations to maximize both user outcomes and business value.

BUSINESS PROBLEM

Starting a team project can feel like a gamble

Teams are often assigned randomly or chosen by social ties. Instructors lack time and data to form balanced groups, and existing tools overlook compatibility in collaboration preferences and goals—producing friction, unclear expectations, and uneven work.

BUSINESS OUTCOMES

Higher course satisfaction and improved academic outcomes

The goal is better collaboration and stronger project outcomes—raising course satisfaction, long-term program reputation, and retention. Success indicators include higher team satisfaction, balanced workload distribution, improved outcomes, and fewer team-change requests.

SOLUTION

A transparent process for compatibility-based team formation

The platform matches students by goals, skills, collaboration styles, and role preferences. It’s grounded in user needs and class context to improve fairness, clarity, and learning outcomes.

DISCOVER

Literature review: team formation overlooks compatibility and balance

Academic literature showed that compatibility—collaboration preferences, goals, and availability—drives satisfaction and outcomes. Early alignment on mindset (not just skills) informed the onboarding inputs.

Letting students freely choose teammates can cause poor matches. Balanced skills reduce friction and improve collaboration. — Lopez et al., 2021
Current formation relies too much on chance; using goals, strengths, and availability can automate better matches. — Lopez et al., 2021
Group strategies should consider skills, goals, and personality; availability and style influence cohesion. — Odo et al., 2019
DEFINE

Proto-personas & opportunity framing

I created two proto-personas—Alex (CS undergrad) and Rachel (CogSci grad). Both experienced mismatched teams, unclear expectations, and uneven workloads. Alex wants strong portfolio projects; Rachel seeks meaningful research partnerships.

Persona: Rachel
Persona: Alex
DEFINE

Business Opportunity Statement

😕
Current State

The status quo relies on instructor assignments or self-selection, rarely considering goals, styles, availability, or work preferences.

🔍
Gap

Products like CATME don’t provide a balanced, transparent process matching interpersonal fit and project goals.

Solution

Help students form better-matched teams with fair collaboration, clear roles, and stronger outcomes.

🎯 Focus

Higher-ed students in project-based courses.

🏆 Success

Better-matched teams, smoother teamwork, stronger results.

VALIDATION PLAN

Pirate Metrics → Outcome-to-Impact

I first used Pirate Metrics to validate the MVP necessity (focusing on acquisition), then layered in Outcome-to-Impact Mapping after observing retention/usage to connect student outcomes to institutional value.

StageWhat I’m MeasuringWhat I’m Trying to LearnHow I Might MeasureSuccess Criteria
🧲 AcquisitionInterest & willingness to tryDo students see value?Landing page with CTA≥ 30% click CTA
✅ ActivationExperienced valueAre teams satisfying?Post-match survey≥ 70% satisfied at week 1
🔒 RetentionStick with team & use systemIs engagement sustained?Peer-review checkpoints≥ 80% teams unchanged
💰 RevenueHigher course evaluationsDo outcomes improve?Compare to past cohortsAvg. score +10%
🔁 ReferralWillingness to reuseDo students want it again?NPS / end-of-course survey≥ 60% would reuse
IDEATE

How might we help students find compatible teammates?

I ran a design studio exercise (6-up) to quickly explore options, then mapped features to user and business outcomes to prioritize.

Design studio exercise
Rapid exploration to widen the solution space.
IDEATE

Hypothesis Mapping

Mapped each feature to a concrete user and business outcome to ensure everything we built had a reason to exist.

Business outcomePersonaUser outcomeFeature
Higher course evals & performanceAlex & RachelJoin a group with shared goalsOnboarding survey + past projects
Improved institutional outcomesAlex & RachelEnjoy group experience & learningPrompt-based grouping
Higher placement ratesAlex & RachelWork aligned to strengthsInterest-based channels
Higher retention & experienceAlex & RachelClear expectations up frontCourse-embedded analysis
Hypothesis prioritization canvas
Prioritizing for value vs. risk to pick the MVP.
IDEATE

Prioritized hypothesis & risky assumptions

Evaluated two candidates against value and risk to decide what to build first.

Hypothesis 1Selected

Higher team satisfaction via onboarding + past project compatibility

Value
High
Risk
Low
Rationale
Uses existing data sources
Hypothesis 2

Stronger performance via prompt-based grouping

Value
High
Risk
High
Rationale
Needs evidence of academic lift
Prioritized hypothesis

We believe we can achieve higher course evaluations and stronger program performance through well-formed teams if students join groups with shared goals and interests, supported by compatibility data from past projects and an onboarding survey.

Risky assumptions

What the prioritized hypothesis depends on being true.

  • Students care about being matched with compatible teammates.
  • Students will complete onboarding.
  • Compatibility (goals, projects, skills) drives satisfaction.
  • Past performance predicts future team fit.
  • Students trust the process.
PROTOTYPING

MVP development & walkthrough

The landing page validated interest but didn’t communicate how it works. I built a clickable prototype to demonstrate onboarding and matching, and to validate the assumption that students would complete the flow.

Design rationale

  1. Onboarding content grounded in insights: questions about goals, collaboration style, and roles reflect literature + survey feedback.
  2. Clearer concept communication: participants needed more context—prototype made value tangible.
  3. No prior tool familiarity required: flow is simple and self-explanatory.
TEST

Unmoderated online testing

Participants

Seven graduate students with recent team-based coursework (CS/Product Design).

Objectives

Move beyond concept interest to assess whether users understand and engage with the value, flow, and functionality: complete onboarding, understand matching, and feel confident joining a group.

Risky assumption under test

Students are willing and able to complete onboarding.

Research questions

  • Do users understand the purpose/value of onboarding?
  • Is joining a group clear and satisfying?
  • Does the team overview reduce uncertainty?

Tasks

  1. Complete onboarding (goals, collaboration style, roles, availability).
  2. Choose a recommended group.
  3. Explore the team overview and reflect on readiness.
RESULTS

Results & next steps

13
unique visitors
8
unique clicks
60%
CTR

Key takeaways

  1. All participants completed onboarding. SUS averaged 82.5 → flow is intuitive and supports the assumption that students will complete it.
  2. Students want insight into teammate working style & communication. Added scenario-based questions (SJT-inspired) to capture behavior/ethic without lengthening the form.
  3. Students want more context before joining. Added a team preview (goals, roles, availability) with privacy-safe details to support confident selection.
ITERATIONS

Two major iterations

Scenario-based questions → richer insights, fewer steps

Replaced two direct questions with one scenario prompt to capture work ethic, communication, and personality— informed by SJT research—to keep the flow lightweight.

Iteration: scenario-based questions

Show member details earlier → more confident selection

Surfacing teammate info (goals, roles, availability) prior to joining improved confidence and reduced uncertainty.

Iteration: early member details
REFLECTION

Reflection & what I’d do next

Quick-and-dirty, then iterate

Small, testable steps (LP → prototype → unmoderated tests) let me validate assumptions early and shape the solution to what students actually need.

Business POV

I framed decisions to maximize both user value and institutional outcomes—so the work ties to satisfaction, retention, and performance.

Future work

Run another usability round on the changes, then validate the assumption that compatibility (goals, past projects, skills) increases satisfaction over time.