Stripe 扩张之路的经验 | Claire Hughes Johnson(Stripe 前首席运营官)
Lessons from scaling Stripe | Claire Hughes Johnson (ex-COO of Stripe)
Claire Hughes Johnson:
What I say to people at Stripe… In our onboarding, I used to run a session. I was like, “If you’re not sure who the decision maker is, one, it’s probably you. And I’d rather you act that way than not because you’re going to like slow the whole company down. Follow a process and get it done, and don’t forget to actually make a decision. And if you don’t know who the decision maker is and you’re worried it’s not, you just ask. Don’t get stuck.” Too many people get stuck and it makes your work terrible, right? What do we all care about? Progress, impact, momentum. If anything I would say about advice to people generally is be a force for positive momentum and it will be actually a real career maker.
Introduction to the Guest
Lenny:
Welcome to Lenny’s Podcast, where I interview world-class product leaders and growth experts to learn from their hard one experiences building and growing today’s most successful products. Today, my guest is Claire Hughes Johnson. Claire was most recently chief operating officer at Stripe for the past seven years, where she helped scale them from a small startup to the legendary company that it is today. Before that, she spent about 10 years at Google where she was VP of self-driving cars, VP of global online sales, director of sales and ops for Gmail, YouTube, Google Apps, and AdWords. Before that, she was in politics. She’s also on the board of HubSpot and the Atlantic. And this week, she’s releasing an incredible book called Scaling People, which in my opinion should be and likely will be on every founder’s bookshelf. In our conversation, we dig into many of the meaty topics that her book covers, including building your operational cadence, defining your company and personal operating principles, your company’s operating system.
Also, tons of tactical advice around saying things that you cannot say, building self-awareness, distinguishing management from leadership, so much more. I say this a couple times in our conversation. If you enjoyed my newsletter and podcast and the fact that it’s very tactical and full of templates and frameworks, you’ll love Claire’s book, and you’ll love learning from Claire. I had such a good time chatting with Claire, and I know you’ll learn a lot from this conversation. With that, I bring you Claire Hughes Johnson after a short word from our wonderful sponsors.
Use Vanta to automate up to 90% of the work involved with SOC 2. Vanta can get you ready for security audits in weeks instead of months, less than a third of the time that it usually takes. For a limited time. Lenny’s podcast listeners get $1,000 off Vanta. Just go to vanta.com/lenny. That’s vanta.com/lenny to learn more and to claim your discount. Get started today.
Claire, welcome to the podcast.
Claire Hughes Johnson:
Thank you, Lenny.
About the Book
Lenny:
So you wrote this book. It’s called Scaling People. It’s coming out this week. I actually read a preview copy, and it’s incredible. Everyone listening to this should buy it, especially if you’re a fan of this podcast. It’s full of frameworks and templates and guides and all these things that I try to do with my newsletter and podcast. And so if you like what I do, you’re going to love this book. And I can’t imagine how much work it must have taken to write a book like this. So my first question just have relieved are you that you’re done with this book and you can move on with your life?
Claire Hughes Johnson:
I am so relieved, Lenny. Writing this book was not my idea. Patrick and John Collison, Stripe’s co-founders, really sort of pushed me into it. And I’m glad they did. I will admit that, as I am with most things they pushed me into, but it was a lot more work than I thought it would be, and it’s very rewarding to have it done. Of course, though I’ve been re-looking at it and realizing there are things I want to add information or tweak what I originally said, but maybe we’ll have to do a second edition. We’ll see.
How Writing Clarifies Thinking
Lenny:
That’s the benefit of a newsletter. I can just edit things and they’re immediately live.
Claire Hughes Johnson:
Yes.
Claire in a Box
Lenny:
I want to talk about John and Patrick a little bit. But before that, something I wanted to ask is I find that when I write stuff, I am able to better understand and crystallize my own thinking. And I’m curious, having written this book, what is it that you were able to better understand and crystallize in your own thinking through that process?
Claire Hughes Johnson:
It’s true, and it’s funny, because if you asked me, I would’ve said I crystallize more by talking and speaking. But whenever I do write something down, I’m glad I did. So I probably do more crystallizing by writing than I would admit, but maybe I’m just lazy and I just like to talk. There’s a part of the book, I think it’s toward the end of the third chapter, which is about hiring, and that’s a really long chapter. Turns out I had a lot to say about hiring and hiring leaders and processes and what you need want to set up. And as I got toward the end of the chapter, I found myself saying to the reader… You maybe have read this and thought, is she for real? You need to do all this work? You need to put all of this in? And I had to say, well, look… I started the chapter saying, if you believe that talent is everything, then your hiring process is everything.
And so yes, you do need to put that work in. But I think, Lenny, to your point, when you see all the templates and the frameworks and the examples and the advice from my career… And I was at Google for almost 11 years, I joined Google when it was about 1800 people pre IPO and left when it was about 60,000. I had eight different jobs while I was there. And then joining Stripe when it was about 160 people, and now we’re over 7,000 people. Yeah, I have a lot of examples, but really what’s crystallized is how much work it is to build, to build a company. You know this. And I hope this book is a bit of a shortcut, but there are no shortcuts. I hope it will accelerate people’s knowledge so that they can get down to work with our product and with our customers.
Learning from the Collisons
Lenny:
There’s a story you share at the end of the book, I think it’s in acknowledgements, about how people went and took John Collison out for dinner and were just picking his brain, and “How did you scale Stripe? How did you build this amazing machine of a company?” And he often came back from these dinners, and he’s just like, “Claire, they just want to talk to you. You did all these things, not me.” And it sounds like that kind of encouraged you to write things down, and then led to this book. One, is that true? And then two, I’m curious, what else did you learn from John and Patrick Collison that have stuck with you? I imagine there’s a lot, but kind of what stands out?
Case Study: Job Levels and Global Support
Claire Hughes Johnson:
Yeah, no, absolutely. I think it is true that at Stripe, we’re fortunate where we have so many users, customers who are themselves founders or interesting companies growing up around the world, whether at scale like Amazon or scaling. I’ve spent time with Discord and Toast and all kinds of interesting companies that are growing up around us. And a lot of their questions are not necessarily about Stripe’s products always. They’re really about, “Well, how do you guys do this thing?” Or “We’re having this challenge. Are you having this challenge?” And John, yeah, would often come back from trips. He would travel more, and he is often probably meets with more customers than anyone in the Stripe leadership team, maybe other than our sales leaders. And they would ask about scaling, and he would joke. He’s like, “We need Claire in a box.” So I think the book is Claire in a box, I guess.
But Patrick also would have that same experience. And when I contributed a chapter to Elad Gil’s High Growth Handbook, even though if you look at High Growth Handbook, which I also really do recommend not just because I’m in it, I’m probably the least, I don’t know, celebrity participant in his chapters, and my chapter got a lot of traction because I think it was very specific. It was very tactical. And Elad actually helped me to realize, look, examples and details and frameworks, my working with Claire document is in there, is like… He said it’s catnip. And I think that is also what inspired Patrick to push me to do basically a longer version of that chapter that I did with Elad. But I’ve learned a lot from both of them. I used to think that I was… My parents are teachers, Lenny. I used to think I was very curious, and I’m a learner and I’ll seek out information.
And I grew up in a very educatory environment, right? Well, once I met the Collisons, the two of them are huge sponges, seeking out knowledge constantly. But also, anytime we were confronted with anything, even things I felt I’d done before, that I had the experience and we were going to build it, they were like, “Well, who have you talked to?” Or “What have you read?” And it was really good. I don’t think I made enough phone calls in my earlier career and asked people’s advice and asked for help and found the person who did that thing five years ago and found out what they learned. And I think that’s probably my biggest lesson from working with both of them, is how much it pays to seek out knowledge from others because we’re all just learning all the time.
Lenny:
Is there a story or example of that comes to mind that was really beneficial where you actually ended up follow that advice and reached out to someone, talked to someone, and that changed the way you think, changed the way you operate?
On People, Money, and Advice
Claire Hughes Johnson:
There are two things that just jumped into my mind. The first one is early on at Stripe… When I joined, we were about 160 people. I started bringing in some leaders. We were building out go to market, we were starting to stabilize our support operations, building out recruiting and HR, all the things. We were really growing. And it became very apparent that we needed to put in some kind of job structure. Levels and ladders is what you would call it, which is there are different levels of pay, and they have to do with your experience and your impact and their expectations of those different levels, right? There’s an engineering ladder. And this stuff is probably making some people listening like their skin start to crawl because it’s never fun or easy to define all that, and it’s not perfect. You’re immediately getting into something that feels pretty suboptimal, but it is worse to have nothing because it starts to feel very unfair in the environment, especially if you have to start to change up compensation and reward or reward systems, right?
So I realized, oh my gosh, we’re going to have to put this in place. We didn’t know HR people, so I basically ran a project. And the first thing I did though, thanks to Patrick and John, is I talked to Square, I talked to Airbnb, and I talked to two or three other companies. But those two conversations, I’m not going to say who said this, but one of them, the person said, “Oh, that’s a blood bath.” They were not encouraging about what we were about to go through. And another one said, “You know what? I’m so impressed that you’re doing that so early. We waited too long.” And actually, that’s what a lot of my book. It’s about is when should you start to think about this thing that you might need, right? And it’s sooner than you think. And so putting in levels of ladders felt like ripping the off, honestly, but I was glad. One company I talked to waited until they were like 800 people, and it was apparently not fun because people don’t like to be… Who likes to be categorized?
The Philosophy of Job Titles
Lenny:
Yeah, and put it at a level that maybe they’re not happy with, right? They’re like, “Oh, I thought I was a lot more senior than that.”
Claire Hughes Johnson:
Yep. Yeah, exactly. It’s not easy. It’s a form of change challenging. And I would not say we did it perfectly, but I’m glad we did it. I think that example was definitely one of them. Another was like we were really… We wanted to roll out 24/7 support in multiple channels, email, phone, chat in multiple languages and getting from where we were to where we wanted to be as quickly as possible. Not many companies have done at the scale, because Stripe has millions of customers. We’re B2B, but we’re B2B at a very high scale, which actually Google was as well. And so that was beneficial to me coming into the Stripe environment because I’d done parts of that for Google. And again, that’s an example of something I thought I knew how to do, sort of, but we certainly didn’t do it perfectly, and it’s certainly different when you’re talking about payments.
That’s people’s money. That is a business’… If they don’t know how to contact you and they have a problem, that is a huge issue. And so I did seek out a lot of advice. And I would say… Did anything change dramatically what we did? I think if anything, the advice pushed me to go faster on some of my intuitions about, for example, using vendors and outsourcing parts of the model. And I realized we’re not going to scale all this internally, especially not at the speed that we’re going, but it’s hard to start to use outside sort of contractors if you haven’t filled figured out all your tools and processes. So that balance was sort of freaking me out, but you just got to push through it.
Title Flexibility and External Selling
Lenny:
There’s a couple directions I want to go, but I’ll go in an unexpected direction. At Stripe, you’re kind of infamous for your titles. When I created this career ladder document.
Claire Hughes Johnson:
[inaudible 00:15:24].
Why Build Operations Structures Early
Lenny:
Yeah, it’s like everyone’s product manager., They’re like a VP of product potential and it’s like product manager. What’s the rationale behind that? I guess, and what’s the benefit of that? But, we don’t have to go too far down the road. I’m just curious.
The House Structure Analogy
Claire Hughes Johnson:
So this is something that Patrick and I actually really agreed on without a lot of discussion, which is not always the case. It has to do with a combination of optionality as you scale and grow, and also culture, right? And so the minute you start titling a lot, you’re signaling hierarchy and authority. And the culture piece to Stripe still today, which is I think we could use more, at least more overt trappings of structure because it can get confusing. And I’ll be the first to tell you that, and I admit that this might have carried on too far. But early on, at Stripe, there’s a real belief. It’s not a particularly hierarchical company. And if you’re the person who has the knowledge, you are the expert on the thing, you better be, one, in the room helping make the decision, and two, driving, helping to drive the decision. And I don’t care how senior you are, right? And that was the cultural signal that was important, which was about mutual ownership, and also expertise not sitting in hierarchy.
And then the optionality thing is probably a little more obvious, which is don’t make somebody the CMO, or even the head of marketing, if you’re marketing team is two people, right? Yeah, you might make the right choice, but two years later, your marketing team’s probably going to be more than two people, say it’s 20. And are you going to have to layer somebody or have too many titles? And then someone feels like they’re losing something, right? It goes back to the levels and ladder saying, but it’s worse because you’ve given something, and then you’re sort of taking it away, and that’s just not… Organizationally, you want more flexibility. Honestly, I’ll say my final thing, which is I have a little bit of a knit where you meet a company. I get what’s happened, which is in order to hire this person, they had to sort of say, “I’ll make you the VP of sales or the VP of this,” but the company’s like 25 people and there’s seven VPs.
If you’re a customer or you’re evaluating it, you’re kind of like, “Really?” It’s a little incongruous with the scale. So we kind of more flexible. We had a lot of growth, head of this or growth lead. I know you’re all about growth, Lenny. Well, we definitely took growth and find that very broadly. But the other thing I’ve said to people internally… Sorry, you can really get me going on this one. I bet you didn’t think that. If you are a stripe and you’re going out into the market, actually it speaks to the same thing, which is you’re going and trying to sell to a customer who’s a lot bigger than you. I’m not saying make up a title. Don’t say you’re the VP of sales, but you can be creative about how you represent your scope because you probably have really big scope because you’re one of the only people helping to sell the product. And that will help you because a lot of more established mature companies are trying to do that hierarchy match, where “Well, bring your SVP because my SVP is coming to the meeting.”
And we could be like, we don’t really have that. It just gives you a little more selling flexibility too.
Lenny:
I like that. I like combo where you can just say something that fits in this situation, even though that’s not your technical title.
What Early Founders Must Get Right
Claire Hughes Johnson:
Yes, you can say, “Oh yeah, I actually am in charge of optimization for our payments product.” I’m sure you are. I’m sure that’s what you
Personal Operating Principles
Lenny:
Do. Coming back to something you talked about with the career ladder, and I had a question around this, you talked about how oftentimes people do it too late, and I’m curious why it’s so important to think about the stuff that you wrote about in this book so early in your company’s life cycle. I think in the book you mentioned that it’s oftentimes as important to get your operational structure and cultural structures in place incorrect as finding product market fit or finding your first few customers, which I think would surprised a lot of people. Can you talk about why you found that to be so important?
Claire Hughes Johnson:
Not only can I talk about it, I wrote a whole book about it, so let’s try to restrain me. But here’s what I would say. Obviously product market fit is the most important. And what I do say in the book is focus on that and don’t get too far. My book is definitely not zero to one. It’s more like maybe 0.5 to 1.5 or one to two. Because I do think when you’re smaller and focused on product market fit and finding your user and getting that traction, that shapes a lot of how you work and your goals and who you hire, and that all makes sense. I think the thing that happens though is, one, some companies don’t quite realize they’re hitting it and they start to get behind on actually building the company part. Because guess what?
It turns out product market fit is just the product, and that is not a company, and that will not scale, to point. You see these companies that sort of fall over and there’s sort of a bad article about them, and often it’s not the product, it’s the fact that they didn’t actually build the company very well, and that started to harm, in fact harm the product and harm the mission. You have this vision, you’re going to solve this problem with this product. And all of a sudden you can’t solve it because you didn’t scale the org properly. You didn’t keep the cultural fabric strong as you grew, right? And so that’s why I think it’s so important. And so let’s say you are hitting traction, and hopefully you do notice it. Because I think a lot of founders, you’re kind of paranoid.
Like Stripe, I don’t think Patrick and John fully embraced that they needed to start scaling maybe until I showed up, and that was part of hiring me. I was like, yeah, this is it. It’s happening. It’s not just look at the numbers. It’s like look at the inbound support demand, look at the inbound sales leads. I just did the math, and I was like, this company should be probably twice the number of people it is right now, which of course freaked everybody out, but it was very obvious to me because I was coming in outside with that perspective. But more importantly, not just scaling things like sales and support… And as you probably know, if you work in payments, you’ve got a lot of other functions that are very important around risk and compliance and you name it, or the machine learning models and that help you do those things.
But for the sort of structures and operating processes that I talk about in the book, I do have this analogy which I think you picked up on to building a house, which is you have the supporting beam. Say it’s a post and beam structure. You need the posts and the beams, and then you’re going to have to do the mechanicals, right? There’s going to have to be some amount of wiring in order for you. I don’t know if you have your solar panels, but you got to bring in the heat, you got to bring in the cooling and plumbing, and then you have foundational stuff that you have to build or the whole structure will fall over. And I think of putting in the posts and beams and the mechanicals and the foundation as actually essential to scale. Because if you do those things well, you build them in such a way. This is almost like a Russian doll kind of thing, but you build them so that they’re replicable, right?
So the way that you do goals as a company can start at the company level, and this is how OKRs were so beautiful for Google and they can replicate down to the individual. And the same common structure allows that to happen at really different levels of scale. And that’s what you’re looking for, is what are these common things? We do not a lot of them, by the way. You don’t want to mandate a lot, you don’t want to put too much structure in place, but enough that everyone can play with it up and down what I would think of as the stack of the company. And if you don’t start putting those things in early, people will just invent those things. And then you’ll have… Picture a house that got added on to 17 times and it’s not even two years old. It looks not super stable. And then you’re going to find yourself having to do a tear down, which I think we’ve all seen companies do that.
How to Define Personal Operating Principles
Lenny:
I definitely want to get into that house structure and all the components of it. But before we get there, if you’re a early stage founder just looking for product market fit, maybe the skipping ahead a little bit, but which elements do you think are the most important that they need to do now? Because they’re going to read your book, which gives them so much advice on all the things you can do.
Claire Hughes Johnson:
Yeah.
Work Style Assessments
Lenny:
If you have to pick a couple things that you have to nail when you’re just starting out before product market fit, what do you think is most important?
Tactics for Uncomfortable Conversations
Claire Hughes Johnson:
I think really that early, keeping it very simple and being focused on that goal of product market, which is like what is the problem you’re trying to solve? What’s your vision?Everything you have to do for an investor pitch deck matters not just for the investors. By the way, people forget this. A lot of the story you tell to investors, early ones especially is the story you should be telling internally to anybody you hire. Why do we exist? What problem are we trying to solve? What early customers have we attracted, and what’s their feedback. That’s what you mostly need, but you need to remember to share it and don’t just use it for fundraising, or don’t just use it for a board meeting or an investor meeting. Use it internally. And I think you can get pretty far actually with that core content. As you start to…
The first thing you’re probably putting in place is a little bit of hiring process, and I think that’s going to matter sooner than you think. Don’t just be tempted to hire people in your friends. Think about what you need, what capabilities you need to build even pre PMF, right? And so as I said, there’s a chapter about that, but I think some of the simplest versions of it is how do we evaluate talent? What kind of talent are we looking for? Where do we go look for talent, figure that out, and sort of train people a bit internally on interviewing. I think interviewing is not a skill that comes naturally. People think it does. It does not. And there’s really basic easy tips and tricks you can find even on the interwebs about interviewing. And I really recommend… And my book has examples of rubrics, questions you can use. How do you really get at… Because it’s hard to really evaluate someone in 30 minutes or 45 minutes.
So I think interviewing some of your fun fundamental early investor kind of content you need. But then when you start to get some traction, then you’re showing to codify and actually document what I call more foundational content. Because if you’re pre-product market fit, you’re probably small enough that you just can tell everybody all the things. You don’t have to send them the packet or have them sit in the onboarding. But the minute that you’re starting to get any kind of hiring speed, you’re going to want to document it more and you’re going to want to start to put some very lightweight processes of how you get things done in place, because again, you’re trying to replicate velocity. It’s easy when you’re all in one room and everyone knows like, “Oh, this is the most important thing to get done today,” hack, hack and hacking away. But then pretty quickly, that is not going to be the case.
Be an Explorer, Not a Lecturer
Lenny:
I definitely want to go one layer deeper on that, but there’s this area I wanted to get to before we dive into some of the weeds around that, which is I found it really interesting that you started your book with this idea of personal operating principles versus here’s how the company should work. It starts with here’s how you should think about yourself. So I want to go… There’s four of them… But before I get into them, can you just describe what is the idea of a personal operating principle and why is that important?
Claire Hughes Johnson:
Remember the book is about two things, company building and company structures, and all that, replicating all that good step and management. So the other thing that the book is really about is management tactical guides to… It would be easy to build companies if there weren’t humans involved, right? But there’s humans and they’re complicated, and I’m complicated and you’re complicated. And there are things that motivate us. There are things that demotivate us. They’re not the same things, though Lenny and I, I think you and I have some things in common, but point is the book starts with you. And I think a lot of people think management starts with the team, or even the company. And actually, I think founders make this mistake. Founders think, well, it starts with my product. And yeah, but it actually starts with you. And so the book starts with sort of my belief system, which is self-awareness, which is the first operating principle. Self-awareness to build mutual awareness is actually the most fundamental thing you need to crack if you’re going to succeed at company building or management, in my opinion.
But I would say I’m one of those people who has strong opinions that are pretty loosely held. This one is a strong opinion strongly held, which is the more that you can seek feedback, seek to understand your motivators, your strengths, your blind spots, your tendencies, and take that on board and expose it to others, you’re going to be a much more effective company builder and manager. So it starts with you. And those operating principles that I articulate are sort of mine, but they’re also foundational to the content of the whole book. I do think authentic leaders tend to have their own, right? Lenny, you probably have a few that you… You maybe have not articulated them all out loud, but I do have mine and they’re in the book, but I think you would also find that some of them you could adopt. If you were looking for were some to start to use as a leader, I would hope that I’ve put forward a couple that might be useful.
The House Metaphor: Three Pillars
Lenny:
I want to talk about these four, but while you’re on that topic, what are ways to help crystallize your own operating principles? What advice would you give people to do this? Because to your point, people probably have them in their head, but they haven’t really written them out.
Claire Hughes Johnson:
That’s right, they haven’t. The book has an exercise that I recommend in it that’s a little bit more about crystallizing your personal values, but that’s kind of the place you want to start. And it’s essentially there’s a whole menu, and you can find these online, of say 70 or 80 different values. And by values, I mean family, ambition, impact competition. People value education. People value different things differently, by the way. And there’s no judgment. You might value being a very competitive person and I might value collaboration above competitiveness, and that’s fine. We probably would both be very effective in a team for different reasons, right? So basically if you take a list of values and you say, okay, if I had to pick 10 of these that matter to me, then if I had to pick five of them, and then you really force yourself if I had to only pick three of them…
And it’s actually good to have this in a dialogue with someone that you work with or well, and you sort of had to explain, well, why? Why, when I’m really pushed, do I have to hold on to say education or learning as a value? Or why do I have to hold on to integrity as a value? And I tell a story in the book about a manager I worked with where transparency was a very important value to him. And the thing is you usually have a story behind that value, right? And in the book, I use the name Eli for him. Eli ends up sharing this story at this offsite that we had. And the transparency value actually was a little bit problematic to manage because Eli would tell everyone everything, including his team, even when we weren’t finished with the plan, right? But Eli got up and told a story of being younger, like seven or eight, and realizing his mother was very sick, and no one really told him what was going on.
And then unfortunately watching the process of her dying and then being taken out to lunch by his stepfather and told, “Your mother is gone.” And okay, well, your whole worldview kind of explodes when you hear that, and you’re like, oh, okay, this transparency thing is really real. This was a formative experience for him and it has changed how he operates, and it will probably have changed it for his whole life. And if you can get to that point on your own, of telling yourself, what was the story? What was the thing that made this so important to me? Then you’re starting to be in a mode of self-discovery and then you’re starting to document, okay, if these are my three top values, and here’s why. And then I think what you want to look for are my, what I would call my work style tendencies? And so you get your values, and then you sort of go on a… I’m sorry, I could go on about [inaudible 00:32:08]. I warned you. I wrote a book about this.
But basically, all these work style assessments, Myers-Briggs, DISC, Enneagram, you name it. And by the way, I would take all of them because I find that very good. I mean some of it’s just data. You’re just taking on data. But a lot of them come down to are you introverted or extroverted? Are you more introverted or extroverted? Where are you on that continuum? And are you more task, if you kind of picture a horizontal and a vertical, are you more task or people oriented? And so I would take your values, and then I would plot yourself. Am I a more extroverted task-oriented person, which means you’re kind of a director, get what done kind of person? Or am I a more extroverted people-oriented person, which might mean actually you’re probably great at being very charismatic and building some followership and maybe selling a vision? A lot of salespeople are very extroverted people oriented people.
And then you start to see, okay, if this is my sort of tendency in my default and this is my value system, what are the ways that I operate that really make up who I am and becomes almost a belief system. And my operating principles in the book, one is to build self-awareness, to build mutual awareness. Another one is say the thing you think you cannot say. I think that I’ve come to believe that often your biggest strength, one, is also your weakness, but two, is something that you don’t know is a big strength because it’s almost like breathing. For me, saying something actually fairly openly and directly but in a non-threatening way is a thing I do. John Collison actually once said to me, he’s like, “It’s so interesting when you give feedback, that can be actually pretty brutal, I leave feeling really optimistic.”
But I don’t mean to be brutal, but I think I can sort of unpack and say this thing, like here’s my observation, here’s going on, and it’s not judgmental, it’s not threatening, it’s actually opening up an opportunity for people. So say the thing you think you cannot say. You would actually find that more of us can do that. And then I come back to distinguish between being a leader and a manager, which is something early in my career, I did not do well, Lenny.
Internal Chaos in Successful Companies
Lenny:
Before we get to that one actually, just to briefly ask you a follow up question, because I love that you’re getting through all four here. This is great. But I was going to ask, is there something.. So clearly, you’re really good at saying the thing you cannot say, and I love that. Many people are not good at this.
Claire Hughes Johnson:
No.
Building Company Documentation
Lenny:
Do you have any tactical advice for someone that is not good at this for how to actually say something uncomfortable?
When Does a Company Need a COO
Claire Hughes Johnson:
I think the main thing is, and Fred Kaufman has this in his book, Conscious Business, this concept of a left hand… He calls it the left hand column, which is you’re in a dialogue with me or you’re watching a meeting happen, and you’ve got a running commentary in your head. And honestly, some of that stuff is pretty harsh, right? You do not want to open your mouth and just say that thing. But what Fred says is, learn how to detoxify the left-hand column. I would say think about a way to say that thing that you think you can’t say. You’ve filtered yourself out, which I don’t like. And I want you to think, okay, can I? And I think that the… Here are the tricks, a couple of them. One is, ask a question.Right? A question is not threatening. By the way, the question could even be, is there something we’re not talking about? It feels like to me… And then you own.
So the next trick is you own it. This is your observation, this is your perception. This is not a judgment. I am not saying, “Lenny, I think you really botched that interview.” That’s not useful. If I said, “Lenny, you know what? I wonder if you missed an opportunity in that interview. Did you feel like you missed an area that…” And then you’re kind of curious. You’re like, “What do you mean?” And I’m like, “Well, I’m kind of looking at this with you, and I’m standing next to you and I’m observing it.” Right? That’s less threatening. So one, ask a question. Two, make an observation that you own. So if I said, “I feel like there’s something we’re not talking about, and I wonder…” Oh, I own it. “I wonder if it’s the fact that these two teams both seem to have the exact same project.”
I talk in the book about a meeting I was in where it was very clear that we had two teams in conflict, and no one was saying the thing that was really pretty bad. I was like, this is pretty bad. We have two teams that seem like they both own a piece of work and are in conflict with one another. But I would say if you do those two things, ask a question, own the observation yourself, don’t pass a judgment, you will get way farther than you would’ve ever thought sharing. And by the way, that sharing, one, there’s probably other people who just haven’t, can’t get it out of their head, and you have ar opened up a door that a lot of others can probably walk through. You’re not alone.
How to Spot a Great COO
Lenny:
You have this framework, I think you call it being explorer, not a lecturer. Is that what you just described? Is that how you describe it?
Claire Hughes Johnson:
It is. And to me, what I just talked about was more of a meeting or a conversation scenario, but I think that this… I’m glad you brought that up. I think this is actually a very fundamental management framework of mine, which is in a one-to-one interaction, your job as the manager… First of all, too many people think your job as the manager is to be the expert and tell people what to do. No, actually, your job is to enable people to be their very damn best on your team. And you have to create an environment and a context and provide them information, and then you need to provide them a form of coaching. Now, again, I think people start think coaching is lecturing, like let me coach you how to make this Excel model. And sometimes they do. Sometimes someone comes to you and says, “Can you exactly show me how to do this thing?”
Fine. But most of management is actually exploring with someone. It is being curious. It is saying, “I have seen this pattern of your work. Have you seen this pattern? Is there something…” I have a whole other framework which is about hypothesis based coaching. I think intuition as a word gets kind of a bad rap, and I kind of get why, look, especially if you work with a lot of engineers, which I do. It’s not particularly always data driven, but guess what a scientific hypothesis is? It’s a well-informed piece of intuition. And I think too many managers wait until they have a million pieces of data to make an observation to someone about an area for improvement. Instead, I would say take some data, form a hypothesis, and then explore it with the person. Because if you’re well intended, which I think any good manager is, I’m bringing up this thing because I’m trying to help you see it and tell me if it’s true so that we can both help make it more effective, better.
One very light example could be, “I felt like in that meeting… How did you feel that presentation went?” And the person sort of says, “It’s fine. I think I got through the material.” You say, “Yeah, I felt like you were maybe a little bit nervous. I’m just exploring. Were you…” And by the way, the person could say, “Oh, no, no. No, no, no, no.” And then you could back off, or you could say, “Oh, well, maybe it was just me, but I noticed some physical. Your leg was shaking a little bit, your voice, you were kind of repeating yourself.” And they’re going like, “What?” And you’re all you’re doing is holding up a mirror… And you have to own it. You have to say, “My experience of you in that meeting was that you seemed nervous to me. Maybe you were not, but actually maybe this is just a physical coaching thing.”
Have you ever had that? I have a few people on my teams who do this weird thing. This is pre virtual world, but when they’re sort of getting it uncomfortable in a meeting, they put back their chair up off the table, sort of exit the circle. And that is a very physically big statement. And they had no idea, Lenny. They had no idea. I’m just watching the meeting, and I’m like, oh my gosh, you’re like four feet from the rest of the group because you do not like this topic. And what I need to explore with you is how do you vocalize that instead of physically exiting the room or exiting the circle? These are just examples. Sorry, I could keep going. But I really think that that attitude of exploration and mutual sort of collaborative, let’s discover some things about you…
And by the way, it can be mutual. They can go right back at you and say, “Well, I observe this.” Great. Great. I’ve interviewed a lot of people for the book, different leaders and managers from lots of different fields, but one of them was Reid Hoffman, who’s a more typical. But Reid, we were talking about the other operating principle, which is management versus leadership. And Reid was pretty honest. He’s like, “Look, I’m more of a leader. I’m not a manager.” He’s like, “I’m not a great manager.” And then he told me the story. He’s like, he had in his first company that he was building, he had a guy that he’d hired who was more operational. And Reid was sort of making an observation to him about something they should do, and the guy goes to him, “Reid, I wouldn’t hire you to manage McDonald’s.”
And Reid was like, “Okay, good. So tell me what we need to do so we can fix this thing.” But what actually Reid’s operating principle, interestingly when unearthed that whole thing, was that he prides… It’s very important to him to create an environment of open feedback. He said, what I love about that story, yeah, it’s funny and embarrassing, but actually that guy was comfortable saying to me, “I wouldn’t trust you to manage a McDonald.” And I think that actually I found inspiring because I don’t think everybody who founded a company or who’s managing someone has created an environment with how much trust in it, right? And that’s how Reid thinks he gets a lot of stuff done, is people just come right back at him with the feedback.
Quick Fire Questions
Lenny:
So we’ve done three of the operating principles that you personally use, which I love. I love that you’re going to going through [inaudible 00:43:25]
The True Value of Offsites
Claire Hughes Johnson:
Distinguish management and leadership is the third one, yep.
Internal Communication Strategies
Lenny:
And then just to summarize real quick, the second one was to say the thing that you cannot say. The first one was-
Claire Hughes Johnson:
Say the thing you think you cannot say, yeah.
How to Run Effective Meetings
Lenny:
And then first, build self-awareness to build mutual awareness.
Claire Hughes Johnson:
Yeah.
Decision Making and Alignment
Lenny:
And what’s cool is you’re sharing all these amazing stories and tactics. In the book, you actually have templates to do each of these things for yourself. So a lot of this is pointers too. If you actually want to do this, go check out the book and you can actually do this. It’s not just in a bunch of high level stuff. And then the fourth is-
Claire Hughes Johnson:
Come back to the operating system.
Wrapping Up the Conversation
Lenny:
Let’s talk about it.
Claire Hughes Johnson:
So this one is, sort of like I was talking about, touchstone documents that you might create for your company. This is our operating principles, our values. This is my touchstone, which is I think that especially high growth environments, but every environment you operate in can get really chaotic, and there’s a lot of ambiguity. There’s a lot of stuff you don’t know, and it’s kind of easy to get paralyzed or to sort of give into the chaos. And you’re like, oh my gosh, I don’t know what this day is going to bring. I’m just going to randomly assign some stuff, and I’m just going to get through it. And all you’re doing in a lot of those moments is creating more chaos. And I think a really important role of definitely managers, but some leaders too is to create a stability when there doesn’t feel like there’s a lot that’s stable.
And where stability comes from is in ritual and in common practices that you share. So we set quarterly goals or monthly goals. And that’s a ritual, and that’s a thing we do, and it’s actually a source of stability. And yeah, it feels like a process. It might feel like a way of managing, but it also has a cadence to it. And I think one of the things that happened is you picture yourself sort of spinning out of control. You think, how do I come back to this is the order I do things, this is how I get decisions made, this is how we make plans, this is how we make decisions. Those touchstones are not processes to run the thing. If they’re done well, they’re stabilizing because they’re a common way of approaching that everybody has, so they can at least hold onto that even when all the other stuff is going haywire.
You’ve got a customer churning, and you’ve got a big launch happening the next day, like, oh my God, oh my God. Come back. What’s our launch? How do we launch products? We have a way of doing that. We do not need to spin out of control and reinvent the wheel here, right? And that’s a stabilizing thing. And the other thing on come back to the operating system for me was, as my career scaled, as I went from a individual contributor, to managing a small team, to managing a bigger team, to managing multiple teams, to managing managers, you get it, I realized actually, and I started to have multiple functions. So I was context switching between… At Google, there was a point where I had some product people, industrial design operations, really BD, really different functions. Actually, how I fundamentally ran them at the bare bones, at the house architecture level was the same.
And that gave me a stability as a leader where I would dive into a meeting. I’d be like, all right, let’s look at the metrics that matter. We all had… We had them for every team. Let’s look at the goals we set. And that also helps you stabilize when your contact switching between seven different projects or seven different teams. And so I wouldn’t say it’s the operating principle that I talk about the most, but I think if you were like, “What’s your sort of… How do you scale yourself?” I would say, “Well, I actually have a common operating system like a computer, and that is how I maintain a sense of stability.”
Lenny:
Perfect segue to the next kind of broad area I want to spend time on, which is this house metaphor and the three components of it that you talked about. And this is like the core of the book. Can you talk about again, the three kind of pillars of this house structure? And then let’s just go through each of these things.
Claire Hughes Johnson:
Yeah, it’s definitely, the beginning of the book is about company building, and the company structure chapter is all about the sort of supporting beams, the mechanicals, and then the foundational stuff. And interestingly, it’s sort of, well, I guess when you build a house, you build the foundation first. So one is the founding documents that you might create, which I’m happy to talk about. And then another are the supporting structures, which are some of the ways you do things we talked, like quarterly business reviews or OKRs, or how you use planning to create a structure that everyone… And then the mechanicals are what I might call the operating cadence, which is essentially the rhythm of how you work, right? The calendar, the year that we all experience tends to dictate a little bit how we work. Mondays feel different than Sundays, right? Well, companies have that same kind of a cadence, which is often also calendar driven, but also can be event driven.
We’ve talked often at Stripe about how our customer event, which we have called Stripe Sessions, is as important internally as it is for the customers because it’s a forcing function for our cadence, how we plan our products, what we want to have achieved by that point, what we want to demonstrate. And that’s true for a lot of companies, but we actually use it in our thinking about our cadence of the year. And actually, we’ve built this other event that I usually help run, which is an internal event that happens generally about six months before that, which is great because you can demo the stuff you think you want to demo internally. You sort of create a cadence of we’re going to push ourselves to do some crazy wild stuff, internally demonstrate it, and then see if we can externalize it by the time we hit the customer event.
But that is a cadence. Quarterly business reviews are part of your cadence, et cetera. So that’s the fundamental, but really while I’m trying to do is say, one, I don’t think this stuff is super hard. You know this. It’s kind of hard work. It’s just putting it in place, and then actually using it. I think where a lot of leadership teams go wrong, especially of young companies, is they experiment with different vehicles to try this stuff. And then they either don’t actually follow them or they throw them out the window after they haven’t tried it for very long, and it creates a lot of chaos. So I would say do very few things consistently and try to do them well, and then see if they’re working for you, and then once a year, maybe think about a revision. But don’t keep throwing out new things you heard that other companies do. And it turns into a weird grab bag of operating stuff. You’re nodding because you’ve seen this too lot.
Lenny:
Yeah, I think a problem I’ve seen is people think there’s going to be this perfect system and process that’s going to not have any flaws, and they’re always like, “Oh, it’s not perfect. We got to optimize it further.” And what I find is it’s always just like, this is the best one you can come up with at the time. This is the best idea you have now. There’s going to be flaws. Just work around those flaws. But just know there’s never going to be the one thing that works.
Claire Hughes Johnson:
There is no one. There’s no perfect org structure, there’s no perfect operating approach, there’s no perfect, yeah, performance and management and level system. But having one and committing to it is good. And don’t let the perfect be the enemy of the good.
Lenny:
There’s another, you mentioned that I thought it’d be fun to talk about, that it’s often chaotic at a company. I imagine people think about Stripe from the outset, like, oh, they’ve got it all figured out, so smooth, just runs like a machine. And I think people look at other successful companies and they’re like, man, things are so crazy at our company. This isn’t normal. But I think, you tell me if I’m wrong, most places are crazy and chaotic internally for a long time and often, right?
Claire Hughes Johnson:
Yeah. There are different kinds of chaos, but it’s so true. What is that? There’s like a saying. Don’t ever believe your best press or your worst press. It’s never as bad as whatever someone’s saying it is never as good. It’s just normal is not pretty. It’s a lot. And that is true. It’s happening everywhere. I used to have a friend who was building a company. We would see each other. We both were from the Boston area, and it’s a long story, but we’d end up on the same flight off in Rhode Island, coming back to Boston occasionally for stuff, for family. And we’d be in getting yelled at by the passengers because we’d be in the aisle of the airplane comparing notes about stuff that was broken.
And we had this expression, it was like, oh, and then I picked up the rock, and under that rock were some really ugly, creepy crawlies. But that’s just like the way it is, is it’s never perfect. But I guess I would go back to what I just said about having some stabilizing ways of doing things because that can create, I don’t know, I’m not trying for a perception that the thing runs a machine, but more of a, that is a well run thing, right? And how do you create that perception? Because you adhere to some ways of running things and that are consistent, and it feels better even to the outside, even if there’s a lot of chaotic stuff going on.
Lenny:
Coming back to the founding documents, could you just talk about what are in this group of founding documents? And I think even more interestingly, what’s a sign that you should invest more time in this area as a startup?
Claire Hughes Johnson:
Yeah. Very classic stuff is in here, nothing that you haven’t seen or examples of. So one is I think it’s good to have a mission. When I joined Stripe, we did not. It came to be apparent that to increase the GDP of the internet was probably the mission, because people kept repeating that back to us, and Patrick had written it on some website copy early on. But it was interesting that candidates and customers kind of grabbed it. It was very Stripe because it’s a little bit intellectual and pointy headed and aspirational, but also it is… The GDP does involve economic progress, which we’re all about, right? We’re building infrastructure for commerce and payments for not just the internet actually. But anyway, point is have a mission, or at least the beginning of what’s your one line of what you’re seeking to accomplish.
And then I’m a big fan of writing sort of what we Stripe called our long-term goals, which were just not our short distance, but our longer distance, like why did we exist? And so the mission is one line, so you need a little more meat behind that, right? And actually, I think if you looked at our long-term goals, which by the way I thought would be a three to five year goal, I would say they’re still relevant today. But one of Stripe’s long term goals is to advance the state of the art and developer tools, which would not be something that everybody, especially every customer of would initially call out. But when you think about it… Lenny, you just did it. You think about it for a minute, you’re like, yeah, the API and the docs and a lot of stuff that we’ve open sourced, Stripe cares.
Our forever user is fundamentally a developer. It’s the person who’s integrating Stripe, right? By the way, simple integration, complex integration, anywhere in between, we really care about their experience, and we care that the tools are excellent, because how are you going to increase the GDP of the internet if you don’t advance the state of the art of developer tools? Right? Anyway, point is articulating that, because until I said that to you and I could talk about it with you and say you came to work at Stripe, you might not understand why we invested in certain things or why it meant so much to us in terms of our user experience and the mission. So articulate those things. And some of them might be a little bit aspirational, but they should feel at least real enough that you can have that conversation about… You look at anyone who works in a company, what they choose to do all day with their time should be guided by things like, what are we trying to accomplish?
What are our long-term goals? So if they don’t know them, how are they going to make the right choices? So that’s one. And then another is a lot of companies write company values, or at Stripe, we wrote operating principles. I think you had [inaudible 00:55:50] on, and she talked about these, and we even sort of took a version of ours and put them out for candidates so that they could evaluate, do I want to join this company, because I kind of want to know what it’s like to work there? And I think that’s really valuable to do because not every company is right for every candidate, and the more you can mutually match the better. But having some operating principles matters. I think you can go farther than that, but that’s where I would sort of start, is those three things.
Lenny:
Awesome, I like the simplicity of this.
Claire Hughes Johnson:
How you know is people are asking you. Especially new hires are asking you a lot of questions about what’s important, or “Why do we do it this way?” You said it yourself at the beginning. Doesn’t writing something down, crystallize it? Time to write it down and crystallize it for everybody who works there.
Lenny:
And just to summarize you as a mission, your operating principle/values. What was the third one?
Claire Hughes Johnson:
Yep. Long-term goals.
Lenny:
Long-term goals.
Claire Hughes Johnson:
And sort of more details on why you exist. What are you really trying to accomplish?
Lenny:
Interesting. And then are those numbers in your experience, or is that a story of what [inaudible 00:56:57]?
Claire Hughes Johnson:
Those are a little bit more, I think headlines. And I think your shorter term goals have numbers against them, right? So if you looked at your long-term goal, which might be… Another one of Stripe’s is about accelerating globalization, and if you thought about what would that require, that would require us to be in a lot of markets. That would require us to have users and customers in a lot of market, and also to eliminate friction across borders. So those things, which is a very high friction thing, unfortunately in payments, and moving money, which it shouldn’t be if you want to advance globalization, accelerate it, right? And so that can then become numerical goals and short term goals.
Lenny:
Basically objectives, and then-
Claire Hughes Johnson:
Yeah, it’s sort of the longer term objective, and then the key results part is early is shorter term. But actually, if you’re having trouble writing your company goals, actually zooming way out and being like, “If we’re going to meet this mission, what do we have to accomplish in the long term?” You can then walk back from that and be like, “Oh yeah, every goal we ever have probably fits in these three to five buckets.” Bam. And then you write your short term goals actually more easily because there’s always going to be one about, say, international expansion. There’s always going to be one about additional products because we’re trying to do X, and you can’t do it with one product, or whatever. You can imagine the example.
Lenny:
Awesome. And I know your book has a actual examples of a lot of this stuff.
Claire Hughes Johnson:
It does. It does.
Lenny:
So again, pointer to that. Okay, so that’s the founding documents. The next piece is operating system. Maybe we go there, just what fits into an operating system for a company? What are the components of that?
Claire Hughes Johnson:
I think a lot of the components we’ve sort of touched on, which is do you have some sort of goals? This is now goes back what we were just talking about. For Stripe, we have an annual set of numeric targets that we put together, we have a system of goals or OKRs, objectives and key results, but sort of like what is your structure for setting milestones that you want to achieve, whether they’re numeric or more like a binary, we got this thing launched, we didn’t? And then QBR, so quarterly business reviews. How do we review parts of the business? What is the cadence? Well, first, what is the form by which we do that? Which would be this… I share examples in the book of this might be the template you fill out if you’re a team and your reporting on how it’s going and versus your strategy and your goal.
And then there’s also getting into metrics and dashboards. What are things that you look at internally to measure progress, the input metrics and the output metrics? And I give some examples of that. And then mostly, I think there are other… As I said, there could be less frequent forms you use, like a user event or a launch, a way of launching products, et cetera, but it’s really simple. It’s mostly goals and how do you review the business. Planning. I talk a lot about planning, which is. You said this earlier, and you and I think both agree, which is there’s no perfect process to plan for the next year or the next two years, but you still need to fight your way through having something, especially after a certain stage. And every COO I meet with, we sort of ring our hands together.
We’re like, oh, planning and everyone hates us, too burdensome, but you still got to keep trying. You got to do it. And so we talk about planning processes and what they might look like and how you set them up. And then that’s how you’d use goals and QBR to measure against the plan, right? So those are some of the operating systems. And then the cadence is just how often do you do these things? Actually, one of our big lessons, I think companies that are moving quickly and that are younger tend to resist some of the calendar based cadences of more mature companies because they seem slow. You’re like, really? You’re going to just achieve that goal in three months? Or are you artificially restricting yourself to some lowest common denominator of time? And so I get that fear, and I would say your cadence doesn’t have to be one quarter or one six month, or even 12 months.
Stripe, we did sort of six month processes for a while. So instead of a year, we did it in six months. Still, there were things that took, by the way, a year or longer, but I think that play around with the timeframe and don’t feel restricted by what other companies do. But one of our lessons on the QBR was sometimes those quarterly, because that stands for quarterly, those quarterly business reviews were too infrequent, especially for new product areas. They we’re still in development. They were still getting a lot of feedback, launching a lot. And so we just said, okay, they’re not quarterly anymore. They’re like every six week business reviews. Fine, change your cadence. The point is to have one, because then it’s predictable for teams. They know what they’re marching toward, they know when they’re going to be reporting out, and they can set their goals in a way that makes sense to make progress in that timeframe.
Lenny:
One quick question there. What’s a sign that your cadence is off? What’s a flag that we should go shorter or longer?
Claire Hughes Johnson:
Well, everyone usually complains about these things, but I think if the… One, nothing, like you said, it’s probably too fast if not enough progress is being made in between whatever your review or your reporting function is, and it’s probably too slow if the content you’re reviewing seems stale. And you’re like, “Well, we knew this,” or “We already did that thing,” or “Yeah, we already had the meeting where we talked about that.” That’s another thing that’s interesting, is some companies will have a pretty frequent metrics review cadence, and then an infrequent strategy review cadence. And what happens is the metrics review becomes the strategy review because you’re not talking about the strategy often enough. And so you’re talking about it through the data, and so then by the time you get to the strategy review, you’re like, we already had this meeting. And that’s just a sign that some things are just off. And to me, it’s about timeliness and freshness of the content, but also that there’s actually new content. If there’s not new content, you’re creating work for people. By the way, give them time to work.
And so I think don’t fool yourself that thinking, having more frequent checks on things is going to actually make things run faster. I would say that the opposite can be true. And so be very wary of actually slowing velocity down by creating overhead. One thing we try to do at Stripe is if we’re looking at metrics, let’s just look at your dashboard live. Let’s not create a special presentation. I actually just share your screen please on your dashboard, right? Which is a good discipline, because one, that means you have to have a really good dashboard that’s real time, that’s web accessible. No one had to pull or massage the data. That’s a good sign. But it’s also, you’re not wasting people’s time prepping all that information, which happened even… By the way, at Stripe, even when we put that in place, we still ended up with versions of that problem.
Lenny:
Yeah, [inaudible 01:04:05] I think mentioned that. I think there’s a term for it, data something, where you randomly get chosen every week and someone has to present your data.
Claire Hughes Johnson:
The metrics review meeting, yes.
Lenny:
And it’s like the next day, you’re going to have to share your meetings and [inaudible 01:04:12]
Claire Hughes Johnson:
Yes. We called it the spin the wheel, the spin wheel on who gets to present. But that has a logic in it, which is then you’re not working. So just prepare it.
Lenny:
Right. That’s awesome. I love that policy. There’s so much more I want to chat about. There’s chapters on hiring, self-development, personal development, all these things.
Claire Hughes Johnson:
Team development. Yep.
Lenny:
What was that?
Claire Hughes Johnson:
There’s a, yeah, intentional. There’s a team building.
Lenny:
Team building.
Claire Hughes Johnson:
And performance management.
Lenny:
Yeah. Okay, so we could go through all that stuff. Instead, I want to talk about the COO role broadly.
Claire Hughes Johnson:
Yes.
Lenny:
I asked on Twitter, preparing for this chat, what people wanted me to ask you about it. And most of the questions ended up being about the COO role and things like that. So I just have a few questions lined up here for you.
Claire Hughes Johnson:
Sure.
Lenny:
Okay. So Amir [inaudible 01:05:04], with little accent at the end there, he asked just at what point do companies need a COO, and how would you judge if someone is a fantastic COO?
Claire Hughes Johnson:
Oh yeah. Well, I would first say most companies, if you looked at the universe of all companies, do not have a COO. I think it’s fewer than 20%. It’s definitely fewer than 30. And I think that’s something to know, that I don’t think it’s an automatic role to have or hire. And I think you see it in more prevalently in earlier stage or high growth companies. You also, by the way, see it in certain business models. I actually think Apple was an interesting version of this, where Steve Jobs was oriented in terms of product and design, but also that Apple has… It’s very intense to manufacture software and hardware that then works together. I learned that when I worked on self-driving cars at Google, and you need a very intensely operational, detailed manufacturing, hit the marks, hit the timelines person. So I think some businesses that have a very deeply operational, say a manufacturing component, that role might be more prevalent.
But point is, it’s not an automatic. I think it’s useful in a high growth… In an environment where you’re having… Think about the founder/CEO of a company that is achieving product market fit and also having to build a company, and hire all the leaders. That is a lot because you are building the product and the business, you are building the company, and you are building all the people, bringing them all in. And that is where I think a COO type of role can give you leverage, which is… Essentially, it’s a layer that takes some of those functions and helps build them with you and on your behalf, and also in some cases, bring some experience in maybe there’s a particular function like go to market that needs to be built. And I think that’s where you see it come up. What I’ve said to some people recently is I’m a little worried, just like there’s a mythical founder, that there’s some mythical silver bullet COO hire that everyone’s like, “I will just find that person.”
And first of all, we’re all human beings. I’m not perfect. I certainly did some things well when I joined Stripe, and other things not as well, and I’m working on my self-awareness of what those things are. But I would say one lower risk strategy could be to bring in, say, a head of business operations or a role that’s sort of COO like and try a couple of functions with someone and see if they scale with the company and with the role, and then maybe you decide they’re a COO. I mean, I mentioned Stripe’s business operations team. You could hire a business ops leader and sort of say, “Hey, build this team to help be the Swiss Army knife to help scale the company, and then maybe that turns into more.” Or there’s some CFOs that are quite operational. They could take on more scope sometimes.
But I think there are other paths to getting that leverage, and there are also ways to de-risk the hire because you could end up searching forever, right? And I worry that it’s become too much of a panacea in people’s minds, like somehow they’re going to find… And people will call me, and they’ll be like, “I just need to find you.” And I’m like, “One, I may not be right for your company, but two, that was a lot of work, and I think we actually, in the end, maybe got pretty lucky.” How would you know someone is fantastic? Someone said something very smart to me, which was… I was in a meeting. It was me and Patrick. So Patrick is the co-founder and CEO of Stripe. And they said that having just the right amount of tension in our relationship was how you knew it was working for the company.
And it gave us both a little bit of pause, but we ended up having quite a good conversation after that meeting, which is there has to be mutual understanding and trust and an ability for Patrick to say, “Hey, can you go do this thing?” And then believing, I will do it at the level of quality and intensity and intentionality that he would like. But there also has to be some friction, where I would maybe say, “No, I’m not going to prioritize that. I don’t think that’s important for the company,” or I’m going to give you feedback that I don’t think we’re doing this well, or he’s giving me feedback. The customer experience is suffering. All your scale stuff is degrading this thing, right? So fantastic is not all hunky dory. Fantastic COO is just the right amount of friction intention with forward momentum and mutual trust, because then the whole is greater than the sum of its parts, right? That’s what you’re looking for.
Lenny:
I was actually going to say, I’ve worked with some founders, and they have this concept that they hire a COO, and they would just solve all these cultural issues they’re having these relationship issues. And sounds like that’s exactly what you’re saying, is that that is not often the solution to some of these deeper issues.
Claire Hughes Johnson:
Well, that would be the other problem, is actually believing… I was getting recruited, Lenny, and people would… Essentially, I felt like the founders were saying to me, “I’m going to give you all of the things I don’t like doing as your job.” And I was like, even if I’m by the way not qualify to do all those things, number one. And two is sometimes that list would be quite long, and that would make me nervous. I was like, “Do you really not running a company actually? Is that what’s going on here?” And really, I think they weren’t confronting elements of their work that needed to evolve and change. And what I loved about joining Stripe was… I think people also think, “I’m just going to hand all this stuff to this person and…” I’d love to say I took all this off of the Collisons plate, and Billy and John and the other people who were there at the time, and no, we actually were more collaboratively worked together, and I think it helped…
Well, one, you don’t feel as isolated because you’re in a team, but also there’s more joint work than people realize, I think at least in the companies I’d like to work for.
Lenny:
For the final 10-ish minutes we have together, and you have to run-
Claire Hughes Johnson:
Yes.
Lenny:
… I was thinking I could go through just a rapid fire set of tactical questions and see maybe one piece of advice you would share with someone that’s maybe struggling with this thing.
Claire Hughes Johnson:
Okay.
Lenny:
And the first is from a also Twitter person, Manuel [inaudible 01:11:52]. And he just had a question around, as you’re scaling, keeping alignment strong is challenging. What would be something you’d recommend to someone that’s scaling quickly and trying to keep people aligned?
Claire Hughes Johnson:
Well, a lot of what we talked about, having common codified documents of what we believe in, how we work, and then using communication practices very intelligently. Never think that one communication, meaning an email or an all hands, reaches the audience. You have to be smart about how you communicate.
Lenny:
Awesome. Amazing. On a different podcast, we talked about how the leaders are often the repeater in chief, just having to repeat the same thing again and again.
Claire Hughes Johnson:
Yes. And just like a marketer, use different channels. Some people read emails, some people watch videos, some people attend the meeting. Repeat.
Lenny:
Love it. That’ll be our clip to take away from this. I was watching an interview with you, and you talked about the value of offsites for creating cohesion within a team. Can you just talk about why offsites are so important to a company and a team?
Claire Hughes Johnson:
I think offsite is really a vehicle. The concept is the following, which is when you yank people out of their day-to-day routine, you create space, and also you imprint memory. And so if you say, “We’re going to do a very different thing with your time today or the next two days, we’re not going to do our emails, we’re not going to do our regular meetings, we are going to sit and work together, we’re going to brainstorm,” you’re basically activating new parts of their brain, and then you’re also having a group experience that cements a belief system usually, or a set of plans. And it also helps bring people along. We formed this thing together, it’s not effective if I say, “I locked myself in a room for three hours, and then I came out and here’s the plan.” You want to lock yourselves as a group, as a team in a room for three hours. How do you do that? And so that’s why I think it’s valuable. It’s just out of time, in a way. You’re taking it out of your day-to-day time, and I can’t not found a good substitute for that.
Lenny:
On a different topic, one of the most common questions I get from product managers and just founders that I haven’t tackled yet, and I’m curious what your take is, is around just keeping the company updated on what’s happening broadly.
Claire Hughes Johnson:
Yes.
Lenny:
What have you found works for just keeping people informed on what’s happening across the company and-
Claire Hughes Johnson:
Having really smart communication practices is something that I think a lot of companies don’t invest in early, and it’s partly because it feels like extraneous, but it’s a lot of time. If you’re going to communicate well, you have to invest in your intranet site and what’s on it. Ideally, everyone logs in and sees information on the homepage of your company internally. Do you have a newsletter? Do you have founders do like a message or a quick video, whether that’s on Slack or email. There’s a lot of smart tools. You can learn a lot from social media in some ways, but you actually need a strategy for it, and you need a set of people who help make sure it happens so that again, it creates stability and cadence. And if I want to find information about X, this is where I go. And I think there’s also that if you do it well, it can replicate down to teams, which is, oh, we have our weekly snippet stock that everybody can see the important news or whatever it is.
But you need to create those things because they’ll start to spring up, but then you’ll have a million of them, and you won’t be able to point people to the core messages. But it is not a thing to be taken lightly. And I think having someone who really not focuses on internal marketing, I’m talking about just good, “Here’s what’s important. Here’s what you need to know.” Sales teams actually do this really well, because they have to, because they have to keep the sellers up to date on the product and up to date on how to pitch it. And so it actually is worth talking to smart sort of sales leaders who’ve scaled and saying, what do you do that keeps everyone on the same page
Lenny:
As you’re talking, I realized [inaudible 01:15:49], who we mentioned a couple times, she left Retool, and she’s working at a startup that has trying to solve this problem, I think it’s called. It
Claire Hughes Johnson:
Is a lot about what they’re working on. And it’s because it is, again, an unsung thing that is critical and that I don’t think people naturally come to.
Lenny:
Next question, what are one to two, or maybe three things that people can do to run more effective meetings? I say give this masterclass on running more effective meetings. And just to boil down, what are a couple things people could probably change?
Claire Hughes Johnson:
I do have a video on YouTube about running an effective meeting, but I think the number one thing is the work of a meeting is not calling the meeting. Calling a meeting is easy. In fact, that is a problem. The barrier is very low, and it should be higher. What you really want to know… People need to know why are we meeting, and what is the point, what’s the objective of this meeting? Is it to make a decision? Is it to share information? Who needs to be here? One of my favorite things to say is make the thing that’s implicit explicit. Too many meetings are implicitly about something and not explicit enough. And I’m like, “No, no, no. I want to know why I’m here. Are we making the decision? Who’s making the decision? And how?” Even better, you say, “Does anyone not need to be here? Because we’ll just send you a note afterwards about what happened? Right? Make it more efficient, but be really explicit about the point of the meeting, and really do some inquiry on whether it’s important, whether it’s needed.
Lenny:
Maybe a final question is around decision making. So product managers who are, a lot of the audience of this podcast, have to, one, make a lot of decisions, get people to alignment, but they also don’t classically have authority over anyone. What advice do you have for aligning and decision making?
Claire Hughes Johnson:
I love product management, so much accountability. So little authority. Such a hard job.
Lenny:
What a fun [inaudible 01:17:41].
Claire Hughes Johnson:
Everyone’s like, “I want to be a product manager.” I’m like, man, that is one of the hardest jobs in tech.
Lenny:
Yeah.
Claire Hughes Johnson:
But anyway, how do you get people to a decision?
Lenny:
Yeah.
Claire Hughes Johnson:
Actually, it’s exactly… And I mentioned in my book, Gokul’s SPADE Framework, which you can look up. He has a coda on it. But actually, it’s the same thing that I said about meetings, which is making it very explicit, that there is a decision to be made, who is making the decision, the criteria by which the decision’s going to be made, who will be informed. There’s all these models. There’s racy and radar, and there’s a million different decision models. Just pick one, make it explicit, explain that’s what’s happening, and get people through it. Follow the model and do it. And by the way, you can always have an asterisk, which is if we want to revisit this decision, this is what we do. But I think too many teams get paralyzed because they’re afraid, like, well, maybe they’re not the decision maker, or maybe… When I say to people at Stripe in our onboarding, I used to run a session, I was like, if you’re not sure who the decision maker is, one, it’s probably you, and I’d rather you act that way than not because you’re going to slow the whole company down.
But really, I think the other thing is, in the book, I talk about this framework that Bezos uses, type one, type two decisions. Is it high impact? Is it irreversible? Is it not? Really evaluate, what kind of decision is this? How hard is it? And then follow a process and get it done. And don’t forget to actually make a decision. And if you don’t know who the decision maker is and you’re worried it’s not you, just ask. Don’t get stuck. Too many people get stuck, and it makes your work terrible, right? What do we all care about? Progress, impact, momentum. If anything I would say about advice to people generally is be a force for positive momentum, and it will be actually a real career maker.
Lenny:
I love that. Maybe we’ll make that the title of this interview. With that, Claire, I know you have to run. Anyone listening, you got to buy this book. Like I’ve said at the beginning, if you like my newsletter, it’s exactly my newsletter, but as a book about operations.
Claire Hughes Johnson:
Thank you. Scaling People.
Lenny:
Scaling People. Is there a website they can go to to check it out on Amazon, or is there-
Claire Hughes Johnson:
They can go to press.stripe.com/scaling-people.
Lenny:
Amazing.
Claire Hughes Johnson:
Or Amazon. Just search scaling people on Amazon.
Lenny:
Cool.
Claire Hughes Johnson:
But thank you, Lenny. I appreciate it.
Lenny:
Absolutely. Just two final questions. Where can folks find you if they want to maybe ask you questions, follow up, reach out? And then two, any other way people can be helpful to you, other than maybe pre-ordering the book?
Claire Hughes Johnson:
Well, definitely pre-ordering the book and giving me feedback on that. I guess Twitter is probably the best place to find me. I’m @chughesjohnson on Twitter. But honestly, I do hope you’ll consume the book in some form and interact with it because the goal is to make it useful. We talked about this, Lenny, your podcast for my book is just trying to be of use, and I hope it is a positive force for positive momentum. And I really appreciate the opportunity.
Lenny:
Absolutely. Thanks for making time for this.
Claire Hughes Johnson:
Thank you.
Lenny:
Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcast, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review, as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at lennyspodcast.com. See you in the next episode.
Glossary
| English | 中文 |
|---|---|
| Amir | Amir |
| Claire Hughes Johnson | Claire Hughes Johnson |
| Conscious Business | 《Conscious Business》 |
| COO | 首席运营官 |
| DISC | DISC(性格测评工具) |
| Elad Gil | Elad Gil |
| Eli | Eli(书中使用的化名) |
| Enneagram | Enneagram(九型人格测评工具) |
| Fred Kofman | Fred Kofman |
| go-to-market | 市场进入 |
| John Collison | John Collison |
| Lenny | Lenny |
| Levels and Ladders | 职级体系 |
| Myers-Briggs | Myers-Briggs(性格测评工具) |
| offsite | offsite(团队外出活动/异地会议) |
| OKR | OKR |
| Patrick Collison | Patrick Collison |
| PMF | 产品市场契合(product-market fit 的缩写,已在正文中展开使用全称) |
| QBR | QBR(季度业务评审,Quarterly Business Review) |
| Reid Hoffman | Reid Hoffman |
| Stripe | Stripe |
| Swiss Army knife | 多面手(瑞士军刀式角色) |
| 基于假设的辅导 | 基于假设的辅导(hypothesis based coaching) |
| 左手栏 | 左手栏(续前文 Fred Kofman 的概念) |
Reformatted by reformat_english.py
Stripe 扩张之路的经验 | Claire Hughes Johnson(Stripe 前首席运营官)
文字稿
Claire Hughes Johnson:
我在 Stripe 常对人们说……入职培训时我过去常主持一个环节。我会说:“如果你不确定谁是决策者,首先,很可能就是你自己。我宁愿你这样去行动,也不要犹豫不决,因为否则你会拖慢整个公司的节奏。遵循流程,把事情做完,别忘了真正做出决策。如果你不知道谁是决策者,又担心不是自己,那就开口问。别卡住。“太多人卡住了,这让你的工作变得很糟糕,对吧?我们都在乎什么?进展、影响力、势头。如果我对大家有什么通用建议的话,那就是成为正向势头的推动者,这实际上会成为你职业生涯的真正转折点。
嘉宾介绍
Lenny:
欢迎收听 Lenny’s Podcast,我在这里采访世界级的产品领导者和增长专家,向他们学习在打造和增长当今最成功产品过程中积累的宝贵经验。今天的嘉宾是 Claire Hughes Johnson。Claire 最近七年担任 Stripe 的首席运营官,帮助公司从一个小型初创企业成长为如今这家传奇公司。在此之前,她在 Google 工作了大约十年,担任过自动驾驶汽车副总裁、全球在线销售副总裁,以及 Gmail、YouTube、Google Apps 和 AdWords 的销售与运营总监。再之前,她从事政治工作。她目前还是 HubSpot 和 the Atlantic 的董事会成员。本周,她将出版一本精彩的书,叫作 Scaling People,在我看来,这本书应该、也很可能会出现在每位创始人的书架上。在我们的对话中,我们深入探讨了她书中涉及的许多核心话题,包括建立你的运营节奏,定义公司和个人运营原则,以及公司的操作系统。此外还有大量关于说不该说的话、培养自我认知、区分管理与领导力等方面的实操建议。我在对话中说了好几次——如果你喜欢我的 newsletter 和播客,喜欢它非常实操、充满模板和框架的风格,你会爱上 Claire 的这本书,也会爱上向 Claire 学习的过程。我和 Claire 聊得非常愉快,我相信你会从这次对话中学到很多。那么,在短暂的赞助商介绍之后,我为大家请出 Claire Hughes Johnson。
Claire Hughes Johnson:
Lenny:
Claire,欢迎来到播客。
Claire Hughes Johnson:
谢谢你,Lenny。
关于这本书
Lenny:
你写了这本书,叫 Scaling People,本周就要上市了。我其实读了一个预览版,非常精彩。所有在听这期节目的人都应该去买一本,尤其是如果你喜欢这个播客的话。它充满了框架、模板、指南,以及我在 newsletter 和播客中一直尝试做的那些东西。所以如果你喜欢我做的东西,你一定会爱上这本书。我简直无法想象写这样一本书需要投入多少工作量。所以我的第一个问题就是——你终于写完这本书、可以回归正常生活了,是不是松了一大口气?
Claire Hughes Johnson:
我确实松了一大口气,Lenny。写这本书并不是我的主意。Patrick 和 John Collison,Stripe 的联合创始人,真的是他们推动我去写的。我很高兴他们这么做了,这一点我承认——他们对大多数推我去做的事情都是如此——但这比我预想的工作量要大得多。能完成它非常有成就感。当然,我后来又翻看了一下,发现有些地方我想补充信息或调整原来的表述,但也许我们得出第二版再说吧。
Lenny:
这就是 newsletter 的好处。我可以直接编辑内容,马上就能上线。
Claire Hughes Johnson:
是的。
写作如何帮助厘清思路
Lenny:
我想聊聊 John 和 Patrick。但在此之前,我想问一个问题——我发现当我写东西的时候,我能更好地理解和厘清自己的想法。我很好奇,在写了这本书之后,你通过这个过程更好地理解和厘清了自己的哪些想法?
Claire Hughes Johnson:
确实如此。说来有趣,如果你问我,我会说我是通过说话和交流来厘清思路的。但每当我把什么东西写下来,我都很庆幸自己这么做了。所以我可能通过写作厘清思路的次数比我愿意承认的要多,也许我只是懒,就是喜欢说。书里有一部分,我想是在第三章的末尾附近,讲的是招聘——那是一个非常长的章节。原来关于招聘我有太多话要说,包括招聘领导者、流程以及你需要搭建的体系。当我写到那一章的结尾时,我发现自己对读者说……你可能读到了会想,她是认真的吗?你要做这么多工作?你要把所有这些都搭起来?而我不得不说,嗯,你看——我在那一章开头就说了,如果你相信人才就是一切,那么你的招聘流程就是一切。
所以,是的,你确实需要投入这些工作。但我觉得,Lenny,就像你说的,当你看到我职业生涯中所有的模板、框架、示例和建议……我在 Google 待了将近 11 年,加入时大约 1800 人,还没 IPO,离开时大约 60000 人。我在那里做过八份不同的工作。然后加入 Stripe 时大约 160 人,现在我们超过 7000 人了。是的,我有很多案例,但真正结晶出来的就是:打造一家公司需要付出多大的努力。这一点你是知道的。我希望这本书能提供一点捷径,但其实没有捷径。我希望它能加速人们的认知,这样他们就能更快地上手我们的产品、面对我们的客户。
“Claire in a box”
Lenny:
你在书末分享了一个故事,我想是在致谢部分,说有人请 John Collison 出去吃饭,就想向他取经——“你们是怎么扩张 Stripe 的?你们是怎么打造这台令人惊叹的公司机器的?“而他经常从这些饭局回来后说,“Claire,他们其实应该找你谈。这些事都是你做的,不是我。“听起来这件事促使你把东西写下来,然后促成了这本书。第一,这是真的吗?第二,我很好奇,你从 John 和 Patrick Collison 身上还学到了什么让你印象深刻的东西?我想有很多,但最突出的是什么?
Claire Hughes Johnson:
是的,确实如此。在 Stripe 我们很幸运,我们有非常多的用户和客户,他们本身就是创始人,或者是世界各地正在成长中的有趣公司,有的已经像 Amazon 那样规模,有的正在快速扩张。我跟 Discord、Toast 以及各种围绕我们成长的有趣公司都交流过。他们的很多问题不一定总是关于 Stripe 的产品。他们真正关心的是,“嗯,你们是怎么做这件事的?“或者”我们遇到了这个挑战,你们也遇到了吗?“John 确实经常出差回来后这样说。他出差比我多,可能在 Stripe 领导团队里比任何人都更多地见客户,也许除了我们的销售负责人之外。他们会问关于扩张的问题,然后他就开玩笑说,“我们需要一个 Claire in a box。“所以我想这本书就是 Claire in a box 吧。
Patrick 也有同样的经历。当我为 Elad Gil 的《High Growth Handbook》贡献一章的时候——即使你翻看那本书,我也真的非常推荐,不仅仅因为我在里面有份,我大概是里面最不出名的参与者了——我的那一章获得了很多关注,因为我觉得它非常具体、非常实操。Elad 其实帮我认识到,那些示例、细节、框架——我的”与 Claire 共事文档”也在里面——他说那就像”猫薄荷”(catnip)。我想这也是 Patrick 推动我把给 Elad 写的那一章扩展成一个更长版本的原因。
向 Collison 兄弟学习
但我从他们俩身上都学到了很多。我以前觉得自己……Lenny,我父母是老师。我以前觉得自己很好奇,是一个学习者,会主动去寻找信息。我是在一个非常重视教育的环境中长大的,对吧?但自从遇到 Collison 兄弟之后,这两个人就像海绵一样,不断吸收知识。而且每次我们面对任何事情,甚至是那些我觉得自己以前做过、有经验、知道该怎么搭建的东西,他们都会问,“那你跟谁谈过了?“或者”你读了什么?“这真的很有益。我觉得在我职业生涯早期,我没有打够电话,没有去征求别人的建议,没有寻求帮助,没有去找五年前做过那件事的人,了解他们学到了什么。我想这可能是我从他们俩那里学到的最重要的一课:向他人寻求知识有多么值得,因为我们每个人都在不断学习。
Lenny:
有没有什么故事或例子特别让你印象深刻——你真的照做了那个建议,主动联系了某人、与某人交谈,然后改变了你的思维方式或运营方式?
具体案例:职级体系与全球支持
Claire Hughes Johnson:
有两件事一下子跳进了我的脑海。第一件是在 Stripe 早期……我加入时大约 160 人。我开始引入一些领导者,搭建市场进入(go-to-market)团队,开始稳定我们的支持运营,搭建招聘和人力资源体系,所有这些事情。公司在真正地成长。很快我们就发现需要建立某种职位架构。就是所谓的职级体系(Levels and Ladders),意思是不同的薪资层级,与你的经验、影响力以及每个层级对应的要求相关。比如有工程师职级阶梯。这些东西可能让一些听众听了头皮发麻,因为定义这些东西从来都不轻松有趣,而且它也不完美。你立刻就会陷入一种感觉很不理想的状态,但什么都不做更糟,因为如果没有这些,环境很快就会变得不公平,尤其是当你需要调整薪酬和奖励体系的时候。
所以我意识到,天哪,我们得把这些建立起来。我们当时不认识做 HR 的人,所以我基本上主导了一个项目。但得益于 Patrick 和 John 的推动,我做的第一件事就是去找 Square 聊,找 Airbnb 聊,还找了两三家其他公司。在那两次对话中——我不会说具体是谁说的——其中一个人说,“哦,那简直是一场血战。“他们对我们即将经历的事情毫不乐观。而另一个人说,“你知道吗?你们这么早就做这件事,我很佩服。我们等太久了。“事实上,这也是我书中很多内容的主题——你应该在什么时候开始考虑你可能需要的这些东西?答案比你以为的要早。所以推行职级体系说实话感觉像是硬撕一层皮,但我很庆幸做了。我交谈过的一家公司等到大约 800 人才开始做,据说过程并不愉快,因为没人喜欢被归类。
Lenny:
而且还要被放到一个自己可能不满意的职级上,对吧?他们会想,“哦,我以为自己资深得多呢。”
Claire Hughes Johnson:
没错,一点没错。这不容易。这是一种变革挑战。我不会说我们做得完美,但我很高兴我们做了。那个例子绝对是其中之一。另一个例子是,我们当时真的很想尽快推出 7×24 小时的多渠道支持——邮件、电话、聊天,而且要支持多种语言,尽可能快地从当时的水平提升到我们想要达到的状态。没有多少公司在这样的规模下做过这件事,因为 Stripe 有数百万客户。我们是 B2B,但是超大型的 B2B,实际上 Google 也是如此。所以这一点对我来说进入 Stripe 环境很有优势,因为我在 Google 做过部分类似的工作。同样,这是一个我以为自己知道怎么做的事情,某种程度上确实如此,但我们当然没有做得完美,而且当涉及支付领域时,情况确实又不一样。
关于人们资金与寻求建议
Claire Hughes Johnson:
那是人们的钱。那是企业的……如果他们不知道怎么联系你,又出了问题,那就是一个巨大的麻烦。所以我确实寻求了很多建议。我想说……有没有什么建议从根本上改变了我们的做法?如果说有的话,那些建议反而推动我更快地按照自己的直觉行事,比如使用供应商、将部分模式外包。我意识到我们不可能在内部扩展所有这些东西,尤其是以我们当时的速度,但如果你还没搞清楚所有的工具和流程,就很难开始使用外部的承包商。那种平衡让我很焦虑,但你只能硬着头皮往前冲。
职衔哲学
Lenny:
有好几个方向我想聊,但我先走一个意料之外的方向。在 Stripe,你的职衔政策是出了名的。当我创建那个职级体系文档的时候——
Claire Hughes Johnson:
[听不清]。
Lenny:
对,就好像每个人都是产品经理。他们看起来像是产品副总裁的候选人,但实际上就是产品经理。这背后的逻辑是什么?这样做的好处是什么?不过我们不用深究太多,我只是好奇。
Claire Hughes Johnson:
这件事我和 Patrick 其实相当一致,没有太多讨论就达成了共识——这并不总是如此。这涉及到随着规模增长而保持可选择性,同时也关乎文化。一旦你开始大量使用头衔,你就在传递层级和权威的信号。Stripe 至今仍然如此——我认为我们可以多一些,至少多一些更明确的结构化标识,因为这容易让人困惑。我第一个告诉你这一点,我也承认这可能走得太远了。但早期在 Stripe,有一种真正的信念——这不是一家特别讲究等级的公司。如果你是掌握知识的人,你是某件事的专家,你最好,第一,在房间里参与决策,第二,推动、帮助推动决策。我不管你资历多深。这就是当时重要的文化信号——关于共同的主人翁意识,以及专业知识并不依附于层级。
头衔的灵活性与对外销售
而可选择性这一点可能更显而易见——如果你的营销团队只有两个人,就不要让某人当 CMO,甚至不要让他当营销负责人。对,你也许选对了人,但两年后,你的营销团队可能不止两个人了,比如说二十个人。那时候你是不是要给上面加一层管理者,或者出现太多头衔?然后有人觉得自己在失去什么?这就回到了职级体系那个话题,但情况更糟,因为你已经给了某人某样东西,然后又要在某种程度上拿回去,这不太好。从组织角度来说,你需要更多的灵活性。老实说,我最后再补充一点,这也是我的一点感触——你遇到一家公司,我能理解发生了什么:为了招到某个人,他们不得不说”我让你做销售副总裁或某个副总裁”,但这家公司才二十五个人,却有七个副总裁。如果你是客户或者在评估这家公司,你会想,“真的假的?“这和它的规模有点不匹配。所以我们更灵活一些。我们有很多”增长负责人”或”增长主管”之类的头衔。我知道你对增长很感兴趣,Lenny。嗯,我们对增长的定义确实非常宽泛。但我在内部还对人们说过另一件事……抱歉,这个话题真能让我说个不停。我猜你没预料到吧。如果你在 Stripe,要到市场上去,其实这和刚才说的是同一件事——你去向一个比你大得多的客户推销。我不是让你编造头衔,别谎称自己是销售副总裁,但你可以在描述自己的职责范围时发挥创意,因为你的职责范围可能确实非常大——因为你是为数不多帮忙卖产品的人之一。这对你有帮助,因为许多更成熟的公司会做那种层级匹配——“让你的高级副总裁来吧,因为我的高级副总裁要来参加会议。“而我们可以说,我们没有那种东西。这也给了你更多的销售灵活性。
Lenny:
我喜欢这个。我喜欢这种组合方式,你可以说一个适合当前场合的说法,即便那不是你的正式头衔。
Claire Hughes Johnson:
对,你可以说,“哦对,我实际上负责我们支付产品的优化工作。“我相信你确实如此。我相信你确实在做这个。
为什么运营结构要尽早建立
Lenny:
回到你谈到职级体系时的那个话题,我有一个相关的问题。你谈到人们往往做得太晚了,我很好奇为什么在你公司生命周期的早期就去思考你在这本书里写的那些东西如此重要。我记得在书里你提到,把运营结构和文化结构建立到位,有时候和找到产品市场契合、找到最初几个客户一样重要,我觉得这会让很多人感到意外。你能谈谈为什么你觉得这如此重要吗?
Claire Hughes Johnson:
我不但能谈这个,我还为此写了一整本书呢,所以请克制一下我。但我会这么说——显然产品市场契合是最重要的。我在书里确实说了,要专注于那一点,不要走得太远。我的书绝对不是从零到一,更像是 0.5 到 1.5,或者一到二。因为我确实认为,当你规模还小、专注于产品市场契合、寻找用户、获取牵引力的时候,那塑造了你很多的工作方式、你的目标、你招聘什么样的人,这些都合理。但我觉得会发生的是,第一,有些公司没有意识到自己已经达到了产品市场契合,于是开始在实际建设公司这件事上落后。你猜怎么着?
事实证明产品市场契合只是产品,那不是一家公司,那也不会规模化到某个阶段。你会看到那些公司踉跄倒下,然后有一篇关于它们的负面文章,通常问题不在产品,而是它们没有真正把公司建设好,这开始损害产品,损害使命。你有这样一个愿景,要用这个产品解决那个问题。突然之间你做不到了,因为你没有把组织规模化好。你没有在增长过程中保持文化肌理的强健。这就是为什么我认为这如此重要。所以假设你正在获得牵引力,希望你注意到了这一点。因为我觉得很多创始人是比较偏执的。
比如 Stripe,我觉得 Patrick 和 John 可能直到我出现才真正接受他们需要开始规模化了,而雇佣我本身就是其中的一部分。我看了之后说,对,就是现在,事情在发生。不仅仅是看数字——看看涌入的客户支持需求,看看涌入的销售线索。我做了个简单的计算,然后说这家公司现在的人数大概应该是当前的两倍。当然这让所有人都吓了一跳,但对我来说非常明显,因为我是从外部带着那种视角进来的。但更重要的是,不仅仅是扩展销售和支持这样的职能。你可能也知道,在支付领域,你还有很多其他非常重要的职能,比如风险、合规等等,还有帮助完成这些工作的机器学习模型。
房屋结构的类比
Claire Hughes Johnson: 至于我在书中谈到的那些组织结构和运营流程,我确实有这样一个类比,我觉得你也注意到了,就是盖房子。你需要支撑梁。假设是柱梁结构,你需要柱子和横梁,然后你还得装各种管线系统,对吧?得走一些线路。我不知道你家有没有装太阳能板,但你得把暖气引进来,得装冷气,得走管道,还有一些基础性的东西必须做好,否则整个结构就会倒塌。我把安装柱梁、管线系统和基础结构视为规模化的核心要素。因为如果你把这些事情做好,以一种特定方式来建设——这有点像俄罗斯套娃——你把它们建设成可复制的模式,对吧?
所以公司做目标的方式可以从公司层面开始,这就是 OKR 在 Google 之所以如此精妙的原因——它可以一直复制下沉到个人层面。同样的通用结构允许它在截然不同的规模层级上运行。你要寻找的就是这些通用要素。顺便说一句,我们实际上没有那么多这类要素。你不想强制规定太多,不想设置过多框架,但要有足够的量,让每个人都能在公司这个”技术栈”的上下各层中去运用。如果你不早早开始搭建这些东西,人们就会自己发明。然后你就会得到——想象一下一栋不到两年就被加建了十七次的房子。看起来不太稳固。然后你会发现自己不得不推倒重来,我想我们都见过有公司这么做。
Lenny: 我确实想深入聊聊那个房屋结构以及它的所有组成部分。但在我们进入那个话题之前,如果你是一个正在寻找产品市场契合的早期阶段创始人,也许我跳得有点快了——你认为哪些要素是他们现在最重要的、必须做好的?因为他们会读你的书,书里给了所有你能做的事情的建议。
Claire Hughes Johnson: 对。
Lenny: 如果你必须挑选几件在产品市场契合之前就必须做到位的事情,你觉得最重要的是什么?
早期创始人需要做好的事
Claire Hughes Johnson: 我觉得在那么早期的阶段,保持极简,专注于产品市场的目标,也就是——你要解决什么问题?你的愿景是什么?你为投资人做的路演 PPT 里的一切内容,不仅仅对投资人有意义。顺便说一下,人们会忘掉这一点。你讲给投资人听的故事,尤其是早期投资人的,恰恰也是你应该对内讲给每一位被你招聘来的人听的故事。我们为什么存在?我们要解决什么问题?我们吸引了哪些早期客户?他们的反馈是什么?这些是你最需要的,但你需要记住去分享它,不要只在融资时才用,不要只在董事会或投资人会议上才用,内部也要用。我觉得凭借这些核心内容,你其实可以走相当远。
当你开始……你首先要建立的很可能是一套招聘流程,我觉得这比你想象的来得更早更重要。不要只是图方便就雇佣朋友圈里的人。想想你需要什么,甚至在产品市场契合之前你就需要建设哪些能力。正如我所说,书里有一整章讲这个,但我认为最基础的做法是:我们如何评估人才?我们在寻找什么样的人才?我们去哪里寻找人才?把这些想清楚,然后在内部对面试做一些培训。我认为面试并不是一种与生俱来的技能。人们以为它是,其实不是。网上就能找到一些非常基础简单的面试技巧和小窍门。我强烈推荐……我的书里也有评分标准的例子和可以使用的面试问题。你如何真正了解一个人——毕竟在 30 分钟或 45 分钟里真正评估一个人是很难的。
所以我认为面试能力以及一些基础的面向投资人的核心内容是你需要的。但当你开始获得一些牵引力之后,你就需要把那些我称之为更基础性的内容进行梳理和文档化。因为如果你还在产品市场契合之前,你大概规模足够小,可以直接把所有事情口头告诉每个人,不需要发资料包或者让他们坐下来参加入职培训。但一旦你的招聘速度开始加快,你就需要更多地文档化,你就需要开始建立一些非常轻量的流程来规范事情如何推进。因为说到底,你是在试图复制速度。当大家都挤在一个房间里,每个人都知道”哦,这是今天最重要的事情”,然后埋头苦干,这很容易。但很快,这种情况就不复存在了。
个人运营原则
Lenny: 我确实想在这一点上再深入一层,但在我们钻进那些细节之前,有一个话题我想先聊聊。我注意到一件很有意思的事:你的书是从个人运营原则这个概念开始的,而不是”公司应该怎么运作”。它从”你应该如何看待自己”开始。书里有四个原则……在我逐一展开之前,你能不能先描述一下什么是个人运营原则,为什么它很重要?
Claire Hughes Johnson: 记住,这本书讲的是两件事:公司建设和公司结构,以及如何复制所有这些好的步骤和管理方法。所以书真正讲的另一件事是管理的实战指南——如果没有人类参与,建设公司会很容易,对吧?但有人类,而人类很复杂,我很复杂,你也很复杂。有些东西激励我们,有些东西让我们失去动力。而且激励我们每个人的东西并不相同——不过 Lenny,我觉得你我之间有一些共同之处。但重点是,书从你自己开始。我认为很多人觉得管理是从团队开始的,甚至是从公司开始的。实际上我觉得创始人也会犯这个错误——创始人觉得,嗯,从我的产品开始。是的,但其实要从你自己开始。所以书从我的信念体系开始,也就是自我认知。自我认知到建立相互认知——这是你在公司建设或管理中要取得成功必须攻克的最根本的东西,在我看来是这样。
但我想说,我是那种有强烈观点但观点又比较松动的人。而这一点,是我强烈持有且坚定不移的观点:你越是能主动寻求反馈,努力理解自己的驱动力、优势、盲点和行为倾向,把这些吸纳进来并展示给他人,你就会成为一个越高效的公司建设者和管理者。所以从你自己开始。我阐述的那些运营原则既是我个人的,也是整本书内容的基础。我确实认为,真诚的领导者往往都有自己的原则,对吧?Lenny,你可能也有几条——你也许没有全部明确表述出来,但我有我的,它们在书里。但我觉得你也会发现,其中一些你是可以采纳的。如果你正在寻找一些作为领导者可以开始使用的原则,我希望我提出的几条对你有所帮助。
如何凝练个人运营原则
Lenny: 我想聊聊你书里的四个原则,不过顺着你刚才的话题,有什么方法可以帮助人们凝练自己的运营原则?你会给大家什么建议来做这件事?因为正如你所说,人们心里大概有这些原则,但并没有真正写下来。
Claire Hughes Johnson: 没错,确实没有。书里有一个我推荐的练习,更多是帮你厘清个人价值观的,但这正是你应该开始的地方。具体来说,有一整套菜单,你在网上也能找到,大概七八十种不同的价值观。所谓价值观,我指的是家庭、雄心、影响力、竞争这类东西。有人重视教育,不同的人看重不同的东西。而且这没有对错之分。你可能非常看重竞争,而我可能把合作看得比竞争更重要,这完全没问题。我们俩在一个团队里可能各自都能很有效,对吧?所以基本上,如果你拿到一份价值观列表,然后说,好,如果我必须从中挑出10个对我最重要的,然后如果只能挑5个,然后你真的逼自己一把——如果我只能选3个……
其实最好找一个跟你一起工作或彼此很了解的人,以对话的形式来做这件事。你得去解释,为什么?为什么当我真的被逼到极限的时候,我必须死守”教育”或”学习”这个价值观?或者为什么我必须死守”正直”这个价值观?我在书里讲了一个我合作过的经理的故事,对他来说,透明是一个非常重要的价值观。关键是,你的价值观背后通常都有一个故事,对吧?在书里我用 Eli 这个化名来指代他。Eli 后来在我们的一次外出团建中分享了这个故事。而他对透明的重视其实有点让人头疼,因为 Eli 会对所有人说所有事,包括他自己的团队,甚至我们的方案都还没成型的时候。但 Eli 站起来,讲了他小时候的故事,大概七八岁的年纪,意识到母亲病得很重,但没有人真正告诉他到底怎么了。然后不幸地目睹了她离世的过程,最后被继父带出去吃饭,被告知:“你妈妈走了。“好,你整个世界观在听到这句话的时候基本上就崩塌了。你会想,哦,原来透明这件事是如此真实。这对他来说是一段塑造性的经历,改变了他行事的方式,而且可能影响了他一生。如果你自己也能到达这一步——对自己讲出,那个故事是什么?是什么让这件事对我如此重要?那么你就开始进入一种自我发现的模式了,然后你开始记录:好,如果这是我最看重的前三个价值观,这是原因。然后我认为你要去寻找的是,我的工作风格倾向是什么?所以你有了自己的价值观,然后你继续往下走……抱歉,我可以一直说下去。我提醒过你,我可是写了一整本关于这个的书。
工作风格测评
但基本上,所有那些工作风格测评——Myers-Briggs、DISC、Enneagram,你能想到的都有。顺便说一下,我建议全都做一遍,因为我觉得非常有用。其中一些就是数据,你只是在收集数据。但很多测评归根结底是:你是内向还是外向?在这个连续谱上你处于什么位置?你是更偏任务导向还是人际导向?如果你想象一个横轴和一个纵轴,你是更偏任务还是更偏人际?所以我建议你拿着自己的价值观,然后给自己定位。我是一个更外向、任务导向的人吗?这意味着你有点像指挥者,把事情搞定那种人。还是我更外向、人际导向?这可能意味着你实际上很擅长展现魅力,建立追随者,也许擅长推销一个愿景?很多销售人员都是外向且人际导向的人。
然后你开始看到,好,如果这是我的默认倾向,这是我的价值体系,那么我行事方式中哪些真正构成了我是谁,它几乎变成了一套信念体系。我在书里的运营原则,一条是建立自我认知,从而建立相互认知。另一条是说出你以为自己不能说的那句话。我渐渐相信,你最大的优势,第一,往往也是你的弱点;第二,往往是你自己都没意识到的大优势,因为它几乎就像呼吸一样自然。对我来说,相当公开和直接地说出一些事情,但不带威胁性,这是我的本能。John Collison 有一次对我说,他说:“很有意思,你给反馈的时候,实际上可能相当犀利,但我离开时却感觉很受鼓舞。“但我并不想表现得犀利,但我觉得我可以把事情拆解开来,说出这个东西——这是我的观察,这是正在发生的事——不是评判,不是威胁,实际上是在为人们打开一个机会。所以说出来你以为自己不能说的那句话。你会发现,我们当中更多的人其实是可以做到这一点的。然后我还要回来谈谈领导者和管理者之间的区别,这是我职业生涯早期做得不好的事情,Lenny。
Lenny: 在我们聊到那一点之前,我想针对这一条问一个跟进问题,因为我很高兴你在这里把四条原则都讲到了,太好了。但我想问的是……很明显,你非常擅长说出那些你以为不能说的话,我很欣赏这一点。很多人并不擅长这个。
Claire Hughes Johnson: 确实不擅长。
Lenny: 对于不擅长这件事的人,你有没有什么具体的操作建议,教他们如何真正说出让人不舒服的话?
说出不舒服的话的具体技巧
Claire Hughes Johnson: 我认为关键在于——Fred Kofman 在他的书 Conscious Business 里有一个概念,叫”左手栏”。就是你在跟我对话,或者你在看一场会议进行的时候,你脑子里有一个持续不断的旁白。说实话,其中一些东西相当尖锐,对吧?你不会想要张嘴就直接把那些话说出来。但 Fred 说的是,学会给左手栏解毒。我会说,想一想有没有办法说出那件你以为自己不能说的事。你已经把它自我过滤掉了,这我不喜欢。我希望你想想,我能不能说出来?我觉得有几个技巧。第一,提一个问题。问题不构成威胁。顺便说一句,这个问题甚至可以是:“有没有什么我们没在谈的东西?我觉得……”然后你把它归为自己的感受。
所以第二个技巧是,把它归为自己的感受。这是你的观察,这是你的感知。这不是一个评判。我不会说:“Lenny,我觉得你搞砸了那次面试。“那没有用。如果我说:“Lenny,你知道吗?我想知道你是不是在那次面试中错过了一个机会。你有没有觉得漏掉了某个方面……”然后你带着好奇:“什么意思?“我说:“嗯,我在跟你一起看这件事,我就站在你旁边观察着。“这样就不那么有威胁性了。所以第一,提一个问题。第二,做出一个你自己承担归属的观察。比如我说:“我觉得有什么东西我们没在谈,我在想……”我把这归到自己身上。“我在想,是不是这两个团队似乎在做完全相同的项目。”
我在书中谈到过一次我参加的会议,当时很明显有两个团队在冲突,但没有人说出那件其实相当糟糕的事情。我心想,这真的很糟。我们有两个团队,看起来都觉得自己拥有某项工作的所有权,而且彼此冲突。但我想说的是,如果你做到这两件事——提出一个问题,自己承担这个观察,不做评判——你会比你预想的走得更远。而且,顺便说一下,这种分享,第一,可能还有其他人也有同样的想法,只是还没法说出口,而你打开了一扇门,很多人可以跟着走进来。你不是一个人。
做探索者,不是讲授者
Lenny: 你有一个框架,我想你把它叫作”做探索者,不是讲授者”。这就是你刚才描述的东西吗?你是这样描述的吗?
Claire Hughes Johnson: 是的。对我来说,我刚才谈到的更多是会议或对话场景,但我认为这个——我很高兴你提到这一点。我认为这其实是我非常基础的管理框架之一,就是在一对一交流中,你作为管理者的工作……首先,太多人认为管理者的工作是当专家,告诉别人该做什么。不,实际上,你的工作是让团队里的人发挥出最好的水平。你需要创造一个环境和上下文,提供信息给他们,然后你需要提供一种辅导。当然,我觉得有些人把辅导理解成讲授——让我来教你怎么做这个 Excel 模型。有时候确实如此。有时候有人来找你说:“你能具体教我做这件事吗?”
这没问题。但管理的大部分其实是一个探索过程,是和对方一起探索。是保持好奇。是说:“我观察到了你工作中的这个模式。你有没有注意到这个模式?是不是有什么……”我还有另外一个框架,叫基于假设的辅导。我觉得”直觉”这个词有点被污名化了,我也能理解原因——尤其是如果你和很多工程师一起工作,我就是这样。直觉并不总是数据驱动的。但你猜猜科学假设是什么?它就是一个有充分依据的直觉。我觉得太多管理者等到手上有了一百万条数据才去跟别人提出一个改进建议。相反,我会说,拿一些数据,形成一个假设,然后和对方一起探索它。因为如果你的出发点是好的——我认为任何优秀的管理者都是如此——我提出这件事是因为我想帮你看到它,你告诉我它是不是真的,这样我们双方都能帮助让它变得更有效、更好。
举一个非常轻量的例子,“我觉得在那次会议上……你觉得那次展示进行得怎么样?“对方可能会说:“还行吧,我觉得我把材料讲完了。“你说:“嗯,我觉得你当时可能有点紧张。我只是想探讨一下。你是不是……”顺便说一下,对方可以说:“哦,不不不,没有没有。“那你可以退一步,或者你可以说:“哦,可能只是我的感觉,但我注意到了一些身体上的表现。你的腿有点抖,你的声音有点重复。“然后对方会说:“什么?“而你做的其实就是举一面镜子……而且你必须自己承担它。你必须说:“我在那次会议上对你的感受是,你在我看起来有点紧张。也许你并没有,但也许这只是一个身体语言方面的反馈。”
你有没有遇到过这种情况?我的团队里有几个人会做一个奇怪的动作。这是远程办公之前的事了——当他们在会议中感到不舒服的时候,他们会把椅子往后推,离开桌子,基本上是退出了讨论圈。这是一个非常有物理感的声明。他们自己完全不知道,Lenny。他们完全不知道。我只是在旁边观察会议,心想,天哪,你离其他团队成员已经有四英尺远了,因为你不喜欢这个话题。而我要和你一起探索的是,你怎么用语言来表达,而不是用身体退出房间或退出讨论圈?这些只是一些例子。抱歉,我可以一直讲下去。但我真的认为,那种探索的态度,以及互相协作、一起去发现关于你的一些事情的方式……
顺便说一下,这可以是双向的。他们可以直接回敬你:“嗯,我观察到了你这个表现。“很好,很好。我为了这本书采访了很多人,来自不同领域的各种领导者和管理者,其中一位是 Reid Hoffman,他算是比较典型的。但 Reid 和我聊了另一个运营原则,就是管理与领导力的区分。Reid 很坦诚。他说:“说实话,我更像一个领导者。我不是一个管理者。“他说:“我不是一个很好的管理者。“然后他给我讲了一个故事。他说,在他创办的第一家公司里,他招了一个更偏运营层面的人。Reid 在跟他观察一件他们应该做的事情,那个人对他说:“Reid,我不会雇你去管理麦当劳。”
Reid 的反应是:“好吧,那告诉我我们需要怎么做,这样我们就能解决这个问题。“但有趣的是,当深入挖掘那件事时,Reid 的运营原则其实是——他非常看重创造一个开放反馈的环境。他说,我喜欢那个故事的地方在于,它很好笑也很尴尬,但那个人能很自在地对我说”我不会信任你去管理一家麦当劳”。我觉得这其实很令人振奋,因为我觉得并不是每个创办公司的人或管理者都创造了一个拥有如此高信任度的环境,对吧?而这就是 Reid 认为自己能把很多事情做成的方式——人们会直接给他反馈。
Lenny: 我们已经聊了你个人使用的三个运营原则了,我很喜欢。我很喜欢你这样逐一讲下来。
Claire Hughes Johnson: 区分管理和领导力是第三个,没错。
Lenny: 简单总结一下,第二个是说出你以为自己不能说的话。第一个是——
Claire Hughes Johnson: 说出你以为自己不能说的话,对。
Lenny: 然后第一个是,先建立自我觉察,再建立相互觉察。
Claire Hughes Johnson: 对。
Lenny: 很棒的是,你分享了这么多精彩的故事和方法。在书里,你实际上有模板来帮你做这些事情。所以这里面很多也是指引。如果你真的想做这些,去看看书,你真的可以实操。它不只是一堆高层的东西。那第四个是——
Claire Hughes Johnson: 回到操作系统。
Lenny: 我们来聊聊。
Claire Hughes Johnson: 这个就像我之前说的,你可以为公司创建一些”基石文档”。比如我们的运营原则、我们的价值观。这就是我的基石——我认为,尤其是高速增长的环境中,但实际上你所处的任何环境都可能变得非常混乱,充满模糊性。有太多你不知道的东西,很容易陷入瘫痪,或者干脆向混乱投降。你会想,天哪,我不知道今天会发生什么,我就随便安排点事,先把这一天熬过去算了。而在很多这样的时刻,你所做的只是在制造更多的混乱。我认为管理者——以及很多领导者——一个非常重要的角色,就是在感觉没有什么稳定可言的时候,创造出稳定性。
稳定性来源于仪式感和大家共同遵循的惯例。所以我们设定季度目标或月度目标。这是一种仪式,是我们共同做的事情,它实际上是稳定性的来源。是的,它感觉像是一个流程,可能感觉像是一种管理手段,但它也有自己的节奏。我觉得会发生的情况是,你想象自己正在失控旋转,然后你想,我怎么回到正轨——这是我做事情的顺序,这是我做决策的方式,这是我们制定计划的方式,这是我们做决定的方式。那些基石不是用来运转公司的流程。如果做得好,它们是起稳定作用的,因为它们是所有人共同的应对方式,所以即使其他一切都乱了套,大家至少还能抓住这些。
你有一个客户在流失,第二天又有一个大型产品发布,天哪天哪。冷静下来。我们的发布流程是什么?我们怎么发布产品?我们有一套做法。我们不需要失控、不需要重新发明轮子,对吧?这就是一种稳定的力量。回到操作系统这个话题,另一个我想说的是,随着我的职业规模不断扩大——从个人贡献者,到管理一个小团队,到管理更大的团队,到管理多个团队,到管理管理者,你懂的——我意识到,后来我开始管理多个职能。所以我需要在不同的上下文之间切换……在 Google 的时候,有一段时间我手下有产品人员、工业设计、运营、BD,职能差异非常大。但实际上,我从根本上如何运作它们,在最底层、在最基础架构的层面上,是一样的。
这给了我作为领导者的稳定性。当我跳进一个会议,我会说,好,让我们看看关键指标。我们每个团队都有这些指标。让我们看看我们设定的目标。当你在七个不同的项目或七个不同的团队之间切换上下文时,这也帮助你保持稳定。所以我不敢说这是我谈得最多的运营原则,但如果你问我,“你怎么实现自我扩展?“我会说,“其实我有一套像计算机一样的通用操作系统,这就是我维持稳定感的方式。“
房屋隐喻:三大支柱
Lenny: 完美的过渡,正好引出我想花时间讨论的下一个大话题,就是你提到的那个”房屋”隐喻和它的三个组成部分。这是这本书的核心。你能再谈谈这个房屋结构的三大支柱吗?然后我们逐个过一遍。
Claire Hughes Johnson: 好的。书的开头讲的是公司建设,关于公司结构的那一章讲的就是支撑梁、运作机制,以及基础性的东西。有意思的是,其实——嗯,我想想,盖房子的时候你确实是先打地基的。所以一个是你可以创建的创始文档,我很乐意展开聊聊。然后另一个是支撑结构,也就是一些做事的方式,比如我们谈过的季度业务回顾或者 OKR,或者你如何通过规划来创造一个所有人都……然后运作机制是我所说的运营节奏,本质上就是你工作的韵律。日历、我们每个人经历的年份,往往会在一定程度上决定我们的工作方式。周一和周日感觉是不一样的,对吧?公司也有同样的节奏,通常也是由日历驱动的,但也可以由事件驱动。
我们在 Stripe 经常谈到,我们的客户活动——叫做 Stripe Sessions——对内部的重要性不亚于对外部客户的重要性,因为它是我们节奏的一个倒逼机制——我们如何规划产品、到那个时间点我们想达成什么、我们想展示什么。很多公司都是这样,但我们实际上把它纳入了全年节奏的思考中。而且我们还建了另一个活动,通常是我帮忙运营的,是一个内部活动,大概在客户活动之前六个月举办,这很好,因为你可以把你认为想展示的东西先在内部做演示。你基本上创造了一个节奏——我们要逼自己做一些疯狂的东西,内部演示,然后看能不能在客户活动到来之前把它外部化。
但这就是一种节奏。季度业务回顾也是你节奏的一部分,等等。所以这就是基础架构,但我真正想说的是,第一,我觉得这些东西并不超级难。你也知道。它就是需要花功夫去做——把它建立起来,然后真正去使用它。我觉得很多领导团队出错的地方——尤其是年轻公司的领导团队——是他们尝试各种不同的载体来做这些事。然后要么没有真正去遵循,要么试了没多久就扔掉了,这会造成很多混乱。所以我的建议是,做的事情要少,但要保持一致,尽量做好,看看它们是否对你有效,然后大概一年做一次修订。但不要不停地抛掉你听说的其他公司的新做法。不然就会变成一个奇怪的大杂烩式的运营体系。你在点头,因为你也见过很多这种情况。
Lenny: 对,我看到的一个问题是,人们总觉得会有一套完美的系统和流程,没有任何缺陷,他们总是说,“这不完美,我们得继续优化。“但我的发现是,永远就是——这是你当下能想出的最好的系统和流程,这是你目前最好的主意。它会有缺陷。绕过那些缺陷就好了。但要清楚,永远不会有一套完美无缺的方案。
Claire Hughes Johnson: 没有完美的。没有完美的组织架构,没有完美的运营方式,没有完美的绩效管理和职级体系。但拥有一个并 commitment 于它,就是好的。不要让完美成为优秀的敌人。
成功公司的内部混乱
Lenny: 还有一个你提到的点我觉得很有意思值得聊聊,就是公司内部往往是混乱的。我猜人们从外部看 Stripe,会觉得他们一切都搞定了,那么顺畅,像一台机器一样运转。我觉得人们看其他成功的公司也会这样想,天哪,我们公司怎么这么乱,这不正常。但我觉得——你说我说的对不对——大多数公司内部在很长一段时间里都是又疯狂又混乱的,而且往往一直如此,对吧?
Claire Hughes Johnson:
Claire Hughes Johnson: 是的。混乱有不同的种类,但这一点确实如此。有句话怎么说来着——永远不要相信对你最好的那些报道,也不要相信对你最差的那些报道。实际情况永远不会像别人说的那么糟,也不会像别人说的那么好。正常运转的样子本来就不漂亮,要做的事情太多了。这就是事实,每家公司都是如此。我以前有个朋友也在创业,我们会见面。我们都来自波士顿地区,说起来话长,但我们偶尔会碰巧坐同一班从罗德岛飞回波士顿的航班,回家处理家里的事。我们会站在飞机过道里,被乘客们抱怨,因为我们一直在互相交换各自公司哪里出了问题的情报。我们之间有个说法,就像是——哦,我又翻起了一块石头,石头底下有一些非常丑陋的、令人毛骨悚然的虫子在爬。但事情就是这样,永远不可能完美。不过我想回到我刚才说的,要有一些稳定的做事方式,因为这样可以建立一种……我不知道,我不是要营造一种公司像机器一样运转的观感,而更像是一种——这是一个运营良好的公司,对吧?你怎么创造这种观感?因为你们遵循了一致的运营方式,即使内部有很多混乱的事情在发生,对外也会让人觉得更好。
建立文件
Lenny: 回到建立文件这个话题,你能谈谈这组建立文件里都包含哪些东西吗?我觉得更有意思的一个问题是,作为一家创业公司,什么迹象表明你应该在这个领域投入更多时间?
Claire Hughes Johnson: 好的。里面的内容都是很经典的东西,没有什么你没见过或不了解的。第一个是,我认为拥有一条使命宣言是好的。我加入 Stripe 的时候,我们还没有。后来逐渐明显起来,“提高互联网的 GDP” 大概就是我们的使命,因为人们不断把这句话复述给我们听,而 Patrick 早期在某个网站的文案里写过这句话。但有趣的是,候选人和客户都自然而然地抓住了这句话。这非常 Stripe,因为它带点知识分子气息,有点学究气,又很有抱负,而且……GDP 确实关乎经济进步,而这正是我们所做的事情,对吧?我们在建设商业和支付的基础设施,不仅仅是为了互联网。不管怎样,重点是——要有一条使命,或者至少要有那么一行字,说明你想达成什么。
然后我非常主张写出类似 Stripe 所谓的长期目标的东西,它不是我们的短期目标,而是更远的目标——我们为什么存在?使命是一句话,所以你需要在这背后补充更多实质内容,对吧?实际上,如果你去看我们的长期目标——顺便说一下,我原以为这会是一个三到五年的目标,但我觉得它们至今仍然适用——其中一个长期目标是”推进开发工具领域的前沿水平”,这不是每个人,尤其是每个客户一开始就能说出来的。但你想想……Lenny,你刚才就做到了。你想一分钟就会发现,API、文档,以及我们开源的很多东西,Stripe 都非常重视。
我们永恒的用户从根本上说是开发者。就是那个在集成 Stripe 的人,对吧?不管是简单集成、复杂集成,还是介于两者之间,我们都真正关心他们的体验,我们关心工具是否出色。因为如果你不推进开发工具的前沿水平,你怎么提高互联网的 GDP?总之,重点是把这些说出来。因为直到我跟你说了这些,我才能跟你深入讨论,然后你来到 Stripe 工作,你才能理解为什么我们投资了某些东西,为什么这些对我们的用户体验和使命如此重要。所以要把这些清楚地表达出来。其中一些可能有一点理想化,但它们至少应该足够真实,让你能够就此展开对话……你看公司里任何一个人,他们每天选择用时间做什么,应该受到这些东西的引导——我们想达成什么?
我们的长期目标是什么?如果他们不知道这些目标,他们怎么能做出正确的选择?这是一点。另一点是,很多公司会写公司价值观,而在 Stripe,我们写的是运营原则。我想你的节目里请过她,她讲过这些,我们甚至把我们的版本整理了一份发给候选人,让他们可以评估自己是否想加入这家公司,因为我得知道在那儿工作是什么样的。我觉得这非常有价值,因为不是每家公司都适合每个候选人,双方匹配度越高越好。但拥有一些运营原则是很重要的。我觉得你可以做得更多,但我会从这里起步,就是这三样东西。
Lenny: 太好了,我喜欢它的简洁性。
Claire Hughes Johnson: 判断的时机就是——人们开始问你问题。尤其是新员工经常问你什么重要,或者”我们为什么要这样做?“你自己一开始也说了,把东西写下来,不就能让它更清晰吗?那就到了该写下来、给所有员工一个清晰版本的时候了。
Lenny: 总结一下,你说的三样东西是使命、运营原则/价值观。第三个是什么来着?
Claire Hughes Johnson: 对,长期目标。
Lenny: 长期目标。
Claire Hughes Johnson: 就是关于你为什么存在的更多细节。你到底想达成什么?
Lenny: 有意思。那根据你的经验,这些是数字化的目标,还是一段描述性的文字?
Claire Hughes Johnson: 那些更多是一些标题性的描述。我认为你的短期目标才会有对应的数字指标。比如说你有一个长期目标——Stripe 的另一个长期目标是加速全球化。你想想这需要什么?这需要我们进入很多市场,需要我们在很多市场拥有用户和客户,还需要消除跨境摩擦。在支付和资金转移领域,这些事情目前还存在很大的摩擦——不应该这样的,如果你想推动全球化、加速全球化进程的话。所以这些就可以转化成数字化的短期目标。
Lenny: 基本上就是目标,然后——
Claire Hughes Johnson: 对,就是较长期的目标,然后关键结果那部分,对应的是更短期的目标。但实际上,如果你在写公司目标时遇到困难,不妨把视角拉远,想一想”如果我们要实现这个使命,长期来看我们必须完成什么?“然后你就可以从那里往回推,“哦,我们所有的目标大概都可以归入这三到五个类别里。“砰,搞定。然后你写短期目标就容易多了,因为总会有一个是关于比如国际扩张的,总会有一个是关于新产品的,因为我们要做 X,而一个产品做不到,诸如此类。你可以想象这些例子。
Lenny: 太好了。我知道你的书里有很多这方面的实际案例。
Claire Hughes Johnson: 是的,有的。
Lenny: 所以再次推荐大家去看那本书。好,以上就是建立文件的部分。下一个部分是运营系统。我们聊聊这个——一个公司的运营系统包含什么?有哪些组成部分?
Claire Hughes Johnson:
我认为我们已经多少涉及了其中的许多组成部分,那就是你是否有某种形式的目标?这就回到了我们刚才讨论的内容。在 Stripe,我们有一套年度数值指标体系,还有一套目标体系或者说 OKR——目标与关键结果——但核心是你用什么结构来设定你想要达成的里程碑,无论是数值型的,还是更像二元判断的——这个东西上线了没有?然后是 QBR,即季度业务评审。我们如何审视业务的各个部分?节奏是怎样的?首先,我们以什么形式来做这件事?这会是——我在书里分享了一些示例模板,比如如果你是一个团队,在汇报进展情况相对于你的战略和目标时,可能会填写这样的模板。
然后还有指标和仪表盘的部分。你在内部用哪些东西来衡量进展,哪些是输入指标,哪些是输出指标?我给了一些这方面的例子。再就是,我认为还有其他一些……正如我所说,可能还有一些使用频率更低的模板,比如用户活动、产品发布,或者产品上线的方式等等,但其实很简单,主要就是目标和你怎么回顾业务。规划。我谈了很多关于规划的内容,也就是——你之前也提到过,我想你我都认同一点:没有什么完美的流程可以用来规划下一年或下两年,但你仍然需要硬着头皮搞出个东西来,尤其是在某个阶段之后。我见过的每一位首席运营官,我们都会一起抱怨。
我们说,唉,规划,大家都讨厌我们,负担太重了,但你还是得不断尝试,还是得做。所以我们讨论了规划流程,它们可能是什么样的,以及你怎么搭建它们。然后你就可以用目标和 QBR 来对照计划进行衡量,对吧?以上就是运营系统的一些组成部分。然后节奏就是说你多久做一次这些事情。实际上我们有一个重要的经验教训,我认为那些运转迅速、比较年轻的公司往往会抗拒更成熟公司那种基于日历的节奏,因为它们看起来太慢了。你会说,真的吗?你真的要花三个月才能达成那个目标?还是你在人为地把自己限制在某个最小公倍数的时间框架里?我理解这种担忧,而且我想说你的节奏不一定非得是一个季度、半年,甚至十二个月。
在 Stripe,我们曾经做过半年为一个周期的流程。所以不是一年,而是六个月。当然,话说回来,仍然有些事情需要一年甚至更长时间,但我认为可以去尝试不同的时间框架,不要被其他公司的做法束缚。不过我们在 QBR 上的一个教训是,有时候那些季度——QBR 里的 Q 就是季度的意思——那些季度业务评审频率太低了,尤其是对于新的产品领域。它们还在开发中,还在收集大量反馈,频繁上线。所以我们说,好吧,不再是季度了,改成每六周一次的业务评审。没问题,改变你的节奏就好。关键是要有一个节奏,因为这样对团队来说是可预期的。他们知道自己朝什么方向前进,知道什么时候要做汇报,并且能够以合理的方式在那个时间框架内设定目标来推进。
Lenny: 快速问一下。有什么迹象表明你的节奏不对?什么信号提示我们应该缩短或延长?
Claire Hughes Johnson: 大家通常会抱怨这些事情,但我觉得如果……一个是你刚才说的,如果在两次评审或汇报之间没有足够的进展,那可能节奏太快了;如果你评审的内容看起来是过时的——“这个我们已经知道了""那件事我们已经做了""对,那个问题的会我们开过了”——那可能节奏太慢了。还有一个有趣的现象,就是有些公司会有比较频繁的指标评审节奏,但策略评审的节奏很低。结果就是指标评审会变成了策略评审会,因为你没有足够频繁地讨论策略。于是你通过数据来讨论策略,等到真正开策略评审会的时候,你会觉得,这个会我们开过了。这就说明有些地方出了问题。对我来说,关键在于内容的时效性和新鲜度,而且确实要有新内容。如果没有新内容,你就是在给人们制造工作量。话说回来,给他们时间去干活吧。
所以我认为不要自欺欺人地以为,更频繁地检查事情就能让事情跑得更快。我想说,有时恰恰相反。所以要非常警惕因为制造管理开销而降低了实际速度。我们在 Stripe 尽量做到的一点是,如果我们看指标,就直接看你的实时仪表盘。不要专门做一份演示文稿。直接共享你的屏幕,展示你的仪表盘就好了。这是一个好习惯,因为首先,这意味着你必须有一个非常好的、实时的、可通过网页访问的仪表盘,不需要任何人去拉取或处理数据。这是好迹象。而且你也没有浪费人们的时间去准备所有那些信息。顺便说一下,在 Stripe,即使我们制定了这个规则,仍然会出现这个问题的各种变体。
Lenny: 对,我记得好像有人提过。我觉得有个专门的术语,数据什么什么,就是每周随机抽人,被抽到的人要来展示自己的数据。
Claire Hughes Johnson: 指标评审会,对。
Lenny: 然后就像第二天,你就得分享你的会议内容什么的。
Claire Hughes Johnson: 是的。我们管它叫转盘,转转盘决定谁来汇报。但这背后是有逻辑的,就是你平时不需要专门准备,到你了再准备就行。
Lenny: 对,太棒了,我很喜欢那个政策。还有好多我想聊的内容。书里还有关于招聘、自我发展、个人发展等等章节。
Claire Hughes Johnson: 团队发展。对。
Lenny: 你说什么?
Claire Hughes Johnson: 有一个,对,是刻意的。有一个团队建设的章节。
Lenny: 团队建设。
Claire Hughes Johnson: 还有绩效管理。
Lenny: 对。好的,这些我们都可以聊。不过我想聊聊首席运营官这个角色,更宏观地谈谈。
Claire Hughes Johnson: 好。
Lenny: 我在 Twitter 上发了问,为这次对话做准备,问大家想让我问你什么。结果大部分问题都是关于首席运营官角色的。所以我准备了几个问题要问你。
Claire Hughes Johnson: 好的。
Lenny: 好。Amir 问,公司在什么阶段需要首席运营官?以及你怎么判断一个人是不是一位出色的首席运营官?
Claire Hughes Johnson:
公司何时需要首席运营官
Claire Hughes Johnson: 哦,对。首先我想说,大多数公司——如果你看所有公司的整体情况——是没有首席运营官的。我觉得不到 20%,肯定不到 30%。这一点需要了解,我不认为这是一个理所当然要设立或招聘的职位。而且我觉得这种情况在早期阶段或高速增长的公司中更为常见。顺便说一下,在某些商业模式中你也会看到这个角色。实际上,苹果就是一个很有意思的例子——Steve Jobs 专注于产品和设计,但苹果还有一个特点:要让软件和硬件协同工作,其制造过程是非常高强度的。我在 Google 做自动驾驶汽车项目时学到了这一点,你需要一个非常注重运营细节、把控制造环节、确保按时按点完成任务的人。所以我认为,一些具有深度运营属性的商业模式——比如包含制造环节的——这个角色可能会更常见。
但这并不是一个标配。我认为它在高速增长的环境中是有用的……想想一个正在实现产品市场契合的创始人兼 CEO,同时还要搭建公司、招聘所有高管——这实在太多了,因为你既在打造产品和业务,又在搭建公司组织,还要搭建人才体系、把所有人引进来。正是在这种情况下,我认为首席运营官这类角色可以给你带来杠杆效应——本质上,它是一个层级,接管其中一些职能,和你一起、或代表你来搭建它们;在某些情况下,还能带来一些经验,比如某个特定职能——像市场进入——需要被建立起来。我觉得这就是你看到这个角色出现的原因。我最近对一些人说,我有点担心——就像存在一种神话般的创始人形象一样——现在也有一种神话般的”银弹”式首席运营官招聘,每个人都觉得”我只要找到那个人就好了。”
首先,我们都是人。我并不完美。加入 Stripe 时,我确实在某些方面做得不错,但其他方面做得不够好,我也在不断提升对自身的认知。但我觉得一种风险更低的策略可能是——先引入一位业务运营负责人,或者一个类似首席运营官的角色,让他试手几个职能,看看他能否随公司和角色一起成长,然后也许你再决定让他做首席运营官。比如我提到过 Stripe 的业务运营团队,你可以招一位业务运营负责人,跟他说”嘿,搭建这个团队,作为帮助公司扩展的多面手,然后看看它能否发展成更大的角色。“或者,有些 CFO 本身就很有运营能力,他们有时也可以承担更多职责。
但我认为获得这种杠杆效应还有其他路径,也有一些方法可以降低招聘风险,因为你可能会一直找不到合适的人,对吧?我担心在很多人心中,这个角色已经变成了一种万能药,好像他们终将找到……人们会给我打电话,说”我就是需要找到你这样的人。“而我会说:“第一,我可能并不适合你的公司;第二,那其实是大量的工作,而且我觉得我们到最后也许是挺幸运的。“
如何判断一位出色的首席运营官
Lenny: 那你怎么判断一个人是否出色?
Claire Hughes Johnson: 有人对我说过一句非常明智的话。当时我在一个会议上,我和 Patrick 在一起——Patrick 是 Stripe 的联合创始人兼 CEO。有人说,我们之间关系中有”恰到好处的张力”,就说明这件事对公司是有效的。
这句话让我们俩都稍微愣了一下,但那次会议之后我们进行了一次很好的对话——必须要有相互理解和信任,Patrick 要能说”嘿,你能去做这件事吗?“然后相信我会以他所期望的质量、强度和意图去完成它。但同时也必须有一些摩擦——我可能会说”不,我不会优先做那个,我认为那对公司不重要”,或者我会给你反馈说我觉得我们这件事做得不好,或者他给我反馈说客户体验在下降——你做的所有扩展工作正在损害这个东西,对吧?所以”出色”并不意味着一切和谐美好。出色的首席运营官,是恰到好处的摩擦与意图,加上前进的势头和相互信任——这样整体才会大于部分之和。这才是你要寻找的。
Lenny: 我正想说,我和一些创始人合作过,他们有一个想法:招一个首席运营官,就能解决所有这些文化问题、人际关系问题。听起来你说的正是这个意思——这往往并不是解决那些深层问题的方案。
Claire Hughes Johnson: 对,那正是另一个问题——实际上有些创始人会相信……Lenny,我当时在被人挖,有些人……本质上,我感觉创始人是在对我说”我要把我所有不喜欢做的事情都交给你作为你的工作。“我心想,且不说我是否有资格做所有这些事——这是第一。第二,有时候那个清单会相当长,这让我很紧张。我在想,“你真的不想运营一家公司吗?这是怎么回事?“实际上,我觉得他们是在回避自己工作中需要进化和改变的部分。而我喜欢加入 Stripe 的原因之一是——人们也常常以为”我就把所有这些东西交给这个人就行了……”我很想说,我把所有这些都从 Collisons 手上、从 Billy 和 John 以及当时在公司的其他人手上接了过来,但不是这样的——我们实际上更多是协作式地一起工作,我觉得这有助于……
嗯,首先,你不会觉得那么孤立,因为你在团队中;其次,人们没有意识到实际上有更多的协作工作——至少在我愿意加入的那类公司里是这样的。
快问快答环节
Lenny: 在我们最后大约十分钟的时间里——你待会儿还有事——
Claire Hughes Johnson: 对。
Lenny: 我想我们可以做一轮快速战术问答,看看针对每个问题你会给出什么建议,也许能帮到正在为此苦恼的人。
Claire Hughes Johnson: 好的。
Lenny: 第一个问题来自 Twitter 上的 Manuel [inaudible]。他问的是,在扩展规模的过程中,保持团队对齐很有挑战。对于快速扩展、努力保持团队一致的团队,你有什么建议?
Claire Hughes Johnson: 我们刚才谈到的很多内容都适用——要有共同的、书面化的文档来阐明我们相信什么、我们如何工作,然后非常聪明地运用各种沟通方式。永远不要以为一次沟通——比如一封邮件或一次全员大会——就能触达所有人。你必须在沟通方式上非常讲究。
Lenny: 太棒了。在另一档播客中,我们讨论过领导者往往是”首席重复官”——不得不一遍又一遍地重复同样的话。
Claire Hughes Johnson: 没错。就像做营销一样,使用不同的渠道。有些人读邮件,有些人看视频,有些人参加会议。重复。
Lenny: 说得太好了,这段我们一定得剪成短视频。我之前看过你的一个访谈,你谈到 offsite 对团队凝聚力的重要性。你能谈谈为什么 offsite 对公司和团队如此重要吗?
Claire Hughes Johnson:
Offsite 的真正价值
Claire Hughes Johnson: 我认为 offsite 本质上是一个载体。核心概念是这样的:当你把人从日常事务中抽离出来,你就创造了空间,同时也留下了记忆印记。所以如果你说”今天或者接下来的两天,我们要做一件完全不同的事情,不发邮件,不开常规会议,我们要坐在一起工作,一起头脑风暴”,你基本上是在激活他们大脑中新的区域,同时也在创造一种群体体验,通常会巩固一套信念体系或一组计划。这也有助于让大家一起参与进来。我们一起制定了这个东西,如果我说”我把自己关在房间里三个小时,然后出来告诉大家这就是计划”,那是不行的。你希望作为团队一起把自己关在房间里三个小时。怎么做?所以我认为这就是它有价值的原因。从某种意义上说,就是跳出时间。你把它从日常时间中抽离出来,我找不到更好的替代方案。
内部沟通策略
Lenny: 换个话题,我从产品经理和创始人那里收到的最常见的问题之一,就是我还没有解决过的,我很想知道你的看法,就是关于如何让全公司了解整体进展。
Claire Hughes Johnson: 对。
Lenny: 你觉得什么方式能让人们了解公司各方面的动态——
Claire Hughes Johnson: 建立真正聪明的沟通实践,我认为很多公司在早期没有在这方面投入,部分原因是它看起来像是额外的事情,但它确实需要大量时间。如果你想做好沟通,就必须在内网站上投入精力,精心打理上面的内容。理想情况下,每个人登录后都能在公司内网首页看到信息。你有没有内部通讯?创始人是否会发一条消息或短视频,不管是发在 Slack 还是邮件里?有很多好用的工具。在某些方面你可以从社交媒体中学到很多,但你确实需要一套策略,需要一组人来确保它落地执行,这样才能创造稳定性和节奏感。如果我想了解 X 的信息,我就知道该去哪里找。而且我觉得如果你做得好,它还可以复制到各个团队层级,比如我们有每周简报,所有人都能看到重要新闻之类的信息。
但你需要主动去创建这些东西,因为它们会自发冒出来,然后你就会有无数个,却无法把人引导到核心信息上。这件事不能掉以轻心。我觉得需要有人真正专注于——不是内部营销,而是做好”这是重要的内容,这是你需要知道的”这类沟通。销售团队其实在这方面做得很好,因为他们不得不这样做,他们必须让销售人员及时了解产品动态和推介话术。所以,确实值得去和那些在规模化方面经验丰富的销售负责人聊聊,问问他们是怎么让所有人保持信息同步的。
Lenny: 你说到这里我想起来了,我们之前提过好几次的那位同事,她离开了 Retool,现在在一家试图解决这个问题的初创公司工作,好像叫——
Claire Hughes Johnson: 她做的很大一部分工作就是这个方向。因为这确实是一件被忽视但又至关重要的事情,大家不会自然而然地想到它。
如何开好会议
Lenny: 下一个问题,你觉得一到两件,或者三件让人们开会更高效的事情是什么?你可以说是在开高效会议方面开了一个大师课。简而言之,大家最应该改变的是什么?
Claire Hughes Johnson: 我确实在 YouTube 上有一个关于如何开好会议的视频,但我觉得最重要的一点是:开会的功课不在于发起会议。发起会议很简单。事实上,这正是问题所在——门槛太低了,应该提高门槛。你真正需要让大家知道的是:我们为什么要开会?目的是什么?这次会议的目标是什么?是做决策?还是分享信息?谁需要参加?我最喜欢说的一句话是:把隐含的东西变成显式的。太多会议隐约是关于某件事的,却不够明确。我会说,“不不不,我想知道我为什么在这里。我们是在做决策吗?谁来做决策?怎么做?” 更好的做法是,你可以说”有人不需要在这里吗?我们会事后给你发个纪要。“对吧?让事情更高效,但一定要非常明确会议的目的,并且认真审视这个会议是否重要、是否有必要。
决策与对齐
Lenny: 也许最后一个问题是关于决策的。这个播客的很多听众是产品经理,他们一方面要做很多决策、让大家对齐,另一方面却通常对任何人都没有管理权限。你对推动对齐和决策有什么建议?
Claire Hughes Johnson: 我很喜欢产品管理这个领域——责任巨大,权力极小。真是太难了。
Lenny: 多有趣的工作啊。
Claire Hughes Johnson: 大家都说”我想当产品经理”,我就想,天哪,那是科技行业最难的工作之一。
Lenny: 是的。
Claire Hughes Johnson: 不过话说回来,怎么让大家达成决策?
Lenny: 对。
Claire Hughes Johnson: 其实,这和我之前说的一模一样……我在书中提到了 Gokul 的 SPADE 框架,大家可以查一下,他有一个相关的 Coda 文档。但实际上和我说会议的那套是一样的:非常明确地说明有一个决策要做,谁来做决策,决策的标准是什么,谁需要被告知。有各种各样的模型,有 RACI、RACI 改版,有无数种决策模型。选一个就行,把它明确出来,解释清楚这就是我们要用的方式,然后带着大家走完这个流程。遵循模型去做。而且你随时可以加个备注:如果我们后续要重新审视这个决策,这是我们的做法。但我觉得太多团队陷入瘫痪,因为他们害怕——也许自己不是决策者,或者也许……我在 Stripe 的新员工入职培训中曾做过一个环节,我说,如果你不确定谁是决策者,首先,很可能就是你自己,我宁愿你以这个前提去行动,也不要犹豫不决,因为你会让整个公司慢下来。
另外,书中我还谈到了 Bezos 使用的框架:一类决策和二类决策。它是否影响重大?是否不可逆?是否并非如此?认真评估这是什么类型的决策,难度多大,然后走一套流程把它完成。别忘了最终要真正做出决策。如果你不知道谁是决策者,担心不是自己,那就直接问。别卡住。太多人卡住了,结果工作变得很痛苦,对吧?我们都在乎什么?进展、影响力、势能。如果我对大家有什么总体建议的话,那就是:成为推动正向势能的力量,这实际上会成为你职业生涯的真正助推器。
结语
Lenny: 说得太好了。也许我们可以把这句话作为这次访谈的标题。说到这里,Claire,我知道你得走了。所有听众,你们一定要买这本书。就像我开头说的,如果你喜欢我的 newsletter,这本书就是我的 newsletter,只不过是以一本关于运营的书的形式呈现。
Claire Hughes Johnson: 谢谢。《Scaling People》。
Lenny: 《Scaling People》。有没有一个网站大家可以去看,或者亚马逊的链接——
Claire Hughes Johnson:
他们可以去 press.stripe.com/scaling-people 查看。
Lenny: 太好了。
Claire Hughes Johnson: 亚马逊也有,直接在亚马逊搜索 scaling people 就行。
Lenny: 好的。
Claire Hughes Johnson: 谢谢你,Lenny,非常感谢。
Lenny: 当然。最后两个问题。一是,大家如果想提问、跟进或联系你,在哪里可以找到你?二是,除了预购这本书之外,大家还有什么方式可以帮到你?
Claire Hughes Johnson: 那肯定首先是预购这本书并给我反馈。Twitter 应该是找到我的最佳途径,我的账号是 @chughesjohnson。但说实话,我真心希望大家能以某种形式阅读这本书并与之互动,因为它的目标就是实用。我们聊过这个,Lenny——你的播客对于我的书来说,就是努力做到有用,我希望它能成为推动积极前进的正面力量。非常感谢有这个机会。
Lenny: 当然,感谢你抽出时间。
Claire Hughes Johnson: 谢谢。
Lenny: 非常感谢大家的收听。如果你觉得这期节目有价值,可以在 Apple Podcast、Spotify 或你喜欢的播客应用上订阅。也请考虑给我们评分或留下评论,这真的能帮助其他听众发现这个播客。你可以在 lennyspodcast.com 找到所有往期节目或了解更多关于节目的信息。下期再见。
术语表
| 原文 | 中文 |
|---|---|
| Amir | Amir |
| Claire Hughes Johnson | Claire Hughes Johnson |
| Conscious Business | 《Conscious Business》 |
| COO | 首席运营官 |
| DISC | DISC(性格测评工具) |
| Elad Gil | Elad Gil |
| Eli | Eli(书中使用的化名) |
| Enneagram | Enneagram(九型人格测评工具) |
| Fred Kofman | Fred Kofman |
| go-to-market | 市场进入 |
| John Collison | John Collison |
| Lenny | Lenny |
| Levels and Ladders | 职级体系 |
| Myers-Briggs | Myers-Briggs(性格测评工具) |
| offsite | offsite(团队外出活动/异地会议) |
| OKR | OKR |
| Patrick Collison | Patrick Collison |
| PMF | 产品市场契合(product-market fit 的缩写,已在正文中展开使用全称) |
| QBR | QBR(季度业务评审,Quarterly Business Review) |
| Reid Hoffman | Reid Hoffman |
| Stripe | Stripe |
| Swiss Army knife | 多面手(瑞士军刀式角色) |
| 基于假设的辅导 | 基于假设的辅导(hypothesis based coaching) |
| 左手栏 | 左手栏(续前文 Fred Kofman 的概念) |
此文档由 AI 分片翻译(translate_long_document)