Lenny Rachitsky explains how GrokBot's team stopped shipping visible features and instead focused on new capabilities. They adopted a "kill as many pixels as we can" mindset, prioritizing invisible automated actions that deliver real impact over UI buttons and dropdowns.
Chapters
adding things to the product is not the goal. There is this old school software tendency to say things like GrokBot now has, and when you think of completing that sentence, it would be like a new button to press, or it'd be a new dropdown, or it'd be a new integration that you can press plus and add. And instead to reframe it as GrokBot can now, which is, I think, a much more human way of kind of describing these capabilities. And I think it's forced us to think more in the frame of what are tools and what are capabilities that we can give GrokBot, not what are new things we can add to the product. Making your bots reliably do really impactful work for you behind the scenes in a way that just works and giving them the capabilities to do that, like that's what users actually care about. And so I think there have been a lot of GrokBot now has things that we've realized are actually just capabilities that don't need Pixels, you know, let's kill as many pixels as we can. Those can just be things that your bot manipulates behind the scenes for you, and you don't need to directly control.