jason kyle, human-centered systems design and leadership

I make sense out of complicated things.

Human-centered systems design & leadership.

Twenty years designing products, organizations, and services around the people who actually have to use them. Complexity is sometimes unavoidable. Confusion usually isn't.

What I'm looking for.

I'm open to design leadership roles on work that leaves people a little better off, with a team I trust and a product I can stand behind, where design helps shape the problem instead of decorating the answer. The fit notes and logistics are on the right; the longer version covers the background, how I lead, and the kind of team I want to be in.

Design doesn't happen
in a vacuum.

The world design operates in has shifted under all of us. The technologies, the politics, the economy, what organizations are actually responsible for, how teams get structured and restructured, the RIFs that cut the people doing the work. None of it is abstract anymore. Craft has to answer to all of it.

And the people we design for are carrying more than ever. Wars. Inflation. Tariffs. Elders to care for. An erratic administration with a complicated relationship with reality, dismantling alliances we spent decades building. Social safety nets fraying. Democracy itself feeling less certain. Unemployment that lands without warning. The systems people lean on are the same ones feeling least dependable right now.

This is where the work matters. Design decides whether the systems people depend on feel like a wall or a door. Whether a form asks for too much, or just enough. Whether someone gets help or gives up. My job is to make those systems work for people, so the helpers can actually help, and so our work serves the greater good it was meant to. When a decision gets hard, four things settle it for me: flexibility, trust given first, education as part of the job, and connection built on purpose.

Outcomes over
output.

Messy, half-shaped problems are my happy place, but the work only sings when the team does. Give me people I trust, a product I believe in, and a room where it's safe to disagree, and good things tend to follow. That doesn't mean I need to hold the pen. I'm as happy executing someone else's vision as I am helping shape one, and I don't need to be in every room. The real win is a team that moves well on its own, with me there when I'm useful and out of the way when I'm not.

The panels here are the whole operating manual: the five practices I actually run day to day, the mantras and expectations I lead a team with, how I set the bar when hiring and growing designers, and some honest field notes on alignment and trust that nobody puts in a job description.

AI is a tool.
Agency is the point.

I use AI to get past blank pages, expose options, and make ideas testable sooner. Judgment, context, safety, and the final call stay with people.

In practice that shows up three ways: discovery that turns scattered inputs into traced evidence instead of another round of meetings, prototyping that lets engineers, PMs, and researchers make something clickable without lowering the bar, and adoption done in the open, with shared prompts, plain disclosure, and a clear path to escalate when something feels off.

Illustrative examples from my own practice, not claims about any employer.

Experience,
compressed.

I didn't begin in a design department. I've run development, ecommerce, marketing, operations, and design, so I understand design as part of a business system, not a department inside one. Five acts so far.

Each role opens to what the job actually was, and the case studies go a level deeper: last mile operations across 100+ delivery stations, a supply chain design program built out of critique and research rituals, and financial services for people banks turned away.

1. IBuilder. Web, ecommerce, retail. How businesses actually operate.
2. IIDesigner. Research, services, frontline systems. Design as ethics, not decoration.
3. IIISystems leader. Logistics, supply chain, global teams. The org chart is part of the UX.
4. IVHuman + machine. Books, discovery, AI. The technology is never the point.
5. VBuilder again. Afieldly, Parlorly, experiments. Ideas become things.

What I'm
building now.

Systems thinking with its shoes off. Each project starts from a real friction: planning a trip, hosting a dinner, finding a shirt that says something, and soon, something for the dogs. Different surfaces, same instinct. Calm infrastructure for the outdoors, the table, what you wear, and whatever's still behind the curtain.

The living
part.

Paperbacks with bent spines. Shows that reward patience. 80s horror with practical effects. Weekend camps that turn into “where next?” conversations. The work matters, and so does everything that fills the rest of the tank.

Let's build something together that respects people.

If you're working on complex human-centered problems, or building teams where people actually want to show up, I'd welcome the conversation.