Mistakes I made as the head of analytics (and what I’d do differently now)

Kyle Salomon reflects on his tenure as the head of analytics and data engineering before joining dbt as a solutions architect, where he learned valuable lessons from mistakes made during his previous role. He emphasizes the importance of continuous learning and staying ahead of platform updates, which he failed to do, resulting in underutilization of tools like dbt. He advocates for distributed ownership of vendor relationships and a proactive approach to new features and paradigms. Salomon also regrets not adopting a more modular and decentralized project architecture, which could have empowered domain teams with greater autonomy. He highlights the pitfalls of sticking to outdated data architectures and job orchestration methods, advocating for more dynamic, trigger-based processes. Additionally, he underscores the necessity of treating infrastructure as code, adopting rigorous governance practices, and maintaining a fail-fast, experimental mindset even when scaling teams. Salomon concludes that dedicating time to explore the full potential of available tools is crucial to achieving compounding value.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.