MAY 16, 2026
Winning Didn't Mean We Were Right
On May 16, 2026, our team won Third Prize at BK Shark 2026 - Startup in Student with Kizuna Hub. I was genuinely proud of it. We'd spent a lot of time turning a messy idea into something we could explain, and having people outside the team recognize it felt important.
I also made a small mistake with that feeling. I started letting the win answer questions it couldn't really answer. The competition had given us a strong signal, but I wasn't being careful enough about what the signal actually meant.
1. We walked into BK Shark wanting proof
When you spend enough time inside an early product, the reasoning starts to feel obvious. Everyone on the team knows the context, the problems you've discussed, and why each feature exists. BK Shark removed that comfort. We had to explain Kizuna from zero to people who had no reason to fill in the gaps for us.
That was valuable before the result was even announced. The pitch forced us to decide what the product was really about and which parts of the story mattered. When that clearer story earned Third Prize, it was easy to feel like we'd received the proof we'd been looking for.
2. Third place felt like validation, so I treated it like validation
I didn't walk off the stage thinking, 'the market has validated Kizuna.' It was subtler than that. The result told us that outsiders could understand the idea and saw enough potential in it to reward the work. Those are useful signals for an early team.
The problem was what happened next in my own head. 'People see potential here' slowly became 'we're probably building the right thing.' Once that happens, assumptions stop feeling like assumptions. They start feeling like things the team can safely build on top of.
3. The competition validated our story more than our market
A competition and a market ask different questions. BK Shark could tell us that the problem was interesting, that our direction was worth discussing, and that we'd learned to tell the story clearly. It couldn't tell us whether a university would pay, whether founders would return after the first useful session, or whether mentors would want to stay involved.
That isn't a criticism of the competition. It's a correction to the way I read the result. An award can tell you that an idea deserves attention. It can't tell you whether somebody needs the product badly enough to change what they already do.
4. Confidence made some questions easier to ignore
The confidence after BK Shark was still useful. The project felt less fragile, and decisions became easier because the team shared a stronger belief that Kizuna was worth pushing forward. I don't want to pretend that kind of momentum is bad. Early products need it.
But confidence can also change the questions you ask. Instead of asking whether universities actually want a system like Kizuna, it's much more comfortable to ask how the university dashboard should look. The second question feels productive because it quietly assumes the first one has already been answered. Sometimes it hasn't.
5. I want future wins to create better questions, not stronger certainty
The stage gives an award a clean ending. Product work doesn't get one. After the photos and the announcement, you go back to the same repository, the same users you still need to understand, and the same assumptions that were there before the competition.
I'm still proud of Third Prize. I just understand the signal differently now. If I win something again, I don't want the feeling to be, 'we were right.' I'd rather take it as permission to ask a harder question next. Recognition can create momentum. The rest still has to be earned.