Transcript
A (0:01)
Hey, everyone. Welcome back to OrkwithReady. I'm Sam Sperlin and I'm joined, as always, by Rodney Evans.
B (0:08)
Hi, Sam.
A (0:09)
Every other week we're tackling one tough, thought provoking listener question and sharing a few ideas that might help. Let's dive in. Rodney, what have you got for us this week?
B (0:20)
Oh, this is good. This is a banger. All right. How would one start an org os if you start from scratch as a completely new company, someone starts with no baggage. How would you do it?
A (0:33)
I would resist the urge to get super fancy about it, totally. You are probably. I don't want to make assumptions about this person who asked the question, but they're listening to our podcast, so you're probably a nerd, A bit of a nerd. And I think the overwhelming urge when presented with a blank canvas and a lot of knowledge about what could go on that canvas is to do a bunch of stuff early on, defining things and creating systems and all of that. And I would say resist the urge and keep the phrase minimum viable everything in your head. As you get started here, really latch onto the idea of using tension to drive decisions and structures and things that you need as you experience it, as opposed to predicting, predicting what you think the tensions are going to be and preemptively creating stuff. And obviously you can go too far in either direction here. There are some things where if you make decisions early on, you prevent lots of pain later. But I think those things are fewer and far between than you might think.
B (1:45)
Yeah, plus one. You know, I had a, I had a card in here that just said, wait until it hurts. Like, don't try to do stuff until there is a shared recognized pain caused by its absence. Just don't learn from our combined, I don't know, 35 years of experience, wait until there's pain to even try the other thing. And I think we should talk about defaults after this because you and I have slightly different views on what they should be. But something that I've noticed in a couple of projects recently is there's a real tendency for smart people to create too much scaffolding or envision scaffolding and then try to apply it consistently at every altitude. Yeah, and here's what I mean by that. I was just working with somebody last week. She's really fucking smart. Like, really makes me feel like a dumb, dumb sometimes. And she, she had created this, like, strategy framework that was really good. Like it was an MBA level framework. I don't have my mba, so I had to Read it a few times. But the thing that was tricky about it, and this is what happens a lot with OS moves, is here's this beautiful thing that is kind of perfect. Now we're gonna do it to everybody. And it's like, what's not. I don't know what the scale of your company is, but like what's necessary for the team that's stewarding and what's necessary for the individual contributors in terms of direction and scaffolding to prioritize is very different. And the same is true of operm and the same is true of strategy work and the same is true of experimentation. There is no one size fits all in Org design. There are defaults that you can start from, but they are inevitably going to be adapted based on what the work is to be done. And so my follow up to Wait until it hurts is don't try to create something that will work for everybody.
