Careerflow360

Choosing a college is rarely just a college-search problem.

Students and parents are trying to answer several connected questions at once:

Yet these decisions are typically spread across multiple websites, spreadsheets, ranking platforms, college websites, career resources, scholarship databases, and application portals.

I designed CareerFlow360 as a unified experience that connects the journey fromcareer exploration to major selection, college discovery, ROI understanding, scholarships, and application planning.

The goal was not simply to build another college-search tool.

The goal was to reduce the cognitive load of a complex, high-stakes decision.

College planning is fragmented

Students may begin with a college search.

Parents may begin with tuition.

Another family member may focus on rankings.

A student may be interested in a particular career but have no idea which major supports it.

Meanwhile, important information is distributed across different sources.

This creates a fragmented journey:

The user is responsible for connecting all of those dots.

The opportunity

I saw an opportunity to design a product that could connect these decisions into a single, personalized journey rather than treating each activity as an isolated task.

How might we help students and families move from uncertainty to confident education and career decisions?

Instead of asking:

“How can we help students find colleges?”

I reframed the problem around the larger decision.

Career → Major → College → Career Outcome

This became the foundation for CareerFlow360's product strategy.

I worked across the end-to-end UX process, including:

• User research
• Research synthesis
• Personas
• Empathy mapping
• Journey mapping
• Problem framing
• Product strategy
• Information architecture
• User flows
• Wireframing
• UI design
• Design system
• High-fidelity prototyping
• Usability testing
• Iteration

The project was developed as an independent product concept.

[VERIFY/ADD: project timeline]

[VERIFY/ADD: whether you worked independently or with collaborators]

Before designing, I wanted to understand the decision—not just the interface.

I conducted research with 26 participants to understand how students and families approach college and career decisions.

Research objectives

I wanted to understand:

1. How students choose colleges.
2. How parents influence the decision.
3. Whether students have already selected a career or major.
4. What information families consider most important.
5. How families evaluate college value and ROI.
6. Where users currently obtain information.
7. What makes the process confusing or overwhelming.
8. What information users wish they could see together.

[VERIFY/ADD: exact research method and participant breakdown]

Three findings became particularly important to the product direction.

The research changed how I thought about the product.

Instead of designing:

College Search

I designed around:

Decision Journey

The connected model

This became one of the central principles behind CareerFlow360.

The product should help users understand not only:

“Which college should I consider?”

but:

“How does this college fit into the future I am trying to build?”

Research revealed that CareerFlow360 needed to support multiple perspectives.

The research suggested that college planning is not one task. It is a sequence of interconnected decisions.

Before CareerFlow360

The experience creates unnecessary cognitive load.

I designed CareerFlow360 around a more connected journey:

The product architecture was designed around the user's decision-making journey rather than around disconnected tools.

Core experience

• Profile — Student / Parent / Mentor / Counselor
• Career Discovery — Career exploration, career information, job outlook, salary / employment information
• Major Discovery — Major exploration, career connections, major-to-college relationships
• College Search & Match — Search, personalized matching, college comparison
• Financial Planning — Cost, ROI, scholarships / financial aid
• Application Hub — Colleges, deadlines, application status, tasks
• Mentorship — Mentors, counselors, guidance

One of the most important parts of CareerFlow360 is onboarding.

The product needs information such as:

• GPA
• Academic interests
• Extracurricular activities
• Intended major
• Career interests
• Budget
• Preferred location
• AP courses
• Other student preferences

But collecting this information creates a UX problem.

The problem

During usability testing, participants understood that information was being requested, but some were uncertain about why CareerFlow360 needed it.

That created friction and reduced confidence during onboarding.

I conducted task-based usability testing with 5 participants using athink-aloud protocol.

Testing approach

Participants were asked to complete realistic tasks while verbalizing their thoughts, expectations, confusion, and decision-making.

I observed:

• Where users hesitated
• What they expected to happen
• What terminology confused them
• Where they questioned why information was required
• Whether the interface communicated the value of each step

[VERIFY/ADD: exact task list]

Users didn't fully understand the value of the information they were providing.

The issue wasn't simply:

“The form is too long.”

The deeper problem was:

Users didn't always understand how their answers would improve their CareerFlow360 experience.

This distinction mattered.

Reducing the number of fields might make the form shorter—but it wouldn't necessarily increase trust.

I redesigned the onboarding experience to make the relationship between:

Question → Purpose → Personalized value

more explicit.

Design improvements included:

• Clearer helper text
• Examples where users might be uncertain
• Stronger visual hierarchy
• Progress indication
• More understandable labels
• Visual cues to make sections easier to scan
• Context explaining why information matters

The goal was to transform onboarding from:

“Why are you asking me this?”

into:

“I understand how this will help personalize my experience.”

After establishing the product structure and major flows, I translated the experience into wireframes and then high-fidelity UI.

The design system was developed to create consistency across:

• Navigation
• Cards
• Forms
• Search
• Filters
• Data presentation
• Comparison experiences
• Progress states
• Recommendations
• Application tracking

The visual language was designed to make a complex information-heavy product feel approachable rather than overwhelming.

[INSERT IMAGE — wireframes]

Low-fi structure

One of the core ideas behind CareerFlow360 is connecting decisions that are traditionally separated.

Instead of forcing a student to begin with a college name, the experience can begin with the student's interests and aspirations.

Example journey

This creates a much more natural decision flow.

CareerFlow360 moves beyond a generic college list.

The goal is to help students evaluate colleges based on their own profile and priorities.

Potential matching factors include:

• Academic profile
• Intended major
• Career interests
• Location
• Budget
• Student preferences
• Programs
• Career outcomes

The experience should answer:

“Why is this college a good match for me?”

rather than simply:

“Here is a list of colleges.”

College decisions often require comparing multiple dimensions simultaneously.

CareerFlow360 brings those dimensions into a more structured experience.

Compare

• Academics
• Programs
• Cost
• ROI
• Career outcomes
• Location
• Other personal priorities

The objective is to reduce the need for users to repeatedly switch between browser tabs and spreadsheets.

Discovery is only the beginning.

Once students begin applying, the problem changes from:

“What should I choose?”

to:

“How do I manage everything?”

CareerFlow360 therefore includes an application hub designed to help users track:

• Colleges
• Deadlines
• Application status
• Tasks
• Scholarships
• Important milestones

This extends the product from discovery into execution.

CareerFlow360 was intentionally designed as more than a single college-search screen.

This roadmap reflects the larger product vision while keeping the initial UX focused on the highest-value user problems.

The final design system and high-fidelity experience bring the research and product strategy together.

Key screens

[INSERT ACTUAL SCREENSHOT — onboarding]

Provide final UI screenshot

[INSERT ACTUAL SCREENSHOT — career exploration]

Provide final UI screenshot

[INSERT ACTUAL SCREENSHOT — major exploration]

Provide final UI screenshot

[INSERT ACTUAL SCREENSHOT — college search / matching]

Provide final UI screenshot

[INSERT ACTUAL SCREENSHOT — college comparison]

Provide final UI screenshot

[INSERT ACTUAL SCREENSHOT — application hub]

Provide final UI screenshot

[INSERT ACTUAL SCREENSHOT — scholarship experience]

Provide final UI screenshot

The objective wasn't to maximize the number of screens.

It was to create a coherent experience across the user's decision journey.

The most important learning from usability testing was thatpersonalization creates a trust problem if users don't understand its value.

The more information the product asks for, the more important it becomes to explain:

Why are we asking?

and

What will you get in return?

This influenced the onboarding experience and reinforced a broader product principle:

Personalization should feel useful, not invasive.

CareerFlow360 is a product concept and therefore does not yet have production-scale business metrics.

I would not claim fabricated conversion, retention, or revenue results.

The next phase of validation would focus on:

1. Measure onboarding completion — Does explaining the value of each question improve completion?
2. Measure decision confidence — After using CareerFlow360, do students feel more confident about their career, major, and college choices?
3. Validate matching quality — Do students and parents agree that recommended colleges are genuinely relevant?
4. Test parent/student alignment — Can the product help families identify disagreements and reach a shared decision?
5. Validate end-to-end journeys — Can users successfully move from Career → Major → College → Application without unnecessary confusion?

CareerFlow360 evolved from a college-search concept into a broadercareer and education decision platform.

The strongest outcome of the project was not a collection of high-fidelity screens.

It was the transformation of a fragmented problem into a connected experience:

The project allowed me to work across the full UX lifecycle—from research and problem framing through product strategy, interaction design, UI design, usability testing, and iteration.

CareerFlow360 taught me that designing for a complex decision is fundamentally different from designing for a simple task.

When the decision involves education, money, career aspirations, and family expectations, users don't simply need more information.

They need:

And ultimately:

Confidence.

That became the central design principle behind CareerFlow360.

Want to explore the complete visual design and high-fidelity screens?