One way MyDataWork makes a difference in your data work
The Tableau workbook is where exploration lives. A sales VP filters the executive scorecard by region and finds a territory that’s been underperforming for two quarters. A marketing analyst slices campaign performance by channel and segment to figure out why last month’s spend underdelivered. An operations lead drills into a service-level dashboard and traces a delay back to one upstream process. The interactivity is the product — not the chart, but the path a user takes through it.
That path is built on a foundation Tableau itself manages well. Tableau Catalog shows you the data sources powering your workbooks, the upstream lineage from connection to dashboard, and impact analysis when sources change. Tableau’s Data Management capabilities extend that further into governance over published data sources, certified content, and connection metadata across your Tableau Cloud or Server estate.
All of that is real value. It also defines a boundary.
Outside that boundary sits a different category of dependency — the things your workbook is built on that Tableau Catalog was never designed to see. The Alteryx workflow that prepared the customer feature set before it landed in your extract. The Power BI dashboard a parallel team built for the same audience, or the second Tableau workbook a sibling team built without coordinating. The CSV of NPS responses your CX research partner exports from the survey tool every month and drops in a shared folder. The Snowflake table that’s part of an upstream pipeline. The Python notebook where a colleague built the churn model whose output drives the segments you visualize. The stakeholder spreadsheet capturing who depends on each dashboard and for what decision.
What’s missing isn’t lineage to named data sources — Tableau Catalog handles that well. What’s missing is the working context around the dashboard: what it’s for, who’s depending on it, what outcome it’s trying to move, and how it connects to the artifacts living outside the catalog’s reach — the CSV that arrives via shared drive, the model output that arrives via extract refresh, the decision the dashboard is meant to inform but that isn’t documented anywhere in Tableau itself.
That working layer matters more now than it used to. AI agents are increasingly being given access to corporate data estates with the promise of answering analyst-level questions across them. The catch: an agent that can read your governed catalog but doesn’t know which dashboard drives which decision, who depends on the CSV upstream, or what outcome a use case is trying to move will give confident answers to the wrong questions. The context AI agents need to give useful answers is exactly the working context that governed catalogs were never built to hold.
That’s the gap MyDataWork fills. It catalogs your .twbx workbooks and published data sources alongside the Alteryx workflows, Power BI files, Excel models, Python notebooks, Snowflake tables, GitHub repos, and dbt models that surround them. Using asset metadata and connection signals — without analyzing business data inside the files — it infers multi-hop lineage across all of them, so you can see a Tableau dashboard, the Alteryx workflow that prepared its features, the SQL join step in between, and the Snowflake source table behind that, all in a single explorable graph. Adjust the depth to show one level of connections or several. Click any node to refocus on it and walk the lineage outward from there. Zoom, pan, and export the graph when you need to share it with stakeholders.
Lineage inferred from asset metadata and connection signals across Snowflake, SQL, Alteryx, CSV, and Tableau — one explorable graph, with adjustable depth and click-to-refocus.
Lineage is one piece. Around it, MyDataWork lets you document the use case each dashboard supports, the stakeholders depending on it, the measurable business outcome it serves, and the progress toward that outcome — all in the same workspace as the assets themselves. The agent surfaces observations a human might miss: a Tableau workbook that’s become hidden infrastructure across multiple use cases, a recently-added asset nobody has linked to documented work yet, a use case with no stakeholder assigned.
Agent observations across the workspace: a Tableau workbook referenced across multiple use cases, a new CSV asset that pattern-matches an existing use case, and a use case missing a stakeholder.
MyDataWork isn’t a replacement for Tableau Catalog. It’s a complement, focused on the working layer — the practitioner’s view of which assets connect to which decisions, who depends on what, and where the business value lives. Here’s where it lands for a Tableau-centric analyst. The next time someone asks an impact question that crosses tool boundaries — if I change the segmentation logic, what dashboards and decisions get affected, and who do I need to tell? — you stop reconstructing context from memory, Slack history, and shared drives. You open one record.
A use case in MyDataWork: objective, target outcome, and baseline-to-target progress — documented alongside the assets that support it.
A 90-day free Explorer plan gets you started now. No credit card. Bring your email and you’re working in minutes.