John Cutler · 13 min read · Product Teams
TBM 423: Why Defining Teams Is So Hard
Read the original on cutlefish.substack.com →
TBM 423 argues that defining teams is hard not due to a skills gap but because multiple frames—product, design, technology, platform, and collaboration—shape how work is described and undertaken. These frames are often undiscussables, so surfacing them requires psychological safety to align reality with intent. The piece emphasizes mapping across frames to move from descriptive ambiguity to actionable team structures, noting that misalignment typically surfaces earliest in UX and product interactions.
Key Takeaways
- Frames (product, design, technology, platform, collaboration) shape how teams are described and operate, yet they often do not align in practice.
- Undiscussables and political costs hinder honest dialogue; psychological safety is essential to surface and address real organizational dynamics.
- Effective team design requires cross-frame mapping (capabilities, journeys, architecture) rather than relying solely on org charts or rigid product definitions.
- Cracks tend to appear early in UX/product where designers work across multiple teams, signaling the need for coherent cross-functional alignment beyond traditional boundaries.
Excerpt
Hint: It’s not some magic skill. This post is for anyone who has tried to answer “What is a team?” and been caught between three things: confusion at why such a simple question was so hard, a gut feeling that if people could just describe reality honestly things would get so much better, and the deflating experience of watching that honesty get met with resistance. Why is it so easy to describe how an organization actually works, and so hard to say it out loud? Chris Argyris called these “undiscussables”: things everyone in the room can see, but that are…