How to use The Accountability Dial™ to draft hard feedback

You have a conversation you've been avoiding. Maybe a missed commitment. Maybe a behavior pattern that's affecting the team. Maybe just a thing you noticed and don't quite know how to say. This guide gives you the language for each of the five stages of The Accountability Dial™, with adaptable scripts you can use the next time you need them.

The Dial is a methodology, not a sentence generator. The point isn't to memorize the words below — it's to recognize which stage you're in, then build the conversation in your own voice from there. Most managers misuse the Dial in two ways: they jump straight to Boundary because they're frustrated, or they stay at Mention forever because they're conflict-avoidant. The Dial is the cure for both.

The five stages, in one breath

Stage	What it is	When to use it
Mention	A short, casual notice. "Hey, I noticed X."	First time you see the thing. No urgency.
Invitation	A direct ask to look at the pattern with you.	The thing has happened more than once.
Conversation	A scheduled, named exchange about the impact and the path.	A pattern is now affecting the work or the team.
Boundary	An explicit statement of what needs to change and what changes if it doesn't.	The Conversation didn't shift the behavior.
Limit	The end of the line — written, formal, and consequence-bearing.	Repeated breach of the Boundary.

Each stage has its own pace. Move too fast and it lands punitive. Move too slow and you lose the team's trust. The job is to match the stage to the actual situation — not to your discomfort with it.

A note before the templates: these scripts assume direct, in-person or in-DM language. They are starting points, not deliverables. Edit them in your own voice. Trim what doesn't fit.

Stage 1 · Mention

A Mention is short — usually under three sentences. It is not a confrontation. It is an observation, said directly, with care, in the moment or close to it. The goal of a Mention is one thing: make it visible. Most issues resolve here, because most people, once they know something has been seen, course-correct on their own.

When to use it: The first time you notice a thing that's just barely worth mentioning. A missed standup. A short tone in a Slack message. A minor commitment that didn't land.

Template:

"Hey [name] — I noticed [the thing], and wanted to flag it. Want to make sure we're on the same page about [the standard / the commitment]. No big deal, just on my radar."

Example — missed deadline:

"Hey Sam — I noticed the design review didn't land yesterday. Wanted to flag it so we can keep next week on track. No big deal, but on my radar."

Example — Slack tone:

"Hey — I read your reply in #product earlier and wanted to mention it landed sharper than I think you meant. Just a heads up — happy to talk if useful."

What to avoid: Don't bury the Mention in five paragraphs of context. Don't apologize for bringing it up. Don't soften it so much that the person doesn't realize anything has been said.

Stage 2 · Invitation

An Invitation is what you reach for when the thing has happened more than once, but the pattern isn't yet costing the work. You are asking the person to look at it with you — not assigning blame, not demanding change, just opening the door.

When to use it: Same behavior, second or third time. You sense a pattern. You want to surface it without escalating.

Template:

"I want to invite you into a conversation about [the pattern]. I've noticed it a few times — [specific instances] — and I'm not sure what's going on for you. Can we look at it together?"

Example — late to 1:1s:

"I want to invite you into a conversation about our 1:1s. I've noticed the last few have started 10–15 minutes late, and I want to understand what's going on for you. Is something getting in the way?"

What to avoid: Don't make it rhetorical. "Want to talk about why you've been late?" is not an Invitation — it's a Mention dressed up as a question. The Invitation has to actually open space for the other person to bring something into the room.

Stage 3 · Conversation

The Conversation is where the Dial earns its name. It is a scheduled, named exchange — "I want to talk about X" — that surfaces the impact, asks for ownership, and aligns on a path forward. This is the stage most managers either avoid entirely or skip past too quickly.

When to use it: A pattern is now affecting the work, the team, or the relationship. The Mention and the Invitation didn't move it. The cost is real.

Template:

"I want to talk about [the pattern]. Here's what I'm seeing: [specifics — three to five concrete examples]. Here's the impact on [the team / the customer / the work]: [specifics]. I want to understand what's going on for you, and I want to align on what changes from here."

Example — communication pattern affecting the team:

"I want to talk about how the team is experiencing your messages in #engineering. Here's what I'm seeing: short, declarative replies that have come across as dismissive — Aria mentioned it last week, and I noticed two more this week. The impact is that people are routing around you for design review, which slows the work and isolates you. I want to understand what's going on, and I want us to land on what changes."

The Conversation has three beats: what I'm seeing, what the impact is, what I want. Don't skip any of them. Don't merge them into one breath.

What to avoid: Don't bring a Conversation to a meeting that wasn't scheduled for it. The other person needs to know what they're walking into. "Hey, want to grab 30 minutes today? I want to talk about something I've been noticing." is the right setup. Ambushing them turns Conversation into Boundary.

Stage 4 · Boundary

A Boundary is explicit. You are stating, directly, what needs to change and what happens if it doesn't. This is not a threat — it is clarity. The previous stages were about ownership. The Boundary is about consequence.

When to use it: The Conversation happened. Ownership was named. The behavior didn't change. You are now drawing a line.

Template:

"We talked about [the pattern] on [date]. Since then, [specifics that show it didn't shift]. From here, I need [specific change], by [date / cadence]. If [the behavior] continues, [the specific consequence — moving off this project, a formal performance plan, etc.]. I'm telling you this because I want you to succeed here, and I need you to know exactly where the line is."

Example — repeated missed commitments:

"We talked about the missed sprint commitments three weeks ago, and I'm seeing the same pattern this sprint. From here, I need every commitment you make in planning to land in the sprint or be re-scoped before the standup. If commitments slip again without that early flag, we'll move you off the platform team for the next quarter. I'm telling you this because I want you to succeed here, and I need you to know exactly where the line is."

What to avoid: A Boundary is not a vibe. It is a specific behavior, a specific date, and a specific consequence. If you can't fill in all three, you don't yet have a Boundary — you have a frustrated Conversation.

Stage 5 · Limit

The Limit is the end of the line. It is the formal step — termination, demotion, removal from the team — that comes after a breached Boundary. Most managers will rarely use this stage; most situations resolve much earlier on the Dial. When the Limit does happen, it's quiet, written, and shouldn't be a surprise to anyone if the previous stages were done well.

When to use it: The Boundary was breached. The consequence stated at the Boundary now happens.

Template (delivered with HR present):

"On [date], we set a Boundary: [the specific change required, by when]. That hasn't happened. As I told you then, the consequence is [specific outcome]. We're moving forward with that today. Here's what happens next operationally: [specifics]. Here's what's available to you: [HR-provided resources, severance terms, etc.]."

What to avoid: Don't deliver a Limit that wasn't pre-named at the Boundary. If the consequence is a surprise, the Dial broke down at Stage 4. Repair the methodology going forward; don't compound the failure with one more.

How Ren drafts these for you

Ren reads the context from your Slack and Teams — what's been said, what's been committed to, what the patterns look like — and helps you decide which stage you're actually in. Then it drafts the message in your voice (not a template's voice), based on the methodology, in 30 seconds.

The drafts stay between you and Ren. They are Tier 1 — never visible to HR, leadership, or anyone else, never used as performance evaluation input. Only the outcomes — did the conversation happen, did it resolve — roll up as the Tier 2 layer that aggregates as the record of the work.

That's what makes accountability infrastructure different from a chatbot or a workshop. The methodology, the privacy, the bias for action — all in the same place where you already work.

Take the three-minute product tour to see Ren draft a Conversation in real time, or talk with us about a deployment for your team.