On the third day of dashboard week we were tasked with having a look at a fake clients database in snowflake, which consisted of a total of 500 billion rows all together. We had to use SQL to create data extracts to answer specific business questions.
Trying to learn from my mistakes from the previous day, I started by dedicating some time towards, making sure that I understood, the brief in the way that the client intended. To achieve this I spent 10-15 mins reading the brief and noting down anything I found unclear alongside my assumptions, and presented it to the client (Robbin) to clarify.
Confident I understood the brief in the way it was intended to be understood I then set out on exploring the documentation for the database and extracting the columns and primary keys that I thought would be necessary to explore the relationship between online orders and returns.
By 11:02, I recognized a gap in my understanding of the time required for SQL tasks. While confident in my ability to produce a reasonable Tableau output in 3.5 hours, the SQL side remained uncertain. I emphasized the importance of clear, presentable outputs as proof of concept and urged myself not to panic but to proceed systematically.
At 11:44, I stumbled upon a realization: not all questions needed immediate answers. I emphasized the need to assess the value of time spent and advised against pursuing non-essential queries. This insight became a cornerstone for efficient time management in a time-sensitive challenge like DBW.
By 12:14, I considered the importance of having an emergency escape option. It became clear that having a fallback plan, especially in moments of uncertainty, could mitigate stress and ensure a tangible output. Distractions were acknowledged, and a potential antidote was proposed—establishing clear goals for each step to maintain focus and purpose.
At 14:54, as my data extraction surpassed 250 million rows, I reflected on the role of a consultant. I recognized that the objective wasn't to achieve the impossible but to deliver maximum value per unit of time. This insight shifted my approach from attempting the unattainable to focusing on providing useful outputs within the given timeframe.
Considering the impending presentation at 4, I shifted from technical intricacies to a more practical approach. I identified columns for potential analysis, created a basic sketch, and extracted high-level figures. Recognizing my limitations, I aimed to produce a super minimum viable product to answer specific questions in Tableau. This approach, while not technically exhaustive, could provide a foundation for the client to build upon, aligning with their objectives.
In summary, today's experience involved navigating challenges, acknowledging limitations, and prioritizing value delivery. The shift in focus from technical complexities to practical outputs demonstrated adaptability and a commitment to meeting client needs within the constraints of time and expertise.