The BI Workbench

About

I'm a BI developer. For about ten years I've built the reporting layer that people actually make decisions with: Tableau workbooks, SQL, data models, Snowflake warehouses, and the Alteryx pipelines that feed them.

The work has run across healthcare and life sciences, consumer goods, and now manufacturing — logistics, supply chain, operations, and dashboards for a cybersecurity team tracking asset risk and remediation. That last one taught me more about access control than any course did.

Day to day it's Tableau and Power BI, SQL against Oracle, Snowflake, Teradata and SQL Server, and a fair amount of time spent on the least glamorous question in analytics: why is this number different from the other report's number.

Why write any of this down

Partly selfish: explaining a decision forces me to check whether I actually understand it, and half of what I know about performance tuning came from writing up an explanation that turned out not to hold.

Partly because the useful lessons are hard to find. There's no shortage of "how to build your first dashboard" content, and a great deal of it is written by companies selling training. There's much less about what happens in year three, when the original author has left, the source table has been renamed, and someone needs to know whether the report is wrong or the business is.

What I write about

Background

Master's in Computer Science, Governors State University. Certified Tableau Desktop Specialist. Most of my career has been in Tableau development and application architecture, with Power BI, Alteryx and Snowflake alongside it.

What you won't find here

On money

This site isn't a business, but it isn't a hobby I'd like to lose money on either. If it ever covers its costs and a little more, it will be through two things: clearly-labelled affiliate links to tools I actually use, and a paid template or workbook pack if enough people ask for one.

What it won't be: sponsored posts, paid reviews, or a recommendation I wouldn't have made for free. The writing comes first, and if the money never arrives, the site still does its job — so there's no pressure to bend an article to make a sale.

On mistakes

If something here is wrong, or doesn't match how your organisation works, that's worth knowing. The version of this job that exists in one company is not the version that exists in the next.

Email is the best way to reach me: tulashobhan@gmail.com.