The Problem We Were Actually Solving
We had invested a significant amount of time and resources into creating a robust and user-friendly interface for THE, which made it very easy for operators to search and optimize for their players. We thought we had solved the age-old problem of usability in complex systems, but we were actually creating a new problem: over-reliance on search volume metrics.
What We Tried First (And Why It Failed)
We first tried to address the issue by providing more information about the current search volume metrics directly in THE interface. We hoped that by giving the operators a clear view of the numbers, they would be able to make more informed decisions about optimization. However, this approach quickly revealed a fundamental flaw in our design. The operators were using these metrics to make decisions without taking into account the actual context of the game. They were optimizing for the wrong things and, in some cases, even causing more problems than they were solving.
The Architecture Decision
At this point, we realized that our architecture decision to focus primarily on search volume metrics had created a blindspot in our system. We were relying too heavily on a single metric to guide our operators, and it was not giving us the desired results. We needed to take a step back and reassess our approach.
What The Numbers Said After
We decided to take a data-driven approach to understand the problem better. We analyzed the search volume metrics, the time it took to optimize for each player, and the overall player engagement numbers. What we found was surprising: the operators who were getting stuck in THE configuration were actually the ones who were using the search volume metrics the most. They were optimizing for high search volumes, but it was not translating to better player engagement.
What I Would Do Differently
If I had to do it again, I would approach the problem differently from the start. I would focus on creating a more holistic view of the system, one that takes into account multiple metrics and context-specific information. I would also make sure to involve the operators in the decision-making process earlier on, so they have a better understanding of the goals and constraints of THE. Finally, I would prioritize education and training for the operators, so they can make more informed decisions about optimization.
The blindspots of search volume metrics in THE configuration were a valuable lesson for us. It taught us to be more mindful of our architecture decisions and to prioritize a more holistic approach to system design. It also highlighted the importance of involving operators in the decision-making process and providing them with the necessary education and training to make informed decisions.
Top comments (0)