Buzz Usborne Portfolio
Principal Designer at Help Scout, previously Atlassian and Skype. His 'Inbox' case study documents a from-scratch redesign of a 12-year-old core product, with concrete iteration counts and an honest account of balancing user resistance against real pain points.
What makes it work
A breakdown of the choices that make this portfolio stand out.
Quantified iteration as evidence of rigor
Stating a specific iteration count and prototype volume substitutes for metrics he can't disclose, while still conveying real design effort and validation.
Named tension between two legitimate constraints
Explicitly framing the challenge as balancing resistance to change with genuine pain points shows awareness of change-management risk, not just visual improvement.
System-level flexibility as the core design problem
Reframing a visual refresh as an information-architecture and systems problem, since the real complexity was structural, not decorative.
Credits collaborators explicitly
Naming cross-functional collaboration rather than presenting the work as solo reads as more senior and realistic for team-based roles.
What Product Designers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
When exact metrics are confidential, quantify your process instead (iteration counts, timeline, prototype volume).
For a redesign of an established product, explicitly name the tension between improving it and disrupting existing users' habits.
Frame a visual refresh as a systems/flexibility problem whenever the real complexity is structural.
Credit the team and customer feedback loops by name.
More Product Designer portfolios
Ready to build your portfolio?
Follow the Product Designer roadmap — skills, projects, and timeline to get hired.