Transcript
Leila (0:00)
Hi, Leila.
Alex (0:00)
Hi.
Leila (0:01)
I came 16 hours to see you guys.
Alex (0:03)
Wow.
Leila (0:04)
Looking forward to it.
Alex (0:04)
Where from?
Leila (0:05)
Australia.
Alex (0:06)
See, that's how much I know and how much I've traveled internationally. I'm like, is that 16 hours away?
Leila (0:11)
I have so many questions, but one. Okay, if you were to distill it down to a handful of core principles that has had you scale the way that you guys have scaled, what would they be? I mean, your people are a clear winner. I mean, freaking brilliant team.
Alex (0:27)
But other than that, I would boil it down to one saying that I think we came up with, I want to say, like, five years ago, which is like, nail it before you scale it. So I think that a lot of the times what people do is they figure out something that works well one time they don't get all the kinks out of it, and then they try and scale that. And so I think that's something that I've done really well is one, I'm not unwilling to jump in there myself first. Anything that's a new initiative in a company, no matter how far beneath my role it may be, I will jump in there and I will spin it up, I will start it up, I will do whatever because I know that I can trust. I know my level of competency. And so I don't want to risk it being an execution issue. So I'm willing to do a lot of new things from the ground up. That's the first piece to it. The second piece is that I'm not afraid to, I would say, wade in the pit of pain. So I think that a lot of people, they, like, really want to get out of it and scale it quickly because they're like, well, yeah, I can't be spending my time doing this no fucking shit. But, like, in order to make sure it's going to work for the long term, we have to be willing to wait in the pain in the short term. And so if that means that I have to be head of a department for six months or eight months or a year or a year and a half to make sure it's done right, then I'll do that until I know that I can. I understand the full scope of a role, to then scale it, pass it off to somebody else so that they can duplicate my results without losing quality. A lot of people, when they scale, they assume, okay, when I scale things dilute, that means you're scaling wrong. If you really want to scale something correctly, then you know it well enough to scale it with quality, meaning you can keep the same KPIs as you scale it that you did when maybe you were doing it yourself. You had other people involved. And so I think that that's probably been an advantage that we've had is I think both Alex and I are willing. There's also two of us, so we can do each deploy ourselves into something. And now we're at the point where we have a handful of individuals on the team that I know I can trust their competence to deploy them into new things as well. But for the first six years of my career, it was really just me going in, nailing it, then scaling it. I think if I had to put it down to how to scale something, that's what it would be. I think where a lot of people miss out is they try and scale it soon before they really understand the full scope of something and they try and replace themselves too soon. Until I can visualize the type of person I need for the role. Like I see them clearly, I see their personality. I see what kind of job they might have had. I see I don't know the role well enough to hire the right person.
