Lead Product Designer job description
Updated
A Lead Product Designer sets design direction across a team and unblocks its work. It is the product design role at level 4 of 5, measured against the same skills as every other rung on the ladder.
This is what product design teams expect from a Lead Product Designer. 37 skills, each with the mastery level set for this rung, and 3 certifications required from here on. It is one of the department templates in Competrace, so after signing up you can add it from Departments → Add from template and edit it.
Not sure how career levels fit together? Read what a career framework is
Skills and expected level
Product design — Lead Product Designer Sets design direction across a team and unblocks its work. RESPONSIBILITIES - Run a critique on contentious work with senior stakeholders present and keep the feedback about the design rather than the person. - Plan a multi-method study across several teams, and decline questions that research cannot answer or that put participants at risk. - Synthesize messy findings from several studies and sources into insights that settle a contested design question. - Map journeys that cross teams and systems nobody owns end to end, and use the map to get those teams to agree what gets fixed first. - Set the governance for what enters the system and what gets deprecated, and resolve a conflict between two teams who want the same component to behave differently. - Solve layouts with hard constraints, such as dense tables, split views or content whose length varies wildly, and keep them usable on every device. REQUIREMENTS - Experience at the Senior Product Designer level (level 3 of 5) or equivalent - Holds IAAP Certified Professional in Accessibility Core Competencies (CPACC), IAAP Web Accessibility Specialist (WAS) and Nielsen Norman Group UX Certification REQUIRED SKILLS Research - User Research Planning — You can plan a multi-method study across several teams, and decline questions that research cannot answer or that put participants at risk. - Qualitative User Interviewing — You can train other researchers to interview well, and design interview guides that a less experienced researcher can run without your presence. - Usability Testing — You can decide when usability testing is the right method against the risk being tested, and turn results into specific design changes the team actually makes. - Research Synthesis and Insight Reporting — You can synthesize messy findings from several studies and sources into insights that settle a contested design question. You say plainly when the data does not support the conclusion people want. - Competitive and Comparative Analysis — You can choose which competing and adjacent products are worth studying for a design question and turn the comparison into a recommendation. You say which patterns to borrow, which to avoid, and why. Structure & Flow - Information Architecture — You can design the information architecture across a product spanning several teams, and you catch structural decisions made elsewhere that will not scale. - Interaction and Flow Design — You can design interaction patterns that other designers reuse, and resolve a conflict between two flows that each look reasonable alone. - User Journey Mapping — You can map journeys that cross teams and systems nobody owns end to end, and use the map to get those teams to agree what gets fixed first. You leave out the detail that will not change a decision. - Wireframing — You can set the wireframing conventions your team uses, and skip wireframing when it would not save real time. - Interactive Prototyping — You can decide what fidelity of prototype a decision actually needs, and build one that persuades a sceptical stakeholder or engineer. Visual & UI Design - Visual Design — You can define the visual language for a product, and resolve a conflict between brand expression and clarity in someone else's favor or your own. - User Interface Design — You can design UI across a whole product with consistent density, spacing and behavior, and set the fidelity bar your team designs to. - Design Systems and Component Libraries — You can set the governance for what enters the system and what gets deprecated, and resolve a conflict between two teams who want the same component to behave differently. - Responsive and Adaptive Layout — You can solve layouts with hard constraints, such as dense tables, split views or content whose length varies wildly, and keep them usable on every device. You set the grid and breakpoint conventions your team works to. Accessibility - Accessible Interface Design — You can set a product's accessibility bar and publish its accessibility statement, including known issues. - Inclusive Design Practice — You can resolve conflicts between inclusion, environmental impact and a commercial or technical constraint, and teach designers to spot exclusion in their own work. - Assistive Technology Evaluation — You can run an assistive technology check across a whole feature, and retest each fix instead of trusting the ticket. Content & Handover - UX Writing and Content Design — You can set your team's tone and terminology guidelines, and settle conflicts where two teams use different terms for the same thing. - Design Critique Facilitation — You can run a critique on contentious work with senior stakeholders present and keep the feedback about the design rather than the person. You coach other designers to take critique without defending. - Design Rationale and Storytelling — You can make the case for a design that is expensive or unpopular to senior stakeholders and get a decision. You frame the same choice differently for engineers, sales and executives without changing what it is. - Engineering Handover and Specification — You can hand over designs that span several teams or an unfamiliar platform, and work out with engineers what genuinely needs specifying instead of documenting everything. You catch the edge case that would otherwise surface in production. - Design QA During Build — You can QA a complex release where the build departs from the design for sound technical reasons, and negotiate what actually gets changed. You review during the build so drift is caught before it is expensive. Design Leadership - Design Strategy — You can create design patterns and components that several teams adopt. Delivery - Project Management — You can keep several people's work in step across teams, agree priorities and hand-offs with them, and keep one shared task list that all of them actually use. - Planning & Estimation — You can estimate work that spans several teams, name the assumptions behind each figure, and rework the plan when those assumptions break. - Ownership & Accountability — You can hold accountability for outcomes delivered mostly by other people, taking the blame when it fails and passing on the credit when it works. - Quality Focus — You can set how quality is checked on complex work shared by several teams, and you spot the problems that only appear where their pieces meet. Craft - Problem Solving — You can make the call on a problem outside your expertise and explain its cost, time and risk. - Domain Expertise — You can bring in good practice from outside the organization and make it work here, and your judgment clearly improves the work you touch. - Continuous Learning — You can judge which new ideas are worth the team's time and which are not, and you make room for the people around you to learn too. Communication - Communication — You can bring disagreeing groups to agreement on the facts and the next steps, and help colleagues frame a difficult or sensitive message. - Collaboration — You can align teams with competing priorities on a common goal, surfacing the conflict early instead of letting it harden into resentment. - Writing & Documentation — You can own the documents behind a large piece of work, coordinating contributions so that people who were not involved can carry it on. - Stakeholder Management — You can hold senior and external relationships, negotiate between competing demands, and deliver unwelcome news without losing trust. Leadership - Leadership — You can lead across team boundaries, build the credibility that makes people follow you by choice, and create room for others to lead. - Mentoring — You can develop other mentors, coach people through career decisions rather than tasks, and lift the capability of a whole team. - Strategic Thinking — You can set direction for an area, choose deliberately what not to do, and defend that choice when it is challenged. REQUIRED CERTIFICATIONS - Nielsen Norman Group UX Certification (required from Senior Product Designer) - IAAP Certified Professional in Accessibility Core Competencies (CPACC) (required from Lead Product Designer) - IAAP Web Accessibility Specialist (WAS) (required from Lead Product Designer)
Lead Product Designer: common questions
The same level in related departments
Level 4 of 5 on the ladders closest to this one.
- Group Product Manager · Product management
- Content Marketing Manager · Content and SEO
- Senior Marketing Manager · Digital marketing
Rather start from a skill than a role? Browse every skill in the library
Use this exact framework in your own org
For managers and HR teams: create a free account, then add product design from Departments → Add from template: all 37 skills, with the mastery expected at each of your 5 career levels — already filled in. Rename or delete anything you don’t want.