Dataedo
Dataedo could do almost anything with your data. People just didn't come back to it. I was the only designer, and that was my problem to fix.
- Role
- Solo product designer · design system in code
- Company
- Dataedo
- Timeline
- Pending
- Category
- B2B SaaS · Data governance
One designer, a lot of product
Dataedo is where a company writes down what its data means. Which table is the real one, where a number in a report comes from, who to blame when it's wrong. Useful stuff. The kind of tool people agree they need and then forget to open.
That was the problem I walked into. Retention was weak. The product had grown for years on top of an old interface, and every new feature made it a little heavier. I was the only designer, so there was no one to split it with: the design system, new screens, old flows that annoyed people. All mine.
I started with the boring part
Redesigning screens one by one would have taken forever and fallen apart the moment I looked away. So I rebuilt the design system first and wrote it in code, not just in Figma. If the components were right, a developer building a new screen on a Friday afternoon would get it mostly right without me.
Most of it you'd never notice, which is the point. Pages stopped floating in the middle and lined up on the left. A handful of slightly different side panels became one. Tables stopped throwing every column at you and started with four. While data loads you now see the outline of the page, not a spinner and a prayer.
Then the menu
If you can't find something, it doesn't exist. The navigation had grown the way navigation does, one item at a time, and you needed a map to use it.
I cut it down. Assets got a single place. Data sources can go in folders, like files. Exports moved into the main menu. The sidebar tree shows the whole path at once. Long pages got a thin outline on the edge so you can see where you are without scrolling back up.
Hundreds of boxes
Lineage shows where data comes from: this report reads from that table, which is built from those three. In a demo it looks great. On a real company's warehouse it's hundreds of boxes and a plate of spaghetti between them.
I stopped trying to draw all of it nicely and started hiding most of it. Sources sit in frames. Objects that only pass data through fold away, so do internal flows. Loops get a small badge so you don't follow them forever. You open it, and the path you were looking for is the one you see.
Something to come back to
You can't design retention directly. You can give people a reason to open the tool on a Monday.
The home page now opens with what changed since you were last here, what's waiting for your review, and what you were looking at last week. Notifications had become noise, so I rebuilt them around following: you pick what you care about, and get a daily or weekly digest in Slack or Teams, grouped by object. Comments moved off a side panel and onto the bottom of the page they're about.
Where it landed
It shipped across the 26.x releases in 2026, while the last pieces of the old Desktop app moved to the web. The thing I'd point to isn't a screen, though. It's that the team now builds with the system, so new screens look like Dataedo even when I'm not around to check.