Chyanne Robbins

I'm drawn to questions that are still a little messy.

The ones where something is happening, but it isn't immediately clear why. Where people's behavior, their environment, the systems around them, and the things we've designed all seem to be interacting at once.

My instinct is to make those questions more intelligible.

I want to understand what's happening, identify the patterns underneath it, and figure out what those patterns might mean. And increasingly, I'm interested in what happens next: how what we learn can be translated into something we can design, build, test, or experience differently.

That way of thinking has followed me through seemingly different fields.

I studied communication because I was interested in people — how we make meaning, influence one another, and understand the world around us.

Public health widened the lens. It taught me to think beyond individual choices and consider the environments, systems, and conditions that shape behavior in the first place.

Then I became a software engineer.

Working in technology gave me another perspective: I wasn't only studying the environments people move through anymore. I was helping build one of them.

I also discovered that I was drawn to what happened behind the interface. Understanding how systems worked, how different technologies connected, and why something wasn't functioning as expected often interested me as much as the experience itself.

And that raised a different set of questions.

What happens when the things we design become part of the conditions shaping how people think, behave, connect, and live?

Today, my work brings together research, technology, and systems thinking.

I'm interested in understanding how people interact with the systems around them, whether those systems are social, organizational, physical, or digital.

Behavioral science and human-centered design give me ways to investigate those relationships systematically — to observe, research, synthesize, frame problems, and explore possibilities.

Software development gives me another way to act on what I learn: building tools, connecting technologies, troubleshooting workflows, and turning practical needs into functioning solutions.

Sometimes that work becomes a prototype. Sometimes an article, a service, a technical implementation, or a new research question.

The artifact can change.

The process I'm interested in is the same: understand before assuming, make sense of what I find, and build or design from there.

There is a much older version of this tendency in me.

In college, a professor once assigned five observations. I came back with twenty-five.

Not because I was trying to do extra work. I had simply become interested in what I was noticing, and once I started seeing patterns, I wanted to keep looking.

I didn't have language for that way of working then.

I do now.

This site is where I follow those questions in public — documenting what I observe, what I'm learning, what I make, and how my thinking changes along the way.

I don't have a neat answer for every question here.