Building a team is a huge milestone for a founder.

You have gone from doing everything yourself to hiring people, figuring out roles, onboarding new employees, and handing over work you once owned entirely. Those are significant accomplishments, especially when you have built the business from the ground up.

But eventually, most founders discover that hiring a team is only the beginning.

The harder question is: How do you actually lead these people well?

How do you create a culture where people know what is expected of them, take ownership of their work, feel valued, communicate honestly, and actually enjoy being part of the team?

The good news is that you do not need another degree in management to figure this out. You do, however, need to get better at one thing that is often overlooked when we talk about leadership:

Conversations.

Culture is built in everyday conversations. No system, strategy, process, or company handbook can compensate for a leader who avoids the conversations their team needs.

I learned this the hard way.

When I was 25, I was put in charge of a team. I was young, passionate, knowledgeable about the industry, and full of ideas about where I wanted the team and organization to go.

There was just one problem: I had never actually led a team before.

The people who hired me believed my other strengths would make up for the lack of management experience. Surely I was a natural leader. Surely I would figure it out.

Eventually, I did figure it out. But not before plenty of mistakes, sleepless nights, missed opportunities, and some relationships that suffered unnecessarily.

Looking back, I can see that there were tools I wish someone had given me from the beginning. And most of them came down to knowing which conversations needed to happen, and how to have them well.

Over the years, these are the seven conversations I have found to be essential for building a healthy, high-functioning team.

And underneath all seven is a simple framework I use in my own leadership work: Curiosity, Clarity, Courage, and Care.

We need curiosity because there is always something we do not know. We need clarity so people leave a conversation understanding more than they did before. We need courage because some conversations are uncomfortable by nature. And we need care because the person in front of us matters more than the outcome we are trying to accomplish.

With those four things as our posture, let’s look at the seven conversations.

1. The Upward Conversation: “How Am I Doing?”

The first conversation is one that many founders skip because it requires us to go first.

The upward conversation is the intentional creation of a pathway for your team to give you feedback.

This matters because you cannot reasonably expect your team to be open with you about mistakes, struggles, concerns, or difficult situations if you have never demonstrated that openness yourself.

Before you can expect your team to receive feedback well, you need to show them what receiving feedback looks like.

That means asking for it.

And not asking as a performance.

Not asking, “Is there anything I could be doing better?” while secretly hoping they say, “Nope! You’re perfect!”

You have to actually mean it.

When you regularly ask your team how you are doing and demonstrate that you are willing to hear the answer—even when the answer is uncomfortable—you begin to create a culture where honesty becomes normal.

You are communicating, We are all still learning here. Feedback is not something that happens because someone is in trouble. Feedback is simply part of how we work.

The key is to make the question specific. “How am I doing?” is so broad that it is easy to answer with a polite, “Great!”

Instead, try asking:

“What’s something I could start or stop doing that would make working here easier or more enjoyable for you?”

Or:

“Can you give me some feedback on how you thought that went?”

Or, after a difficult conversation:

“Now that you’ve had some time to think about it, is there anything else you want to share with me?”

Then comes the hardest part: accept the answer without immediately defending yourself.

You can explain later if necessary. But your first response should simply be, “Thank you for telling me that.”

Listen. Reflect back what you heard. Let the person know what you plan to do with the feedback.

That final step matters because people need to know that their honesty actually went somewhere.

Asking for feedback is not a sign of weak leadership.

It is leadership.

And when your team sees you practicing that kind of humility, they are much more likely to extend it to one another.

2. The Delegation Conversation: “Here’s What Done Looks Like”

Delegation is one of the most misunderstood parts of leadership.

Many founders believe they are delegating when they assign someone a task and give them a deadline.

But delegation is not simply assigning a task.

Delegation is transferring ownership.

And transferring ownership requires a conversation.

A lot of delegated work comes back differently than the founder expected, and the founder concludes that the employee is not capable.

Often, that isn’t actually the problem.

The problem is that the founder never clearly communicated the destination.

Imagine telling someone to get in the car and “drive west,” then becoming frustrated when they end up in San Diego instead of Bend.

They weren’t necessarily a bad driver.

You simply never told them where they were going.

Good delegation requires clarity on the front end.

What does success actually look like? What does “done” mean? What decisions can this person make without you? What decisions require your approval? Are you collaborating on this, or is this fully theirs?

Those things need to be explicit.

You also need to establish when you will check back in.

A check-in is not automatically micromanagement. In fact, a clearly defined check-in can provide a safety net for both the leader and the employee. It gives the employee a place to bring questions and gives the leader a defined opportunity to assess progress without hovering every day.

Then comes the part many founders struggle with most:

Step back.

Once you have transferred ownership, let the person own it.

If you continue checking in, changing direction, or inserting yourself into every decision, you have effectively taken the ownership back.

Try language like:

“Here’s what I want this to look like when it’s done.”

Or:

“You don’t need to check in with me on those decisions along the way. I trust your judgment there.”

Or:

“Let’s reconnect Thursday. Come ready to tell me where you got stuck.”

Your team cannot read your mind.

Give them the picture, make the ownership clear, establish the safety net, and then get out of the way.

3. The Empowerment Conversation: “What Do You Think?”

Delegation and empowerment are related, but they are not the same thing.

Delegation is about transferring ownership of an outcome.

Empowerment is about changing the ongoing dynamic between you and your team.

If your team is constantly coming to you with every question, every decision, and every tiny problem, you can eventually become the bottleneck for almost everything.

At that point, the problem is bigger than any individual task.

It is a leadership pattern.

The goal of empowerment is to teach people to think for themselves so that you are no longer the only person holding the keys to every door in the business.

One of the simplest ways to start is to answer questions with questions.

When someone comes to you and asks, “What should I do?” try:

“What do you think?”

Or:

“What are you going to do next?”

Those questions force people to engage their own judgment before defaulting to yours.

This is especially important when someone makes a mistake.

Your instinct may be to take the work back because it feels faster and safer. But if you continually rescue people from the consequences of their decisions, they never develop the confidence and judgment you need them to have.

Instead, talk through what happened. Ask what they would do differently. Help them think through the situation.

Then send them back in.

Think about teaching someone to drive. Eventually, you want them to be able to drive safely when you are not sitting in the passenger seat. That means they need opportunities to develop their instincts and judgment while you are still there to coach them.

That is empowerment.

You are not abandoning your team.

You are preparing them to succeed when you aren’t in the room.

And if you have created a dependent team, that does not mean you have a bad team.

It means there is a leadership pattern you can change.

4. The Feedback Conversation: “Here’s What I Observed”

This is the conversation I get asked about most often, and for good reason.

Giving constructive feedback is hard.

Especially if you are a people pleaser.

Many of us have unconsciously convinced ourselves that feedback threatens relationships. We worry that telling someone the truth will make them angry, hurt their feelings, or damage the trust between us.

But avoiding feedback is often much more damaging to a relationship than giving it.

Think about your closest friendships. You probably want a friend who will tell you when you have food in your teeth or your pants are unzipped.

A friend who is too uncomfortable to tell you is not necessarily caring for you. They may simply be protecting themselves from the discomfort of telling you.

The same is true at work.

Your team deserves a leader who cares enough to tell them the truth.

This is why I use the CLEAR feedback framework:

C — Context: State where and when you observed the behavior.

L — Layout the behavior: Describe exactly what you observed, without adding assumptions about intent.

E — Effect: Explain the impact the behavior had.

A — Ask: Get their perspective and find out what you might be missing.

R — Resolve: Agree on what happens next.

For example, constructive feedback might sound like:

“Yesterday during the team meeting, you interrupted Jess multiple times while she was giving her update. I noticed that she seemed uncomfortable, and it became distracting for the rest of the team. What was going on for you during her presentation?”

Notice what is missing.

There is no accusation about motive. There is no “you always do this.” There is no emotional monologue about how disappointed you are.

There is simply an observation, an impact, and a question.

The same framework works for positive feedback:

“John, the email you sent to the client yesterday was excellent. You were clear about the timeline delay, kind and apologetic, and you immediately offered to jump on a call with them. The way you handled it really demonstrated our values. Tell me about your thought process.”

Good feedback is not a sandwich.

It does not require you to hide the difficult thing between two compliments.

It requires clarity and care.

And when those two things are present, feedback becomes one of the most powerful tools you have for developing your people.

5. The One-on-One Conversation: “What’s Really Going On?”

Most leaders have one-on-one meetings on their calendars.

The problem is that many of those meetings have become status updates.

A real one-on-one should be different.

It should be a coaching conversation, not a work session.

One leader I worked with had become incredibly burned out by her one-on-ones. She felt like they were a waste of time, but even more than that, she felt burdened by the responsibility to solve every problem her employees brought to her.

The problem was not necessarily the one-on-one.

It was her understanding of her role within it.

Her job was not to be the fixer.

Her job was to be the coach.

A useful one-on-one can begin with a simple open-ended question:

“What’s most on your mind this week?”

Then let them talk.

When they finish, ask:

“And what else?”

Once they have gotten everything out, help them focus:

“What’s the real challenge for you here?”

That question is particularly powerful because it shifts the conversation toward what is actually within their control.

Then ask:

“If this worked out exactly as you hoped, what would that look like?”

And eventually:

“What do you think you should do next?”

Finally:

“How can I support you?”

You may need to keep these questions written down the first few times you try this.

That’s okay.

Over time, the conversation becomes natural.

And something interesting begins to happen: your employees start finding answers they did not realize they were capable of finding.

Sometimes they will even come up with answers you would never have thought of.

That is a win for everyone.

6. The Team Meeting Conversation: “How Are We Doing Together?”

If your team is sitting in a meeting thinking, This could have been an email, the meeting probably is not doing its job.

Team meetings should not primarily be information-transfer meetings.

They should be opportunities for connection, alignment, and culture-building.

As a founder, you may naturally feel connected to the business because you are constantly interacting with the mission, the decisions, the customers, and the bigger picture.

Your team does not necessarily have that same experience.

They may be completing their individual responsibilities from their own little corner of the organization without ever developing a sense that they are part of something bigger.

A founder friend of mine described this realization perfectly: he said he had not actually built a team. He had built a bunch of people, put them in silos, and asked them to accomplish individual tasks.

That distinction matters.

Your team needs opportunities to connect to the mission, to one another, and to the work they are contributing.

This is why I use a simple structure called BANG for the first ten minutes of a team meeting.

B — Bravos: Celebrate specific wins publicly.

A — Alignment: Reconnect the team to the “why.” Share client feedback, revisit a team value, or highlight something that demonstrates what you are building together.

N — Numbers: Review the metrics that matter.

G — Glue: Make space for personal updates and connection.

That last piece may feel unnecessary to some founders.

It isn’t.

People are humans before they are employees. The personal details matter. Knowing that someone’s child had a big game or that they are preparing for a move or celebrating something important helps people relate to one another as actual human beings.

That is how teams become teams.

From there, build the rest of the agenda around what the team actually needs to accomplish. Ask yourself before the meeting: What do I want my team to know, feel, or understand when they walk out of this room?

Invite disagreement.

Ask:

“What’s something we’re doing that could be better?”

You are not promising to implement every suggestion. You are communicating that honesty is welcome.

And save detailed project updates and individual problem-solving for another channel. Those things may belong in an email, an ad hoc meeting, or a separate conversation.

The team meeting has a different job.

It is where you build the glue.

7. The Hard Conversation: “We Need to Talk About This”

And finally, we arrive at the conversation most leaders would prefer to avoid.

The hard conversation.

Maybe someone has received feedback multiple times and nothing has changed. Maybe two employees are in ongoing conflict. Maybe someone’s behavior is damaging the culture. Or perhaps you have reached the point where the right decision is to separate from an employee.

Whatever the specific situation, there is usually a story we have created in our heads about how terrible the conversation is going to be.

And that story is often worse than the conversation itself.

We tell ourselves we are avoiding the conversation to protect the relationship, the peace, or the other person.

But if we are honest, sometimes we are avoiding it to protect ourselves.

We don’t want to feel uncomfortable.

We don’t want to be disliked.

We don’t want to look like the bad guy.

We don’t want to deal with the emotional aftermath.

The problem is that avoidance has a cost.

Silence allows problems to deepen.

Unclear communication creates confusion.

And trying to soften bad news until it sounds like good news often leaves people feeling even more frustrated.

Think about receiving difficult news. Most of us don’t actually need our leaders to make the news feel good.

We need them to make it clear.

There is a profound difference between kindness and avoidance.

You can care deeply about someone and still tell them the truth.

The hard conversation begins with curiosity. Before you become direct, check your own story.

What are you assuming about this person or this situation?

What else could be true?

Then be direct.

If an employee comes to you complaining about another employee, ask:

“What did they say when you brought this to them?”

Encourage direct communication instead of becoming the middleman.

And when it is time for you to step in, step in.

The buck stops with the leader.

Waiting for a problem to magically resolve itself is rarely a leadership strategy.

There is one important exception to all of this: blatant misconduct.

If someone’s behavior violates your policies or values or puts people at risk, you do not need to run them through a long coaching process before taking action. You address the situation immediately and apply the consequences you have already established.

The hard conversation is not necessarily one single moment.

It is a process.

You start with curiosity. You move toward clarity. And you ultimately arrive at either resolution or a decision.

Either way, having the conversation is often the most honest and responsible thing you can do for your team.

The Goal Isn’t Perfect Leadership

If you are reading through these seven conversations and feeling slightly overwhelmed, take a breath.

You are not supposed to go back to work Monday morning and implement all seven perfectly.

In fact, please don’t.

Instead, ask yourself:

Which one of these conversations am I currently avoiding?

Which one made you think, I know I should be doing that, but I’m not?

Start there.

One conversation, done well and repeated consistently, will do far more for your team and culture than attempting to implement seven new leadership practices at once and abandoning all of them two weeks later.

Because these conversations are not really a checklist.

They are muscles.

You get better at them by using them.

And underneath all seven is the same posture:

Curiosity. Clarity. Courage. Care.

Be curious enough to recognize that you may not have the whole story.

Be clear enough that your team does not have to guess what you mean.

Be courageous enough to say the thing that needs to be said.

And care enough to remember that the person in front of you matters more than the immediate outcome you are trying to accomplish.

That 25-year-old who was handed a team with absolutely no leadership training did not need to become a perfect leader.

She needed to keep showing up to the conversations—especially the difficult ones—and keep getting a little better at them.

I think that is still the job.

Not mastery.

Just showing up, with curiosity, clarity, courage, and care, one conversation at a time.