I Got a Teams Message: 'Why Do We Need a Semantic Layer?'

It was Monday morning. Our team was sitting through a technical architecture meeting. I could see Sarah's face — confused, frustrated, checking her watch. When the meeting ended, I got a Teams message: "Hey, can we chat? Why are we talking about semantic layers with a fancy name? We have a data warehouse. We have SQL. We have Tableau. Why do we need ANOTHER layer? Isn't that just... more complexity?" I smiled. This was the question I get asked every few months. But Sarah's frustration was real — and valid. I called her immediately. "Let me tell you a story," I said on the Teams call. "Then it'll make sense. And stop you from thinking we're adding complexity just for fun." The Story: Revenue Doesn't Match Six months ago, our CFO called an urgent meeting. Marketing's revenue report showed $2M. Finance's revenue report showed $1.8M. Same period. Same data. Different numbers. Marketing's query: SELECT SUM(sale_amount) FROM transactions WHERE date >= '2024-01-01' Finance's query: SELECT SUM