By the end of this lesson you can
- Describe the roles of product managers and engineers.
- Collaborate effectively in a product trio.
- Avoid common friction between design, product and engineering.
The idea
Most product teams centre on a trio: a product manager, a designer and an engineering lead, working with the wider team.
- Product managers own the problem and outcomes: what to build and why, priorities and stakeholder alignment.
- Designers own the experience: how people will use it, what it looks and feels like, and evidence about users.
- Engineers own how it is built: architecture, feasibility, quality, performance and security.
Responsibilities overlap, and the best teams share ownership of outcomes.
Ways of working
- Involve engineers in discovery so feasibility is considered early.
- Share work in progress, not just finished designs.
- Join stand-ups, planning and retrospectives.
- Pair with engineers during build to solve detail problems quickly.
- Agree a definition of done that includes design quality and accessibility.
Agile rhythms
Teams often work in sprints (one to two weeks) or continuous flow (Kanban). Design usually works slightly ahead of development, but stays involved through build and release.
Why it matters in real projects
Most design problems at work are really collaboration problems: late surprises, misunderstood requirements and designs that cannot be built. Strong relationships with product managers and engineers get better products shipped faster and make the job more enjoyable. Collaboration skills are assessed in nearly every design interview.
A realistic example
A designer spends three weeks perfecting a dashboard and presents it to engineers, who explain that the data updates only once a day, so the real-time charts are impossible. Much of the work is wasted.
On the next project, the designer invites the engineering lead to early sketching sessions and shares rough work weekly. Constraints surface in day two, the design uses daily summaries with clear "last updated" times, and the build finishes ahead of schedule.
Step by step
Map roles
Write who owns what on your team.
Invite engineers early
Include them in discovery and sketching.
Share work in progress
Show rough work weekly.
Join team rituals
Attend stand-ups, planning and retros.
Pair during build
Sit with engineers on detailed problems.
Agree done
Include design and accessibility checks in the definition of done.
Common mistakes
Mistake Big reveals of finished designs.
Instead Share early and often.
Mistake Treating engineers as implementers only.
Instead Involve them in problem solving.
Mistake Disappearing after handoff.
Instead Stay involved through build and release.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 30 min
Collaboration plan
Write a collaboration plan for a project.
Steps
- Map roles and responsibilities.
- Plan when engineers and PMs will see work.
- List team rituals you will join.
- Draft a definition of done including design checks.
Deliverable
A one-page collaboration plan.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Product trios share ownership of outcomes.
- PMs own the problem, designers the experience, engineers the build.
- Involve others early and share often.
- Stay involved through delivery.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Agile delivery (opens in a new tab)GOV.UK Service Manual
Your notes
Marking complete updates your course and roadmap progress.