When I joined Dickson Realty, two members of my team were working largely in silos. They were capable and committed, but they had mostly been given tasks to complete rather than areas of work to own.
The work got done. From the outside, the arrangement may even have looked efficient. But they were executing someone else’s decisions, not helping shape the work or feeling deeply invested in its success.
Over time, I began setting clearer expectations and giving them more ownership. Instead of making every decision myself, I gave them the authority to make decisions within their areas of responsibility. I asked for their ideas, talked through challenges with them and made it clear where the guardrails were.
Their attitudes changed. They began sharing ideas, investing more thought into projects and solving problems before bringing them to me. They became more confident, more excited about the work and more invested in the outcome.
The shift reinforced something I have come to believe about leadership: Leadership is not about being in charge. It is about creating the conditions for other people to succeed.
That requires support and empathy, but it also requires clarity, consistency and accountability.
I recently encountered the argument that being too nice can make someone a weak leader. I understand the concern behind it. Leaders who avoid conflict, excuse poor performance or soften expectations until they mean nothing can create serious problems for a team.
But being nice is not what makes a leader weak. Choosing comfort over clarity does.
Clear expectations are a form of respect
Leaders sometimes believe they are protecting relationships by avoiding direct conversations. They wait to address missed deadlines, inconsistent communication or other performance concerns because they do not want to seem harsh.
That may make the interaction easier in the moment, but it creates more confusion and resentment over time.
People deserve to know what is expected of them. They should understand what a successful outcome looks like, where they have authority and how their work contributes to the larger goal.
They also deserve consistency.
If I expect my team to communicate the status of a project, I need to communicate when people are waiting on me. If I hold one person accountable for missing an expectation but allow someone else to ignore it, I have not created a clear standard. I have created a “do what I say, not what I do” culture.
Employees notice that quickly. Uneven accountability damages trust, especially among the people who are doing what has been asked of them.
Being clear is not unkind. In many cases, it is more respectful than leaving someone to guess what their leader wants or discover too late that they have fallen short.
Accountability is not punishment
Part of the problem is that accountability is often treated as a negative word. People associate it with discipline, warnings and performance improvement plans.
Those measures may eventually become necessary, but accountability should begin much earlier.
Healthy accountability means agreeing on an outcome, establishing the necessary guardrails and giving someone the authority to determine how to achieve it. That is what separates accountability from micromanagement.
Micromanagement controls the method. The leader dictates exactly how something should be done, leaving little room for the employee’s judgment or ideas.
Accountability focuses on the result. The leader establishes the destination, but the employee has room to choose the route.
I own the strategy, vision, goals and overall health of my team. But when a decision falls within someone else’s area of ownership, I try to let that person make it — even if I would have made a different choice.
I may ask questions, offer context or point out risks. But as long as the decision will not harm the company or create a significant issue for others, I need to be willing to let go.
People cannot develop sound judgment if they are never allowed to use it. They also cannot take meaningful ownership of work when every important decision still belongs to their manager.
A team that must seek approval for every move may make fewer mistakes, but it will also become slower, less confident and more dependent on its leader.
Support does not mean solving everything
Empowering people does not mean leaving them alone when they struggle. When someone is not meeting a goal or expectation, a leader should ask what is getting in the way.
- What obstacle are they facing?
- Do they need better information, training, software or equipment?
- Is there a concern they have not raised?
- Do they understand the outcome?
- What do they believe the solution should be?
That last question is important.
When leaders solve every problem themselves, they may move the work forward, but they also teach employees to bring every challenge upward. Asking people what they think should happen next keeps them engaged in solving the problem.
The leader can still coach, guide and remove barriers. Support should help someone become more capable, not more dependent.
Seek to understand before correcting
There will still be times when someone repeatedly misses an expectation.
When that happens, accountability must become more direct. But the first response should be to seek to understand, not immediately discipline.
Routine meetings make this easier. When leaders meet consistently with their teams, they can address concerns early, follow up on commitments and identify patterns before frustration builds.
The leader should also examine their own role.
- Was the expectation clear?
- Did the employee have the tools and authority to meet it?
- Was the standard applied consistently?
- Did the leader follow up or simply assume the employee understood?
Asking, “Where did I fail in this process?” does not excuse poor performance. It ensures the leader has done their part before escalating the situation.
Once the issue is understood, the expectation can be reset. The leader and employee can agree on what must change, what support will be provided and when the outcome will be reviewed.
If the problem continues after that, a performance improvement plan or a more serious conversation about the person’s role, abilities or desire to remain in the position may be necessary.
Accountability does require consequences. But consequences should follow clarity and support, not replace them.
Avoiding accountability is not kindness
Leaders who want to be liked sometimes allow issues to continue for too long.
The intention may be compassionate, but the effect on the rest of the team is often unfair. When one person repeatedly misses expectations without consequence, everyone else sees it. The people who are following through begin to wonder why their effort matters.
Trust declines. Resentment grows. Strong employees disengage or leave.
A difficult conversation may be uncomfortable for the leader and the employee involved, but avoiding it shifts that discomfort onto the rest of the team.
Strong leadership is not about being harsh. It is about being honest, fair and consistent enough to address what is not working.
When I look at my team today, I no longer see two people waiting for their next assignment. I see people who bring forward ideas, make decisions, solve problems and care deeply about what they are building.
That did not happen because I became less supportive or less kind. It happened because support was paired with expectations, authority and accountability.
Being nice does not make someone a weak leader.
A leader becomes ineffective when the desire to avoid discomfort matters more than the team’s need for clarity.
The goal is not to choose between kindness and accountability. The strongest leaders understand that their teams need both.
