4 & 5
VP of Design | Snagajob
He is VP of Design at Snagajob, the leading marketplace for hourly workers. He co-wrote 'Org Design for Design Orgs', the first book dedicated to the organization, management, and operations of in-house design teams.
In 2001, Peter co-founded Adaptive Path and was instrumental in its growth from a small boutique firm to a renowned international consultancy. More recently, he led the global design team at Groupon, including product/UX, marketing, and brand design where he doubled the team from 30 to 60 and was instrumental in the first redesign of Groupon.com since the company launched.
Peter is also perhaps most (in)famous for coining the word “blog” in 1999. Really. In the OED and everything. Since then, he’s been blogging continuously at peterme.com.
Before and since he co-founded the foundational UX firm Adaptive Path in 2001, Peter Merholz has been dedicated to parts of his users' journeys of a product: discovery through marketing and outreach, documentation, product onboarding, and customer success. Peter will begin with a reminder of making sure that your work in Developer Relations, Community, or Developer Experience aligns with your values and emotional needs. Taking that first step will help how you approach your DX work around the user journey and with necessary empathy.
Peter will also discuss his experience with assessing his users' emotional needs as they go through the product journey. He will share his techniques and ways to assess where users get stuck or move away from products when the product (or an experience related to the product) triggers fear or frustration.
Finally, empathy is a core part of making this UX and DX journey work. How do you build teams of developer advocates and community managers to be empathetic, but also not make them a buffer to other members of your company? All members in Marketing, Product, Engineering, etc. also need to observe customers empathetically to be innovative and competitive; so what are some team and communication structures that you can put in place to ensure that the value of DevRel, Community Management, and Dev Experience doesn't stay within those teams, but helps to lead and unite teams toward the shared goal of meeting user needs?