I’ve had a lot of titles, and I’ve worked across a lot of kinds of design: art direction, visual systems, brand, campaigns, websites, interaction, content, product, and the strange in-between places where those things start to blur.

For a long time, I thought that made my career harder to explain. Now I think it makes it clearer.

I design relationships between people and the systems they depend on.

Sometimes that system is a federal research platform. Sometimes it’s the website for one of the world’s largest technology companies. Sometimes it’s an operating system, a public health message, a brand, a campaign, a component, or a piece of writing. The medium changes, but the relationship is the thread.

This article started as a way to map my values for the next part of my career. It still does that. It’s for hiring managers, creative directors, design directors, and in-house teams who want to know who they’re getting before we’ve met. It’s also for me. If I start to drift, doubt the work, or doubt myself, this is what I come back to.

The framework is useful. But the more important thing is the pattern underneath it.

I’m interested in how people feel when they meet a system. Do they feel invited, or managed? Oriented, or quietly lost? Respected, or like the thing was built for someone else and they are lucky to be allowed in?

That is where design becomes personal to me.

I don’t have a clean boundary between what is personal and what is professional. I don’t mean that everything needs to be confessional. I mean the same instincts show up everywhere: in the way I arrange a room, the way I move through a city, the way I notice a sign, a chair, a transit map, a keyboard, a toy, a website, or the first few seconds of a new device turning on.

Does this thing know I’m here? Does it invite me in? Does it assume too much? Does it make me feel capable? Does it treat me like a guest?

That is the part of technology I have always loved. I’m not a technologist in the classical sense. I don’t come to it first through code or a computer science degree. I come to it through use, feeling, behavior, culture, and the way an object or system meets a person.

A toy can teach you this before you ever learn the word affordance. A rounded button, a bright piece of plastic, a shape that tells your hand what to do. You don’t need instructions. You understand the invitation.

I think about digital design the same way. A smartphone is an app inside an operating system inside a device inside someone’s actual life. Every layer has a tone. Every layer has a texture. Every layer can either add friction or make the person feel more at home.

That’s why technological humanist feels closer to the truth than technologist alone.

I love technology because it is one of the ways humanity expresses itself. It carries our curiosity, our shortcuts, our care, our laziness, our imagination, and our blind spots. It’s us, turned into systems and screens. So I think we owe the people it runs through some tenderness.

That belief has followed me into the work.

When I worked on a public health site in the early days of the pandemic, the audience was almost impossibly broad. In a way, it was everyone. The country was scared, and the work needed to understand that before it tried to say anything. The tone had to feel calm and trustworthy, the way a doctor with a good bedside manner would.

When I worked on a federal research platform, the design problem was trust. The institution needed participation from people who had every reason to be skeptical. The system had to feel human before it asked anyone to believe in it.

When I worked inside a large technology company, a straight design argument was not always going to move the conversation. So I watched how the organization made decisions, then reframed the issue in terms it already understood: brand consistency, customer trust, and the cost of letting small breaks accumulate. What looked like a design problem was really an organizational one.

That has become one of my strongest instincts.

Observe before advocating.

Before changing a relationship, understand the relationship.

Convictions

These are the things I try not to compromise.

First, humanity comes first. The person on the other side of the system should never become an abstraction. That sounds simple, but a lot of work starts drifting away from the person the moment the process gets complicated. Stakeholders multiply. Metrics take over. Systems protect themselves. The user becomes a segment, a funnel, a persona, a ticket, a target market.

I try to pull the work back toward the person. The person who is anxious. The person who is busy. The person who does not know the internal logic. The person who speaks another language. The person who has been left out before. The person who wants to get through the task and still feel intact.

Good design should not make people feel stupid. If a system needs too much explaining, I don’t start by blaming the person at the other end. I look at the system. What is unclear? What is hidden? What did we assume they would know? Where did we ask them to translate our structure instead of adapting the structure to them?

That is what democratic design means to me. Not making everything bland or frictionless, but making the work generous enough to be entered.

Inclusion works the same way. It is not a checklist you finish at the end. It is a set of choices that decide who feels expected, who feels tolerated, and who feels invisible. Different languages. Different abilities. Different relationships with technology. Different histories with institutions. Different levels of comfort, skepticism, access, time, attention, and trust.

Those differences are not edge cases. They are the work.

Integrity matters because designers know exactly how to push people around. We know how to hide the exit, soften the warning, overstate the benefit, make the bad option harder to find, and use polish to make a weak idea feel more convincing than it is.

I don’t want to make things that trick people into saying yes. I want the work to earn its yes.

Lenses

These are the ways I try to see.

Human-centered design gives you a structure. Empathy gives it depth. I don’t mean empathy as a soft word you put in a presentation. I mean the practiced ability to notice what a person may be carrying into an interaction before they ever touch the interface.

Fear. Impatience. Curiosity. Skepticism. Exhaustion. Hope. Confusion. Pride. A need to feel competent.

Good design makes room for those states without making a spectacle of them. It knows that people are rarely meeting a system in a vacuum. They arrive with a day, a body, a history, a mood, a language, a device, a level of trust, and a reason for being there.

That is why I try to observe before I advocate. Designers are trained to see what is wrong quickly, and sometimes we do. But seeing the design problem is not the same as understanding the system around it.

Who has to approve this? What are they afraid of? What language does this organization already trust? Where has this conversation failed before? What is being said indirectly? What does the work need in order to survive contact with reality?

Patience is not passivity. Sometimes patience is the strategy.

The obvious problem is not always the real one. A visual problem might be a governance problem. A UX issue might be a content issue. A content issue might be an organizational issue. A brand issue might be a trust issue.

I try to map the system before I start designing inside it. That does not mean overcomplicating the work. It means respecting the conditions the work has to live in.

The best solution is not always the most beautiful one in isolation. It is the one that understands where it is, who it is for, and what relationship it has to repair, clarify, or protect.

Standards

These are the things I hold the work to.

I care about work that lasts past the first reveal. Trends are useful. Taste changes. Culture moves. I’m not against the present tense. But I don’t want the work to collapse the moment the mood changes.

You don’t design a home only for the week you move in. You design it for the life that will happen there. I think about design the same way.

Will it still make sense later? Can someone else use the system after I leave? Does it have enough structure to grow? Does it have enough warmth to stay alive?

Durability is part of care.

So is invitation.

I love things that make use feel natural. The rounded key. The obvious handle. The screen that seems to know what you need next without making you feel managed. The detail that makes you want to touch, click, read, move, or keep going.

Interaction should feel like an invitation. That does not always mean playful. Sometimes the right invitation is quiet. Sometimes it is serious. Sometimes it is almost invisible. But the person should feel a way in.

Does it invite touch? Is it straightforward to use? Does it offer a little delight?

Those are not extras to me. They are evidence that somebody cared.

Trust comes from that. Not from a claim, or a line in a deck, or a polished surface. Trust has to be demonstrated in use.

The work earns trust by being clear. By doing what it says. By not overpromising. By giving people control where control matters. By being honest about what it is asking for. By staying consistent in the places people may never consciously notice.

I don’t want to polish what has no substance. I don’t want to make claims the work can’t support. I want the thing to hold up.

The belief at the center

This is the map I hold myself to: humanity first, democratic design, contextual inclusion, integrity, empathy, observation, strategic sight, durability, invitation, and trust.

But there is one belief underneath all of them.

I see a failed design before I see a failed human.

That is where I start.

If someone is confused, I look at the system. If someone feels excluded, I look at the system. If someone does not trust the message, I look at the relationship we are asking them to enter. If someone cannot find their way in, I don’t assume they were never meant to.

It is easy to talk about design as output. A page. A campaign. A system. A case study. A launch.

But I keep coming back to the relationship.

What does this thing ask of people? What does it give back? Does it make them feel more capable? Does it treat them like a guest? Does it earn the trust it asks for?

That is what I actually believe.

The thread is already in the work, whoever you are. It is worth finding.

Mine took a while to name.

I design relationships between people and the systems they depend on.

A note on process

I used Claude and ChatGPT as a collaborator while developing of this article. Not to invent my values, but to pressure-test them. It helped me find structure, catch contradictions, and put clearer language around things I had been carrying for years.

That earlier version was useful. It gave the ideas a shape.

This version gets closer to the center.

The thinking is mine. The work is mine. The values are mine. If I’m going to write about integrity, I should be honest about how the language got here.