When I first read the brief for this challenge, my instinct was to build something for everyone. Fans need navigation help. Organizers need oversight. Volunteers need coordination. Venue staff need operational data. Why not build one app that covers it all?
That instinct was wrong, and figuring out why shaped almost everything that came after.
Picking one problem instead of four
During the challenge's explainer session, one comment stuck with me: an app trying to serve every persona ends up serving none of them well. So I made a deliberate choice to narrow the scope. FlowOps AI is built for exactly one person: the stadium volunteer standing at a gate, trying to keep fans moving safely during a match with eighty thousand people in the building.
That single decision changed the whole shape of the product. Instead of a general dashboard, I built a focused tool around two things a volunteer actually needs in the moment: knowing where the crowd is building up, and being able to communicate with a fan who doesn't speak their language.
