Online training on November 3 led into an offline vocational high school customer-centered problem-solving competition on November 10, 2025. The two sessions were separated by one week.
The challenge was not explaining a method once. It was making sure questions created online became validation criteria for the offline prototype and presentation.
Leave questions rather than finished ideas online
Requiring a complete solution online would encourage teams to spend the week implementing their first idea. Instead, they recorded the first customer, observed problem scene, current workaround, and largest unknown.
Each team chose one small check before the offline event:
- ask two or three real users about the same problem;
- verify that required data or a sensor existed;
- explain the core flow with a paper screen;
- reduce the success scene to one sentence.
The week became a chance to collide the first assumption with reality rather than finish the product.
Explain why the offline result differs from the first document
On competition day, review did not reward only fidelity to the original idea. When customer, problem, feature, or demo changed, teams explained why.
Discovering that users experienced a different problem, required data was unavailable, or implementation was riskier than expected was useful evidence. Teams revised scope and success criteria rather than hiding the discovery.
A pivot became a decision based on evidence, not a failure to follow the plan.
Judge connections rather than feature count
A competition can make polished screens and feature volume appear dominant. Review instead examined:
- whether the observed problem matched the solution;
- whether the demo showed the essential customer change;
- whether the team could explain each technology choice;
- whether failure and limitation were visible;
- whether the next hypothesis was concrete.
This compared product reasoning across teams with different implementation experience without forcing identical output.
Present the change between online and offline
Presentations followed problem → online hypothesis → evidence gathered during the week → changed decision → demo → remaining question. The audience saw learning, not only the final feature.
Students practiced explaining why priority changed and what came next rather than merely apologizing for an unimplemented feature.
Working Backwards in this competition was neither just online material nor an offline presentation template. It preserved learning between the two moments, connecting the first question to a real prototype and a changed judgment.
Comments