The video discusses the importance of having hard conversations with founders and provides examples of such conversations. It emphasizes the need for honesty and the importance of addressing the underlying questions behind these conversations.

- The speaker discusses the importance of having open and honest conversations, both with customers and within teams.
- They emphasize the need to talk to customers directly and not rely solely on advisors.
- The speaker also talks about the challenges of having hard conversations with co-founders and employees.
- They stress the importance of learning how to disagree and communicate effectively without damaging relationships.
- The speaker encourages transparency and honesty with employees, as well as acknowledging when someone may not be the right fit for a company.
- They conclude by acknowledging that nobody is perfect and that it's important to not put anyone on a pedestal.

- One character is struggling with PTSD and addiction but doesn't want others to know
- Another character, who has overcome addiction, notices and decides to support them
- The analogy used is that the supporting character jumps down to the bottom of the well with the struggling character
- The supporting character does this because they have climbed out of the well before and know the way out
- Being a YC partner is similar, as they have made mistakes before but can guide others through them
- The idea of playing error-free ball is a lie
- The conversation ends positively.

The video emphasizes the importance of open and honest conversations, both with customers and within teams. It discusses the challenges of having difficult conversations with co-founders and employees and stresses the need for effective communication and transparency. The speaker encourages acknowledging when someone may not be the right fit for a company and emphasizes the importance of not putting anyone on a pedestal. The video also uses an analogy of supporting someone struggling with PTSD and addiction to highlight the role of a YC partner in guiding others through mistakes. Overall, the conversation ends positively.

In this video, Y Combinator partners Michael Seibel and Dalton Caldwell discuss the importance of having honest and difficult conversations with startup founders. While having hard conversations can be uncomfortable, Seibel and Caldwell argue that this transparency is essential for founders to grow and ultimately, these experiences help founders have their own hard conversations that they've been avoiding with the people around them.

Apply to Y Combinator: https://yc.link/DandM-apply
Work at a Startup: https://yc.link/DandM-jobs

Chapters (Powered by https://bit.ly/chapterme-yc) - 
00:00 - Intro
00:39 - Definition
02:35 - Being likable
03:52 - Validating decisions
06:54 - Fundraising
08:31 - Deep dives
11:37 - Co-founders
15:42 - Employees
18:37 - Nobody's perfect
19:50 - Outro

I think so much about being a YC partner is exactly that.

And the only thing that I could say is I know the way out.

This is Michael Seibel with Dalton Caldwell.

At YC we often have to have challenging conversations with founders when giving them advice.

Today we would like to talk through some of the hard conversations that founders don't want to have.

Dalton, why don't you set this up for us?

Well, look, let's start by trying to define a hard conversation.

By definition, If it's a conversation you're looking forward to having, it is not a hard conversation.

That's why it's called a hard conversation.

And so, you know, a hard conversation is when the stakes are high.

It could be you're saying something risky or you're making a point.

Maybe you're doing something that's impolite or saying something that's impolite.

Because again, think about an easy conversation.

You're just like, hey, you're great, way to go.

A hard conversation is when you're vulnerable.

You're saying something that someone in the conversation is uncomfortable.

You know, it's funny as you set that up, what's tricky being a startup advisor is that you know it's gonna help someone to have hard conversations with them, but you also know that they're not going to enjoy it.

And I think as a YC partner in the early days, I think I measured my effectiveness based on how much fun founders had talking to me.

And only after a couple of batches did I realize that doesn't really do anything.

And Then when I started having honest conversations and talking about my actual opinions about their product or about how hard they were working, the job changed.

Yeah, I mean, if you just agree with someone, it's easy to, you know, and you like mirror their body language.

Like there's all these techniques you can do to be likable where you're like, oh wow, like you're so smart.

And the problem is it's not that helpful if, it's just not that helpful.

Like, and again, if you think about us as founders or think about friends, think about friendship with people, the people that you would consider your true friends in life are the people that can say the things to you that no 1 else will.

And if you're surrounded by crowds of people that for whatever reason are unable or unwilling to tell you the truth about anything, you're having a bad time.

How are you going to learn when you're giving people inputs and their output back to you is dishonest?

Because they would just want to make sure that you feel good.

So let's talk about some of the hard conversations that we have with founders.

The founder comes to office hours with us.

It is obvious they've already made a decision.

And they want us to spend an hour validating that they've made the right decision.

Because Dalton, if we were being 1,000% honest, What would we actually just say like gluttonly?

Well, I think there's 2 ways to handle this.

The easy conversation is to take them at face value and be like, oh, wow, seems like you've thought about this really well.

Without the information to even verify that.

And what I think the hard thing is, is not even disagreeing with it.

It's to say, it's the question behind the question, which is, hey, it seems like you've already made a decision.

Like, what's the question behind the question?

Is it that someone else, is it that your co-founder disagrees with you and what you're trying to do is bring my opinion into it to prove that you're right?

Is it that someone else disagrees with, like, like there's always a real question hiding behind the scenes.

When I bring this up, they're like, yeah, there is a question behind the question.

I think if you really want to understand office hours in a nutshell, 60 to 80% of the time, a founder will go into office hours with 1 question and we won't even end up talking about that thing.

This comes up a lot with like people talking about applying to YC.

Like people are always like think it's really important.

Michael, I have some really important questions I want to ask you about applying to YC.

And he talks to them and it's just like, Should I apply to like, like there's no,

Should I report my revenue monthly or quarterly?

And so again, I get where they're coming from and what they want, what they're really, the question behind the question I think is I feel insecure and I want to talk to you, Dalton and Michael, about this so that you give me validation that I should apply.

And so that's the actual question behind the question, not, hey, I have this really complicated question about the application that's, I don't know.

We're talking to an early stage company And it's becoming obvious that they're not going to be able to raise the amount of money that they want to raise.

And they're not going to be able to execute this magical explosion of spending that they want to execute, that they've convinced themselves is what's required to get product market fit.

You know, that's a really tough 1 because you want people to be optimistic as we've spoken about before.

And it's hard to, you never want to be short on someone's startup.

And so what I would usually say on this 1 is think about what a great life of philosophy it is to set your expectations low and prepare for the worst.

And then if you get surprised, You get surprised on the upside, not the downside.

And so the key in this hard conversation is not to debate someone that their plan is bad.

Keep the optimism, you know, but isn't it better to sort of have a plan for the worst and not be surprised on the downside.

And if you're surprised on the upside, fantastic.

And again, people don't want to hear this.

Do you want to bring the parachute with you or not?

Like I'm not trying to be grim by saying bring a parachute, but wouldn't you want to bring the parachute?

What's the downside of bringing the parachute?

All right, so here's another 1 that comes up a lot.

Dalton, I'd like to spend 2 hours really going deep on this problem, but our office hours don't go that long.

How do you deal with the, I want to do a deep dive?

This is another 1 of those question behind the questions.

And again, it can be different things depending on the people.

I think sometimes what's going on is you're an idiot and I don't have confidence you can give me advice unless I spend 2 hours showing you a slide deck so I can explain everything to you.

Sometimes it's not really about the meeting, I just want a lot of face time so we can build a relationship or whatever.

There's usually, when someone asks that, there's something else going on.

And again, It's usually the first 1 for me where they think we don't understand.

But like, instead of them directly saying, I am concerned that you do not sufficiently understand our business.

And so I wanna make sure you do X, Y, and Z.

Okay, that's a hard conversation, but then I'm like, okay, I know where you're coming from.

But some weird, like, can we meet for 3 hours?

I want to know the question behind the question, you know?

Well, and what's so funny is if they just said, I don't think you're smart about this particular thing, we would get to the meeting.

Now, I think there's a couple others that I see.

1 is this assumption that we are like God-like advisors with complete understandings of every user base and every problem in the world.

And like, they can kind of like shortcut talking to users if they just spend enough time talking to us.

And so that 1 is just like folks, like so often in this 1, I'm just like, you're having a conversation with me that you should have with your customers.

I think the other 1, which I really try to push back on is, I'm lazy and I didn't come up with the agenda.

I wanna like roam my random thoughts and over the course of 2 hours, we will have 20 minutes of productivity, but I don't wanna organize my thoughts and I want you to accommodate that.

And for that 1, I'm always just like, that's like, you're not training yourself for success here.

Like if your competitors can get 20 minutes of input, 20 minutes of output, they will do way better than 2 hours of input, 20 minutes of output.

Just that seems to kick people into gear.

I think we can shift gears to a couple of other contexts for hard conversations.

Let's talk about hard conversations, not with us, but with co-founders.

The thing I want to set up here is The classic thing is people become co-founders.

They've never once had a disagreement or hard conversation.

And then the first time they have a hard conversation,

This is why we like teams who know each other for at least a little bit and have some kind of work or personal relationship.

Because I always say that when you have some kind of non, if you have some kind of base relationship that you might want to maintain, even if this startup doesn't work, you won't say that thing.

Or you'll think really hard before saying that thing that will like shatter the relationship.

But when you're like, oh, the only reason why I'm even talking to you is because of this startup, and now I'm convinced that our startup's fucked, which by the way, you will be convinced your startup's fucked just continuously.

Man, you can't, you know, there are things you can't unsay.

And Wow, sometimes the original sin was like, you shouldn't have started the company with this person.

But like, let's say you are doing a company with your co founder, and it's just really frustrating.

What's the advice you give the founders on how to kind of process them?

I think it's like, you have to learn how to fight, and maybe fight's the wrong word, how to disagree.

It's like, you have to learn how to fight and maybe fight's the wrong word, how to disagree.

It's like you have to learn how to pull your punches and have a disagreement that's a real disagreement and actually release the pressure of the disagreement in a way that doesn't cross the line so that the relationship is irreparably harmed.

And if you've never been through a major disagreement with someone or had the skills for both of you to have a fundamental disagreement and talk it through yet not blow the relationship up?

And again, this is a skill like any other skill, man.

You know, it's funny, because the analogy that I'm thinking in my head is that like, you know, it's a pressure release valve and you don't want to just rip it open.

But if you don't release any pressure, you also have-

If you let the pressure just build, build, build by only having superficial conversations for years, 1 day someone will snap.

And on the flip side, if you just like leave it open all the time and you fight constantly That ain't gonna work either.

No, it's sort of like the happy medium thing.

I Think the biggest thing that I had to learn and and Amy our former batch director used to talk about this a lot, is this concept that like, people will deal with conflict differently.

I love to engage and like lean in and talk through conflict, but it's just as likely the person I'm working with wants to avoid conflict or wants to take time to process conflict or doesn't process conflict through conversation.

I have to understand who I'm talking to and realize that when I have to kind of take a step back, even though I'm unsatisfied, because I'm creating more of a problem by like continuing to push forward.

And I think that this is 1 of those situations where You can't blame the other person for like not acting correctly.

Like you have to take responsibility because you can both blame each other into an explosion all day long, right?

So next, what about what about employees?

Again, the dynamic might be a little bit different, but if you're only ever having easy, superficial conversations with people, it's cool until it's not.

And sometimes the best way to work with folks at your company or whatever, colleagues, employees, whatever we want to call them, is to find the right way to have some of these hard conversations.

And you know what they are, you know, You're probably, I'm sure someone watching this is like, yeah, I can think of a few hard, I can think of some things I would say if I weren't afraid of the consequences.

You know, like there's a right way and a wrong way to do it.

We're not saying go blow people up, but If you're just avoiding hard conversations, no 1 wins.

And most importantly, the employee doesn't win.

Because the employee probably knows something's wrong.

And if you're the boss, they probably expect you to be the 1 kind of addressing it.

You know, 1 thing that I say about employees a lot, and I want to limit this to like startups and startup employees, like first, like Allow the idea in your head that you might have picked the wrong person, that the person isn't the right fit.

Like, like it's like, even if you did your best and interviewing and they're really good and da da da, like allow in your head the idea that like that might not be the right fit and like this person might be able to do 10x better work somewhere else.

That would make their life better just as much as it would make your life better.

Allow for that because sometimes people feel like they have to solve unsolvable problems.

Then the second thing I think about with like good startup employees is they want honesty like they good startup employees kind of understand this is a really hard task and that like the likelihood of being successful is really Low And they want to be in the know, they want transparency, they wanna know how the company's doing, and they wanna know how they can do 10x better to impact the outcome of the company.

That's why you join a startup, because you want an early stage startup, because you wanna impact the outcome of the company.

I've been often surprised at sharing bad news, like, oh, we only have 2 months of runway.

But for great startup employees, they're like, all right, how the fuck are we going to fix this?

I mean, if we're all in the trenches together, maybe we can make something happen.

But like, it's really bad when like, you know your startup's in the trenches and your like, employees are like clueless.

Well, I thought everything was going fine.

I think that to our credit, you and I say this a lot.

If we were doing office hours with ourselves, what would we say?

And yeah, man, I think sometimes we dodge hard conversations.

Like, we're not saying to be vulnerable here.

We're not saying we always get this right 100% of the time.

In fact, I might argue in many times, the first conversations we have are wrong.

I think the only thing that we do well is we continuously ask ourselves, are we lying to ourselves?

And sometimes we assume that the initial salvo of questions are complete bullshit ourselves.

I guess what I'm trying to say is no one's perfect.

And that should be freeing and empowering and make you feel optimistic and not bad.

You know, to close out, this reminds me of this like scene in the West wing where 1 of the characters has a drug problem, it's that's pretty bad.

Another character is going through PTSD and is really struggling but doesn't want anyone to know.

And this character is like a drug addict that like cleaned up and so on and so forth and is noticing the first character is struggling.

You know, the way that kind of story goes is that other people who don't understand how much pain the person's in will say, oh, you should go see a psychiatrist, or you should go get a prescription.

Like, they'll do these superficial things.

And so he actually, the analogy is he jumps down to the bottom of the well with them.

It's like, I'm at the bottom of the well struggling, and then my friend jumps down with me.

And the thing that they say at the end is that like, well, I'm jumping down with you because I've climbed out of this well before, and I know the way out.

And I think so much about being a YC partner is like, is exactly that.

Like I've made all these mistakes before.

And The only thing that I could say is I know the way out.

opposed to like, oh, we play error-free ball, which is obviously a lie.


Speaker 0: I think so much about being a YC partner is exactly that. I've made all these mistakes before.

Speaker 1: And I'll probably make them again. And I'll probably make them again. And the only thing that I could say is I know the way out.

Speaker 0: This is Michael Seibel with Dalton Caldwell. At YC we often have to have challenging conversations with founders when giving them advice. Today we would like to talk through some of the hard conversations that founders don't want to have. Dalton, why don't you set this up for us?

Speaker 1: Well, look, let's start by trying to define a hard conversation. By definition, If it's a conversation you're looking forward to having, it is not a hard conversation. A hard conversation sucks. That's why it's called a hard conversation. You don't want to have them.

They're bad. Right? Or they don't feel good. They don't feel good. They don't feel good.

You dread the hard conversations. And so, you know, a hard conversation is when the stakes are high. Like it could go bad. It could go off the rails. It could be you're saying something risky or you're making a point.

Maybe you're doing something that's impolite or saying something that's impolite. Because again, think about an easy conversation. Easy conversation is superficial. You just agree with someone. You're just like, hey, you're great, way to go.

That's an easy conversation, right? Yes. Hard conversation is not that. A hard conversation is when you're vulnerable. You're putting yourself out there.

You're saying something that someone in the conversation is uncomfortable.

Speaker 0: You know, it's funny as you set that up, what's tricky being a startup advisor is that you know it's gonna help someone to have hard conversations with them, but you also know that they're not going to enjoy it. And I think as a YC partner in the early days, I think I measured my effectiveness based on how much fun founders had talking to me. And only after a couple of batches did I realize that doesn't really do anything. And Then when I started having honest conversations and talking about my actual opinions about their product or about how hard they were working, the job changed. Did you experience that?

Speaker 1: Yeah, I mean, if you just agree with someone, it's easy to, you know, and you like mirror their body language. Like there's all these techniques you can do to be likable where you're like, oh wow, like you're so smart. Everything you say is correct. Ha ha ha, your jokes are funny. You know, you can do this stuff.

And the problem is it's not that helpful if, it's just not that helpful. Like, and again, if you think about us as founders or think about friends, think about friendship with people, the people that you would consider your true friends in life are the people that can say the things to you that no 1 else will.

Speaker 0: Yes.

Speaker 1: And if you're surrounded by crowds of people that for whatever reason are unable or unwilling to tell you the truth about anything, you're having a bad time.

Speaker 0: 1, how are you gonna learn, right? How are you going to learn when you're giving people inputs and their output back to you is dishonest? Because they would just want to make sure that you feel good. So let's talk about some of the hard conversations that we have with founders. Let's take an easy 1.

I'll give you an easy first example. The founder comes to office hours with us. They have already made a decision. It is obvious they've already made a decision. And they want us to spend an hour validating that they've made the right decision.

That's kind of a hard conversation. Because Dalton, if we were being 1,000% honest, What would we actually just say like gluttonly?

Speaker 1: Well, I think there's 2 ways to handle this. There's the dishonest way. The easy conversation is to take them at face value and be like, oh, wow, seems like you've thought about this really well. I see no errors in your logic. You're a genius.

You did it again.

Speaker 0: Exactly. Yeah. Without the information to even verify that. Like with no actual facts

Speaker 1: to verify. Wow. What an amazing strategy. This is just A plus work. And then, then there's the hard thing.

And what I think the hard thing is, is not even disagreeing with it. It's to say, it's the question behind the question, which is, hey, it seems like you've already made a decision. Cool. Why are we talking about this?

Speaker 0: Yes, why are we here right now?

Speaker 1: Like, what's the question behind the question? Is it that someone else, is it that your co-founder disagrees with you and what you're trying to do is bring my opinion into it to prove that you're right?

Speaker 0: Yes.

Speaker 1: Is it that someone else disagrees with, like, like there's always a real question hiding behind the scenes. And man, people, it's always there. When I bring this up, they're like, yeah, there is a question behind the question. Yes. By the way, isn't

Speaker 0: this such a common theme? I think if you really want to understand office hours in a nutshell, 60 to 80% of the time, a founder will go into office hours with 1 question and we won't even end up talking about that thing. That's not the actual question.

Speaker 1: That's not the actual. This comes up a lot with like people talking about applying to YC. Like people are always like think it's really important. Michael, I have some really important questions I want to ask you about applying to YC. And he talks to them and it's just like, Should I apply to like, like there's no,

Speaker 0: there's no there, there.

Speaker 1: It's a no op. There's nothing. There is

Speaker 0: no question. Should I report my revenue monthly or quarterly?

Speaker 1: It's like, like who, like just. Yeah. And so again, I get where they're coming from and what they want, what they're really, the question behind the question I think is I feel insecure and I want to talk to you, Dalton and Michael, about this so that you give me validation that I should apply. Great. And so that's the actual question behind the question, not, hey, I have this really complicated question about the application that's, I don't know.

Speaker 0: All right, let's stick with hard ones. We're talking to an early stage company And it's becoming obvious that they're not going to be able to raise the amount of money that they want to raise. And they're not going to be able to execute this magical explosion of spending that they want to execute, that they've convinced themselves is what's required to get product market fit. What do you do in those situations?

Speaker 1: You know, that's a really tough 1 because you want people to be optimistic as we've spoken about before. And it's hard to, you never want to be short on someone's startup. And so what I would usually say on this 1 is think about what a great life of philosophy it is to set your expectations low and prepare for the worst. And then if you get surprised, You get surprised on the upside, not the downside. And so the key in this hard conversation is not to debate someone that their plan is bad.

Keep the optimism, you know, but isn't it better to sort of have a plan for the worst and not be surprised on the downside. And if you're surprised on the upside, fantastic. Right, man? And again, people don't want to hear this. This is a hard conversation to have.

It's like going up in the airplane. Do you want to bring the parachute with you or not? Like I'm not trying to be grim by saying bring a parachute, but wouldn't you want to bring the parachute?

Speaker 0: Yeah, if

Speaker 1: you had the choice. What's the downside of bringing the parachute?

Speaker 0: You don't use it? It's fine. All right, so here's another 1 that comes up a lot. Dalton, I'd like to spend 2 hours really going deep on this problem, but our office hours don't go that long. How do you deal with the, I want to do a deep dive?

Speaker 1: Yes. This is another 1 of those question behind the questions. And again, it can be different things depending on the people. I think sometimes what's going on is you're an idiot and I don't have confidence you can give me advice unless I spend 2 hours showing you a slide deck so I can explain everything to you. Sometimes it's not really about the meeting, I just want a lot of face time so we can build a relationship or whatever.

And so this is-

Speaker 0: Bond and stuff, yes.

Speaker 1: Yeah, okay, that's fine. But you see what I'm saying, man? There's usually, when someone asks that, there's something else going on. And again, It's usually the first 1 for me where they think we don't understand. Again, maybe we don't, I don't know.

But like, instead of them directly saying, I am concerned that you do not sufficiently understand our business. And so I wanna make sure you do X, Y, and Z. Okay, that's a hard conversation, but then I'm like, okay, I know where you're coming from. All right, I hear you. But some weird, like, can we meet for 3 hours?

I'm always like, why? I want to know the question behind the question, you know?

Speaker 0: Well, and what's so funny is if they just said, I don't think you're smart about this particular thing, we would get to the meeting.

Speaker 1: Yeah, okay.

Speaker 0: We would get to the meeting. Now, I think there's a couple others that I see. 1 is this assumption that we are like God-like advisors with complete understandings of every user base and every problem in the world. And like, they can kind of like shortcut talking to users if they just spend enough time talking to us. And so that 1 is just like folks, like so often in this 1, I'm just like, you're having a conversation with me that you should have with your customers.

Like, talk to them. Like, I don't use your product. Talk to the people who do. I think the other 1, which I really try to push back on is, I'm lazy and I didn't come up with the agenda. I wanna like roam my random thoughts and over the course of 2 hours, we will have 20 minutes of productivity, but I don't wanna organize my thoughts and I want you to accommodate that.

And for that 1, I'm always just like, that's like, you're not training yourself for success here. Like, you expect more from yourself. Like if your competitors can get 20 minutes of input, 20 minutes of output, they will do way better than 2 hours of input, 20 minutes of output. Just that seems to kick people into gear. What's another 1 that you're excited by?

Speaker 1: I think we can shift gears to a couple of other contexts for hard conversations. Let's talk about hard conversations, not with us, but with co-founders. The thing I want to set up here is The classic thing is people become co-founders. Yes. They've never once had a disagreement or hard conversation.

It's all been superficial. We're best friends. We work together. It's all wonderful. And then the first time they have a hard conversation,

Speaker 0: That's it. Explosion.

Speaker 1: You've seen this, man. Like what's going on here? Like,

Speaker 0: well, first things first, right? This is why we like teams who know each other for at least a little bit and have some kind of work or personal relationship. Because I always say that when you have some kind of non, if you have some kind of base relationship that you might want to maintain, even if this startup doesn't work, you won't say that thing. Or you'll think really hard before saying that thing that will like shatter the relationship. But when you're like, oh, the only reason why I'm even talking to you is because of this startup, and now I'm convinced that our startup's fucked, which by the way, you will be convinced your startup's fucked just continuously.

That's like a normal feeling. And then you're like, well, fuck it. Man, you can't, you know, there are things you can't unsay. And Wow, sometimes the original sin was like, you shouldn't have started the company with this person. But like, let's say you are doing a company with your co founder, and it's just really frustrating.

What's the advice you give the founders on how to kind of process them?

Speaker 1: I think it's like, you have to learn how to fight, and maybe fight's the wrong word, how to disagree. It's like, you have to learn how to fight and maybe fight's the wrong word, how to disagree. It's like you have to learn how to pull your punches and have a disagreement that's a real disagreement and actually release the pressure of the disagreement in a way that doesn't cross the line so that the relationship is irreparably harmed. And it's a skill you have to learn. And if you've never been through a major disagreement with someone or had the skills for both of you to have a fundamental disagreement and talk it through yet not blow the relationship up?

Yeah. And again, this is a skill like any other skill, man.

Speaker 0: It's a skill. You know, it's funny, because the analogy that I'm thinking in my head is that like, you know, it's a pressure release valve and you don't want to just rip it open. Yeah. But if you don't release any pressure, you also have-

Speaker 1: It builds up and blows up. Either way it blows up.

Speaker 0: Either way it

Speaker 1: blows up. If you let the pressure just build, build, build by only having superficial conversations for years, 1 day someone will snap. Boom. And on the flip side, if you just like leave it open all the time and you fight constantly That ain't gonna work either. No, it's sort of like the happy medium thing.

Speaker 0: I Think the biggest thing that I had to learn and and Amy our former batch director used to talk about this a lot, is this concept that like, people will deal with conflict differently. I love to engage and like lean in and talk through conflict, but it's just as likely the person I'm working with wants to avoid conflict or wants to take time to process conflict or doesn't process conflict through conversation. And like, I have to look at those cues. I have to understand who I'm talking to and realize that when I have to kind of take a step back, even though I'm unsatisfied, because I'm creating more of a problem by like continuing to push forward. And I think that this is 1 of those situations where You can't blame the other person for like not acting correctly.

Like you have to take responsibility because you can both blame each other into an explosion all day long, right? Like that's easy. So next, what about what about employees? What do you think there?

Speaker 1: I think it's the same sort of situation. Again, the dynamic might be a little bit different, but if you're only ever having easy, superficial conversations with people, it's cool until it's not. And sometimes the best way to work with folks at your company or whatever, colleagues, employees, whatever we want to call them, is to find the right way to have some of these hard conversations. And you know what they are, you know, You're probably, I'm sure someone watching this is like, yeah, I can think of a few hard, I can think of some things I would say if I weren't afraid of the consequences. You know, like there's a right way and a wrong way to do it.

We're not saying go blow people up, but If you're just avoiding hard conversations, no 1 wins.

Speaker 0: No. And most importantly, the employee doesn't win. Because the employee probably knows something's wrong. And if you're the boss, they probably expect you to be the 1 kind of addressing it. You know, 1 thing that I say about employees a lot, and I want to limit this to like startups and startup employees, like first, like Allow the idea in your head that you might have picked the wrong person, that the person isn't the right fit.

Like, like it's like, even if you did your best and interviewing and they're really good and da da da, like allow in your head the idea that like that might not be the right fit and like this person might be able to do 10x better work somewhere else. That would make their life better just as much as it would make your life better. Allow for that because sometimes people feel like they have to solve unsolvable problems. Then the second thing I think about with like good startup employees is they want honesty like they good startup employees kind of understand this is a really hard task and that like the likelihood of being successful is really Low And they want to be in the know, they want transparency, they wanna know how the company's doing, and they wanna know how they can do 10x better to impact the outcome of the company. That's why you join a startup, because you want an early stage startup, because you wanna impact the outcome of the company.

I've been often surprised at sharing bad news, like, oh, we only have 2 months of runway. I would think would be demotivating. But for great startup employees, they're like, all right, how the fuck are we going to fix this? And then you can get juice from them. You're like, well, all right.

I mean, if we're all in the trenches together, maybe we can make something happen. But like, it's really bad when like, you know your startup's in the trenches and your like, employees are like clueless. Well, I thought everything was going fine. We raised a bunch of money. You never told me anything was wrong.

And you're like, ugh.

Speaker 1: I think that to our credit, you and I say this a lot. If we were doing office hours with ourselves, what would we say? And yeah, man, I think sometimes we dodge hard conversations. Like, we're not saying to be vulnerable here. We're not saying we always get this right 100% of the time.

Speaker 0: In fact, I might argue in many times, the first conversations we have are wrong. I think the only thing that we do well is we continuously ask ourselves, are we lying to ourselves? Or is there like, what did you say? What's the deeper question?

Speaker 1: What's the question behind the question? What's the question behind the question?

Speaker 0: What's the question behind the question? I think we are good at asking that. And sometimes we assume that the initial salvo of questions are complete bullshit ourselves. Like, within YC itself.

Speaker 1: And I think that's life, man. I guess what I'm trying to say is no one's perfect. Don't put anyone on a pedestal. It doesn't matter who they are. They have their own shit.

And that should be freeing and empowering and make you feel optimistic and not bad. Right? Isn't that the right takeaway here?

Speaker 0: That's the right takeaway. You know, to close out, this reminds me of this like scene in the West wing where 1 of the characters has a drug problem, it's that's pretty bad. Another character is going through PTSD and is really struggling but doesn't want anyone to know. And this character is like a drug addict that like cleaned up and so on and so forth and is noticing the first character is struggling. You know, the way that kind of story goes is that other people who don't understand how much pain the person's in will say, oh, you should go see a psychiatrist, or you should go get a prescription.

Like, they'll do these superficial things. But this character knows. And so he actually, the analogy is he jumps down to the bottom of the well with them. It's like, I'm at the bottom of the well struggling, and then my friend jumps down with me. And the thing that they say at the end is that like, well, I'm jumping down with you because I've climbed out of this well before, and I know the way out.

And I think so much about being a YC partner is like, is exactly that. Like I've made all these mistakes before.

Speaker 1: And I'll probably make them again. And I'll probably make them again. And The only thing that I could say is I know the way out. As

Speaker 0: opposed to like, oh, we play error-free ball, which is obviously a lie.

Speaker 1: All right, man, great chat. Thanks.

See all Y Combinator transcripts on Youtube

The Hard Conversations Founders Don't Want to Have