How did Zapier start, and what was their initial strategy?

Zapier began as a side project developed during nights and weekends. Their initial strategy was horizontal, focusing on integrating as many apps as possible rather than targeting specific industry personas. This was driven by user requests after a TechCrunch launch highlighted unmet integration needs.

Why did Zapier commit to being a remote-first company from the beginning?

The commitment to remote work was partly out of necessity for the founding team, who were juggling other jobs. It also aligned with their core value of autonomy and wanting to build a company where they themselves would want to work, free from the constraints of a physical office.

What are the key values Zapier cultivates for its remote team?

Zapier emphasizes values like 'default to action' and 'autonomy'. This means empowering employees to make decisions, take initiative, and identify tasks independently, rather than waiting for directives, which is crucial for a successful remote environment.

How does Zapier manage communication across a distributed team and different time zones?

Zapier intentionally makes communication explicit, teaching employees when to raise communication bandwidth (e.g., from Slack to Zoom). They also foster asynchronous communication norms, with expected response times for messages and a focus on written documentation.

What are Zapier's core processes for product development and team alignment?

Zapier uses OKRs (Objectives and Key Results) as a framework for team alignment, with shared ownership between Product Managers, Designers, and Engineers. They also emphasize explicit processes and documentation, and have regular design review cadences.

How does Zapier handle internal knowledge sharing and documentation in a remote setting?

They use an internal blog tool called 'Async' for more thoughtful, long-form communication and documentation, complementing Slack's real-time chat. They also use a wiki tool called 'Quit' for lasting documentation like processes and hiring rubrics.

What role do company retreats play in Zapier's remote culture?

Zapier holds two company retreats per year to build empathy and strengthen in-person relationships, which is vital for text-based communication. These retreats often include hackathons and, more recently, unstructured time for spontaneous collaboration and bonding.

How does Zapier conduct design critiques remotely?

Remote design critiques involve explicit processes like 'nine-box' design exercises done via video calls, where participants sketch ideas and hold them up. There's an emphasis on encouraging participation and shared visual artifacts (photos posted in Slack) to foster creativity and feedback.

What is Zapier's advice for startups building a remote company culture?

Zapier advises that building a remote culture is more about guiding principles than just tools. Key aspects include establishing autonomy, encouraging written communication, documenting everything, and empowering individuals to default to action from the very beginning.

Key Moments

Mike Knoop on Product and Design Processes for Remote Teams with Kevin Hale

Y Combinator

Science & Technology3 min read64 min video

Mar 6, 2019|9,863 views|179|5

YC Y Combinator Mike Knoop Zapier Kevin Hale Interview Podcast Remote Remote Work Craig Cannon

Save to Pod

Key Moments

TL;DR

Zapier's CPO on building remote product design processes, culture, transparency, and tools.

Key Insights

Remote work necessitates explicit processes for communication, decision-making, and knowledge sharing, which ultimately benefits all companies.

Zapier's success stems from its horizontal strategy of integrating numerous apps and fostering an open platform, driven by necessity and user demand.

Building a remote-first culture requires intentionality, focusing on values like 'default to action,' autonomy, and excellent written communication from the outset.

Internal tools, like Zapier's 'Async' blog, are crucial for managing information overload and facilitating thoughtful, long-term communication in remote settings.

Effective remote design collaboration relies on explicit processes, asynchronous workflows, and occasionally shared, focused in-person or virtual sessions.

Company retreats are vital for building empathy and strengthening relationships, mitigating potential misunderstandings inherent in text-based communication.

FOUNDING PRINCIPLES AND EARLY GROWTH

The discussion begins with the founding of Zapier, emphasizing its early commitment to remote work, stemming from co-founder Mike Knoop's experience and the company's focus on automating workflows between various web applications. Zapier's business model addresses a critical need in the exploding SaaS market: enabling disparate tools to communicate. This horizontal strategy, focusing on integrating more apps rather than specific verticals, proved successful due to the necessity of connecting the growing number of specialized software tools used by businesses.

THE POWER OF PLATFORMS AND PARTNERSHIPS

An early strategic decision for Zapier was to become a platform by enabling partners to build integrations. This was driven by the realization that they couldn't build all desired integrations themselves. The value proposition for partners wasn't just distribution but also retention, as integrations allowed them to fulfill customer requests, saying 'yes' to integration needs that were previously on their backlog. This approach significantly accelerated Zapier's growth and app directory.

CULTURE AND VALUES FOR REMOTE SUCCESS

Zapier's remote-first culture is built on core values like 'default to action' and empowering autonomy. Founders intentionally designed the company culture to foster these traits, recognizing that remote work demands proactive individuals. This emphasis on self-driven employees, who can identify and act on opportunities without constant supervision, is crucial. The company actively seeks candidates who demonstrate this initiative and can thrive in an environment where explicit communication and documentation are paramount.

MANAGING COMMUNICATION AND KNOWLEDGE IN A DISTRIBUTED TEAM

Effective communication is a cornerstone of Zapier's remote operations. Recognizing that Slack alone can lead to noise, they developed an internal blog called 'Async' for more thoughtful, long-term communication and documentation. This system allows for curated feeds and ensures crucial information isn't lost in high-volume text-based channels. The company also encourages asynchronous communication, understanding that focused deep work is essential for productivity, and provides guidelines on when to escalate communication to higher-bandwidth formats like video calls.

SCALING DESIGN AND PRODUCT COLLABORATION REMOTELY

For product and design teams, Zapier emphasizes strong relationships between Product Managers and Product Designers, fostering shared ownership. They utilize frameworks like OKRs (Objectives and Key Results) to ensure alignment across teams, with a blend of top-down strategic direction and bottom-up initiative. Design critiques and collaborative exercises are conducted using tools like Zoom, with explicit guidelines to encourage participation and creative risk-taking. Processes are documented and shared, enabling teams to iterate rapidly and receive focused feedback.

STRATEGIES FOR MAINTAINING MORALE AND TEAM COHESION

To combat the challenges of remote work, Zapier invests in two company-wide retreats per year. These in-person gatherings are vital for building empathy, strengthening relationships, and fostering a shared understanding among employees. While hackathons and structured team activities are common, recent retreats have incorporated significant unstructured time, allowing for spontaneous cross-team collaboration and idea generation. This balance between structured connection and organic interaction helps maintain morale and reinforces the company's collaborative spirit.

Mentioned in This Episode

●Software & Apps

●Companies

●Organizations

●People Referenced

Key Principles for Remote Team Success

Practical takeaways from this episode

Do This

Establish clear communication protocols and teach the organization when to increase communication bandwidth (e.g., from text to video calls).

Set explicit expectations for responsiveness (e.g., acknowledging Slack messages within 24 hours).

Encourage employees to develop social networks outside of work to support mental well-being.

Hire for 'default to action' and empower individuals to make decisions and identify other valuable tasks when blocked.

Be explicit about processes, decision-making frameworks, and writing down and sharing work and information.

Utilize tools like internal blogs (Async) for thoughtful, long-form communication that complements fast-paced chat (Slack).

Schedule regular company retreats (e.g., twice a year) to build empathy and strengthen in-person relationships.

Incorporate unstructured time into retreats to allow for cross-team collaboration and spontaneous idea generation.

Foster a culture of continuous feedback and iteration, using tools and processes like design reviews and surveys.

For new remote companies, intentionally build a culture that encourages autonomy, written communication, and explicit processes from the start.

Avoid This

Do not expect employees to keep up with every Slack channel; encourage leaving channels that are not relevant.

Do not rely solely on ephemeral communication like Zoom calls for knowledge sharing; document processes and decisions.

Do not over-plan every minute of company retreats; allow for unstructured time and serendipitous interactions.

Do not assume that remote work is solely about tools and processes; it is fundamentally a cultural shift.

Do not fall into the trap of believing a real company needs a physical office; focus on output and impact.

Do not get discouraged by initial skepticism from investors or employees about the remote model; validate through success.

Do not optimize for random 'water cooler' moments over consistent, reliable work output and clear processes.

Common Questions

Zapier is a software that automates tasks between different web applications. It allows users to connect various tools they use for work, eliminating manual data entry and copying, and running automations in the background to increase productivity.

Topics

Mindset & Self-Improvement Technology & Innovation Business & Entrepreneurship Company Culture Product Development Startup Strategy Remote Work Team Collaboration Founder Journey Process Documentation

Mentioned in this video

Software & Apps

Slack

A communication and collaboration platform used extensively at Zapier as their primary 'company office'. The discussion covers managing noise, channel expectations, and Zoom etiquette.

Help Scout

A company that uses a tool called P2 for internal communication, which inspired Zapier's own internal blog tool, 'Async'.

Jira

A project management tool that Zapier can integrate with. Notifications can be sent to JIRA when issues are closed in other systems.

A WordPress plugin used by Help Scout for internal communication, which served as inspiration for Zapier's 'Async' tool.

Basecamp

A company known for its remote work culture and as an inspiration for Zapier's own remote-first approach. They were mentioned as a successful fully distributed workforce.

Companies

Salesforce

A CRM company often used as an example of a platform business. The discussion mentions its AppExchange as a distribution channel for partners.

Facebook

Mentioned as a company famous for its internal tools and for having a dedicated team for them. This was brought up in the context of Zapier's own internal tool development.

Y Combinator

A startup accelerator that Mike Knoop and Kevin Hale have strong ties to. They discuss their experiences applying to and going through YC, and how it shaped Zapier's early days and remote-first approach.

Automatic

An early remote-first company that Zapier looked up to for inspiration and as proof that large remote organizations are possible.

Zapier

A piece of software that automates tasks between different web applications. It helps users be more productive by connecting tools and automating data transfer, with a focus on being a horizontal, integration-focused platform.

GitHub

A platform used by project managers for managing team workflows. Zapier can integrate with GitHub to automate notifications for issue changes.

Wufoo

A form-building software company founded by Kevin Hale, which was a remote-first company. This served as an early inspiration and case study for Zapier's remote work model.

Organizations

TechCrunch

A news publication that featured Zapier during its launch. The launch announcement led to a surge in user requests for app integrations not yet supported.

Envision

A large, largely remote organization mentioned as an example for Zapier to look up to.

Concepts

Quit

A wiki or collaborative documentation tool used by Zapier for long-form documentation like processes and hiring rubrics.

People

Kevin Hale

Partner at Y Combinator, founder of Wufoo. He shares insights on founding a remote company, Y Combinator's process, and the evolution of product and design strategies.

Daniel Kahneman

A Nobel laureate in Economics, known for his work on cognitive biases and fast vs. slow thinking. His ideas are referenced in the context of Slack's immediate, 'fast thinking' communication style versus slower, more deliberate thought in internal blogs.

Mike Knoop

Co-founder and Chief Product Officer of Zapier, with a background in front-end engineering and product design. He discusses scaling design teams and Zapier's product and remote work strategies.