Collaboration, Portfolio and Career

Introduction

Great ideas only matter if they reach users. That needs teamwork with developers, product managers, researchers and business stakeholders. And to do this work professionally, you need to show your skills. This lesson covers both.

Working with developers

• Involve them early. Developers spot technical limits, and suggest simpler ways, before a design is polished.
• Speak a shared language: components and tokens, states, breakpoints.
• Hand over clearly: annotated designs, every state (hover, focus, error, empty, loading), responsive behaviour, interaction details and accessibility notes. Link to the design system.
• Be available for questions, and review the built version, not just the design.
• Be realistic about constraints, and prioritise what matters most to users.
• Respect their craft, and thank them.

Working with product managers and stakeholders

• Understand the goals of the business, and connect your work to them.
• Explain your reasoning with research evidence, not just taste.
• Present options and trade-offs, with a recommendation.
• Listen to constraints such as budget and deadlines.
• Manage feedback: ask what problem a suggestion is solving, rather than adopting solutions blindly.
• Share work early and often, so there are no big surprises.
• Learn to say "not yet" and "here is what we could do instead".

Working in agile teams

Many teams work in short cycles. Keep ahead with research and discovery, design just enough to build, validate with users often and aim for small, testable improvements. Avoid handing over perfect designs months before building.

Building a portfolio

A portfolio shows how you think, not only how things look. Hiring managers read many, so make yours clear and concise.

Include two to four strong case studies. Each should cover:

1. The problem and context, including your role and the team
2. The goal and constraints
3. Your process: research, ideas, sketches and prototypes, including the messy parts and what you discarded
4. Key decisions and why, with evidence
5. The solution, with images, and short flows or clips
6. Results: measurements or feedback, honestly reported, and what you learned
7. Reflection: what you would do differently

Tips:

• Be honest about your contribution in team projects.
• Show real thinking with real users, even in small projects.
• Use projects you care about: redesigns of services, volunteer work, personal projects. Do not copy others' work or present concepts as shipped products.
• Respect confidentiality: get permission, and remove sensitive details.
• Make the portfolio accessible, fast and easy to read, since it demonstrates your skills.
• Keep it updated.

Career paths

• UX researcher: studies users and shapes decisions
• UX or product designer: designs flows and interfaces
• Interaction or visual designer: focuses on behaviour or aesthetics
• Content designer or UX writer: words and structure
• Accessibility specialist
• Design systems designer
• Service designer: whole end-to-end services
• Design lead, manager or director

Entry routes include degrees, short courses, self-study, internships and moving from a related role such as development, marketing or customer support. Practical evidence of skill matters greatly.

Keep growing

• Practise regularly: small redesigns, critiques and experiments.
• Learn research methods, basic analytics, accessibility and how things are built (HTML and CSS help a lot).
• Seek feedback and mentors, and give feedback to others kindly.
• Join communities, read case studies and attend events.
• Learn the business side: how products make money, and how decisions are made.
• Look after wellbeing and boundaries.
• Stay curious as tools such as AI change the work. Use them as assistants, and keep human judgement, empathy and ethics at the centre.

Try it yourself

Choose a project and write a one-page case study outline using the seven headings above. List what evidence you would show for each, and what is missing. Plan one small project that would fill the gap.

Summary

• Collaborate early and clearly with developers, with complete handovers, shared language and review of the built result.
• Work with product managers and stakeholders using evidence, options and trade-offs.
• Build a concise, honest portfolio of process-rich case studies, and keep learning across research, accessibility, code and business.