I’ve always identified as a data scientist, but by working in a design-driven field like interactive media and communication has made that label feel both accurate and incomplete at the same time. In more traditional environments for data scientists, the role is relatively straightforward. You build models, test hypotheses, optimize systems, and evaluate outcomes through clear, quantitative metrics. The work is structured, and the feedback loops are tight.

In my current environment, that structure is much looser. Instead of a direct line between model and outcome, my work sits inside longer chains of interpretation. I might analyze behavioral data or build a segmentation model, but the result rarely ends at a technical output. It moves into design discussions, user experience decisions, and narrative choices that extend far beyond the scope of the analysis itself. Once my work is handed off, its influence is still there, but it becomes embedded in something larger and less visible.

That difference changes how success is defined. In more conventional data science roles, success is often measurable in ways that are easy to benchmark. In design contexts, those metrics still matter, but they are not sufficient on their own. A model might be considered successful not just because it performs well statistically, but because it helps a design team see user behavior differently or rethink an interaction flow. The value is real, but it is distributed across interpretation, collaboration, and implementation rather than contained in a single number.

This is where the comparison with peers becomes complicated. Data scientists in more technical environments often have clearer markers of progression. Their contributions are easier to evaluate in isolation: model improvements, production deployments, research outputs. It is not less rigorous, but it is harder to separate from the broader creative process it supports.

That separation also affects visibility. When a product decision is made based on behavioral analysis, the analytical work behind it is rarely singled out. It becomes part of the design or product narrative. A model is not just a predictive tool; it becomes a way of shaping how a team understands experience and makes design decisions. That requires interpretive flexibility that goes beyond traditional technical training.

A significant part of the work is also communication. The same dataset can lead to very different conversations depending on who the audience is. Each individual values different kinds of evidence and frames problems differently. Part of my role is making sure insights remain meaningful as they move across those boundaries. That translation process is often invisible, but it is central to how decisions actually get made.

It can be difficult not having a direct comparison point with peers whose work fits more cleanly into established categories. But it has also forced a new perspective. It is less about moving deeper into a single technical domain and more about moving across domains without losing rigor in translation.

In that sense, being a data scientist in a design field exists in a space between measurement and meaning. It is less linear, less easily categorized, and less visible in conventional terms but it reflects a broader shift in how analytical work operates when it becomes embedded in creative and experiential systems.