Making Deadlines Impossible to Miss
Prototyp3 Case Study - 3 Week Iteration Cycle
Company: Prototyp3, an EdTech platform connecting college students with real company projects for hands-on experience
My Contribution: Tested existing dashboard, identified deadline visibility as the root cause of low completion rates, redesigned progress tracking, and validated the solution with users
Timeline: 3 weeks
The Problem
Students weren't finishing their Prototyp3 projects. Low completion rates threatened corporate sponsorships and platform credibility.
Our assumption
Students needed better project management tools. So we built a complete dashboard with progress tracking, milestones, and resources.
After testing
Students still couldn't answer "What's due next?" or "Am I behind?" We'd built a solution without validating it solved the actual problem.
The real problem from testing
Students couldn't see deadlines. No dates on milestones, no timeline visibility, no sense of urgency. They'd get to Week 7 of an 8-week cohort and panic.
Why this matters
Fixing deadline visibility = fixing completion rates = proving platform value to sponsors.
"We were in the second-to-last week and I didn't realize we were so close to the deadline."
— Student who didn't finish
Research Findings from V1
Synthesizing patterns across participants
Critical findings (4/4 participants):
Couldn't see deadline dates anywhere
No sense of timeline position
Important info buried below company descriptions they'd read once
"We were in the second-to-last week and I didn't realize we were so close"
— Student who finished
Quality Assurance before testing V2 with users
Before testing V2, I ran an AI-powered QA audit that caught 23 accessibility and design issues.
Fixed immediately (critical for testing):
Touch target sizes (WCAG compliance)
Color contrast on overdue state
Empty states
Documented for later:
Hover states, loading states, edge cases
Rationale: 3-week timeline meant strategic trade-offs. Fixed what would break testing, documented the rest.
Designing the Solutions
Make deadlines impossible to miss, create urgency when overdue
1. Added dates and timeline visibility
Every milestone: "Week 5 • Due November 10, 2025"
Progress section: "Week 5 of 10 • 6 weeks remaining"
Clear cohort end date visible at all times
2. Designed overdue state that screams at you
Red background, warning icon, high-contrast text
"Overdue by 1 day!" positioned at the very top
Validated in testing: noticed in <5 seconds
3. Added accountability mechanism
Helper text: "Check off milestones as you complete them"
Students self-track progress
Visible commitment to deadlines
Reorganized information architecture
Move frequently-used info to the top
Progress & Milestones at top (used daily)
Resources moved up (needed for work)
About/Skills pushed down (one-time reference)
Usability Testing: Proving It Worked
Tested V2 with same 4 students who couldn't use V1.
Test design: 3 screens showing progression:
Week 1 (empty state, 9 weeks ahead)
Week 5 on-track (due in 2 days)
Week 5 overdue (missed deadline)
What I measured:
Time to find deadline (<10 seconds = success)
Whether overdue state grabbed attention (<5 seconds)
Self-reported confidence (target: 4-5 out of 5)
Why this validation approach: Same users, same questions, directly comparable results. No ambiguity about whether fixes worked.
[VISUAL: 3 test screens shown in sequence with annotations showing what was tested]
Screen 1: Week 1 (First Day)
Testing timeline awareness and empty state comprehension
Can students immediately identify where they are in the cohort (Week 1 of 10), how much time remains, and when the first deadline is? Does the empty Team Resources state clearly indicate what action to take?
Screen 2: Week 5 (On Track)
Testing progress perception and upcoming deadline urgency
Can students quickly identify they're midway through (50%), recognize a completed milestone, and immediately spot what needs attention next? Does "Due in 2 days" create appropriate urgency without mental calculation?
Screen 3: Week 5 (Overdue)
Testing overdue state visibility and urgency communication
Does the red overdue state grab attention in under 5 seconds? Can students immediately identify what's late and perceive it as urgent? This is the core test validating the deadline visibility fix.
Results
4/4 noticed overdue state in <5 seconds
4/4 found next deadline in <10 seconds (vs unable in V1)
5/5 confidence rating on deadline tracking
Overdue state grabbed immediate attention:
"Wow, I really like that it grabs my attention right away. It is pretty urgent and is the first thing that I need to address."
— Somto, Student
Information architecture fix validated:
"Yes absolutely. With it moved down the page and now that the milestone, resources are at the top, I feel like I have what I need to complete my deliverables on time."
— Somto, Student
"Due in X days" format eliminated mental calculation:
"Due in two days is infinitely more useful than due November 30, 2025. I don't need to do mental calculation. Step 1: look at date. Step 2: figure out today. Step 3: calculate difference. With 'due in 2 days' it's one step."
— Justin, Engineer/Mentor
Fast onboarding confirmed:
"When I looked at test two, I instantly have an idea of where everything is now. The barrier to entry or onboarding process is very fast."
— Justin, Engineer/Mentor
Concluding the Impact of this Iteration
What this design accomplishes:
Students can immediately see where they are in timeline
Overdue states create unavoidable urgency
Deadline visibility enables planning ahead
Self-tracking creates accountability
Expected business metrics impact:
Improved completion rates (primary platform metric)
Reduced last-minute panic and incomplete projects
Better sponsor satisfaction and platform credibility
Next Steps
If this project continued, here's how I'd prioritize remaining issues:
From V2 Testing (High Priority):
Fix Screen 1 timeline visibility - Somto couldn't identify "Week 1 of 10" position, though it worked on Screen 2
Resolve date format choice overload - Justin identified too many formats (Oct 6, Oct 13, Dec 15 + "9 weeks" + "2 days") create cognitive load. Keep relative time OR absolute dates, not both
Increase text spacing throughout - Justin noted "flood of text" feeling
From QA Audit (Medium Priority):
Design hover and focus states for desktop keyboard navigation
Add loading states for milestone check-offs and resource uploads
Handle edge cases: multiple overdue milestones, many team members (5+), first/last week scenarios
From V1 Testing (Not Yet Addressed):
Improve empty state visibility for Team Resources (Justin initially missed it)
Consider progress bar alternatives - currently decorative with no functional value
Add project-specific milestone customization (Somto's request - generic milestones limit usefulness)
Future Validation:
Test overdue state (Screen 3) with fresh users first to eliminate sequential bias
Track post-launch metrics: completion rates, milestone check-off adoption, dashboard engagement