The following are three examples of ad hoc requests you might get as an analyst and examples of how you might communicate your findings (Note: These are not the same requests you will respond to in the project). In the real world, these short reports would likely be included in an e-mail, but for the sake of this Project, you will organize your findings as multi-line comments in a SQL file.
Reporting just the facts:
I need to send a quick status update to our Growth Team this morning on how our groups are doing. I'd like to know the average, minimum, and maximum number of members in our LetsMeet groups.
Thanks for your help!
Since Cat simply asked you to report back with some numbers, your response might include a bullet-pointed list like the following:
Reporting quick insights:
Engineering is looking into a bulk event uploading feature to support some of our more active groups, but before they add the feature they need some information. Do you have any insights into how LetsMeet groups are uploading their events currently?
Look forward to hearing your thoughts!
Isabella didn't provide too many details about the numbers she is interested in but did ask you to provide some insights into how users are uploading their events. After performing a short exploratory analysis, the information you communicate back to her might look something like the following snippet:
Making a recommendation:
Hi again! Thanks for the information on your bulk event uploading findings. As a follow-up, can you make some recommendations on groups we should target for beta testing the bulk event uploading feature? I'd love to hear your thoughts once you've had a chance to dig deeper into the data. Can you get this to me by EOD today?
In this case, you need to not only provide insights into the data but also make recommendations based on your findings. This might look something like the following: