Matt Van Itallie

Second, we are really insistent on following our communication norms. We happen to be a global remote organization, but I frankly would do this even if we're all sitting in the same building. That means in practice that we are intentional about how we communicate, that we communicate about how we communicate, and that we know what our colleagues' preferences are.

You can't always be communicated with like you'd prefer, but we should at least know what our communication preferences are. So if we're not following someone else's, we're wearing them down rather than adding more energy. After that, I'd say demonstrated evidence of excellence in their field really matters. And then after that,

You can't always be communicated with like you'd prefer, but we should at least know what our communication preferences are. So if we're not following someone else's, we're wearing them down rather than adding more energy. After that, I'd say demonstrated evidence of excellence in their field really matters. And then after that,

You can't always be communicated with like you'd prefer, but we should at least know what our communication preferences are. So if we're not following someone else's, we're wearing them down rather than adding more energy. After that, I'd say demonstrated evidence of excellence in their field really matters. And then after that,

demonstrated experience in startups as everybody listening to this must know there are very different feelings for very different stages of an organization's life and some people can be wildly successful at different stages but you have to find courses for courses that match the stage that you're in especially in the products that are at the product market fit phase that kind of

demonstrated experience in startups as everybody listening to this must know there are very different feelings for very different stages of an organization's life and some people can be wildly successful at different stages but you have to find courses for courses that match the stage that you're in especially in the products that are at the product market fit phase that kind of

demonstrated experience in startups as everybody listening to this must know there are very different feelings for very different stages of an organization's life and some people can be wildly successful at different stages but you have to find courses for courses that match the stage that you're in especially in the products that are at the product market fit phase that kind of

mentality is different from rapid growth. It's different from an organization that needs to stay excellent. It's different from turnaround. And it's been a very long time since we've hired someone who hasn't recently worked in a startup.

mentality is different from rapid growth. It's different from an organization that needs to stay excellent. It's different from turnaround. And it's been a very long time since we've hired someone who hasn't recently worked in a startup.

mentality is different from rapid growth. It's different from an organization that needs to stay excellent. It's different from turnaround. And it's been a very long time since we've hired someone who hasn't recently worked in a startup.

Definitely fighting it as we've grown. If you are driving a stick shift, Google it if you don't know what a stick shift is, listeners. And you don't stall. That means you're riding the clutch too hard. You don't stall, at least occasionally. If you extrapolate it slightly, if you don't find yourself in pain points, at least sometimes, that means you have over-engineered it from the beginning.

Definitely fighting it as we've grown. If you are driving a stick shift, Google it if you don't know what a stick shift is, listeners. And you don't stall. That means you're riding the clutch too hard. You don't stall, at least occasionally. If you extrapolate it slightly, if you don't find yourself in pain points, at least sometimes, that means you have over-engineered it from the beginning.

Definitely fighting it as we've grown. If you are driving a stick shift, Google it if you don't know what a stick shift is, listeners. And you don't stall. That means you're riding the clutch too hard. You don't stall, at least occasionally. If you extrapolate it slightly, if you don't find yourself in pain points, at least sometimes, that means you have over-engineered it from the beginning.

And I definitely believe that about product scalability. So many things... can feel like the right thing to do. They feel right, man. You just feel like it's a sense of accomplishment. But if you are not getting to product market fit, if you are not getting growth, if you're not getting a feature adoption, nothing else matters.

And I definitely believe that about product scalability. So many things... can feel like the right thing to do. They feel right, man. You just feel like it's a sense of accomplishment. But if you are not getting to product market fit, if you are not getting growth, if you're not getting a feature adoption, nothing else matters.

And I definitely believe that about product scalability. So many things... can feel like the right thing to do. They feel right, man. You just feel like it's a sense of accomplishment. But if you are not getting to product market fit, if you are not getting growth, if you're not getting a feature adoption, nothing else matters.

I think we've done a really quite a good job of being rigorous for the products that are at the earliest stage and features that are at the earliest stage. When we we do a very comprehensive code scan and when we are building a new version of that piece of functionality, a new module, we hand create it.

I think we've done a really quite a good job of being rigorous for the products that are at the earliest stage and features that are at the earliest stage. When we we do a very comprehensive code scan and when we are building a new version of that piece of functionality, a new module, we hand create it.

I think we've done a really quite a good job of being rigorous for the products that are at the earliest stage and features that are at the earliest stage. When we we do a very comprehensive code scan and when we are building a new version of that piece of functionality, a new module, we hand create it.

We run the analytics, produce a CSV and build it by hand, usually for a month or two, because that's, of course, not at all scalable. Number one, it saves a huge amount of engineering time. And number two, you really have to be sure you're building the right thing.