Why?
- It saves time in reviewing stats daily & allows for quicker cross-matching.
- It provides stakeholders real-time access to progress on OKRs without pinging you.
- it's powerful in creating alignment with leadership during business reviews.
1. Use a tool that hooks into all your data sources like sheets, analytics, CRM etc. I personally use Google Data Studio which is pretty easy to setup.
2. Learn the purpose behind each visualization type. Using the right visual for the job can make recognizing trends/anomalies so much easier.
E.g. Use a line chart for time-driven trends, bar chart for categories, tables for leader boards, pie charts for items with a few values.
3. Invest time early on to ensure the report scales. As you add more values, update records, create more categories etc., your dashboard should consume that without re-configuration.
5. Always conduct a sanity check through random sampling.
6. Reporting widgets should match the laid out OKRs & product north stars. Avoid bloat & vanity metrics. Too many dials spoil it.
7. Always think about segmentation. Aggregates are insufficient (& often misleading).
As a Product Manager, you might be asked a lot of questions during an interview. One of them includes technical questions. Here are 4 types of technical questions that you might come across.