Being part of a company experiencing rapid growth is both gratifying and challenging. This growth, which brings new products, increased user adoption, and a significant boost in revenue, is a direct result of your collective efforts and the value you get to your users.

As the company expands, we must adapt and grow in sync, reevaluating our product development strategies and finding innovative ways to collaborate with other teams. Your adaptability and visionary thinking are not just important; they are the key to succeeding in this rapid growth period. With this new prosperity time for the company, new user needs, business opportunities, and new products start to arise, and with them, some issues may appear in the scene; in addition, some metrics, like time to market and fast user engagement, are more critical to reach for the company now than ever.

This “beautiful problem” will inevitably impact all teams, and sometimes, it reveals scalability issues in how we develop products and services. UX teams are no strangers to this phenomenon; as they are in charge of creating product experiences, they can fall into a design dynamic that is not very scalable or manipulable in the future. We called this dynamic: “the UX monolith scenario.” I’ll explain the concept in a few paragraphs ahead.

Similar to the front-end concept, a UX monolith is a user experience that is complexly connected and dependent on a whole; this makes its modification difficult because it requires reviewing and intervening in all the existing steps of the process once you want to change something. We stumbled upon this scenario and quickly realized all the experience inconsistencies we created for users. One example of the lousy result we were building was the multiple experiences of creating questions for all the products. Even though every product was different due to functionality and purpose, they shared joint experience challenges, like creating questions for users whether it was for an academic evaluation, survey, or assessment, so we decided not to move on with several design approaches but to create a unique question generator experience capable enough to support all products that may need it.