The buzz around data and artificial intelligence (AI) often overshadows a fundamental truth: the core of any successful endeavor remains distinctly human. As businesses navigate the complexities of the digital age, the importance of human insight, empathy, and value-driven strategies becomes increasingly evident.

The concepts of taxonomy and folksonomy hold significant implications, especially in the context of emerging technologies like OpenAI. While traditional taxonomies offer structured hierarchies of knowledge, allowing for a systematic approach to information organization, folksonomies represent a more fluid and emergent way of categorizing information based on user-generated tags and metadata.

However, the challenge arises when technological advancements fail to incorporate divergent thinking and promote groupthink through convergent taxonomies. This phenomenon is particularly evident in language models, where developers' linguistic and cultural biases can influence the interpretation and representation of (the dominant) language.

When driving data projects, you will encounter business stakeholder challenges that often go unspoken. This is not always because people hold back but because they don't fully know how to vocalize their constraints.

If they can't directly address their requirement, chances are we can't either. To hear others' speech, we start by asking questions from different perspectives.

Change management wouldn’t be so hard if it weren’t for…the people. Open issues or objections left unresolved today cost time down the road. Suppose work starts before these concerns are mitigated. Stakeholders might get frustrated or begin to hold back their participation. Work produced might have difficulty getting implemented. Buy-in realizes impact.

It can be challenging when stakeholders cannot translate business questions into technical requirements or do not provide enough context for data teams to do so. From there, the data team is often left to maintain the status of a series of ad hoc projects rather than connect these business questions to a larger more defined data strategy.

Most data teams cover WHAT and HOW with standard reports and KPIs. They will optimize processes and analyze business domains impacting the company's bottom line from a data perspective.

But how many data teams truly understand the WHY behind the reports they generate? How many actively consult with the business as a true partner to understand the underlying business concerns behind the numbers? Without the WHY, delivering true value in the WHAT and HOW is ten times harder.

When defining needs is ignored, it can stifle progress faster than the stickiest government red tape. For example, when we cannot translate our business requirements into data or more technical requirements, we lose the ability to make informed decisions. Or, when we lack the courage to confront the poor content of a colleague, we lose the collective ability to influence as a team and move the group, initiative, or business forward. Guess what? That was in our control, too.

CURIOSITY 101

Curiosity starts with empathy. Bring curiosity wherever we go to increase possibilities for connection and creativity.

COHESION 101

A genuine consideration and regard for others that makes the group stronger and more resilient.