What Happens After the Applause

I helped organize StartLab, a university startup competition in Belarus. We changed the venue and judging panel and revised the application questions. After the competition, some participants went on to interviews with accelerators. Others received an opportunity to work with a bank's lab. The winners received money to develop their projects. These were concrete openings beyond the classroom.

I value events like this. Explaining an idea to people outside a university department can help a student discover that someone else is interested. A deadline can push a team to get its prototype ready to show. Attention from others can give people confidence to continue. That first moment of recognition has a useful job to do.

Access to a lab still has to become work in that lab. An introduction to an expert has to become a conversation that clarifies a next step. When you are building your first project, you may not even know what to ask for. There is a distance between receiving an opportunity and knowing how to act on it. Crossing it alone can be difficult.

After the final comes the work that is harder to photograph. The team needs to meet again, return to the prototype, and find someone willing to use it. That person's questions may be less comfortable than the judges' questions. The explanation that worked during the pitch may mean very little to them. This is where the project begins to face a different kind of test.

I would include a conversation about that work in the support offered. A month after the competition, for example, I would ask what the team had tried and where it had stopped. Those answers provide a better basis for help than another general wish for success. A specific obstacle gives the next action a purpose.

Follow-up can depend entirely on one person who cares enough to make time. They offer an introduction or ask, 'How is it going?' I respect that commitment. I also want it to have support of its own: an agreed next meeting and a way to involve other people. Otherwise, assistance may end when that person's spare evenings run out.

A related question appears in my work as a CTO. A demonstration has a date. The system's ordinary life after launch can continue for a long time. Someone will encounter an error; someone else will need an explanation. We have to plan for that work. A student idea also needs someone to consider what happens after the moment of public attention.

Support can have clear limits. Organizers do not have to guide every team indefinitely. Participants should understand what kind of question they can return with and where the commitment ends. A specific, bounded offer is more useful than the impression that everything will somehow work out after winning.

Some projects will close. People may test an assumption and decide they no longer want to pursue it. That can be a worthwhile educational result, giving them experience to use in their next choice. Keeping a project on a list of promising initiatives long after everyone has moved on makes it harder to understand what the competition achieved or what its participants need.

At a future final, I would like to hear from the previous year's teams. What did they do afterward, and which opportunities were they able to use? Their accounts could improve the support offered and give new participants a fuller picture of the work ahead.

A good competition can begin something that lasts. By the time the room is empty, people should still have a way to continue the conversation. That is how I want to judge the environment I help create.