Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics.
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
We need shared definitions to tell meaningful stories with our data. And then use a company specific example like how a customer's journey can not be understood with differing definition between marketing and sales. The marketing team can't measure the quality of the leads they're producing unless they can directly link a customer's whole journey from acquisition to churn. Otherwise it's just vanity metrics. But don't be too harsh, vanity metrics are really common in business. A company needs strong data leadership to create a culture of using data to justify decisions to a culture of using data to inform decisions.
Definitely try to use examples to help them get a glimpse into the issue. I like to explain documentation errors by pointing out when what are supposed to be sequentially recorded timestamps are recorded out of order in my work’s database. Sometimes the data quality isn’t there.