UX Engineering —
Founding a Discipline at Boeing

The Problem

Design and engineering teams at enterprise product organizations routinely struggle with the same failure: work that looks right in Figma doesn't survive contact with production. Screens drift from intent. Edge cases get resolved in code without design input. Inconsistencies accumulate. Nobody owns the gap.

At surface level this looks like a communication problem. Add more standups. Improve handoff documentation. Write better specs. Most organizations try these things. Most organizations keep having the same problem.

The Research

Between 2019 and 2022, working as Lead UX Designer at Jeppesen Sanderson, I investigated this pattern systematically across products, teams, and release cycles. Not as a formal research initiative — as a working designer who kept noticing the same failure modes repeating and decided to understand why.

I interviewed engineers about where design intent broke down in implementation. I traced inconsistencies back to their origin points. I mapped the moments where decisions got made in engineering that should have involved design — not because engineers were doing something wrong, but because there was no established mechanism for design to stay in the conversation past handoff.

What I found was consistent across contexts: the gap between design and engineering wasn't a talent problem or a tool problem. It was organizational. Design stopped at delivery. Engineering started at receipt. The space between those two moments was ungoverned.

The Insight

A designer who could reason fluently in both domains — who understood component architecture, implementation constraints, and production realities — could close that gap. Not by doing engineering's job, but by staying present through it. By catching the moments where feasibility pressure caused design intent to erode quietly, and bringing those decisions back into the open.

This was the UX Engineer role: not a hybrid of designer and developer, but a specialist in the translation layer. Someone accountable for the fidelity of design from intent through implementation.

The role didn't exist at Boeing as a formal function. Building the case for it would require making the structural argument at an executive level — not just advocating for a new hire, but proposing a new organizational capability.

The Proposal

In July 2022 I moved from Jeppesen Sanderson to Boeing proper, and began formalizing the business case. I drew on two years of documented observations, pattern analysis, and cross-team feedback to construct an argument grounded in operational impact rather than design philosophy.

The case I brought to senior leadership was straightforward: here is the failure mode, here is its root cause, here is the role that addresses it, here is what success looks like, and here is a one-year pilot to prove it. I proposed defining the operating model, engagement boundaries, and success criteria up front — so the pilot would produce a genuine answer, not just activity.

The proposal was approved.

The Pilot

Over the following year, I ran the UX Engineering pilot against the operating model I'd defined. The work centered on the translation layer: closing the gap between design artifacts and production output, coaching designers on implementation-aware thinking, and establishing the feedback loops between design and engineering that handoff-based workflows had never supported.

The pilot also surfaced something the research had suggested but not fully predicted: engineers and software leaders outside the design org actively sought out design guidance when a knowledgeable, credible resource was accessible. UX Engineering wasn't just valuable to designers. It was valuable to the whole product organization.

The Outcome

The pilot demonstrated measurable improvements in design-engineering collaboration quality — enough to move from provisional to permanent. UX Engineering became a recognized function with a defined operating model, a seat in product planning conversations, and a roadmap for growing the team.

The more durable outcome was cultural: design and engineering teams had a shared vocabulary, a shared point of accountability, and a working model for how the two disciplines could stay in dialogue through implementation — not just up to it.