The MQM experience culminates with capstone, a hands-on learning project that gives students the opportunity to apply what we have learned to a real-world business problem. For my MQM capstone project, my team worked on a revenue optimization model for the FIFA World Cup 2026 group stage.

At a high level, we explored how matches could be allocated across host cities and stadiums in a way that maximized projected revenue while still respecting realistic tournament constraints. It was a chance to bring together analytics, business thinking, teamwork, and leadership while learning how to break down a complex problem tied to a global event that reaches far beyond the pitch.

A Practical Application of My MQM Skills

The project stood out to me because the World Cup is much more than a sporting event. It is a global business, logistics, tourism, and cultural event that has evolved dramatically over time. To build a useful model, we first had to understand the history of the World Cup, how the tournament structure has changed, how host cities are selected, and why venue allocation is more complicated than simply placing the highest-demand games in the largest stadiums. Factors like team popularity, stadium capacity, local market demand, travel patterns, tourism, and tournament rules all had to be considered.

The most challenging part of capstone was understanding the full complexity behind FIFA World Cup planning. At first glance, the problem sounds straightforward: predict revenue and optimize venue assignments. The more we studied it, the more we realized how many historical, operational, geographic, and commercial factors shape the tournament.

Our team then had to balance that real-world complexity with analytical ambition. We used data analysis, feature engineering, predictive modeling, and simulation to evaluate different possible match allocation outcomes. However, one of the biggest lessons was that technical skill alone is not enough. A model can be mathematically interesting and still not be useful if it does not reflect the actual decision-making environment. Throughout the project, we had to think carefully about assumptions, constraints, and how to translate our results into a practical business recommendation.

From Individual Contributor to Team Leader

Coming into the project with a strong foundation in analytics, the areas I grew the most in were project management and team leadership. One of the biggest challenges was learning how to identify my teammates’ strengths and help place people in positions where they could contribute the most. Some teammates were stronger in research, others in technical modeling, writing, visualization, or presentation. I had to think beyond just completing my own work and focus on how to help the team operate more effectively as a whole.

In a project with many moving parts, it is easy for the team to get lost in the details or duplicate work. I learned the importance of breaking a complex problem into smaller workstreams, keeping the team aligned, and making sure everyone understood how their part contributed to the final deliverable. That kind of coordination is not always visible in the final presentation, but it is what determines whether a project actually comes together.

A New Approach to Problem-Solving

Capstone changed the way I approach problem-solving. It reinforced the idea that strong analytics starts with understanding the decision, not just the data. Before building a model, I now ask: What problem are we really solving? Who will use this output? What constraints matter? What assumptions are we making? How can we make the final recommendation clear enough for someone to act on?

My advice for incoming MQM students is to treat capstone like a real client engagement. Do not just focus on the technical output. Focus on the problem, the team, the assumptions, and the final story. Start early, communicate constantly, and learn your teammates’ strengths. The best projects come from teams that know how to combine technical analysis with clear communication and strong project management.