UI/UX Education Program
Structured Curriculum Design · 5-Month Program
Role
Curriculum Designer & Lead Facilitator
Timeline
2022–2024
Platforms
In-person + Remote cohort delivery
Status
Ongoing
Overview
Most design education produces learners who can follow a tutorial and replicate a Dribbble shot — but can't solve a problem they haven't seen before. I designed a 5-month structured UI/UX curriculum from first principles: built around execution, real-world projects, and the specific gap between what learners are taught and what the industry actually requires.
The Problem
Design education has a structural failure: it teaches tools, not thinking. Students graduate knowing how to use Figma but not how to frame a problem, make a design decision under constraints, or defend their choices to a product team. Real projects start too late. Feedback loops are weak. Portfolio output is hollow — full of hypothetical redesigns that signal nothing to a hiring team.
Constraints
These constraints shaped every design decision:
Learners come in with zero background — the curriculum had to work for complete beginners while producing job-ready output.
Five months is non-negotiable. Every week had to earn its place.
Execution standards, not just completion standards. 'Finished' was not enough. Work had to meet a bar that holds up in a real hiring context.
The curriculum had to be facilitator-transferable. I couldn't be the only person who could run it. It had to be documented well enough for another facilitator to deliver consistently.
My Role
I designed the full 5-month curriculum structure from scratch, defined learning outcomes for each month, designed the real-world project integration (starting month 3), built the feedback and critique system, developed the portfolio development framework, facilitated delivery in multiple cohorts, and iterated the curriculum based on cohort outcomes.
Approach
I built the curriculum backwards — from the endpoint, not the start. The question was: what does a job-ready designer need to demonstrate? A portfolio with 2-3 case studies showing real decisions and real constraints. A positioning statement that communicates a clear professional identity. The ability to articulate design decisions in a critique context. Every month's work was chosen because it directly contributed to those endpoint requirements.
Key Decisions
Decision 1
No Figma Until Week 3
Most curricula start with Figma on day one. I delayed it deliberately. Learners who start with the tool optimize for the tool, not for thinking. Three weeks of sketching, problem framing, and visual principles before any software — this created designers who use Figma as a tool, not as a crutch.
Decision 2
Real Projects From Month 3, Not Month 5
The standard approach puts real projects in the final stretch. By then, students have practiced bad habits for months. My approach: real problems start at the midpoint, when there's still time to build good habits through iteration. The pressure of a real brief accelerates learning in a way that exercises cannot.
Decision 3
Critique Over Feedback
I replaced feedback sessions with structured critiques. In a critique, the designer presents their decisions and defends them — they don't just receive comments, they practice explaining their thinking. This mirrors real design team dynamics and produces designers who can communicate under pressure.
Outcome
Learners produced portfolios with real decision-making visible in case studies
Transition rate from program to employment/freelance measurably improved
Curriculum transferred successfully to additional facilitators
Program ran across multiple cohorts with consistent output quality
Facilitator at Women Techsters using elements of this framework
What I'd Do Differently
Month 1 was still slightly too tool-adjacent by week 3. I'd extend the no-software period to week 4, and introduce Figma through a systems component task rather than an open exploration exercise. The structured entry point produces better tool relationships.