One misconception we encounter repeatedly is that design begins once requirements are complete. The business decides what needs to be built, engineering estimates the effort, and then a designer turns those ideas into attractive interfaces. It is a tidy process on paper.

Real products rarely behave that way.

A customer interview can completely change a roadmap. A UX workshop can reveal that the problem being solved is actually a symptom of something much larger. A prototype can expose assumptions that looked perfectly reasonable inside a planning meeting but collapse when placed in front of users. By the time visual design begins, many of the most important product decisions have already been made.

This is why we think about product design as a connected system rather than an isolated role. Every decision influences the next one, and when one stage is missing, the effects usually appear somewhere else in the product.

Across our product engagements, we’ve found that organisations rarely hire the wrong designer. More often, they expect one designer to solve problems that belong to research, product strategy, UX, engineering, and business alignment at the same time.

A client once approached us looking for additional UI support. Their platform had grown quickly, and they believed the experience simply needed a visual refresh. The request sounded straightforward enough.

But as our Product Discovery sessions progressed, a different picture emerged.

Different teams described the product in different ways. Customer workflows had evolved while internal processes had not. Several features had been introduced to satisfy individual requests, but nobody had stopped to ask how those additions affected the overall experience. By the time we reviewed the interface, the visual design wasn’t the biggest issue anymore.

The real problem was that the product had lost continuity.

Adding another UI designer would have produced better-looking screens, but those screens would still have represented disconnected product decisions.

The project changed direction long before new interfaces were created. Discovery clarified priorities, UX simplified workflows, and only then did visual design begin shaping the experience.

That engagement reinforced something we now see repeatedly.

Products rarely become coherent because someone creates better screens.

They become coherent because better decisions are made before the screens exist.

This is where the idea of an embedded design team becomes important.

A researcher doesn’t ask the same questions as a UX designer. A product strategist isn’t solving the same problems as a UI designer. Someone responsible for design systems is thinking about scalability, while engineering collaboration focuses on implementation and technical feasibility.

None of these disciplines replace one another.

They strengthen one another.

When organisations ask why a single designer isn’t enough, the answer isn’t about talent. Many exceptional designers have broad skill sets. The challenge is that modern digital products require different kinds of thinking at different stages. Expecting one person to move comfortably between research, strategy, interaction design, interface design, testing and engineering collaboration often creates compromises long before anyone notices them.

Great products aren’t built because one designer works harder.

They’re built because specialists make connected decisions.

The most valuable output of a design team is rarely the Figma file. It is shared understanding.

During complex product engagements, different stakeholders naturally bring different priorities. Leadership thinks about business growth. Product managers focus on roadmaps. Engineers consider technical constraints. Customer-facing teams understand operational realities. Without someone connecting those perspectives, every department begins optimising its own version of the product.

A multidisciplinary design team becomes the place where those perspectives meet. Research brings evidence into strategic discussions. UX translates business objectives into customer journeys. UI gives those journeys a usable form. Design systems create consistency as the product grows. Engineering collaboration ensures that good ideas survive implementation.

The outcome isn’t simply a better interface. It is a product that makes sense from multiple perspectives at the same time.

Artificial intelligence has made product design significantly more collaborative than it was only a few years ago.

During Design for AI engagements, the team is no longer deciding only how an interface should look. It is deciding how much responsibility AI should take, when people need explanations, where confidence should be communicated, and how automation fits naturally into existing workflows. These questions cannot be answered through visual design alone.

They require Product Discovery to understand user behaviour, strategy to evaluate business value, UX to shape interaction models, and engineering to understand technical realities. AI introduces another layer of product thinking rather than replacing the need for it.

This is one reason we rarely approach AI as an isolated feature. The most successful AI products we’ve worked on emerged because multiple disciplines contributed to the same decision rather than treating intelligence as a separate initiative.

One of the less visible advantages of working with a design team is that someone is always thinking beyond the next release.

Early-stage products often move quickly. New features are added every sprint, different designers contribute to the interface, and engineering teams make small adjustments during implementation. None of these decisions seems significant in isolation. Over time, however, they begin creating inconsistencies that users notice even if they cannot explain them. Buttons behave differently, navigation changes between modules, and familiar interactions slowly lose their predictability.

This is where a design system becomes more than a library of reusable components. At Kormoan, we see it as a way of preserving product decisions. It creates a shared language between designers and engineers, ensuring that as products evolve, the experience continues to feel coherent rather than assembled from separate projects. A single designer may establish visual consistency, but maintaining that consistency across years of product growth requires a team thinking beyond individual screens.

Many organisations still describe product development as a sequence: strategy, design, then engineering. It sounds organised, but it rarely reflects how good products are actually built.

Some of the most valuable product decisions happen after development has already started. Engineering identifies technical constraints that influence interactions. Product managers uncover new business priorities. Customer feedback reveals behaviours that prototypes never exposed. If design disappears after handing over screens, those decisions become disconnected from the original thinking.

One thing we’ve learned while working across Product Discovery, Product Design and engineering is that products improve when conversations continue rather than stop. The objective isn’t a perfect handoff. It is continuity.

This is another reason a design team creates more value than a single designer. Different specialists remain involved as the product evolves, protecting the reasoning behind earlier decisions instead of allowing them to disappear during implementation.

At Kormoan, we’ve found that strong products rarely emerge from one discipline working exceptionally hard. They emerge when each design decision builds naturally on the one before it.

Business Goals
↓
Product Discovery
↓
User Research
↓
UX Strategy
↓
Interaction Design
↓
UI Design
↓
Design System
↓
Engineering Collaboration
↓
Product Launch & Iteration

When one stage is skipped or disconnected, the impact usually appears much later in the product. What looks like a UI issue may actually be a discovery problem. What feels like an engineering constraint may have started with an unclear product decision. The strength of a design team lies in protecting these connections from beginning to end.

One benefit of working with an embedded design team is that it gradually changes how an organisation makes decisions.

Instead of waiting until interfaces are complete, product discussions begin involving research earlier. Engineering gains visibility into design intent before implementation. Business stakeholders become part of customer conversations rather than reviewing screens at the end of the process. Over time, design stops being a department that delivers outputs and becomes a capability that shapes decisions across the organisation.

That shift is difficult to achieve through a single hire, regardless of how talented that individual may be. Products become stronger when multiple perspectives challenge and improve one another throughout the development process.

Hiring a designer is rarely the wrong decision.

Expecting one designer to solve every product problem usually is.

As products become more sophisticated, they require different kinds of expertise at different stages. Discovery questions assumptions. Research explains behaviour. UX simplifies complexity. UI creates clarity. Design systems preserve consistency. Engineering ensures those decisions survive in the real product. None of these disciplines replaces one another, and none can consistently deliver their best work in isolation.

At Kormoan, we’ve come to see product design less as a role and more as a conversation between people who solve different parts of the same problem. The interface may be the most visible outcome of that conversation, but it is rarely where the real work begins.

Perhaps that is the difference between hiring a designer and building a design team.

One creates deliverables.

The other creates better product decisions.