Over the past four years, my role at Spinny has evolved significantly. From being a product design manager, I have stepped into a leadership position where I now head the entire design function. This transition has brought new responsibilities, challenges, and opportunities, as I work to build a design culture that fosters creativity, collaboration, and a user-centric approach across the organization. I have led the design team through substantial growth and refinement, focusing on developing robust processes, cultivating a thriving design culture, and ensuring that our designs align with business goals and user needs.
As the Head of Design, my role now goes beyond managing individual design projects. I am responsible for shaping the overall design vision at Spinny, ensuring that our design work is aligned with the company’s strategic objectives. I work closely with cross-functional teams, including product, engineering, business and marketing to drive design initiatives that create value for both users and the company. One of my primary goals has been to elevate design as a key driver of business success and to empower my team to contribute meaningfully to the product development process.
When I first joined Spinny, one of the key areas I identified for improvement was the lack of a structured design process. Over time, I have introduced various frameworks to streamline design workflows, enhance cross-team collaboration, and ensure alignment with business objectives. As the head of design, I have worked on further optimizing these processes, ensuring they scale effectively as we continue to grow.
Upon joining Spinny, I quickly recognized the need for a structured design function within the company. At the time, designers were dispersed, collaborating with one or more product managers. It was crucial to establish clarity regarding prioritization, especially for designers working across different teams or with multiple product owners. The existing approach, primarily relying on Jira, seemed more suitable for developers rather than designers.
Airtable was free to use and we used to prioritise all our work weekly, Airtable alone was not going to solve this problem so I also introduced a weekly sync with all the PMs that my designers work with within a single project planning call. This call was more like a standup, and I ensured the forum was only used to discuss project prioritisation and not projects in detail. These calls usually get over within 20 mins.
What a typical sprint board looks like.
The impact of implementing Airtable as the preferred tool for planning design sprints and introducing weekly sync calls with product managers was highly beneficial for product designers in my team: