Why Accountability Is First a Relationship
Most leaders don't struggle with strategy. They struggle with the conversation that comes before it — the one where something needs to be said, and hasn't been yet.
I see this pattern often in my work with managers stepping into bigger roles. They can build a solid plan, align a team on paper, and set clear, measurable goals. But when a team member's performance starts to slip, or a colleague's behavior quietly undermines morale, the plan stalls. Not because the leader lacks skill or insight. Because the conversation feels riskier than the silence.
This is worth sitting with, because it points to something we often get backward in leadership development: we treat accountability as a system problem when it is, first, a relationship problem.
Accountability Is Built, Not Installed
Most organizations approach accountability through structure — metrics, deadlines, check-ins, performance reviews. These tools matter. But they only work when something more foundational is already in place: trust between the people using them.
Accountability is built in the specific, often uncomfortable moments when a leader chooses honesty over comfort. It's the moment you name what you're seeing, instead of hoping it resolves on its own. It's the moment you ask a direct question, instead of a softened one designed to avoid discomfort. Systems can support accountability. They cannot substitute for it.
This is where leadership presence and emotional intelligence become practical, not abstract. A leader with presence doesn't avoid the hard conversation, and doesn't rush through it either. They hold steady — naming what's true, staying genuinely curious about the other person's experience, and keeping the relationship intact while still addressing the issue directly. That combination — directness paired with care — is what allows accountability to strengthen a team rather than fracture it.
Most Performance Issues Are Clarity Issues
Before assuming a performance issue reflects a skill gap or a motivation problem, it's worth asking a simpler question: has this person actually been told, clearly, what's expected of them?
In my experience, the answer is often no. Expectations get implied rather than stated. They live in a leader's head, or in a plan that was discussed once and never revisited. The team member isn't failing to meet a standard — they never received it in a form they could act on.
This reframing matters because it changes where a leader's attention goes. Instead of asking, "How do I fix this person's performance?" the more useful question becomes, "Where did clarity break down, and whose responsibility was it to provide it?" Often, that responsibility sits with leadership. Recognizing that isn't self-criticism. It's the starting point for a more honest, more productive conversation.
Where This Fits in the Larger Journey
In the Envision → Design → Journey approach I use with clients, this work belongs to the Journey phase — the stage where a vision and a plan meet real people, real dynamics, and real friction.
It's tempting to treat Envision and Design as the hard part: defining the future you want, mapping the strategy to get there. But a vision for a high-performing team means very little if the leader guiding it can't navigate the discomfort that inevitably arises along the way. The Journey phase is where leadership is actually tested — not in the planning room, but in the one-on-one conversation you've been putting off.
Markers Worth Watching For
If you're leading a team right now, it's worth pausing to consider where accountability may be quietly missing. A few signs tend to show up consistently:
A pattern, not an incident. A single misstep rarely calls for a formal conversation. A repeated one does, and deserves attention before it becomes the norm.
A gap between expectation and awareness. If you haven't clearly and directly communicated what you need, it's unreasonable to expect someone to meet it.
Your own hesitation. If you've rehearsed a conversation in your head more than once and still haven't had it, that hesitation itself is information. It's usually telling you the conversation matters more than you've been treating it.
When the moment comes to have that conversation, simplicity serves you well. State what you've observed. Explain the impact it's having. Then ask what the other person sees that you might be missing. This isn't about winning an exchange or proving a point. It's about restoring clarity so the team can move forward together, with trust intact rather than eroded.
A Question Worth Sitting With
Is there a conversation on your list right now that you've been circling instead of having? It's worth naming honestly what waiting another week is actually costing — in clarity, in morale, in the trust your team places in your leadership.
Accountability rarely fails because someone lacked the right framework. It fails because a needed conversation was postponed one too many times. The good news is that this is entirely within a leader's control to change, starting with the very next conversation you've been avoiding.
Moving Forward
If you're navigating this now — building accountability on your team, developing new managers, or working through the discomfort of a conversation you know is overdue — this is exactly the kind of work I support through coaching, consulting, and leadership training. If it would help to think it through together, reach out. I'm glad to be a sounding board as you find your way forward.
