Uncategorized

Connect analytical work to business outcomes: a closer look at the new MyDataWork

Your team knows how to build a dashboard, reconcile a forecast, or improve a model. Explaining how that work supports the business often requires a separate effort: finding the right files, identifying who depends on them, and assembling a progress report from scattered notes. MyDataWork brings those connections into one workspace. It links analytical assets

Connect analytical work to business outcomes: a closer look at the new MyDataWork Read More »

What metadata only means, and why it’s the right depth

What MyDataWork holds about your estate, what it never holds, and why structure answers the questions your data can’t. “We only read metadata” reads as either reassuring or limiting, depending on where you stand. It’s good news if you’re trying to adopt something new without waiting weeks to clear a security review. It can sound

What metadata only means, and why it’s the right depth Read More »

See your whole analytics estate in one picture

Introducing Architecture & Value — the leadership view that turns the work your team already tracks into a single portfolio of tools, value, and dependencies. Deterministic, aggregate, and built for the team lead. A two-minute walkthrough of Architecture & Value, from the tool portfolio to the audited full-workspace view. A dozen tools, and no single

See your whole analytics estate in one picture Read More »

Start with a plan, not a blank page: Solution Packs in MyDataWork

Your data work has never had a home before. That’s not a criticism of your tooling — it’s the simple reality this product exists to change. The spreadsheets, queries, dashboards, and notebooks that run your part of the business live in folders and memory, and until now there’s been no system whose job was to

Start with a plan, not a blank page: Solution Packs in MyDataWork Read More »

Scope an AI agent before you build one: MyDataWork Agent Studio for data teams

Everyone is racing to give AI agents more autonomy. The hard part isn’t wiring an agent to tools — it’s deciding which agentic use case is worth building, which systems it needs, and what guardrails keep it safe. Agent Studio is the place you answer those questions, from the systems you already work with, before

Scope an AI agent before you build one: MyDataWork Agent Studio for data teams Read More »

Lineage Beyond the Warehouse: How MyDataWork Connects Work Across Tools

Most data-lineage tools are strongest where the work is governed, centralized, and platform-visible: warehouse tables, SQL transformations, dbt models, semantic layers, and dashboards connected to known sources. Inside that world, they can be genuinely useful. But a lot of analytical work still happens outside that clean boundary. It happens in Excel, in Alteryx, in local

Lineage Beyond the Warehouse: How MyDataWork Connects Work Across Tools Read More »

Your Assets Don’t Know Why They Exist: The Use Case Layer in MyDataWork

Open any analyst’s working folder and you will find the same thing: spreadsheets, SQL scripts, Alteryx workflows, dashboards, notebooks, a model or two, and a handful of exports. Each file is the product of real effort and real judgment. And not one of them can tell you why it exists. A file named dc_starting_inventory.xlsx does

Your Assets Don’t Know Why They Exist: The Use Case Layer in MyDataWork Read More »

Scroll to Top