Samsung Solve for Tomorrow: make the problem measurable

Editorial overview

Samsung Solve for Tomorrow asks public-school teams to use STEM in response to a community problem. The familiar phrase can produce vague projects: an app for wellbeing, a sensor for safety, a campaign for sustainability. The competition becomes meaningful only when a team can show whose problem it is, what currently happens and why the proposed technical intervention might change that situation.

The staged format is useful. An initial written application has to make the case economically; later teams must demonstrate the idea through video and presentation. That development exposes whether the project has substance. A concept that sounds impressive in five answers may become difficult to explain once judges ask about users, testing, cost, maintenance or unintended effects.

From an editor's perspective, the contest is best for schools that can protect student ownership while offering practical support. A teacher can organise access and safety, but students should remain visible in problem definition, design choices and interpretation of evidence. The goal is not a corporate-looking pitch. It is a credible account of a team learning enough to make a responsible intervention.

Quick Facts

For current dates, eligibility and registration details, see the Samsung Solve for Tomorrow (USA) competition page.

Review Evaluation

Rated Advanced. Competitive teams need credible community research, practical STEM reasoning, iterative design, teamwork, and increasingly polished communication across each round.

Define the community problem before the device

Checked on 2026-09-19: the 2026–27 open call runs from 30 September to 23 November 2026. Eligible U.S. public schools serving grades 6–12 enter through an employee aged 21 or older, with one student team per teacher or eligible employee. The current theme areas include environmental sustainability, sports and social change, accessibility and open innovation.

Spend time with the people who experience the problem. Interview users, observe the setting and collect baseline information where appropriate. Ask what has already been tried and why it falls short. A strong problem statement names the group, condition and consequence without exaggerating.

Do not assume the solution must be an app or electronic device. STEM could involve material design, environmental monitoring, data analysis, mechanical systems or a process that combines several disciplines. Choose the approach that fits the problem and the team's access to safe testing.

Turn the idea into a testable claim

Write a simple theory of change: if the team introduces this feature for these users under these conditions, which outcome should improve? Then decide what evidence could support or challenge that claim. Measures might include accuracy, time saved, resource use, accessibility, reliability or user experience.

Prototype cheaply before committing to a polished build. Paper interfaces, simple models and simulated data can reveal whether the concept makes sense. Record failed versions and explain what changed. Iteration is not evidence of weakness; it shows that the team allowed results to influence design.

Keep ethics and privacy in the design brief. Projects involving health, personal data, vulnerable people or public safety require adult oversight and careful limits. Do not collect more data than the project needs, and do not imply that a student prototype is ready for high-stakes use.

What the stages reveal

Checked on 2026-09-19: the open application uses five questions. The programme then names 100 semifinalists for a three-minute video stage, followed by ten finalists who develop a presentation. The current prize structure reaches hundreds of schools, with a national top award listed at $50,000 in technology and classroom resources.

The first application should establish the logic of the project: problem, users, STEM mechanism, expected impact and team plan. Avoid filling every answer with background statistics. Select evidence that changes the reader's understanding of the need or the proposed response.

The middle-stage video should show the team thinking and building. Use visuals to demonstrate context, prototype or testing rather than decorating narration. The closing presentation must then answer the questions that a three-minute video leaves open: feasibility, limitations, learning and next steps.

Read prior winners as case studies

Checked on 2026-09-19: Samsung's official announcement for the prior cycle highlights winning schools in Nevada, West Virginia and California and describes projects rooted in local needs. The current cycle's structure differs in the number of national winners, so entrants should use the current rules for awards and the prior cases only as examples of problem selection and execution.

Compare how each project establishes proximity to the issue. The useful lesson is not to choose the same technology. It is to show why this team noticed this problem and how the design responds to conditions that generic research might miss.

Ask whether the project could survive outside the presentation. Who would maintain it? What materials or permissions are required? What happens if a component fails? A realistic limitation can strengthen the entry because it shows that the team understands the system beyond a demonstration.

A school-team workflow

Set roles for research, design, testing, documentation and communication, but rotate enough that every student understands the whole project. Hold brief design reviews where the team states what was learned and which assumption changed. Keep photographs, data, diagrams and consent records organised from the start.

Before each submission stage, ask an unfamiliar teacher or community partner to summarise the project after seeing it once. If they cannot explain the problem and mechanism, simplify. Technical richness is valuable only when the audience can follow its relationship to the community need.

Key Takeaways

Start with a specific community and a measurable problem, then choose the STEM approach that genuinely fits. Prototype early, treat failed tests as information and keep student decisions visible. Use each competition stage to add evidence rather than merely add polish, and be explicit about safety, feasibility and limits.

Sources checked

• https://www.samsung.com/us/solvefortomorrow/about/
• https://www.samsung.com/us/solvefortomorrow/
• https://news.samsung.com/us/samsung-awards-2-million-to-student-innovators-16th-annual-solve-for-tomorrow-competition/