Learning from Failure
失敗から学ぶ
The following week, the three founders visited ten different shops together.
This time, they did not bring the app; they only brought questions.
They asked the owners what made a tool easy or hard to use.
One baker said that she had no time to type during busy hours.
A café owner told them that the app used to feel far too .
"I just want to press one button and be done," he explained simply.
Another owner said that photos would help her far more than long forms.
Maya wrote down every , even the ones that were hard to hear.
The founders realized that they used to design for themselves, not for shops.
Back in their small room, they threw away most of the old code.
Ken rebuilt the app around a single, simple rule: fewer taps, less typing.
Now a shop could post surplus food with just a photo and a price.
The whole , which used to take five minutes, now took twenty seconds.
Rio suggested that they test the new version with the same busy baker.
This time the baker smiled and said that the app finally felt .
"You listened," she told them. "Most people who build things never do."
Within days, three more shops asked if they could join the test too.
The founders learned that good ideas are shaped by the people who use them.
"We used to ," Maya said. "Now we ask, and then we build."
Rio started collecting every piece of in one shared .
The soon became the most important file the team owned.
Slowly, quietly, "Table for Ten Thousand" was beginning to feel real.
For the first time, shops were coming to them, not the other way around.
But running a bigger test would cost money that three students did not have.
They needed , and that meant facing a room full of investors.