The Rise of Builder Teams

As AI lowers production costs, the logic behind large functional product teams begins to break down.

As discussed in Part 1, the shift toward outcomes and more fluid ways of working is already reshaping how teams operate. For many years, product organizations were built around large groups divided by discipline: UX, product management, engineering, and research operated as separate functions with clearly defined responsibilities. Work moved from one group to another through a series of handoffs. Product teams defined the requirements. Design created the experience. Engineering implemented the solution. Research informed the process at specific stages.

This structure made sense when production was expensive and specialization was necessary. Each role focused on a specific part of the process, and coordination happened through formal processes and documentation.

Today, that model is beginning to shift.

Advances in AI, prototyping tools, and development platforms are reducing the cost and speed of production. At the same time, the boundaries between disciplines are becoming more fluid. Designers can prototype and experiment more deeply with technology. Engineers contribute to product thinking and interaction design. Product managers engage directly with user research and experience decisions.

As these capabilities converge, the need for large functional teams begins to decrease.

In their place, a new model is emerging: small, blended teams built to move from opportunity to outcome.

These are builder teams.

What builder teams look like

Builder teams are typically small groups designed to move quickly from opportunity to outcome. Instead of large departments coordinating work across handoffs, these teams bring together the capabilities needed to understand a problem, shape a solution, and build the system that delivers it.

A typical builder team might consist of three to five people working closely together. But an important part of the team is not human.

As AI becomes embedded in team workflows, it becomes a collaborator. It generates prototypes, explores variations, assists with development, and accelerates experimentation.

As a result, builder teams operate as small groups of humans working alongside AI systems that expand speed and capability, allowing people to focus more on insight, decision-making, and direction.

From functions to aptitudes

One of the most important changes in this model is how teams are composed.

Traditional organizations build teams based on functions. A project might require a product manager, a designer, several engineers, and possibly a researcher. Each person is expected to contribute according to their role.

Builder teams shift this thinking.

Instead of assembling teams based solely on titles, organizations begin to assemble teams based on the aptitudes required to solve the problem.

An aptitude describes a capability that helps the team move from opportunity to outcome.

One critical aptitude is human insight. Someone on the team needs to understand people, uncover unmet needs, and generate insights that reveal meaningful opportunities. This aptitude often emerges from backgrounds such as design research, anthropology, psychology, or human centered design.

Another important aptitude is experience craft. This capability shapes how value is delivered through the experience itself. It includes designing interaction models, structuring experiences, ensuring usability, and creating coherent and compelling interfaces.

Teams also need strategic aptitude. Someone must align opportunities with business value, define success metrics, and make decisions about which opportunities are worth pursuing.

Finally, there is a technical aptitude. This capability ensures that the experience can actually exist in the world. It includes architecture, system design, AI integration, and building the platforms that power the experience.

Some organizations also emphasize orchestration aptitude, which helps coordinate work across systems, stakeholders, and teams when experiences span multiple parts of the organization.

What matters is not that each aptitude maps neatly to a specific job title. A designer may contribute both human insight and experience craft. An engineer may contribute both technical capability and product thinking. A product manager may bring strategic alignment and orchestration.

The goal is simple. Ensure the team collectively has the capabilities needed to understand people, design the experience, align the opportunity, and build the system.

What this means for UX

These shifts have important implications for UX teams.

If production becomes easier and faster, the value of UX cannot be defined primarily by producing artifacts. The role of UX expands into understanding people, identifying opportunities, shaping product direction, and ensuring that experiences actually produce the outcomes they were designed for.

In a builder team environment, designers are not simply responsible for interface design. They contribute to insight generation, opportunity framing, experimentation, and iteration. Their work becomes deeply integrated with product and engineering rather than separated from it.

AI further amplifies this shift. Designers increasingly guide AI systems to explore ideas, generate prototypes, and test possibilities. The designer’s role becomes less about producing every artifact and more about directing the creative and strategic process.

This does not diminish the importance of craft. Experience design remains critical to delivering meaningful value. But craft exists within a broader context where teams are responsible for discovering and delivering outcomes rather than simply producing design deliverables.

What comes next for UX teams

As these patterns continue to develop, UX teams are likely to look quite different from the teams many organizations have today.

They will be smaller and more autonomous. They will blend disciplines instead of separating them into strict functions. They will collaborate with AI as a creative and operational partner. And they will focus on driving outcomes rather than producing artifacts.

The tools, technologies, and organizational structures will continue to evolve as AI capabilities expand. Yet the core purpose of UX remains consistent.

The role of UX is not simply to produce designs. It is to discover opportunities, shape meaningful experiences, and ensure that technology creates real value for people.

A question for teams

For organizations thinking about the future of product development, the question is not whether these shifts will happen. Many teams are already experiencing them.

The more important question is whether our team structures are evolving to support this way of working.

Are teams small enough to move quickly and learn together?
Do they bring together the capabilities needed to understand people, shape experiences, align strategy, and build systems?
Are they embracing AI not just as a tool, but as a collaborator within the team?

The rise of builder teams points to a different way of operating.

The next step is not just adopting new tools, but redesigning how teams are structured to move from opportunity to outcome.