A Growth Framework for Design Teams

It’s been a rough summer. The company I spent the past three years reimagining the future of urban mobility with <a href="https://www.theverge.com/2023/7/18/23798584/vanmoof-e-bikes-is-bankrupt" rel="noopener ugc nofollow" target="_blank">declared bankruptcy</a>, and what was left of the design team that I built came to an end. There have been countless articles written in a variety of languages discussing the rise and fall of VanMoof, but I’m not going to write about that. What I will share are some of the good stories from the past three years, focusing on what went right. And trust me, there was a lot that went right before it all went wrong. In this post (hopefully one of many), I’ll share the design team’s growth framework with a look inside the process that created it. Why is a growth matrix important? Regardless of team, growth matrices provide clarity around individual roles and responsibilities. They help people to understand what’s expected of themselves and of each other, and provide clear guidance for how one can expect to progress in their career. For managers, the growth matrix helps improve retention and engagement, ultimately leading to more creative and empowered teams. While design often works side-by-side with engineering and development, it’s important for design teams to have their own explicit frameworks for growth to accommodate the unique aspects of their function and ways of working. For example, the relative scale of design teams often leaves less room for specialization, and working across an organization requires a general understanding of business and technology even at entry level design positions. <a href="https://bootcamp.uxdesign.cc/a-growth-framework-for-design-teams-e0c1775615d2">Click Here</a>