Group Flow - Rethinking fairness in group projects
Group projects don't fail because of lazy students. They fail because teams can't coordinate. GroupFlow is a research-driven collaboration platform that fixes that.
The silence between teammates was the real problem.
In every classroom, the same story played out one student carrying the weight, another disappearing into silence, and a third trying to hold the team together while balancing their own deadlines, jobs, and stress.
My initial assumption: free-riding was the cause. What research revealed: unequal contributions are almost always accidental caused by poor coordination, not laziness.
WHY THIS HAPPENED - 6 ROOT CAUSES
Hard to Align Schedules
One Person Does More Work
Delays in Decision-Making
Teammates Didn't Follow Through
Unclear Roles
Efforts & Quality Were Uneven
The Scale of the Problem
68%
of students reported scheduling conflicts as a core issue
58%
experienced unfair workload splits
83%
said roles were never clearly defined
81%
said grades didn't reflect their actual effort
Asana, Slack, and Notion solve task management. None of them address fairness, contribution visibility, or academic-specific accountability the things that actually break group projects.
02 Research
38 surveys. 12 interviews.
One problem tree that changed everything.
I conducted in-depth interviews with business and management students across multiple courses. Each session was 30–40 minutes, moderated, recorded, and synthesized through affinity mapping, a high-frequency matrix, and a 5-Whys root cause analysis.
"We usually just split the slides and hope everyone finishes their part."
65% of participants cited scheduling as their biggest challenge. Different jobs, classes, and time zones make coordination nearly impossible.
"It's not that people don't want to help — we just can't find a time."
Without contribution visibility, under-performing teammates go unnoticed until the final deadline — when it's too late to fix.
"You only realize someone didn't do anything when it's too late."
Instructors assess group work without visibility into who contributed what — systematically rewarding and penalizing the wrong students.
"Professors assume everyone worked equally."
32 of 38
students felt frustration with contributions
24 of 38
students reported unclear roles
19 of 38
experienced communication gap
When the direction changed
My initial instinct was to design a system that would monitor and report student contributions — a kind of "performance dashboard." But testing revealed this felt punitive and surveillance-like, which created more anxiety than it solved.
The pivot was significant: instead of designing a tool to expose laziness, I reframed the challenge around supporting structure before the problem occurs — helping teams set themselves up for success, not catching failures after the fact.
BEFORE PIVOT
"How might we prevent free riders in group projects?"
AFTER PIVOT
"How might we improve coordination and scheduling so contributions become more balanced naturally?"
Key insight from pivot: Students don't need surveillance — they need scaffolding. The best intervention is one that makes good behavior the default, not the exception.
Four principles that kept every sign decision honest.
Transperacy
Make contributions visible without making people feel watched. Visibility enables natural accountability.
Coordination First
Help teams organize early. The root problem is structural, not motivational.
Low Friction
Must feel lighter than a Jira board, or students won't use it. Simplicity is the feature.
Fairness without Surveillance
Accountability should emerge from clarity never from monitoring or punishment.
GroupFlow - Where Asana ends, fairness begins.
A collaboration platform that gives student teams the structure they need — and gives professors the visibility they've never had.
AI-POWERED
The right person for the right task - suggested, not forced.
Skill - Based Onboarding + Role Suggestion
Students enter skills, work style, and availability during onboarding. GroupFlow's AI analyzes this to suggest balanced role assignments but students retain full agency to adjust. The system supports decisions; it doesn't make them.
FOR PROFESSORS
Grades what actually happened
Instructor Dashboard
Professors see contribution levels, flagged issues, and team dynamics alongside final submissions — so grading reflects reality instead of assuming equal effort across the board.
View prototype
06 Usability Testing
5 participants. 4 tasks. 3 real issues found and fixed before launch.
Moderated usability tests with business and management students who regularly work on group projects. Each session was 25–30 minutes with think-aloud protocol.
98.5%
Task Success Rate
97%
Avg Confidence Score
96%
Avg Ease Score
88%
NPS Score
ISSUE 01 : HIGH SEVERITY
Onboarding felt too long students wanted an exit
4 out of 5 participants said the onboarding process was exhausting, especially during busy academic periods. No way to skip non-essential steps.
Fix: Added "Skip for now" option. Broke flow into lighter, digestible steps. Reduced cognitive load with simplified visual hierarchy.
ISSUE 02 : HIGH SEVERITY
Meeting scheduler had no project context
Participants couldn't tell which project a meeting was linked to, and there were no reminders — leading to confusion and missed follow-up.
Fix: Added mandatory project selector before scheduling. Project name and reminders now surface inline within the scheduling screen.
ISSUE 03 : HIGH SEVERITY
No team progress view before submission
All participants wanted to see their team's overall completion status before submitting. Without it, students felt anxious and uncertain at the finish line.
Fix: Added Team Progress Overview with contribution percentages per member, progress bars, and status tags directly in the project workspace.
07 Market Validation
We tested demand before building. Here's what the data said.
Before committing to full development, three pretotyping experiments were run to validate core assumptions about adoption, engagement, and faculty trust.
FAILED
Will professors trust GroupFlow data for grading?
YOUTUBE + FAKE FRONT DOOR | 2 WEEKS | DEMO VIDEO + LANDING PAGE
Created a YouTube demo of the Professor Dashboard and linked to a sign-up page. Target: 3 out of 5 professors sign up for the newsletter.
0/5
Professor sign-ups (target - 3/5)
What this taught us: Faculty adoption needs an institution-level push, not a cold YouTube ad. The channel was wrong — not the value proposition. Next step: direct professor partnerships through university pilot programs.
What I'd do differently and what the pivot made possible.
01.
Assumptions are where design starts not where it ends
Make contributions visible without making people feel watched. Visibility enables natural accountability.
02.
Systems should enable behavior, not force it
Every enforcement idea we tested failed. Students responded to tools that supported collaboration — not tools that monitored or punished. Agency is a design requirement.
03.
Visibility does the heavy lifting
When contributions are visible, teams naturally become more balanced. You don't need surveillance. You need transparency.
04.
A failed experiment is still research
The professor YouTube experiment failed completely. That told us faculty adoption is an institutional problem — a finding that changed our entire go-to-market strategy.
50%
Fewer scheduling conflicts
40%
Fewer last-minute workload shifts
50%
Fewer scheduling conflicts