Team Structure
Working with senior leaders across Tech, Product and Engineering to set the vision, OKRs and roadmaps for the domain.
Objective & Challenges
At Cazoo, downsizing the company meant that teams and their output required adjusting. OKRs needed to be more focused and verified collectively. We had to shift our ways of working and mindset from growth to driving margin/achieving profitability. The challenges we faced for phase one:
-
New teams with different remits
-
An aggregate view of opportunities & bets
-
Prioritisation with reduced capacity
The Approach
The approach was simple - get the basics right, get the teams up and running and motivated, get closer to the detail of OKRs and work together to make it happen!
Domain Team Structure
We needed to change the shape of the team to allow for better alignment to value streams.
The task of moving people and re-shaping teams and their output was complex and took many sessions collaborating with Heads of Product and Engineering to establish the 'right fit'.
​
-
Team objective / OKRs / Stakeholders / Commercials
-
Team members based on skillset
-
Opportunities for optimisation xxx
Opportunity Mapping
In collaboration with Product, Engineering, stakeholders the UX team lead a session to create a birds eye view of the experience space. We mapped out all the ecommerce journeys and invited people to help us:
​​
-
Identified opportunities
-
Map common themes
-
Cross-referenced the themes with data and research
-
Create a prioritised roadmap of themes
Roadmap & Capacity
​After themes were established we needed to translate this into a realistic roadmap for Tech and stakeholders:
-
Working sessions with the team leads in, Product, UX and Engineering to create an initiatives roadmap
-
We assessed sliced work according to priorities, milestones and created phases.
-
The roadmap was prioritised with stakeholders and senior tech leaders