Why it’s hard to build one product inside a company full of products
Building a product is hard enough. Building one inside a company that already runs many products, serves many clients and delivers many projects at once is harder still. I know this from the inside, having spent years allocating the same people across a large number of parallel projects. The challenge is rarely talent or ideas. It is focus.
Everyone competes for the same people
In a company full of products, the new one has to fight for everything: designers, developers, attention from management and a place on a roadmap already full of commitments to paying clients. Client work wins almost every time, because it has deadlines and invoices attached. The new product moves forward in the gaps, which means it barely moves at all.
A clear owner
The first condition for progress is an owner: one person accountable for the product, with the authority to make decisions and the responsibility to defend them. Without that, every choice becomes a negotiation between departments, and the product drifts towards whatever the loudest client wants this month.
A clear goal and room to say no
The second condition is a goal everyone can repeat in one sentence, and the third is permission to say no: to requests that pull the product away from that goal, to features one client wants but the market doesn’t, to borrowing the product team for an urgent delivery. Those refusals are uncomfortable in a delivery-driven company, but without them the product never gains momentum.
Protecting a small space
It also helps to protect a small, stable core team, even if it is only a few people, rather than rotating whoever is free. Continuity builds knowledge, and knowledge builds speed. A company full of products can absolutely build one more, but only if it treats that product as something that needs its own space, rather than a side project that happens when everything else is done.
Is your design system starting to fade?
I’d like to hear about it →