From Rush to Reflection
Recently, we experienced a valuable lesson during the launch of our product's web version. We released the first version for internal testing, and while I was satisfied with the mobile experience, the desktop version aesthetically bothered me in some aspects. It felt as if there was a grid, but it resulted in a fragmented layout with elements feeling like isolated islands, and oddly, a "scroll shore" protruding in the middle.
However, some team members made logical arguments:
I accepted their reasoning, and we proceeded to prepare the product for release, acknowledging the solid point about mobile optimization. But something kept nagging at me. In the rush of morning calls, I didn't have time to fully consider it, but in the evening, upon reflection, I requested a check on the usage statistics for our mini-app in Telegram (fortunately, we had logged traffic data), especially since the web version was mainly intended for LinkedIn use. To our surprise, desktop traffic accounted for 40-45% of the total, which was unexpectedly high!
领英推荐
Debriefing with my colleague, who based his argument on experiences from a previous project, we concluded that it's unwise to ignore relevant data about the product. While experience and knowledge are valuable and can often save time, they can sometimes be irrelevant. If there's a way to verify these insights, why not do so?
For myself, I noted the importance of revisiting decisions made under pressure or emotional stress, analyzing the assumptions behind them, and creating situational triggers for the team and me to better understand and apply our experiences. Writing this post is a way to internalize the situation and increase the likelihood of timely responses in the future.
Do you revisit your decisions?
P.S. Connect with me on MindShare for a personalized consultation