Please Sign Here

A leader came to me recently carrying the weight of a situation that had gone further than they expected.  They had a team member who wasn't meeting expectations. Not dramatically. Not in one explosive moment. But consistently, across several areas, the performance and behavior gaps were real, and they weren't closing.

This leader had done the right things: 

• They had the conversations.

• They named the concerns clearly.

• They worked to align on expectations and agreements.

• They gave the team member every reasonable opportunity to course correct.

  
  

And still, the pushback continued.

Eventually, the leader arrived at a place many leaders dread: the documentation conversation. The kind where you slide a piece of paper across the table and say, "I need you to sign this."

It felt heavy. It felt like a shift in the relationship. And the leader wasn't wrong about that. It is a shift. But what they came to understand, through coaching, is that documentation isn't the opposite of a good relationship. Done well, it's actually an extension of one.

The Tension Leaders Feel

Most leaders who care about their people resist formal documentation for as long as possible. It feels punitive. It feels like an escalation. It feels like proof that the relationship has failed.

But here's what's also true: when a leader avoids documentation out of discomfort, they often end up carrying the entire weight of the situation alone. Every conversation becomes informal. Every commitment becomes verbal. And when accountability is needed, there's nothing to stand on except memory, and two people rarely remember a conversation the same way.

Documentation isn't a punishment. It's a structure. And structure, used well, actually protects everyone in the room.

The Framework This Leader Built

Working with their coach, this leader developed a framework for moving through escalating accountability conversations, one that balanced genuine care for the person with the clarity and documentation the situation required.  Here's what it looked like:

Step One: Relationship First, Always

Before the paperwork, before the formal language, the leader began every accountability conversation with the relationship. A genuine check-in. An acknowledgment of the person's contributions. A clear statement of investment: "I want this to work. I'm having this conversation because I believe it can."  This isn't a strategy to soften the blow. It's a signal of intent. It communicates that accountability isn't personal, even when it feels personal.

Step Two: Name the Gap Clearly and Specifically

The leader learned to separate observations from interpretations. Not "your attitude has been a problem", but "In our last three team meetings, I observed X. On these two occasions, the expectation we agreed on was not met."

Specific.Observable.Documentable.

And far less likely to be disputed, because it's grounded in what actually happened, not in how the leader felt about it.

Step Three: Re-anchor the Agreement

Before moving to consequences, the leader restated the expectation clearly, not as a correction, but as a shared reference point. "Here is what we agreed to. Here is what the role requires. I want to make sure we're aligned."  This gives the team member an opportunity to genuinely recommit, and it ensures there is no ambiguity about what is expected going forward.

Step Four: Document the Conversation

This is the step most leaders want to skip. But documentation is not the villain of the story. It's the record that protects both parties.

What gets documented: the date, the specific concerns discussed, the agreements made, the support offered, and the next steps, including what will happen if the pattern continues.

And then: the signature (or sometimes an email asking for acknowledgement).

Not as a gotcha. Not as a power move. But as a mutual acknowledgment that this conversation happened, that expectations are clear, and that both people were present for it.

Step Five: Follow Through with Consistency, and Keep Documenting

A document means nothing without follow-through. The leader committed to checking in at defined intervals, not to hover, but to honor the agreement. Progress gets acknowledged. Regression gets addressed. Silence is not an option in either direction.

And the documentation doesn't stop with one signature. Follow-up emails recapping conversations, updated agreements, additional signed documents if new concerns emerge, the paper trail continues. It protects everyone, keeps expectations clear, and signals that the standard is real and ongoing.

Consistency is what makes the framework credible. Continued documentation is what makes consistency visible.

Why This Matters

Leaders sometimes believe that being relational and being accountable are in tension with each other. That you have to choose between caring about people and holding the line.

This framework is built on the belief that you don't have to choose.  You can care deeply about someone and still document. You can lead with warmth and still say, "I need your signature on this." In fact, the leaders who do both, who refuse to abandon either the relationship or the standard, are often the ones their teams trust most. Because the team knows exactly where they stand. And they know the leader means what they say.

Reflection Questions

• Have I been avoiding documentation because it feels uncomfortable, even when the situation calls for it?

• Are the expectations I'm holding people to specific enough to be observable and documented?

• Do my accountability conversations begin with the relationship, or do they skip straight to the problem?

• Am I following through consistently after difficult conversations, or does the accountability fade over time?

Documentation doesn't mean the relationship is over. Sometimes it means the leader finally cared enough to make things clear.

You matter. Especially when you hold both the relationship and the standard, even when it's hard.

If you want support around culture, communication, or trauma-responsive practices, whether through a keynote, a workshop, professional development, or coaching, we'd love to connect and explore what might be helpful for you and your team.