![rw-book-cover](https://substack-post-media.s3.amazonaws.com/public/images/67005d2b-aa5f-4d79-b4ee-228b80544369_2766x2766.jpeg) ## Metadata - Author: [[Ergest xheblati|Ergest Xheblati]] - Full Title:: Good Questions Bad Questions - Category:: #🗞️Articles - URL:: https://sqlpatterns.com/p/good-questions-bad-questions - Finished date:: [[2024-10-21]] ## Highlights > It’s a well-known fact that many data teams are overloaded with requests. Everyone is trying to validate some hypothesis, get a report or dashboard made or quench some curiosity. Since we don’t know the cost of each question — and the data team isn’t voicing their concerns — we feel like we can ask anything. ([View Highlight](https://read.readwise.io/read/01jappw5gy00t48zkdd139557z)) > What to you as a leader might sound like an interesting question, to the data team it’s either an hour worth of effort to run some queries or a two week effort to build a brand new pipeline to bring data into the data warehouse, clean it, model it and then run a query. ([View Highlight](https://read.readwise.io/read/01jappwbbnd001fj77zyya2a9x))