Podcast Appearances
people tell us exactly what to do after that like once the foundation is there and people can roughly get what they what what the feature is they'll tell us what else selling they need they'll tell us like where else we need to make it work they'll tell us what sucks about it and it gets very easy from there they're on and whoever worked on it they do that full cycle there's no one that's like receiving the feedback and summarizing it for the engineer they're receiving the feedback they're getting the github issues they're getting the replies on on on twitter
And they're figuring out the roadmap and the cycle for it.
So that first phase is the hardest.
But from there, again, the feedback loop kicks in.
Things get better over time.
One of the things that we try to do is...
Like the founders, we try to make sure that the whole team has perspective on everything that we care about, the market, our competitors, what we're trying to do, our position in it.
If they properly understand that, they naturally land on their own priorities.
For us, motivation is a huge thing.
I said earlier, we know it's a long game.
If it's a long game, your strategy should be, how can I stay in it the longest?
The only way to do that is to work on stuff that is exciting every single day.
We kind of let the whole team grab stuff that they're excited about.
What's the biggest problem they want that they think is the worst thing that's hurting us?
They're just going to grab that and work on it.
They roughly end up having good judgment if we're doing a good job providing them like the right context about what's going on.
So typically people just grab stuff.
There's been times where our team really want to work on something and I like vocally disagree with it.
I was like, I don't think we should work on that.
And they've been right.