EVNTO

The problem

At Mansoura University, activities run by different volunteer teams and IEEE societies had no shared home — students had to track each team’s own channel to find and book anything, with no single place to see what was happening across campus. EVNTO, built with the IEEE Vectories team, was our attempt at that missing centralized layer.

Constraints

This was a student-team concept project rather than a funded product build: our evidence base was a competitive review of similar booking/event apps plus a survey we ran among students, not a live pilot with real bookings. The resulting report was meant to justify and steer a build, not to report on one that had already shipped.

What I did

I worked on the research that shaped the product decisions: reviewing how comparable activity/event platforms handled discovery and booking, then running and analysing a student survey to check which of those patterns actually mattered to our own campus audience versus which were just assumptions. Those findings fed directly into the recommendations for how EVNTO’s booking flow and information architecture should work.

What I’d credit

The concrete output was the research report and its recommendations, which the team then used as the basis for prototyping — I don’t have adoption or usage numbers to point to, since it stayed at the concept and prototype stage. What stuck with me was how much a “just build it” instinct benefits from being slowed down by even a small, deliberately-designed survey first.

Team repo on GitHub.