Look for persistent friction where tools feel clumsy, data is missing, or handoffs repeatedly break. Ask teammates and community members what slows them down, and shadow workflows to witness reality. Favor problems you can test within days, because rapid cycles create learning loops, evidence, and confidence before enthusiasm fades.
Break the big fascination into concrete skills employers recognize, like APIs, accessibility, cost optimization, or stakeholder research. Design tasks that expose you to those capabilities under realistic constraints. When done, document exactly which skills you exercised, what you measured, and how your choices balanced speed, quality, and sustainability.
Pitch small iterations to real users, mentors, or colleagues, and watch what they actually do. Keep the playful core intact by reserving time for exploration, yet commit to measurable outcomes. Balance experimental depth with a deliverable rhythm, so fulfillment and employability rise together rather than compete for attention.