Note- this was part of the hiring assignment which I completed in 1 day

Life of a frustrated analyst:

Constantly create dashboards and visualizations that may not get used

• Business data requests often have a limited shelf-life. Hence, they only needed what they needed in that instance to get going with a decision
• Dashboards have a limited ability to add ever changing business context to explain what they thought the data results actually meant
• Collaboration was challenging on dashboards. Dashboards give them limited ability to collaboratively interact with the data together as a team and chat or question the data

Answering 'urgent' data requests

• “Hey! Sales are low in January, why do you think so? Did we also receive less demo requests in Jan? Let’s check?”
• “Hey the product usage from our free users spiked in March! That’s amazing, maybe the new feature did it or was it something else? Let’s validate?”

Going back and forth over numerous emails and Slack messages to explain the numbers

• Where the actual contextual knowledge lies and accumulates but is washed away
• “Something is fishy, can I trust this data?” “Who built it?” “Did it change recently? “hmmm, it somehow doesn’t look right? “ “How is this number calculated?” “Why did we choose this logic?” “Oh maybe it’s still referring to the ‘new_arr’ field we discontinued using from last week”

via Airbook blogs

Feature Conceptualisation

Unified experience for both data and revenue teams

• Airbook has made it easier for teams to collaborate on data to gather requirements, explain context through charts, understand underlying business logic, address follow up questions and export the analysis in any format together on a single page.

• But it’s still hard for an analyst to track all the incoming requests on Airbook which is currently through a notification system