GYUHO Lee © 2026
"Why can’t we see all the university's Info at once?"
Diruni
Timeline
Aug – Nov 2025
TEAM
Individual
MY ROLE
UX Research
Concept
Visual Design
Interaction Design
Prototyping
Usability Testing
This case study rethinks how international students navigate German university applications. The problem wasn't just a lack of information, but critical details scattered across too many places to act on. The goal was to simplify the structure, not the content.
Why is every information on a different page?
That frustration was the brief. Diruni structures German university details into a single, scannable view, cutting the time between research and decision.
01. Highlights
Application Guidance:
Fully Personalized, Optimized for Efficiency
No more confusing instructions, inaccurate information, or scattered resources. Diruni streamlines the entire journey, from university search to application management, through one clear and unified experience.
Faster access
Users no longer need to navigate across scattered websites and tabs. Key university information is now reachable in just a few focused steps.
Maybe it should have worked this way from the beginning.
Smarter preparation
Study-abroad preparation often begins with fragmented research and uncertainty.
Diruni brings essential information into one clearer starting point.
Better
visibility
Because admissions competitiveness is rarely explained clearly, many students hesitate during planning.
Diruni visualizes admissions patterns to support more confident decisions.
And more.
Students often manage applications across scattered notes, tabs, and bookmarks.
Diruni brings search, recommendations, application tracking, and updates into one unified dashboard.
02. Design Challenge
Taking on the Problem
This shouldn’t be this hard.
But it is.
Before designing anything, I needed to understand why the process felt so broken. Not just which features were missing, but what was actually making students stuck.
⌛
Too much time wasted in the preparation phase
😵💫
Inefficiency caused by scattered information
💲
Low UX quality leading to extra costs
Designing an Intuitive, Efficient
Experience
Principles
Primary Audience 🎓
Non-EU applicants
Secondary Audience
EU students (including exchange and local applicants)
Design Objective
Streamline DAAD’s complex admission workflow into a clear, user-friendly interaction model.
Data Principle
Maintain accurate, up-to-date entry requirements with Non-EU criteria set as the default standard.
My Challenge
Strategy, Turbo Mode
Helps study-abroad applicants quickly set up their initial strategy
Info at a Glance
Essential information can be grasped at a glance
Solution
'Focused, Fast, Intuitive'
Restructuring the application journey around clearer UX priorities
Reducing friction between information, verification, and action
Focusing only on information that directly supports decision-making
03. Discovery
Mapping the Chaos
: Uncovering the Student Journey
Before designing solutions, I mapped the application process firsthand to understand where students lost time, clarity, and confidence.
Three recurring patterns stood out.
Research Timeline
Most students spent 1–3 weeks comparing requirements and planning applications.
Fragmented Resources
Information was spread across university sites, DAAD, PDFs, and forums.
Firsthand
I experienced the same repeated verification process myself.
04. Problem Framing
Hidden Challenges Shaping
the Journey
Through surveys and firsthand application experiences, I identified recurring UX gaps that shaped the project’s core design direction.
UX Outcomes
Observation Framework
Analyzed key Insights
Three core drivers of inefficiency
Core Questions
Even though the service is well-designed, I was curious why it still doesn’t fully enable efficient workflows. I started with two key questions:
Q1
Are DAAD services fully supporting students in their study-abroad journey?
Q2
Can existing platforms truly support confident decision-making?
Key Insights
Based on the two guiding questions, this survey validated key pain points and captured real user experiences. The results provided clear insights that directly informed the design direction.
71%
Dissatisfied with the DAAD portal
8 in 10
Faced missing or unclear information
Hardest step
Searching & document interpretation
2 in 3
Delayed decisions due to low clarity and confidence
CORE CAUSES OF INEFFICIENCY
Complexity
Accessibility
Accuracy
No personalization, filtering, or save options
Varied university websites → difficult to consolidate info
Multiple links (3–4) needed to reach results
Information scattered across university sites, DAAD, uni-assist, forums, PDFs
05. Diruni’s Strategy
A Streamlined Journey
Diruni’s UX strategy focused on reducing these root problems first.
Users repeatedly faced difficulties not because information was missing, but because of structural inefficiencies that began in the earliest stages of planning.
This section outlines how I analyzed those problems structurally and defined the core UX priorities before moving into design.
UX Outcomes
UX Priority Model
Key Problem Definition
Hypothesis
UX Priority Model
Before designing solutions, I identified which problems created the most friction instead of trying to solve everything at once.
Constraints — What limits the experience?
Each university follows different rules
Non-EU students must meet additional requirements.
DAAD information is scattered across multiple formats and languages.
➔ Data consistency became the top priority before improving the experience itself.
Success Criteria — What defines success?
Students can find essential information quickly
Tasks can be completed with minimal verification
Navigation feels intuitive across all flows
➔ Ultimately, the goal was to enable faster, more confident decisions.
The Hardest Part
The main issue wasn’t information overload, but fragmented workflows and repeated checking.
UX Priority Model
Principles
Behind the Model
Clarity Over Complexity
Even with large amounts of information, the structure remained simple, clear, and easy to navigate.
Focused Curation
Unnecessary details were reduced so users could focus on information that directly affected decisions.
Iterative Problem-Solving
The system was refined through repeated testing and feedback during the design process.
Efficiency & Flow
The experience was designed to reduce cognitive load and shorten the path to actionable information.
Key Problem Definition
These patterns became the foundation for restructuring the application flow throughout the product :
Unclear Paths, Repeated Checking
Problem
Application information is spread across fragmented paths, making it difficult to gather and understand requirements consistently.
Impact
Repeated verification: Students repeatedly search, compare, and cross-check requirements before feeling confident enough to proceed.
UX Strategy
Structure information into clearer, more consistent flows to reduce unnecessary confusion and repeated checking.
Different Answers, Different Outcomes
Problem
Admission requirements aren't consistently documented. Students turn to direct inquiry, only to face slow responses, conflicting answers, or none at all.
Impact
Stress and delays: When the official answer varies by person and day, students can't trust what they know or plan what's next.
UX Strategy
Cover the common cases upfront with standardized guidance, so most questions never need to be asked. For the rest, surface the right contact directly, no searching required.
Hypothesis
How can international students plan their application strategy
faster and more accurately?
Diruni approached this question with two core hypotheses :
Hypothesis 1
➔ Integrated information accelerates strategy planning
Users previously had to manually combine scattered information.
Key Structures : Search tab, summary cards, procedural tables, school-specific checklists
Goal : Reduce Time Cost
Hypothesis 2
➔ Personalized management reduces errors, omissions, and rework
Each user’s schools and requirements differ, requiring a personalized view.
Key Structures : Application Manage, Saved, checklist templates
Goal : Reduce Cognitive Load & Verification Cost
Design Priorities
Simple & Immediate
I made minimizing the Time-to-first-answer and reducing unnecessary friction the core principle of Diruni’s design.
To achieve this, I focused the design on reducing three key burdens users face in practice. Time, Cognitive, and Verification Costs.
UX Efficiency Kit
🕑 Time Cost — Save Time
💭 Cognitive Load — Understand Instantly
✅ Verification Cost — Eliminate Errors
Design Approach
Feature Sprint
Core Feature Structuring
Prioritized core features through a card-sorting session with four international students.
Defined Diruni’s core journey: compare → decide → plan.
View PDF
IA & Flow Design
Built the information architecture around how students search, compare, and prepare.
Simplified the main flow into: search → review → plan → manage.
View PDF
Wireframe Validation
Tested the initial structure and user flow through early wireframes before high-fidelity design.
View PDF
Refined the architecture through user testing and iteration.
06. Exploration
Minimal Clicks,
Maximum Clarity
Interface
at a Glance
Diruni was built around three things that kept slowing people down: too much time spent searching, too much to hold in your head, and too many steps just to confirm one fact.
The structure adapts to where each user actually is in the process, so nothing feels out of place or premature.
Time Cost
Problem
This is what “Unclear Paths, Repeated Checking” looked like in practice.
I kept running the same searches twice. DAAD’s “International” and “All Degrees” split appeared meaningful at first, but often resulted in duplicate searches and unnecessary re-checking.
Even simple decisions meant checking the same information over and over again.
Direct Access to Core Information
Search was placed at the center of the experience to reduce unnecessary navigation during early planning.
In testing, users reached key university information faster and felt more confident moving forward without repeated searching.
Saving Progress, Faster Revisit
Users often restarted their research because there was no lightweight way to save schools during exploration.
To reduce repeated searching,
Introduced quick-save interactions
Built a centralized “Saved” space for tracking shortlisted schools
Filter Redesign: Fewer Options, Clearer Intent
Users didn’t need more filters. They needed meaningful ones.
The original system overwhelmed users with filter options that added complexity without improving decision-making.
The original filter felt overly complex:
Over 10 options
Many filters didn’t really help
Hard-to-understand terminology
Example: Overly Complex Term System
Although the system was only indicating enrollment periods, it used mixed labels such as Quarter, Trimester, and Semester.
The issue was not the information itself, but the amount of interpretation users had to do before making a decision.
As a result, what should have been a straightforward choice became confusing.
Users had to decode terminology before making decisions
Seasonal options expanded into unnecessarily segmented choices
Confusing combinations made the filtering logic harder to trust
What users actually wanted to know was simple:
“I just want to apply for a specific term." 🙋♂️
Simplified Filter
Improvements
Removed unnecessary terminology
Prioritized high-impact criteria first
Simplified the path from exploration to decision-making
Result
The redesigned filter focused on fewer options, clearer criteria, and a shorter path to decisions.
Once the filters made sense, people stopped going back and started moving forward.
Cognitive Load
Intuitive Information Structure
When exploring universities through DAAD, important information was often separated across inconsistent structures, making it difficult to identify what actually mattered.
As users struggled to interpret and compare information across different sources, they repeatedly slowed down to verify what they had already seen.
Common issues are..
EU / Non-EU pages often overlapped, with links that led nowhere.
Missing key details or overly long explanations
Ambiguous labels that required extra interpretation
Deadlines buried in inaccurate links
What User Testing Revealed
Users stalled. Not because the information was wrong, but because too much landed at once. (Left)
Splitting it into stages changed that. Users knew exactly where they were, and kept moving. (Right)
Final Design (Refined)
Overview-first structure for faster scanning
Clear separation between actions, dates, and documents
Consistent patterns across every school page
Structured Flow
Stage 1 → 2 → 3
Overview → Process → Documents
A standardized structure reduced the need to reinterpret information across different schools.
Quick look
Step by step
The paperwork
By revealing only the information needed at each step, the process became easier to follow and mentally lighter.
Key Info Card : 5-Sec Scan
Before (DAAD)
After (Diruni)
The redesigned card focused only on the information users needed to decide whether to explore further.
In testing, users understood the card within seconds without missing key details.
Verification Cost
Reducing Confusion, Building Trust
Even after finding the right page, I wasn't sure I could trust it. Dates felt outdated, links sometimes led nowhere, and there was no way to know if what I was reading still applied to my situation.
User testing revealed two clear needs:
Verify information at the source
Act on it immediately
Checklist: One-tap action to move forward
Visit Website: Access the official source in one tap
Error-Free Verification
Following every step on the official checklist still wasn't enough. Students were asked for documents never mentioned upfront. 6 in 10 had to recheck and resubmit, sometimes missing deadlines entirely.
Designed structured checklists that track school-specific requirements in real time, helping users prepare documents quickly with fewer missing steps.
Clear steps. Never miss.
No stale info here.
Supporting Features
After defining the core UX, I introduced a set of lightweight features designed to make the application journey faster, clearer, and easier to navigate.
Competition Insights: When Official Data Is Missing
Not all universities publish admissions data, especially art schools where official indicators are often unavailable.
NC data available
Art students, no need to worry
To reduce uncertainty, I designed an alternative benchmark using applicant experiences and community-based feedback patterns.
“I want to quickly understand how competitive this school is.”
Open Now: Schools You Can Apply to Right Now
Some users did not start with specific target schools:
“Show me what I can apply to today.”
Instead of forcing broad exploration, this feature prioritized schools that users could apply to immediately.
Prioritized currently available programs
Defaulted to Non-EU criteria with a simple EU toggle
Designed as an action-first view, not a browsing list
07. Design Outcome
Numbers That Changed the Journey
Small structural changes led to clearer decisions, faster progress, and less friction. These outcomes are based on lightweight prototype testing and comparative task observation, designed to validate directional behavioral shifts rather than production-scale KPIs.
Testing day. Four friends preparing for university, powered by kebabs.
Later stages vary widely by individual context, so evaluation focused on early, comparable steps. The comparison uses the 'TH Ingolstadt' admission workflow as the reference model.
Clearer Decisions, Less Rework
Information verification dropped from an average of 12 checks per school to 3, helping users move to the next step with greater confidence.
“I didn’t feel the need to go back and confirm things again.”
Benn
22, Congo
Navigation Complexity ↓
The time required to understand a school’s key requirements and preparation steps dropped from an average of 55 minutes to 15, making the school selection process significantly more linear.
Lower Cognitive Load
To minimize errors and confusion, a simpler process was needed.
Reducing the number of tabs from an average of 8 to 3 during requirement checks and document preparation significantly lowered cognitive load caused by fragmented information and repeated verification.
What Actually Changed
The journey shifted from 'navigation-heavy' to 'action-driven'.
Students stopped backtracking. The flow became a forward motion.
Why This Result Matters
The problem was never the amount of information. It was knowing what to do next.
By reshaping the journey into an action-first flow, Diruni helped users move forward without second-guessing or getting stuck.
“It feels like something is guiding me forward,
instead of making me fight through information.”
Gabriel
21, Spain
Reflection
Honestly.
This started as a personal frustration and became a real design process. The messiest part wasn't the wireframes. It was figuring out which problem was actually worth solving.
Good UX isn't about reducing information.
It's about reducing uncertainty.
A Studio Filled With Ideas..🧠
My desk never really stayed clean during this project. Sketches piled up on post-its, and flows were crossed out and redrawn again and again. But watching that mess slowly turn into something that actually worked felt like the whole point of the process.
"NEXT ARCHIVE"
Fixie AI
nooding
