Building a Collaborative Culture: Lessons from Pocket and Figma

Building a Collaborative Culture: Lessons from Pocket and Figma

In the fast-paced world of tech, the journey from a small startup to a user-centric powerhouse can be a daunting task. Two companies that have navigated this journey with remarkable success are Pocket and Figma. Each organization, despite its unique challenges, has discovered that the key to thriving lies in maintaining focus, cultivating collaboration, and fostering a culture of reflection. By examining their approaches, we can derive valuable insights on how to effectively build products and processes that resonate with users while driving team cohesion.

At Pocket, a team of just 20 people managed to amass 20 million users. This extraordinary feat was not merely a result of an innovative product but was largely due to the team’s ability to focus on critical goals. In the early days, when the team was small, they rallied together around a singular mission: to provide users with access to content for later enjoyment. This singular focus allowed them to make quick decisions and act decisively, a stark contrast to the scattered efforts that can emerge as teams grow.

Similarly, Figma’s Product Management (PM) team emphasizes the importance of cross-functional collaboration and transparency. By engaging in frequent brainstorming sessions that draw input from diverse perspectives, they ensure that great ideas are refined through collective insight. This collaborative spirit is essential in driving product development forward. The PM team's culture of trust and inclusion mirrors Pocket’s approach, where feedback is not only welcomed but actively sought from users and team members alike.

However, as teams grow, maintaining this focus and collaboration can become a challenge. Pocket learned that adding more people can sometimes lead to a dilution of direction. The integration of new team members necessitated a recommitment to their core mission, emphasizing the need to prioritize what truly matters at any given moment. This sentiment resonates with Figma's approach of utilizing tools like the "Buy a Feature" prioritization exercise, which helps align the team's focus on what features or improvements are most valuable to users.

To navigate the complexities of product development effectively, both teams have embraced the concept of co-creation with their users. Pocket shifted its Beta channel from simply delivering updates to fostering conversations that encourage user collaboration. By treating users as partners in the development process, they are able to gather actionable feedback that directly shapes their product roadmap. Figma echoes this sentiment by encouraging PMs to share their hard problems and seek input from colleagues early in the development process. This not only aids in problem-solving but also builds a sense of community and shared ownership among team members.

One of the most valuable practices that both Pocket and Figma have adopted is the regular reflection on their processes and outcomes. Pocket’s commitment to retrospectives, or “retros,” is an integral part of their culture, mirroring Figma's structured reflection sessions. These retrospectives provide an opportunity for teams to celebrate successes, acknowledge challenges, and identify areas for improvement. By asking targeted questions such as “Are we building the right things?” and “How effectively are we making decisions?” both teams can ensure that they are continuously evolving and adapting to the needs of their users.

As we reflect on the journeys of Pocket and Figma, several actionable insights emerge that can be adopted by teams looking to enhance their collaborative and product development efforts:

1. Maintain Focus: Establish clear priorities and ensure that every team member understands the current goals. This can be achieved through regular check-ins and alignment meetings that reinforce the importance of tackling one critical task at a time.

2. Encourage User Collaboration: Shift your feedback mechanisms from one-way communication to collaborative discussions. Actively involve users in the product development process, seeking their input and insights to create a more user-centered product.

3. Implement Regular Reflection: Schedule regular retrospectives to assess progress, celebrate achievements, and identify areas for improvement. Use structured frameworks like “start, stop, continue” to guide these discussions and ensure that everyone’s voice is heard.

In conclusion, the stories of Pocket and Figma illustrate that success in product development is not solely about having the best ideas; it is equally about cultivating a collaborative culture that values focus, user engagement, and continuous reflection. By embracing these principles, teams can navigate the complexities of growth while remaining aligned with their mission and responsive to the needs of their users.