Sitemap

Member-only story

Why designers should be embedded into product teams and what that even means

Operating “like an internal agency” is rarely the ideal.

9 min readDec 6, 2020
Image of a statue embedded in tree roots. From Unsplash.com
Photo via https://unsplash.com/photos/ugm-yDj9Hi4

Consider these two schools of thought for how a product company might structure its teams:

#1 — Project Teams

In a project organization, individuals from different departments are assigned temporarily to projects. Members work together temporarily to complete their work, usually in anticipation of a pre-determined deadline. Individuals may work on multiple projects at a time.

#2 — Product Teams

In a product-based organization, designers are distributed into product teams. These teams — sometimes “pods”, “squads” or “scrum teams” — support a particular product or product area indefinitely. They exist independently of organizational silos and have minimal dependencies on others from outside of the team. Product teams tend to be more conceptually aligned with agile practices.

Reality doesn’t always break down cleanly into one of these two categories, but it’s still a useful dichotomy.

Now, let’s say that you’re a designer in an organization that already has partial product teams.

--

--

Sean Dexter
Sean Dexter

Written by Sean Dexter

Staff Product Designer @ Walmart Data Ventures. Prev: Meta, HubSpot & Cigna. I write about UX, agile, & product. linkedin.com/in/seandexter1/

No responses yet