Lenny Rachitsky argues that if you can't write a compelling launch post for a feature, don't build it. Frame work as capabilities instead of UI elements, and let the bot handle functionality behind the scenes rather than adding unnecessary buttons and controls.
Chapters
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. The one thing we talk about internally is anything that we're working on for GrokBot What is the launch post? What is the thing that we would actually tell users? If it's not compelling, maybe we shouldn't be working on it. Adding things to the product is not the goal. There have been a lot of GrokBot now has things that we've realized are actually just capabilities that don't need pixels. 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.