Choosing a project worth doing

Welcome to the UI/UX Portfolio Project. This course walks you through building one strong portfolio piece end to end — because a portfolio is what actually gets you hired, and it must show your process and thinking, not just pretty screens. It all starts with choosing a project worth doing. This lesson covers choosing a project worth doing. Let's pick the right project. Let's begin.

Why the project (and the choice) matters

YOUR PORTFOLIO IS WHAT GETS YOU HIRED — for UX/UI roles, employers care far more about your
PORTFOLIO (+ the thinking behind it) than your CV or certificates. This course builds ONE strong
project you can show. But it starts with picking the RIGHT project.

WHAT EMPLOYERS ACTUALLY WANT TO SEE (this shapes everything):
- YOUR PROCESS + THINKING — not just final screens, but HOW you got there: the problem, research,
  decisions, iterations, trade-offs. A portfolio piece is a CASE STUDY of your process, not a gallery
  of mockups. (This is the #1 thing beginners miss — they show pretty screens, no thinking.)
- PROBLEM-SOLVING — that you can identify a real problem + design a solution, with rationale.
- CRAFT — solid visual + interaction design (the screens look + work well).
- COMMUNICATION — that you can tell the story clearly (a case study is storytelling).
So the project must give you material to SHOW your process, decisions, + craft — not just a nice UI.

CHOOSING A PROJECT WORTH DOING (the criteria):
- A REAL, MEANINGFUL PROBLEM — solve a genuine user problem (an app/site/feature that addresses a
  real need). Real problems -> real research + decisions -> a rich case study. Avoid vague "redesign
  X for no reason".
- SCOPED RIGHT — big enough to show your process (research -> IA -> flows -> wireframes -> UI ->
  case study), small enough to FINISH well. One focused product/feature/flow, not a whole massive
  app. Depth over breadth. (Finish it — an unfinished project shows nothing.)
- SHOWS THE SKILLS YOU WANT — pick a project that lets you demonstrate the work you want to be HIRED
  for (mobile app? SaaS dashboard? e-commerce? Pick what fits your target role).
- SOMETHING YOU CARE ABOUT — genuine interest -> better work + a more engaging story. Solve a problem
  you understand or care about.

Your portfolio is what gets you hired — for UX/UI roles, employers care far more about your portfolio (and the thinking behind it) than your CV or certificates — this course builds one strong project you can show — but it starts with picking the right project. What employers actually want to see (this shapes everything): your process + thinking (not just final screens, but how you got there: the problem, research, decisions, iterations, trade-offs — a portfolio piece is a case study of your process, not a gallery of mockups — the #1 thing beginners miss: they show pretty screens, no thinking); problem-solving (that you can identify a real problem + design a solution, with rationale); craft (solid visual + interaction design); and communication (that you can tell the story clearly — a case study is storytelling) — so the project must give you material to show your process, decisions, + craft, not just a nice UI. Choosing a project worth doing (the criteria): a real, meaningful problem (solve a genuine user problem — an app/site/feature that addresses a real need — real problems → real research + decisions → a rich case study — avoid vague "redesign X for no reason"); scoped right (big enough to show your process — research → IA → flows → wireframes → UI → case study — small enough to finish well — one focused product/feature/flow, not a whole massive app — depth over breadth — finish it: an unfinished project shows nothing); shows the skills you want (pick a project that lets you demonstrate the work you want to be hired for — mobile app? SaaS dashboard? e-commerce? — pick what fits your target role); and something you care about (genuine interest → better work + a more engaging story).

Types of projects and this course

WHERE TO GET A PROJECT (options):
- INVENT A PRODUCT — design an app/site solving a problem you notice (a fresh concept). Full creative
  control + a clear problem. Great for beginners. (E.g. an app for a real frustration you have.)
- REDESIGN AN EXISTING PRODUCT — take a real app/site with usability problems + redesign it (with a
  RATIONALE — identify real issues via a heuristic evaluation/research, then improve). Shows critical
  thinking. (Don't just "make it prettier" — solve real problems.)
- A REAL / CLIENT PROJECT — freelance, volunteer (a local business/nonprofit), or a real brief.
  Real constraints + a real user = a strong, authentic case study. The best if you can get one.
- A DESIGN BRIEF / CHALLENGE — use a brief (Briefbox, Sharpen, daily-UI-style, bootcamp briefs) for a
  ready problem to solve.
- IMPROVE A FLOW / FEATURE — a focused piece (redesign a checkout, an onboarding, a booking flow) —
  smaller scope, still shows full process. Great for a focused, finishable project.

WHAT MAKES A PORTFOLIO STRONG (aim for this):
- 2-3 STRONG, COMPLETE case-study projects > 10 shallow ones. QUALITY + DEPTH over quantity.
- Each shows the FULL PROCESS + your thinking + polished outcomes.
- This course builds ONE such project properly (repeat the method for others).

WHAT THIS COURSE COVERS (the full project journey): choosing a project, lightweight USER RESEARCH,
PERSONAS + problem statement, INFORMATION ARCHITECTURE, USER FLOWS, WIREFRAMES, defining the VISUAL
STYLE, designing HI-FI SCREENS, taking a design to a REAL LANDING SCREEN, writing the CASE STUDY,
PRESENTING + handling feedback, + PUBLISHING your portfolio.

THE PRINCIPLE: your PORTFOLIO (showing PROCESS + thinking, not just screens) gets you hired. CHOOSE a
project worth doing: a REAL, meaningful problem, SCOPED to finish, showing the SKILLS you want, that
you CARE about (invent / redesign / real brief / a focused flow). Aim for a few DEEP, complete
case-study projects. This course builds ONE properly, end to end. Pick well — the project is the
foundation of your portfolio.

Where to get a project (options): invent a product (design an app/site solving a problem you notice — full creative control + a clear problem — great for beginners), redesign an existing product (take a real app/site with usability problems + redesign it, with a rationale — identify real issues via a heuristic evaluation/research, then improve — shows critical thinking — don't just "make it prettier"), a real / client project (freelance, volunteer — a local business/nonprofit — or a real brief — real constraints + a real user = a strong, authentic case study — the best if you can get one), a design brief / challenge (use a brief — Briefbox, Sharpen, daily-UI-style, bootcamp briefs — for a ready problem), and improve a flow / feature (a focused piece — redesign a checkout, an onboarding, a booking flow — smaller scope, still shows full process). What makes a portfolio strong (aim for this): 2–3 strong, complete case-study projects > 10 shallow ones — quality + depth over quantity; each shows the full process + your thinking + polished outcomes; this course builds one such project properly (repeat the method for others). What this course covers (the full project journey): choosing a project, lightweight user research, personas + problem statement, information architecture, user flows, wireframes, defining the visual style, designing hi-fi screens, taking a design to a real landing screen, writing the case study, presenting + handling feedback, and publishing your portfolio. The principle: your portfolio (showing process + thinking, not just screens) gets you hired; choose a project worth doing: a real, meaningful problem, scoped to finish, showing the skills you want, that you care about (invent / redesign / real brief / a focused flow); aim for a few deep, complete case-study projects; this course builds one properly, end to end — pick well; the project is the foundation of your portfolio.

The mistake beginners make

The first mistake is showing screens, not process — a portfolio of pretty mockups with no thinking/rationale; a portfolio piece is a case study of your process (research/decisions/iterations). The second mistake is a vague/pointless project — a "redesign for no reason" with no real problem; pick a real, meaningful problem. The third mistake is too big to finish — a whole massive app that stays unfinished; scope it to a focused product/feature you can complete. And quantity over quality — ten shallow projects instead of 2–3 deep ones; depth + completeness win. And a project that doesn't fit the target role — showing irrelevant work; pick a project matching the job you want. Show process not just screens, pick a real problem, scope to finish, prioritise depth, and match your target role.

Your turn

---

Your turn

1. Understand what gets you hired: employers want your PROCESS + THINKING (problem, research, decisions, iterations) - a portfolio piece is a CASE STUDY, not a gallery of pretty screens (the #1 thing beginners miss).
2. Pick a real, meaningful problem: choose a project that solves a genuine user problem (avoid 'redesign X for no reason') so you have real research + decisions to show.
3. Scope it to finish: pick one focused product/feature/flow - big enough to show your full process (research -> IA -> flows -> wireframes -> UI -> case study), small enough to complete well (an unfinished project shows nothing).
4. Match your target role: choose a project type that demonstrates the work you want to be hired for (mobile app / SaaS dashboard / e-commerce / a focused flow) and that you genuinely care about.
5. Choose the source: invent a product, redesign an existing one (with a real rationale), take a real/client/volunteer project, use a design brief, or improve a specific flow - aiming for a few DEEP, complete case studies over many shallow ones.

Key points

• Your PORTFOLIO (+ the thinking behind it) gets you hired for UX/UI — far more than a CV/certificates. Employers want: PROCESS + THINKING (problem/research/decisions/iterations — a CASE STUDY, not a gallery — the #1 thing beginners miss), PROBLEM-SOLVING (with rationale), CRAFT (visual/interaction), and COMMUNICATION (storytelling).
• CHOOSE a project worth doing: a REAL, MEANINGFUL problem (genuine user need -> rich case study; not 'redesign for no reason'), SCOPED right (big enough to show the full process, small enough to FINISH — depth over breadth), shows the SKILLS you want (fits your target role), and something you CARE about.
• Sources: INVENT a product (full control + clear problem — great for beginners), REDESIGN an existing one (with a real rationale — not just prettier), a REAL/client/volunteer project (best — real constraints/users), a DESIGN BRIEF (Briefbox/Sharpen), or IMPROVE a focused FLOW (checkout/onboarding — finishable).
• A strong portfolio = 2-3 DEEP, COMPLETE case studies > 10 shallow ones (quality + depth). Each shows the full process + thinking + polished outcomes. This course builds ONE properly, end to end.
• The mistakes: showing screens not process (it's a case study), a vague/pointless project (pick a real problem), too big to finish (scope it), quantity over quality (go deep), and a project that doesn't fit the target role.