- They have two products—Figma Design and FigJam—so we have two teams solely focused on the product. We then have “horizontal” platform teams that build features and solve problems across both products, e.g. the “Enterprise” group that focuses on making both of these products amazing for large enterprises and the “Infrastructure” group that ensures the reliability and performance of both products.
- Design, Research, and Product Management are part of Figma’s larger Product organization.
- The product team is our proximity to customers. We spend a lot of time with them, and crucially, we do our best to maintain a close relationship with the community. Some of our leaders regularly reach out to the community (e.g. on Twitter) to ask what they want to see us do better, and we spend time sifting through all of the amazing discussions that follow on these platforms. Some of our PMs are close enough to customers that we can just text them to ask for feedback on an idea. Dylan spends a lot of time looking at customer feedback because he wants to have a pulse on how our users feel and build intuitions around what’s important to them.
- The leadership team sets high-level company priorities to frame key strategic investments. It’s then up to product teams to chart out the path to reach those goals.
- A bigger planning cycle happens twice a year, with product teams revisiting their goals and roadmaps.
- Over time, we began formalizing things more, with a cadence for different altitudes (annual company priorities, larger half planning, and quarterly refreshes/adjustments).
- [In the early days] Instead of OKRs, they have well-defined headlines — essentially, claims that they’d like to make by the end of some period. It produced the right debates and allowed teams to be more creative about measuring whether they’ve achieved that headline. Came back to OKRs much later.
- Crits are a central part of our design culture at Figma. We believe it’s important for everyone to see how designers share ideas and offer feedback on projects. We encourage every employee to attend at least one crit per year, regardless of their role or position.
Improving code review time at Meta
- Nearly every product team at Meta uses experimental and data-driven processes to release and iterate on features.
- Introduced a feature called Next reviewable diff. Used machine learning to identify a diff that the current reviewer would likely want to review.
- Improved reviewer recommendations. Built a new reviewer recommendation system, incorporating work hours awareness and file ownership information. This allows reviewers that are available to review a diff and are more likely to be great reviewers to be prioritized. We rewrote the model that powers these recommendations to support backtesting and automatic retraining.
- Added a Stale Diff Nudgebot. For diffs that were taking an extra long time to review, Nudgebot determines the subset of reviewers most likely to review the diff. Then it sends them a chat ping with the appropriate context for the diff along with a set of quick actions that allow recipients to jump right into reviewing.
- Mighty’s short-term goal was to make people more productive with their browsers.
- The biggest fraction of users passionate about Mighty were mainly compelled by its speed.
- Many users didn’t continue paying for the product for various reasons. Some of the top ones were networking stutters, stability issues, and missing features (like webcam support).
- While Suhail (Founder, CEO) was the one to make this decision and has the full context on the decision, as I see it, the benefits of Mighty weren’t substantial enough to handle the drawbacks, thus churn was unlikely to be quickly brought down to reasonable levels.
- Mighty ended up being incredibly challenging. Building a feature-compatible browser was only one of our several tough challenges.
- All this fiddling with badges and checks is a waste of time. It degrades the value of Twitter’s platform and does its users a disservice. Instead of self-defeating $8 cash grabs, Twitter should focus on deepening its users’ ability to create value for each other through entertainment, knowledge, and connection—and to bring more valuable creators into the network.
- People tend to seek the most efficient paths to gaining social status. Social networks succeed when they give a meaningful segment of the population a uniquely efficient path to winning status.
- Instead of focusing on status symbols, Twitter—and anyone building a social network—should focus on helping users create things for each other that have real value: entertainment, knowledge, and connection.
- A person’s status is ultimately a function of the value they create for others. Making the symbols of status more visible without increasing value creation is like printing money without increasing the economy’s productive capacity.
- Twitter allowing anyone to buy a blue check makes about as much sense as Harvard allowing anyone to purchase a degree: the value proposition evaporates when anyone can get it.
- With status alone, life feels empty. Admiration is not a substitute for friendship. People don’t just want to be high status. We also want to have genuine, non-transactional relationships. We want to feel like we’re a part of a community that is bigger than ourselves. We want to work toward goals that matter to us alongside others who feel the same way.
It’s easy to imagine that they are, as it lets us off the hook as habits become negative, or even addictions. If someone else is thriving without the habit we seem to need, then it’s likely a desire pretending to be a need.
What do you need to achieve high standards in a particular domain area? First, you have to be able to recognize what good looks like in that domain. Second, you must have realistic expectations for how hard it should be (how much work it will take) to achieve that result – the scope.