This message was deleted.

Ooh good question. I absolutely love that we can have a shared source of truth for data. Our previous solution was “try to search for documents in Google Drive - I dare you.” It wasn’t working well for us, but Secoda is now our source of truth. Anyone who wants to know anything about our data resources has only one place to look for answers.

The general idea of "the Notion of data documentation" would be one, but a small thing that I'm finding really valuable is the ability to @ tag resources. For example when I'm writing a description of some table/view in our data warehouse, I will @ tag the primary source table from our production database. As more ELT/ETL integrations are put in place sure you'll be able to see this in lineage, but I like being able to quickly navigate; for example this is a description of a view in bigquery which primarily gets its data from our production postgres

users

table:

although I’m inherently biased on making the data team more productive, we chose and adore Secoda because the ux is focused on delivering understanding to the stakeholder/end-user. collections enriched with different types of resources help bridge the technical understanding in a friendly way. youre never more than 2-3 links away from finding out “what happens with data”

I believe that the existing integration of different functionalities in Secoda makes a difference. Analysts want to answer questions; the relevant tables & columns to do so are only vehicles - the ability to link Q&As to given resources provides way more context than mere table & column descriptions could do. Plus it helps to draw analysts into the ecosystem of Secoda for data related Q&As. Otherwise the discussions will happen in Slack (or any other messenger tool) and the tribal knowledge will most likely not make it into the data catalog.

On my side, I love the Dictionnary functionnality. All words and terms used on daily basis at Kard ("User", "Active User", .... ) are defined and linked with a sql formula to compute or retrieve the information. When one of these word is used during a presentation, the link towards the secoda entry is included in the slide. We all aligned and speaking about the same thing. There are also collections helping us grouping words and kpis by team but you said one thing 🙂

Same with @chilly-pillow-52933. Currently we are focusing on dictionary implementation to make alignment between metrics definition. From the users, they love to use Slack integration so can easily to find the definition of a metrics when needed.

We are still in the process of getting Secoda fully implemented and rolled out but one of the biggest draws for us was the friendly user interface. Getting business users engaged will help us be successful so we are hoping this will help drive great adoption. 🙌

Hey All Thank you so much for all the great feedback! It has been a very busy couple of days so far with the traveling and workshops at our offsite, but the things highlighted here are very helpful and we’ll be sure to keep them top off mind when having the Secoda discussions with our colleagues!