Community

Opportunity 313

My Role
Product Design
UX/UI Design
Timeline
2026 · MVP built · Preparing for pilot validation
Three proposed mobile interface screens for this case study

A clearer path to opportunity.

Detroit has no shortage of opportunities. Finding the right one is the hard part. Opportunity 313 brings fragmented information into a single discovery experience, with clear details and a next step families can act on.

I structured the experience around the decisions families need to make, supported by separate workflows for youth, parents, providers, and administrators. A shared listing format helps connect discovery with reliable information.

The challenge

Programs are scattered across flyers, social media, school messages, and provider websites. Families have to piece together age requirements, cost, location, and deadlines before they can decide whether an opportunity fits.

How might we help a family find something relevant—and know what to do next?

Design decisions

Relevance before volume

Age and interests guide discovery. Practical details such as location, schedule, eligibility, and cost help families judge fit before following an application link.

Trust is part of the workflow

Providers submit structured opportunities for administrator review. Discovery depends on the quality and freshness of the information behind each card.

One system, distinct responsibilities

Parents manage youth profiles, families discover and save opportunities, providers submit listings, and administrators review them. Each role has a clear purpose.

The experience

  1. Discover — Browse opportunities aligned with age and interests.
  2. Evaluate — Review eligibility, cost, schedule, and provider details.
  3. Act — Save an opportunity or continue to the provider.

New interface study · Illustrative content · Proposed design, not a shipped screen.

Current stage

MVP built · Preparing for pilot validation

The iOS MVP includes role-based access, youth profiles, discovery, saved opportunities, provider submissions, and administrator review. Pilot testing is the next step; improvements in enrollment or repeat usage have not yet been established.

Next validation

  • Observe families finding and evaluating a relevant opportunity.
  • Check whether providers can submit and maintain complete listings.
  • Measure useful actions, listing freshness, and repeat discovery during the pilot.
A useful directory is more than a list of links. Consistent information and a trustworthy publishing process make discovery actionable.
← All projects