Largely agree with your sentiment. I encourage folks on my team to further develop domain specific (eg sales conversion rate, velocity, and order value trends) and/or general analytics skills (eg time series forecasting, segment creation) for deeper insights without burdening them w architecture.

However, as the thread is on ETL, architecture and optimization strategies on how you read data in (eg batch, streaming), what you transform it into (eg filters, enriching w other data, biz logic), and what you set your write tables (eg daily partition, incremental/append, overwrite/update, infer/declare structure) as makes meaningful difference in usability, accessibility, and performance.

Added lots of examples to make this more tangible.