What makes a Platform Team work with Mason Jones from Zapier
May 28, 2024
auto_awesome
Mason Jones, recently of Zapier and a former leader at Lattice and Credit Karma, shares his journey into platform engineering. He discusses the importance of visibility in engineering processes and the challenges of transitioning from monolithic to microservices architecture. Mason dives into effective team communication strategies and the balance between immediate goals and user-centric approaches. He highlights the value of standardization and data-driven decision-making while navigating the intricacies of product management.
Mason Jones emphasizes the cultural shift required for transitioning from traditional infrastructure teams to dedicated platform teams, focusing on enhancing developer experience through user-centric practices.
Effective communication within the organization is crucial, as different messaging strategies tailored to engineers and leadership can drive buy-in and support for platform improvements.
Deep dives
Navigating Platform Engineering at Zapier
Mason Jones discusses his new role as Director of Engineering at Zapier, focusing on the necessity of evolving from traditional infrastructure teams to dedicated platform teams. This evolution aims to enhance developer efficiency and satisfaction by emphasizing a customer-centric approach to engineering. By centralizing efforts on improving developer experience, the team seeks to transform how engineers interact with their tools and workflows, moving beyond just maintaining infrastructure. Jones reflects on his journey from Credit Karma, where he learned the impact of platform development, highlighting that small changes can yield significant benefits across engineering teams.
The Importance of Treating Platform Development as a Product
Jones emphasizes the concept that platform engineering should be viewed as a product itself, complete with users, bugs, and areas for improvement. This perspective necessitates a structured approach to communicating changes across teams, ensuring that all engineers understand the tools they use. He notes the challenges encountered at Credit Karma, where rapid changes often left engineers confused about new implementations. Implementing regular updates and clear messaging could enhance awareness, fostering a more organized environment for adopting new tools and practices.
Reorienting the Engineering Mindset
Transforming the focus from infrastructure to platform requires a significant cultural shift within the organization. Jones describes the need for teams to prioritize customer feedback from engineers rather than just addressing operational noise. Engaging with users through surveys and direct interactions is essential for understanding their pain points and improving the developer experience. By cultivating a mindset that considers engineering as customers, the teams can work towards impactful solutions that genuinely address user needs while balancing operational demands.
Communicating the Value of Platform Changes
Effective communication about the improvements made by the platform team is critical for gaining buy-in from both engineers and leadership. Jones discusses tailoring messages for different audiences, ensuring that the benefits of changes are clearly articulated and understood. For engineers, highlighting efficiency gains is vital, while for leadership, emphasizing time savings and productivity can illustrate broader organizational impacts. By packaging information appropriately, the platform team can foster a culture that values continuous improvement and supports the adoption of standardized practices.
Mason Jones recently started a new role at Zapier, where he’s bringing his platform leadership experience from Lattice and Credit Karma.
In this episode, Mason shares his thoughts on what makes a platform team work, common tradeoffs in platform development, and the challenges of making your team’s work visible and understandable to the whole organization.
Find the transcript at: https://www.unblocked.fm/episodes/mason-jones-zapier/
Timestamps
(0:00) Introductions
(0:39) Mason’s journey to Zapier
(4:39) How Mason joined the platform team
(8:48) Naming teams
(11:10) The mechanics of reorienting
(15:46) Transitioning from infrastructure to platform
(20:44) Goal-setting using data
(24:39) Mason’s take on product managers
(28:48) Detangling a monolith into services
(33:49) Federating vs. centralizing
(37:04) How Mason approaches standardization
(41:22) How to communicate
(44:58) The value of case studies
(47:08) What Mason wants to achieve in a year
Follow Mason on LinkedIn: https://www.linkedin.com/in/masonjones/
Follow Rebecca on LinkedIn: https://www.linkedin.com/in/rmurphey/
Links and mentions
• Zapier: https://zapier.com/
• Credit Karma: https://www.creditkarma.com/
Get the Snipd podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share & Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered podcast player
Listen to all your favourite podcasts with AI-powered features
Discover highlights
Listen to the best highlights from the podcasts you love and dive into the full episode