--- ## What I've Been Noticing As I've been working in the world of [[data culture]], I keep encountering the term "data literacy." But what I'm actually observing in effective teams looks more like fluency and I think this distinction is important. - "Data literacy" creates a binary: you're either literate or illiterate; this framing misses what happens when people actually work with data well. ## The Language Learning Analogy Think about language: "I can read French" doesn't mean fluent. I can stumble through a menu, catch the gist of a news article. But fluency means: - Understanding idioms - Reading subtext - Recognizing sarcasm - Adapting to context ## What [[Data Fluency]] Looks Like Most people can "read" a dashboard or interpret basic charts. Maybe they've worked in spreadsheets, manage their own budget at home, or are a whiz at setting up inbox rules in Outlook (which is somehow still wildly clunky). Fluency is different: - Sensing which questions the data is asking - Recognizing when correlation hides causation gaps - Translating technical findings for specific audiences - Knowing what you don't know ## Why This Distinction Matters Data literacy sounds like checkbox completion. Data fluency develops over time, with practice, in context. You can't mandate fluency the way you mandate training. Fluency emerges when: - People feel safe asking questions - Experimentation with interpretation is encouraged - Admitting uncertainty is normalized - Data becomes ongoing conversation, not quarterly presentations What could change about the process of helping people navigate new digital changes if we frame capability as __developmental__ instead of __binary__? ## The Cultural Implication My opinion is that this shift re-sets the foundation of a house that's bound to sit crooked. It asks leaders to look at the skill holistically, allows employees to grow incrementally, and sets the goal posts where they ought to be: on confidence. ---