Blogs / Tetrahedral Model: Building Stronger Ties in Product Teams
Tetrahedral Model: Building Stronger Ties in Product Teams

Design · 7 Min Read

Tetrahedral Model: Building Stronger Ties in Product Teams

A practitioner-developed model for examining relationships across product disciplines. By Fas Lebbie

Strong product organizations need more than talented people. They need productive relationships between them. As leaders, we put considerable effort into building capabilities in Product, Engineering, Design, and Research. But capable teams can still struggle to work together. The difficulty often sits between disciplines: in how evidence travels, how constraints enter decisions, and how disagreements get resolved.

The Tetrahedral Product Organization (TPO) model offers a way to examine those relationships. Its focus is not simply the four disciplines, but the six connections between them.

These ties carry information, negotiation, and shared problem-solving.

Looking at them can help leaders distinguish a capability problem from a coordination problem

Sometimes the team does not need another process or a different reporting line. It needs a better connection.

Where This Comes From

TPO is my synthesis, developed from years of working across product disciplines in agency, consulting, and embedded organizational roles. Those experiences preceded the model’s formal articulation.

During my doctoral studies at Carnegie Mellon, I encountered tetrahedral reasoning as a way to examine interconnected concerns. Buckminster Fuller’s work formed part of that theoretical background. John Wood’s use of tetrahedral reasoning in design is another relevant intellectual reference.

In my earlier doctoral work, I explored relationships among theory, place-based research, entrepreneurial practice, and knowledge transfer. Four nodes and six relationships helped me consider how these concerns might inform and challenge one another, particularly how practice could feed back into theory.

TPO brings that relational approach to product work. Its contribution is not the geometry, but the questions it helps us ask about coordination across disciplines. It remains an evolving conceptual and diagnostic model informed by professional experience, not a formally tested organizational intervention.

[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop

Four Nodes, Six Relationships

In this model, the four nodes represent distinct capabilities:

  • Product Management: Product direction, prioritization, business needs, and market judgment.
  • Design: Shaping user experiences, interactions, interfaces, and usability.
  • Engineering: Technical architecture, implementation, reliability, and performance.
  • Research: Investigating behavior, testing assumptions, and generating evidence for decisions.

These are analytical distinctions, not mandatory departments.

Research may sit within Design, operate independently, or be distributed across teams. Designers also conduct research. Separating these capabilities here makes it easier to examine how evidence informs the work, regardless of reporting lines.

A tetrahedron has four vertices, each connected to the other three, producing six edges. In TPO, this gives us a conceptual and diagnostic structure for examining every pairwise relationship among the four capabilities. The structure helps us examine those relationships; it does not guarantee they work well.

The nodes give us a starting point. The six relationships reveal how the work connects.

Product and Design

Strategy and user experience should inform each other. Business goals need to meet an understanding of what people are trying to do.

When that relationship weakens, design can become decorative. Strategy proceeds without sufficient attention to experience, and the organization risks becoming a feature factory.

Product and Engineering

Technical feasibility should shape strategic decisions, not arrive after commitments have been made. Engineering needs room to question assumptions and influence the roadmap.

When that relationship becomes one-way, engineering becomes an order-taking function. Unrealistic timelines can push technical debt into future work.

Product and Research

Research should help challenge and develop product direction. Market and user evidence need a route into decisions, including decisions leaders would rather not revisit.

When that relationship fails, research becomes an exercise in confirmation bias. Findings get selected to support predetermined strategies rather than inform them.

Design and Engineering

Technical constraints can inspire creative solutions, while implementation can strengthen design intent. That requires negotiation before either discipline treats its work as settled.

Without it, “Design vs. Engineering” battles take over. Teams produce solutions that look good but perform poorly, or technically sound products that people struggle to use.

Design and Research

User insights should inform design decisions, and design proposals should remain open to examination with users.

When that connection weakens, research becomes a post-hoc justification. Assumptions harden into solutions before anyone has seriously questioned them.

Engineering and Research

User behavior can inform technical decisions, including where performance improvements matter most.

Without that connection, optimization happens in isolation. Technical metrics improve while their relationship to user impact remains unclear.

When Things Go Wrong

What concerns me is how easily weak connections can hide behind visible activity. Meetings happen. Work gets delivered. Yet the information needed for good decisions does not always reach the people making them.

I’ve noticed patterns such as Research feeding Product while Engineering remains outside the conversation. Or defensive language taking the place of joint exploration: “They can’t build it,” rather than “What would make this possible?”

Other signs include groups investigating the same problem separately, metrics that pull teams in different directions, and disputes settled by rank rather than evidence.

These are professional observations that informed the model, not findings from formally deploying it.

A strong relationship in one area can also conceal a weak one elsewhere. Product and Design may work closely while Engineering receives decisions too late. Research may have excellent access to users but little influence on priorities. Looking only at overall team sentiment can miss those differences.

Building Better Connections

Fixing bad links does not necessarily mean redrawing your structure.

[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop

Start with the practices that shape how people work across it.

Map information flow. Does research reach everyone who needs it? How do technical constraints enter product discussions? Where does context get lost?

Connect measures of success. Examine whether one team can meet its targets while making another team’s work harder. Shared measures should clarify a common outcome, not simply add another reporting requirement.

Use rituals with a purpose. Joint reviews, paired exploration, and technical deep dives are useful when they bring necessary perspectives into a decision. More meetings are not the objective.

Create opportunities to see another discipline’s work. Product managers can observe research. Engineers can join design critiques. Designers can examine usage and performance data alongside technical colleagues.

Make the relationship itself discussable. A retrospective can examine not only what went wrong, but where information stopped, assumptions diverged, or decisions became difficult to challenge.

The Fields: Looking Beyond Pairs

Some coordination problems only become visible when three disciplines work together. I use “fields” to describe these three-way interactions. Four nodes permit four distinct fields; the examples below explore three of them.

A pair can appear well coordinated while missing a third perspective. Product and Design might agree on a direction without understanding its technical implications. Engineering and Research might identify a behavior pattern without connecting it to product priorities.

For example, Product, Design, and Engineering can examine a user problem alongside strategic priorities and implementation constraints. Design, Research, and Engineering can connect observed behavior with interaction choices and technical possibilities. Product, Research, and Engineering can explore whether a market need warrants a particular technical investment.

The diagnostic question is what becomes visible when a third capability joins the discussion.

A field is useful when it reveals something the pairwise relationships leave unresolved, not simply when three teams attend the same meeting..

A Practical Starting Point: The Synergy Audit

Start with a recent piece of work rather than an abstract assessment of the whole organization.

[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop

  1. Map the flows. Trace how information moved among Product, Design, Engineering, and Research. Who received context, and who received only a decision?
  2. Spot negative patterns. Look for defensive language, duplicated effort, escalated conflicts, and conflicting measures of success. Which relationship needs attention?
  3. Choose a focused intervention. Identify a practice that could improve the weak connection. It might be earlier technical involvement, direct access to research, or a joint review before a commitment is made.
  4. Check what changes. Decide what you will observe. Does relevant evidence arrive earlier? Are constraints discussed before plans harden? Do fewer decisions need to be reopened because a perspective was missing?
  5. Build on what helps. Retain useful practices, adjust those that add overhead, and keep watching relationships that remain difficult.

The audit is a starting point for inquiry, not a score of organizational maturity. Use it to identify a specific coordination problem and examine whether your response helps.

Beyond Process: The Mindset Shift

For me, the value of this model is the shift in attention. It asks leaders to examine the spaces between disciplines as carefully as the disciplines themselves.

That can involve trade-offs. Bringing another perspective into a decision may take longer now while exposing a problem that would be harder to address later. Not every tension needs to disappear. Some disagreements reveal constraints the work needs to accommodate.

Start by tracking a week of cross-disciplinary interactions. Notice where context travels naturally, where it stops, and where people work around a connection they no longer trust. Choose one relationship to improve.

The aim is not to make every exchange frictionless. It is to make the friction useful enough that people can work through it together.

References

  • Wood, John. 2004. “The Tetrahedron Can Encourage Designers to Formalise More Responsible Strategies.” Art, Design & Communication in Higher Education 3(3): 175–192. DOI: 10.1386/adch.3.3.175/1.
Photo of Fas Lebbie

September 21, 2025 . Written by Fas Lebbie

Share