Solve for Tomorrow 2026

Researching the problem

• —The scale of the problem: who it affects and how
• —Statistics and expert opinion on the problem
• —What already exists in the country and why it does not solve everything
• —Field research: observation, interviews, surveys
• —Helps: a stakeholder map plus a table of what partners gain

Solution and benefit

• —How the project solves the problem — the benefit in qualitative and quantitative terms
• —Helps: the design-thinking algorithm

Prototype and context

• —What the prototype is made of: software (front/back) · hardware (chip, sensors, controllers, power) · form factor
• —Scenarios: where (city/indoors/outdoors) · who (customer/user) · when (24×7, seasonal, time of day)
• —What could go wrong? Heat, frost, dust, damp, animals
• —Who might break, hack or steal it — deliberately or not. How do you reduce that?

Building and testing

• —First version: a low-fidelity prototype (paper/mock-up) → a high-fidelity one (software, hardware, mechanics)
• —User interviews — in person, by phone, on a call, in chat
• —Expert interviews — someone from the profession who knows the problem
• —Testing in the field, with a user, with an expert

💡 Photograph and film your testing and interviews — you will need that material for the final presentation.

Refining

• —The prototype: specifications, code, the quality of the form factor (cardboard became PVC)
• —Updating the use scenarios and the project's evolution
• —A view from every side using SWOT

Presentation and upload

• —Structure — follow the presentation template provided
• —Check what you filled in — against the presentation checklist
• —Cross-check with the systems-description canvas (nothing forgotten?)
• —Deadline — 30.07.2026 by 23:59, in your account on solvefortomorrow.kz