AMA session on Product Led Growth with Rory - Head of Growth at Supabase ⚡️

@arjun_rakesh_k_o Copple and Ant do a great job on the leadership front to communicate priorities across the company. The teams are themselves usually figure out the actual solutions to some of the challenges and feature priorities that we focus on. Usually a few weeks out from launch week we will look at how the teams are progressing on the major things we have identified as priorities and make a judgment call on how shippable they are. This isn't just "does the feature work" - we think about documentation here because without good documentation it's harder to use the product. We also ship things every month so we don't necessarily hold features back for launch week - we just try and ship and shout as much as possible. Being async really helps a lot here as it's quite easy to facilitate the movement of information around the company (slack, github, notion, a lot of RFCs, and video recordings). When it comes to the content side of things things are currently a bit more fluid. I would love to say we have all of this ready ahead of time but it wouldn't be unusual for a blog post to be finished an hour before a feature goes live. This has been happening less and less as we get more experience around launch weeks.

@aquibbaig This one is a bit harder for me to answer compared to others in the team as it sits a bit more inside engineering. Inian and Copple have some "product principles" that the team use as a guiding light when making decisions that are geared towards enabling the team to move as autonomously as possible.

@gayatri_gaidhani 1. Tech twitter is pretty buzzing and it's amazing how willing folks are to engage on there. It's an extremely valuable source of feedback for us too. 2. IMO this comes back to building useful features (which are stable enough for release) and good documentation. Supabase is a developer tool first and foremost. If we get these things right folks want to build and showcase the problems they can solve. Also, because Supabase is Postgres under the hood, a lot of the time we are just helping folks get more out of a database which is already amazing. p.s obviously we are big fans of Toplyne too :D

@souvik2003 User onboarding and activation is definitely an interesting topic.....Wes Bush talks about "product bumpers", "conversational bumpers", and "empty states" [1] as a good starting point. I would say activation starts really before the users even start using Supabase and relates to the product decisions we make. Downstream from this, content and examples coming both from our own devrel team and the community are essential here. If a developer can clearly see how our developer experience can help their workflow then using Supabase becomes an obvious choice. Developers have a lot of different jobs to be done and at this point Supabase is a diverse tool that can be used to solve many problems for developers. Solid fundamentals are key here - content, examples, and solid documentation geared getting developers on a straight path to achieving their objective. Feedback for us comes from a whole bunch of sources: community (which includes twitter, github and other social sources), support tickets, calls with our users. We also have a feedback widget in our dashboard and occasionally run an exit survey if someone deletes a project. As our user base has grown exponentially, the feedback has too. We are still iterating around the best process to triage, prioritise and route it to the right team. We regularly review all the feedback that comes in and factor it into the decision making process for each of the feature teams. The product teams at Supabase take a lot of ownership over the features they are working on as experts in their own product and review feedback weekly during the team syncs. We also make a lot of use of notion to facilitate getting information moved around to the team. [1] https://productled.com/book