Back to Devoured - November 13, 2026
DEVOURED
Design should make it easier to ship

Design should make it easier to ship

Design Karl Koch
Good design should prioritize implementation feasibility, encouraging designers to act as 'design engineers' who reduce the overhead of constant iteration.
What: Author Karl Koch argues that design quality must account for build costs and that designers should collaborate early with engineers rather than pushing for constant interface churn that ignores technical constraints.
Why it matters: The industry is moving away from the 'handover' model toward 'shared ownership' where design systems and design engineering roles align to prevent wasted development effort.
Deep dive
  • Designers must factor implementation effort into their assessment of 'good design'
  • Design systems that create friction for developers are failing their primary purpose
  • Design engineering allows for faster iteration with lower overhead
  • Early and frequent collaboration during the build process reduces the need for expensive rework
Original article

I read Sean Goedecke’s Working with designers and found myself agreeing with a lot of it. He clearly enjoys what designers bring to a product, whilst being fairly fed up with some of what comes along with it. Repeated changes, disagreements, and design systems that make the thing you’re trying to build harder to build.

I think designers should be interested in that combination. Someone can value our contribution and still find working with us unnecessarily difficult.

From our side, it’s easy to judge a design by how much better it makes the product look or feel. And that matters, obviously. But we also make decisions that create work for other people, sometimes quite a lot of it, and I think that cost belongs in our assessment of whether the design is any good.

Say I propose a new layout that means rebuilding a bunch of an existing interface. There might be a really good reason to do that. People might be struggling to find something, or the current structure might make a simple task needlessly complicated. I should be able to explain the improvement well enough that we can decide together whether it’s worth the work. If I’m mostly rearranging things because I prefer them that way, I’m asking quite a lot of someone else’s time for my own satisfaction.

And when we discover that something is more difficult to build than expected, I want the designer involved in figuring out what happens next. We might simplify it, find another approach, or decide the original idea is worth the effort. That conversation is part of designing the thing; it’s where we learn whether our idea holds up.

Sean’s account of designers repeatedly changing each other’s decisions sounds particularly exhausting. If two of us disagree, we need to work through that and agree on how to proceed. Having an engineer implement each competing preference in turn is a pretty expensive way to have a design conversation.

There’s a slightly different dynamic when you’re working as a design engineer, too. If you’re building your own designs, changing your mind carries a lot less overhead. You can notice that something feels wrong with real content, try another approach, and make the decision there whilst you’re building. A bunch of those changes might never be visible to anyone else because they happen before you have something ready to share.

I think that’s one of the things I enjoy about working this way. You have room to keep figuring the design out without every adjustment becoming another request for someone else to pick up. You’re doing the rework yourself, you understand what it involves, and you can decide on the fly whether it’s worth it. Changing your mind becomes a fairly ordinary part of making the thing, with much less opportunity for it to strain the relationship between people.

I feel similarly about design systems. They should make it easier for teams to build good interfaces consistently. So if people are constantly working around the components, I’d want to understand what they’re trying to do and why the system makes it difficult. There’s useful information there about what the product actually needs.

A beautiful component library that teams struggle to use has more work to do. Especially if the components in the design file are ahead of what’s available in the application. That gap becomes someone’s problem every time they try to build a screen, and we should care about closing it.

I wrote about designing for handshakes rather than handovers a few years ago, and this still feels like the important part to me. Responsibility stays shared whilst the thing is being made. You keep talking, look at the actual implementation, and adjust as you learn more.

Taking an interest in what it takes to make your design work should be a fairly ordinary part of being a designer.

I’d like an engineer to enjoy working with me because we made something good together, and because getting there felt like a shared effort. That seems a pretty reasonable thing to ask.

Explore all 57 articles in today's digest

Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi