Oct 20, 2026

4 min read

Your Product’s Seams Are Your Org Chart

Users find the places where one team’s work meets the next long before we do. How I find those seams, and get someone to own them.

Introduction

Every product I have worked on had a place where it felt like two products taped together.

A setting you could see but not change. A status that meant one thing on one screen and something else on the next. A step where the user had to copy a number from one place and type it into another.

Users find these seams before we do. And they are rarely design mistakes. They are the shape of the company, showing through the interface.

Melvin Conway described this in the late 1960s: organisations build systems that mirror how their own teams communicate. Each team designs its own part well. The trouble lives where one team’s part meets the next, because nobody owns that space.

Early in a design career, the job is to make a screen good inside one team’s area. Later, the job moves to the seams. Here is how I work on them.

1. Follow one object, not one screen

Screens hide seams, because every screen belongs to someone. Objects don’t.

So I pick the thing that moves through the product, like a claim, an order or a client setup, and follow it from the person who creates it to the person who closes it. Every time it changes hands between teams, I write it down.

On Backlot, one bill passes through three apps: the crew member who pays, the coordinator who approves and the producer who pays it back. Each app could be well designed on its own and the bill could still get lost between them. Following the bill, not the screens, is what showed me where.

2. Count the translations

A seam costs the user a translation. They re-type something the product already knows. They check a status in a second place because they don’t trust the first. They ask a colleague what a label means.

I count these, one per handoff, and list them next to the object’s journey. That list is usually the most valuable backlog in the company, and it belongs to nobody, because each item sits between two teams’ roadmaps.

3. Give every shared state one name and one owner

The most expensive word in most products is “approved”. Ask three teams what it means and you will often get three answers: approved by a manager, approved for payment, approved and paid.

When a state crosses a team boundary, I want one name, one meaning and one team that owns it. The screens, the API, the notifications and the support replies all use the same word. If a payment is “queued”, then “sent”, then “in your account”, every surface says exactly that, in that order.

A glossary sounds like admin. It is one of the cheapest design tools there is.

4. When you can’t move the boundary, design the handover

Not every seam can be removed. Some teams will stay separate. Some systems are old and some rules exist for good reasons.

Then the job is to make the handover honest. On Tracker I-9, a client’s package settings are managed at the distributor level, so the client page shows them read-only. Instead of a disabled field that just says no, hovering over it tells admins where the settings are edited. The boundary is still there. The user just isn’t stranded at it.

A good handover says three things: who owns this, where to change it and what happens next.

5. Bring a seam map to the roadmap meeting

Seams don’t get fixed by better screens. They get fixed when someone with authority decides who owns them.

So before roadmap conversations, I make one page: the object’s journey, each team as a lane, every seam marked, and for each one, the translation it costs the user. It turns “design has concerns” into “this is where we lose people, and nobody is responsible for it.”

The ask is never “fix all of this”. It is “give each of these an owner”. That is a smaller request, and it is the one that changes things.

6. Know which seams to keep

Some seams protect people. The person who raises a claim should not be the person who approves it. A compliance check should feel like a separate step, because it is one.

Those seams should stay visible. The aim is not a product with no boundaries. It is a product where every boundary is there on purpose, and the user can see why.

Closing thoughts

Seniority in design is not about bigger screens. It is about wider objects. The further you follow one thing through a company, the more of the real product you can see, and the more of it you can change.

Key Takeaway

Most of a product’s worst moments live between teams, not inside them. Follow one object across the company, count the translations it costs the user, and ask leaders for one thing: an owner for every seam.

Be the first to know about every new letter.

Stay ahead in the world of web design with expert insights, industry trends, and practical tips.

No spam, unsubscribe anytime.