irst off, it’s just more fun to have another designer on the team; someone who knows where you’re coming from, who is living in your problem space, and is right beside you for quick questions. The domains that each product team work within are quite complex; it can be difficult for a designer who’s not in that domain to have the contextual knowledge needed to be a good sparring partner. Second, this helps Oda grow and maintain expertise. New teams at Oda are usually the result of a bigger team being split in two (the absorb and split model), and when we make these splits we can send one designer to each team. Then we hire two new designers, make two new duos, and expertise is passed along. A diagram showing how teams can grow by absorbing new team members until the team grows too big and splits naturally into two teams. Similarly this makes internal mobility much friendlier. A designer looking for a new challenge can move to a new team without stripping the old team of all its design expertise. Single-person dependencies are never good so this makes it easier for us to manage life in general — designers can take long vacations or parental leave and design work doesn’t come to a halt.
I like this idea of two designers per team.
Maybe this is similar to having a designer and a content strategist on each team at minimum