Design Leadership · Leeroy
Leading a design team from delivery to product ownership
Once Leeroy’s core platform was in place, the nature of our design work changed. We no longer needed just to build new features. We needed to understand how the products worked for customers and users, improve what already existed and decide what mattered most to develop next.
As UX Design Manager, I was the line manager for four designers, one in each product team. I wanted them to move beyond mainly delivering solutions towards researching user needs, framing problems and taking greater responsibility for what their teams built.
I proposed a new split of responsibilities between product designers and Product Managers, then led the change with management and the product teams. Alongside that, I coached the designers into their new roles and worked with them to develop a shared design process, design principles and a common UI component library.
The outcome was product designers who took greater responsibility for UX discovery, backlog planning and the quality of the user experience. More decisions could be made within the product teams, while keeping Leeroy’s four products connected.
- My role
- UX Design Manager, line manager for four product designers
- Year
- 2019–2021
- Team
- Four product designers, one in each product team, working together as one design team
- Industry
- Restaurant tech, SaaS and fintech
- Products
- Ordering and loyalty app, POS and table service, back office and kitchen display
- Company
- Leeroy Group
The short version
The problem
As more customers began using Leeroy’s products, designing new interfaces from predefined requirements was no longer enough.
Designers needed to get involved earlier, understand the problems and influence what their teams prioritised. At the same time, we had to keep the experience consistent across four products serving different users in very different settings.
My contribution
As UX Design Manager, I had line management responsibility for four designers and led the shift from UX/UI delivery to broader product design ownership.
I clarified roles with management and product teams, coached the designers and worked hands-on with the team on our shared design process, critique, principles and design system. I also helped the teams see the whole user journey across the products.
The outcome
Product designers began running UX discovery, framing user problems and driving backlog planning and prioritisation together with their teams.
Shared principles and ways of working supported independent decisions within the product teams and a more connected experience across products.
When the designer’s role needed to change
Leeroy developed a restaurant platform with four product areas: POS and table service, a back office, an ordering and loyalty app, and a kitchen display.
Each product had its own cross-functional team and dedicated designer.
While we built the core platform, much of the design work involved turning ideas and requirements into interfaces developers could build. But once customers were using the products, we also needed to understand how existing solutions worked in practice, identify new needs and prioritise improvements.
From delivering solutions to understanding the problems
I saw a need to change the designer’s role. Designers shouldn’t only get involved after someone else had decided what to build. They needed to be able to run UX discovery, investigate user needs and frame the problems worth solving.
They also needed greater responsibility for UX quality and the business value their work was intended to create, before and after launch.
The shift was from mainly delivering solutions to helping own the problems.
- Mostly designing: from ideas to development-ready design
- Designing the core products, while the platform was built
- The backlog was a shared team responsibility
- Running UX discovery, and framing the problem for new or improved user experiences
- Development-ready design for the developers to build
- Driving what to do: the backlog planning and prioritisation with the team
- Ensuring UX quality and business impact, before and after launch
Clearer responsibility for the backlog
Leeroy didn’t have separate product owners. The backlog was a shared responsibility in each product team.
I proposed giving the product designer a clearer role in driving backlog planning and prioritisation, working together with the team. Not everyone agreed at first; we needed to clarify how responsibility would be shared between designers, Product Managers and the teams.
We agreed that Product Managers owned product discovery and overarching roadmap themes. Product designers ran UX discovery, framed user problems, drove backlog work with their teams and delivered development-ready design. As UX Design Manager, I developed the designers and coordinated our shared design work.
The role therefore combined aspects of what larger organisations often split between product owners and designers.
- Product discovery with customers and users
- The roadmap and its themes
- Align user and business needs
- Run UX discovery and frame the problem
- Backlog planning and prioritisation with the team
- Development-ready design for the developers
- Work closely with the product manager
- Shared product design work
- The design system and the design process
- Skills, retros and design critique
- Hiring, and the everyday line manager work
A change that needed agreement
I led the proposal with management and the product teams. The important part wasn’t a new title, but a shared understanding of who was responsible for what and how decisions would be made.
Once expectations were clear, I could help each designer grow into the role.
Helping four designers grow into greater responsibility
As UX Design Manager, I had formal line management responsibility for four designers. I had recruited some of them myself. Each worked in a separate product team, while also belonging to the design team I led.
My responsibility was to develop their skills and independence, while protecting time for the design work we needed to do together.
Coaching alongside the real work
We held regular one-to-ones and set individual development goals. I worked closely with the designers on discovery, problem framing, prioritisation and following up on the user experience.
A clear role description, workshops and training supported their skills in research, prioritisation and understanding business value. But much of the most useful coaching happened in our day-to-day work: exploring a problem, testing an assumption or reviewing an early prototype together.
The goal was for the designer to be able to do the same independently next time.
One designer’s journey
One designer in the team was highly skilled at creating solutions but often became involved once the direction was already set.
What needed to change wasn’t their ability to design an interface. It was their opportunity and confidence to contribute earlier.
We worked together on discovery, feedback and design critique. I coached the designer in framing problems, testing assumptions and using research to influence conversations within the product team.
Over time, the designer began running workshops independently, testing assumptions and using user insights to shape product decisions.
That made the designer more independent and helped the team make better-informed decisions.
For me, it was a tangible sign that the change was working: the designer was no longer waiting for a solution to design, but helping establish which problem needed solving.
Improving together as a team
We used retrospectives every sprint, small experiments and regular check-ins to improve how we worked together and how people felt about the new responsibility.
A few shared habits became particularly valuable:
- Fortnightly demosbrought feedback earlier and made the team’s work visible to sales, support and management.
- Design critiquehelped us exchange knowledge and improve ideas while there was still time to change them.
- Design sprintslet the teams test concepts with users and stop weaker approaches early.
- Cross-functional ideationinvolved developers and other perspectives while problems and solutions were still being explored.
My responsibilities as line manager
I was also responsible for hiring, individual development, everyday line management and aligning design capacity with Product Managers as priorities shifted. I made sure designers had time to contribute to our shared design system alongside product development.
- Design process
- Way of working
- UI component library
- Consistency between products
- Design critique
- Design principles
- UX discovery
- UX discovery, and framing the problem
- Backlog planning and prioritisation with the team
- User flows, prototypes and testing with users
- Development-ready design for the developers
- UX discovery, and framing the problem
- Backlog planning and prioritisation with the team
- User flows, prototypes and testing with users
- Development-ready design for the developers
- UX discovery, and framing the problem
- Backlog planning and prioritisation with the team
- User flows, prototypes and testing with users
- Development-ready design for the developers
Here I was also the Product Manager: discovery, roadmap and priorities
- UX discovery, and framing the problem
- Backlog planning and prioritisation with the team
- User flows, prototypes and testing with users
- Development-ready design for the developers
Shared product design work
The work no single product team owned: the overall experience, and the parts shared between products.
Design system
Time for the designers to continuously improve the design system, alongside the product development.
Design process
Making sure we kept following one design process, from discovery to delivery.
Skills and coaching
Developing each designer’s craft, and supporting them in their new responsibilities for user needs and the backlog.
Retros and design critique
Regular retros, and design critique where designers showed their work early and learned from each other.
Hiring and capacity
Recruiting designers, and aligning design capacity with the product managers when priorities shifted.
Shared principles instead of approvals
With more decisions happening inside product teams, we needed shared ways to reason about design. Four designers worked on different products and use cases, but the experience still had to feel connected.
I didn’t want to become the person who had to approve every solution.
My goal was to give designers the foundations they needed to make sound decisions themselves.
One design process everyone could use
Together, we developed a five-step process: Discover, Define, Design, Test and Deliver.
It gave us a shared language from research and problem framing through prototypes, usability testing, development-ready design and follow-up. Designers could more easily understand one another’s work and support each other across teams.
- 1DiscoverResearch with customers and users, and their needs and pains.
- 2DefineOpportunities, user flows and what to solve first.
- 3DesignConcepts and prototypes, shared early.
- 4TestWith users, before anything is built.
- 5DeliverDevelopment-ready UI, followed up with the team.
Design critique while there was still time to change
We made design critique a regular part of the work. Designers brought sketches and prototypes, not just finished screens.
We started with the user and their task: Who is this for? Which problem are we trying to solve? What needs to work? Feedback had to be specific, respectful and actionable.
When designers from other products joined, they could spot dependencies and inconsistencies with our shared patterns.
Critique became an opportunity to learn and improve, rather than a late approval stage.
Show work early
Designers brought sketches and prototypes, not finished screens, while there was still time to change direction.
Start from the user and the goal
Feedback began with who the design was for and what it should achieve, not with taste.
Specific and kind
Concrete, respectful feedback that the designer could act on.
Eyes from other products
Designers from the other product teams spotted where a flow broke a pattern, or touched their product.
Design principles for different users
Based on our research, the designers, product teams and I developed principles for each product. Diners, restaurant staff and restaurant owners had very different needs and working environments.
The principles helped designers make decisions within their own product teams without having to check every detail. They provided a common direction without making every product the same.
- The mobile ordering and loyalty app, and the self-service ordering kiosksDiners
- The brand comes first: the app is the restaurant’s, not ours
- Order in a few taps
- Always know the status of the order
- One membership in the app and at the till
- The POS and the kitchen appsRestaurant staff
- Fast in the rush: the most common orders in the fewest taps
- Large touch targets, readable at a glance and from a distance
- Orders from every channel in one place, in the right order
- One tap to mark an order ready
- The POS back officeRestaurant owners and administrators
- Set it once, use it everywhere: products, prices and menus for the POS, the app and self-service ordering
- See every venue and sales channel at a glance
- Safe to change, with a clear view of what goes live where
A shared UI component library
We also created shared interaction patterns and a common UI component library. A diner on a phone, staff at a busy till and an administrator at a desk needed different interfaces, but the same foundation should connect the products.
The apps used native iOS and Android components. We added shared patterns and a visual theme for each restaurant brand.
I made sure the design team had time to keep developing that common foundation even when product delivery was busy.
The principles and component library allowed us to combine autonomy within teams with consistency across products.
One design team connecting four products
The design team worked on products for diners, restaurant staff and owners. But the user experience didn’t stop at product boundaries.
An order could start on a diner’s phone, continue through the POS and kitchen, and finish when the food was collected. Later, the same diner might receive an offer and return.
Improving that experience required us to understand the whole service.
Mapping what diners see – and what happens behind the scenes
The designers and I developed a service blueprint covering six stages: Discover → Order → Pay → Prepare → Pick up → Return.
We mapped both diner actions and what happened backstage: staff at the till and counter, the kitchen, and the responsibilities of the back office and underlying systems.
I reviewed each part with the relevant Product Managers. This made it easier to see where the service could fail even when individual interfaces appeared to work.
Scroll sideways to see the whole flow.
From user insight to the right product team
We placed problems and opportunities from research at the point in the service blueprint where they occurred and connected each insight to the responsible product team.
Product designers brought those insights into their teams’ priorities and roadmaps. We described improvements in terms of what users would notice and the KPIs they were intended to influence.
When an improvement involved several products, it needed to be included in several teams’ planning.
An example: points lost at the till
We found that diners weren’t receiving loyalty points when they paid at the till rather than in the app.
From the diner’s perspective, this was a problem with their membership. For us, fixing it required changes to both the app and the POS system, developed by different teams.
It showed why we needed to work from the whole journey and coordinate product planning. I explore the work in more detail in the separate Leeroy Loyalty case.
Four designers could work independently in their product teams, while taking shared responsibility for the dependencies between products.
What changed when decisions moved closer to the teams
Through clearer responsibilities, coaching and shared practices, the design team’s role in product development changed.
Designers framed the problems
Product designers began running UX discovery, framing user problems and driving backlog planning and prioritisation together with their teams. They continued delivering development-ready design and took clearer responsibility for following up on UX quality and intended business value.
Product Managers had more room for direction
With product designers taking greater responsibility for the backlog, Product Managers could focus more on product discovery and the broader roadmap themes.
More decisions happened close to the work
Design principles, critique and shared components gave designers the support to make sound decisions with their teams without needing sign-off on every detail.
We connected the service across products
The blueprint and shared design work made dependencies visible and gave product teams a better basis for improvements across the diner journey.
These were primarily qualitative changes in responsibilities, collaboration and team capability. There are no reported metrics that attribute an increase in development speed or design quality to the change.
What I took with me
Clear responsibilities enable autonomy
It’s not enough to tell a designer to take more ownership. Product Managers, product teams and designers need to understand who is responsible for what. Once we clarified the roles, designers could get involved earlier and make decisions with greater confidence.
Shared principles work better than approvals
As more people take responsibility, not every decision should go through one person. My job as a design leader became creating a shared direction, making our reasoning visible and helping others make good decisions themselves.
Design the whole service, not just one product
Each team needs to understand its own users, but also how its work affects the next step. The blueprint revealed dependencies that might otherwise have fallen between teams.
My goal was never to have more design decisions come through me. It was to help designers understand the problems, take ownership and make better decisions themselves.
“I worked closely with Mikaela for several years. What impressed me most was her ability to lead product discovery, turn customer and user insights into product direction, and drive product development through her leadership of the design team — always with contagious passion and drive!”
