Most engineering teams are organized around specialization. Front-end developers, back-end developers, designers, DevOps. Each person is deeply skilled in their domain. Each handover between them is a queue.
The Theory of Constraints says a chain moves at the speed of its slowest link. In software, the slowest link is rarely a person — it’s the space between people. The handover. The waiting. The context that gets lost when work moves from one specialist to another.
The Cost of Handovers
A feature that touches front-end and back-end requires at least two people. That means:
- Waiting time. The back-end developer finishes the API, but the front-end developer is in the middle of something else. The feature sits.
- Context loss. The front-end developer picks it up, reads the API spec, has questions. A Slack thread starts. Maybe a meeting.
- Ping-pong. The API doesn’t quite match what the front-end needs. Back to the back-end developer. Who is now in the middle of something else.
Each handover introduces delay that has nothing to do with the actual work. The feature isn’t hard — it’s just stuck in transit.
This is the difference between resource efficiency and flow efficiency. Resource efficiency optimizes for keeping each person busy. Flow efficiency optimizes for how fast work moves through the system. Most teams optimize for the wrong one.
One Person, One Feature
Toyota figured this out decades ago. In manufacturing cells, one worker follows a product through multiple stations instead of handing it off between specialists. The product never waits. The worker might be less efficient at individual stations than a specialist would be — but the product is done faster because it never sits in a queue.
The software equivalent: one developer takes a feature from database to UI. No handover, no queue, no context switch. The cycle time drops dramatically because the interdependencies simply don’t exist anymore.
This doesn’t mean everyone needs to be an expert at everything. It means the boundaries between front-end and back-end matter less than the cost of coordination across them. A developer who can write a decent React component and a decent API endpoint ships faster than two specialists who need to synchronize.
It Works for Design Too
The same logic applies to the designer-developer handover. Traditional flow: designer creates mockups, hands them to a front-end developer, front-end developer implements them, designer reviews, finds issues, sends them back. Repeat until both sides are tired of the conversation.
A designer who can write markup eliminates this entire loop. They build the component themselves — exactly as they intended it. No interpretation gap, no specification document that tries to capture every spacing value and hover state, no three rounds of “the padding is 12px not 16px.”
The design is right because the person who designed it built it. The front-end developer can focus on behavior and state management instead of translating Figma frames into CSS.
The Death of the Specialist
This shift isn’t theoretical. Front-end developers who started writing APIs are now full-stack engineers. Designers who learned HTML and CSS are shipping their own components. The specialist roles that defined teams five years ago are dissolving — not because specialization is bad, but because the handover cost exceeds the specialization benefit.
The math is simple. If a specialist is 30% faster at their part of the work but the handover adds two days of waiting, you’re better off with a generalist who does the whole thing in one go.
This doesn’t happen overnight, and it requires investment in people. Someone who was hired as a front-end developer needs support and time to become comfortable with back-end work. But the return on that investment is immediate: features that used to bounce between two or three people now flow through one.
Flow Over Resource
Stop optimizing for keeping specialists busy. Start optimizing for how fast a feature moves from idea to production. The constraint isn’t skill — it’s coordination. Remove the handovers, and the work flows.