Google Data Studio in 10 Minutes: Step-By-Step Guide
datascience-school.com
datascience-school.com
Data studio is a little too technical for most people, but not technical enough for another large group of people. It like photoshop + pivot tables. It works incredibly well for a small set of people who are semi-technical, already know how to analyze data, and have some graphic design senses. I expect google to kill it eventually, or integrate it into analytics/google ads/dbm/etc and kill the spreadsheet integration.
Ironically the CTO wanted a format that lacked reproducability
A core concern of mid/upper level management is sustainability, reproducibility, and maintainability of processes. The CTO wanted a format that could be reliabily reproduced by the skill sets that were staffed, even if the report itself was less robust than the Data Studio version. By introducing a new capability to a client, the CTO is in a bind to either adjust staffing to ensure deliverability of that capability or potentially risk losing a client if they ever have to switch back to the previous reporting after having elevated the clients expectations.
And the issue expands beyond that one client. It can potentially disrupt the expectations of other clients, and shift internal demand away from the types of reports your existing staff are capable of producing. And that's a huge can of worms since the demand may shift faster than attrition, leaving the CTO in the uncomfortable spot of having an existing staff with a rapidly dwindling internal demand and yet still needing to aggressively hire for the newer skillset.
If it had been used internally, rather than being exposed to the client, then it probably would have been received better by the CTO.
A technical analogy would be the CTO learning that a manager had approved exposing an unofficial API to important external users, and that the users loved it. So then you either piss the users off by taking it away and shifting them back to the cruddy old official API, or suddenly have a need to put resources behind ensuring that unofficial API is up to snuff and matches the same SLA with your official one.
Data Studio fits squarely in this market of tools for them, and that space is growing and pretty crowded. There a multiple big businesses built on producing tools just like that, for example Tableau (public company valued at ~10B as of today).
Granted, Data Studio is more basic but it is free and nicely integrates with the rest of Google data product suite (Analytics, Sheets, BigQuery). I don't think it will go away, and I think it is actually the strongest part of google cloud offering (and the biggest gap in AWS cloud product lineup).
AWS has a similar product, QuickSight[1]. It's not my favorite to use, but integrates with the AWS ecosystem as easily as Data Studio integrates with the Google ecosystem.
Besides, without something like Google Sheets or Excel it is not that useful, inevitably you have a ton of small data across the org that is stored in spreadsheets.
One obvious play for Amazon is to just pay a ton of cash and acquire something like Airtable, but they don't seem to be for sale.
So, who is datascience-school besides a location in Singapore? Who are the founders, who else is involved, what are their stories/history and motivations. All of this would lend some credibility to any organization.
So I'd like to see Google's stories/history and motivations.
> Data Science School offers online data science and engineering courses with practical assignments.
If Data Science School is going to give their personal information to someone and potentially take their money, Data Science School wants to know who they are.
Data Set Configuration Error
Data Studio cannot connect to your data set.
Failed to fetch data from the underlying data set
I wish the error messages would be a little more helpful.
Here’s a link to steps where you can confirm whether billing is enabled for this project and enable it if needed.
https://cloud.google.com/billing/docs/how-to/modify-project#...