Skip to main content
or read the full transcript

Live demos

Want to watch a live demo?

Atlan engineers bootstrap, test and deploy enterprise context on real data.

About this session

3 min1 speaker

Natalie explains why lineage down to the column won HelloFresh's evaluation, along with clear owners and descriptions. After two earlier catalogs, teams expected another tool nobody would use, so during the POC her team worked with personas across data domains to understand their use cases and pain points first.

Full transcriptSearchable

Natalie Hallak

0:05 So like, like I mentioned at the beginning, for us the, the key, the main big thing was the data lineage, right? But not from like a, a high level, but all the way to the column details. And then one of the things that we saw during the POC is we had more than 10, if not 15 different ways of calling customer name, right? So we realized that the way we were standardizing even columns was completely different from, from team to team. But the data lineage was one of the biggest winner compared to the other data catalog we saw even during our POC, right?

0:45 The data lineage was the most important, just to have that understanding of where's the first point of entry of the data all the way down to which dashboard it's, it's being used. And you know, just having the, the right owner and the right understanding of description was quite key for us. So I would say this is one of the biggest differentiator. I mean, I, I... There's a lot more, but yeah, this was a key thing for us. Initially, we, we had quite a bit of resistance because we actually had two previous data catalog before moving to Atlan.

1:22 So a lot of the initial thought is, "Okay, here we go with another data catalog, which I might never use." But one of the things that we've done during our POC was to engage with different personas across different data domains team, right? To, to really understand the use cases, the pain points in order to bring that into, into the POC. And this started to excite quite a lot of, of people, right? And that facilitate a lot of the choice for us to go with Atlan compared to, for example, other data catalog where we've done also a POC for.

2:05 So really, I would say really understanding the different pain points of the different personas because a data engineer will have different problems than, you know, from what the business is looking for. We used to get quite a lot of Slack messages saying, "When can I use Atlan?" Or some people were already seeing the value of Atlan during the POC itself.

Back to the video