Case file 002 · Astrato, by Vizlib · three years · two pods
Astrato, three years inside a data platform
Shad Abbaslou · Product Design Lead · Hands-on across AI, Agents and Workflows
20 min read · 14 min skimmed · 48 slides


Rebuilt & running · fictional data
Astrato · the workbook builder
Filter the dashboard, select an object and restyle it, ask Ana about what you are looking at.
The brief, in three lines
- Whatthe workbook builder, join canvas and AI assistant of a Snowflake-native analytics platform
- Fordata teams turning their own warehouse into models and dashboards
- Problemthe canvas where every model begins had been filed as a bug
The teams
Two pods, 29 people, one designer between them
A decision made on the preparation side turns up on the visualisation side as a chart someone has to read. Being the only designer on both pods meant carrying that context across: three years of making two halves feel like one product.
THE PRODUCT, NOT A PICTURE
A walkthrough, 28 seconds, recorded from the rebuild. The workbook, step by step: a filter, the data model, Insights answering with its SQL, the answer kept, the event log and the preview. Each step is captioned as it happens, and the transcript has the same words.
Phase 1 of 4 · widenThe problem
What was wrong, who it was hurting, and how we found out.

The join canvas
VK-4532 · Join canvas · usability problems
The problem arrived as a ticket. The fix was geometry.
- Messy join lines, overlapping diagrams
- One-directional left-to-right line connections only
- No expand / collapse on tables
- No zoom on the canvas
- No indication that a table exists out of view
"Messy overlapping join lines" JIRA VK-4532 · THE PROBLEM AS FILED

Research · 6 moderated sessions
Four of five called it easy. I watched their eyes to be sure.
Think-aloud sessions on UserTesting.com, with attention heatmaps over the canvas, because where people actually look while building a join is not always where the interface assumes.
Research · 6 moderated sessions
The research programme, and where it landed.

Research · 6 moderated sessions
Protocol · Think-aloud
watching where the canvas surprised people

Research · 6 moderated sessions
Recordings · 2 in the deck
Think-aloud sessions on UserTesting.com, with attention heatmaps over the canvas, because where people actually look while building a join is not always where the interface assumes.

Research · 6 moderated sessions
Recordings
sessions 4668969B and 4668969E, 26 and 20 minutes

Research · 6 moderated sessions
Heatmaps · Attention
Attention gathered on the data list at the left and on each table’s header; the join lines, the thing the canvas exists to show, drew far less. So the rebuilt canvas names each table’s joins under its header, where people were already looking.

Research · 6 moderated sessions
Heatmaps · Attention
where people actually looked while building a join
Task difficulty after the redesign
4 of 5 participants rated it 4 / 5 towards "very easy"
4 of 5 answered 4, one answered 3, nobody answered 5 95% interval for 4 of 5: 36% to 98% A strong signal and a weak statistic, which is why the page never turns it into a percentage
Research · 6 moderated sessions
The task, the question and the heatmaps, and what they found
5 participants
What it foundSet on the redesigned canvas, the one the product runs, where a join takes four clicks; one task and one question were the whole evidence base
5 participants
What it found4 of 5 answered 4, one answered 3, nobody answered 5 95% interval for 4 of 5: 36% to 98% A strong signal and a weak statistic, which is why the page never turns it into a percentage
The moderated sessions
What it foundOn the data list and the table headers, much less on the lines; each table now names its joins under its header, and hovering one lights its line
Phase 2 of 4 · narrowThe decision
The one thing worth fixing, and the rules we set ourselves.
The join canvas
An analyst who cannot read a model does not file a bug about it; they quietly build a second one. That is what the join canvas was costing, and it is why the redesign started with geometry rather than styling.
The flow · end to end
The whole model lives or dies at one decision: can an analyst read the joins they just made.
The blueprint
The join canvas
Astrato Insights
An assistant that answers a data question with a chart asks people whose whole job is querying data to trust a black box.
Pick the fields it may draw on ("based on 144 fields"), type a prompt, get measures, dimensions and SQL blocks back. The design position that mattered: the SQL stays visible and editable at every step. For people whose job is querying data, hiding the query would have broken trust.
How others show their working
Every assistant that writes queries for analysts has to decide how much of the query to show. What each of these shows, from its own documentation.
Showing the working, assistant by assistant
The SQL it generated for the question
What the analyst can do with itEdit it, rerun it, and save the pair to a repository of verified queries the assistant draws on next time
The search tokens the question became: the measures, attributes and filters
What the analyst can do with itEdit the tokens; the documentation asks users to check them before sharing an answer
A DAX query, with comments
What the analyst can do with itRun it, keep or discard it, and ask for it to be explained step by step
The fields in scope, then the answer, its blocks and its SQL, as three views of one thing
What the analyst can do with itChange the scope, edit the SQL at any step, and add the answer to the sheet as an object they own
Phase 3 of 4 · widenThe work
What we drew, tried, threw away and kept.
The join canvas
The redesign fixed the geometry first: joins route around tables, connect from any side, snap to a grid, and creating one takes 4 clicks.


The join canvas


Rebuilt & running · fictional data
AS-06
No join label is covered by a table or crossed by another join.

Astrato Insights
An AI assistant that shows its SQL
Pick the fields it may draw on ("based on 144 fields"), type a prompt, get measures, dimensions and SQL blocks back. The design position that mattered: the SQL stays visible and editable at every step. For people whose job is querying data, hiding the query would have broken trust.
Astrato Insights
Astrato Insights
Seven seconds, recorded from the rebuild. Insights is opened and asked for MRR by region. It answers in its default view, four regions ranked, then shows the SQL that produced the answer, open to edit, with Add to sheet beneath it.

Rebuilt & running · fictional data
AS-04
Insights and Ana read only what the sheet shows.

Rebuilt & running · fictional data
The SQL is not a disclosure panel opened after the fact; it is present at every step, and editable.

Astrato Insights
Every assistant that writes queries for analysts has to decide how much of the query to show. What each of these shows, from its own documentation.

System & handoff
Specs shipped as designed
Every new component is a maintenance cost someone pays later, so new ones appeared only when an existing one genuinely couldn't stretch. With eighteen engineers across the pods, precision in the spec was cheaper than conversations after the build.

System & handoff
Sixteen screens of the workbook editor, one system underneath.

Rebuilt & running · fictional data
Every dashboard in the product starts in the join canvas
The model is the load-bearing layer: every sheet, every answer and both exits sit on it.

Rebuilt & running · fictional data
AS-05
Publishing snapshots the workbook, and any version can be restored.
Phase 4 of 4 · narrowWhat shipped
What went out, what it changed, and what I would do again.
What was broken · what changed · 01 of 06
Join lines crossed tables they had nothing to do with, every connection was forced left to right, and reading a model meant untangling it first. It was on file as VK-4532, affecting BI developers and data analysts.
Rebuilt the canvas geometry rather than restyling it: joins route around tables, connect from any side, and snap to a grid, and creating one takes four clicks.
4 of 5participants rated the join task 4 out of 5 towards “very easy” after the redesign.USERTESTING, 6 MODERATED SESSIONS
What was broken · what changed · 02 of 06
The canvas complaints were opinion, argued release after release, so nothing was prioritised.
Ran think-aloud sessions on UserTesting.com with attention heatmaps over the canvas, so what people looked at while building a join became evidence rather than a claim.
6moderated sessions, two of them in the deck at 26 and 20 minutes. The clutter stopped being an opinion and became measurable.SESSIONS 4668969B & 4668969E
What was broken · what changed · 03 of 06
An assistant that answers a data question with a chart asks people whose whole job is querying data to trust a black box.
Kept the SQL visible and editable at every step (Default, Block and SQL views of the same suggestion), and made the field scope explicit up front: “based on 144 fields”.
Insights shipped as something its users can check: nothing is returned that cannot be opened, read and rewritten by the analyst it was generated for.ASTRATO INSIGHTS, AS SHIPPED
Outcome
Three years, one coherent product
4 clicks, down from a maze that forced every connection left to right
Met4 of 5 participants rated it easy, across 6 moderated sessions; a strong signal from a small sample
MetThe SQL stays visible and editable at every step of Insights
MetNot measured; the hindsight below says what I would change, and the plan after it how
Not measuredOutcome
Three years, one coherent product
Outcome
What I would do differently
- Spend more of the years on what does not age. Most of what I shipped in three years has been touched by someone else since; the work that compounded was structural. I would have moved to the model and the canvas sooner.
- Measure the bill, not only the task. The case for the canvas was the duplicated dashboards and the query bill they ran up, and the research measured how easy the task was. I would instrument the bill from the first sprint.
- Run more than five sessions before quoting a percentage. Four of five participants rating the task easy is a strong signal and a weak statistic.

Rebuilt & running · fictional data
AS-02
Three years, one coherent product
A filter applies to every object on the sheet and says how much of the data is left.
THE PRODUCT, NOT A PICTURE
The finished product, running
Filter the dashboard, select an object and restyle it, ask Ana about what you are looking at.
Open it full screen ↗
Case file 002 · Astrato, by Vizlib · three years · two pods
Questions
Three years, one coherent product
The other decks001 · OI·DS003 · Safe Space004 · Novo Nordisk005 · JBS