Lenny Rachitsky: commitment

Transcript context

…I also think that with this particular category of tool, and with a lot of other B2B software, not... Like no means not now, right? Not right now because it doesn't fit our budget. It doesn't fit our change management situation. "Oh, we have this exec that's really wedded to this other tool," but those things change, right? So, we keep in contact with them. They're in our CRM where we make sure we follow up, and we've had a lot of these where we've been said no to, like two years ago, and now we have some new features, and then go like, "Oh, yeah, it seems like you're ready for our scale," or whatever. You mentioned that when you have these debates and questions that come out, you have features that a big company wants. There's this category of, "We know we will not build things for middle managers that want reporting and custom stuff just to track what's happening," versus something an IC wants to be more productive and successful, Linear. Give us a little sense of some of the more complicated debates that aren't necessarily in that bucket. I think the complicated debates are often when we do add a new native feature, do we extend an existing feature and make it more powerful or do we add a new sort of service? And a big part of that is trying to figure out exactly who's going to use it, what are the actual real life use cases that we know about? Like that I know that Bob from Company X has this workflow and this is how it would work for him. Here are the different variations where it would work. So, tying it all the way back to real people is-…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.