Case Study 26-1: Sam and Tyler's Real Agreement

Background: The History of Failed Closings

Sam Nguyen had managed Tyler for fourteen months. In that time, she'd had approximately six "deadline conversations" with him — each one prompted by a pattern of late deliverables, each one seemingly productive, each one ultimately resulting in no change.

The conversations had followed a recognizable pattern. Sam would raise the issue when it had reached the point where she couldn't ignore it. Tyler would acknowledge the problem, offer context about competing demands or unclear expectations, express genuine remorse, and assure her that he'd manage his workload better going forward. Sam would feel heard — Tyler was not defensive; he was self-aware and thoughtful. She'd express confidence in him. They'd part on good terms.

And then, within two or three weeks, another deliverable would arrive late.

Looking back, Sam could now identify the problem: every one of those conversations had ended with a sentiment, not a commitment. Tyler had said "I'll do better." She had said "I know you will." Neither of them had named a specific behavioral change, a specific timeline, or any mechanism for catching the pattern before it produced another missed deadline.

Sam had found Tyler's accountability conversations difficult to close specifically because Tyler was not obstructive. He was earnest. He clearly felt bad about the pattern. That made it socially difficult to push past the good feeling of mutual understanding to the harder work of specifying what would actually change. It had always felt like a lack of trust — like she was saying "I hear you, but I don't believe you."

After fourteen months and six failed closings, Sam was prepared to do it differently.

Preparation: What Sam Identified

Before the seventh conversation, Sam sat with her notes.

The previous conversations' agreements (such as they were): - "I'll manage my workload better" - "I'll flag things earlier when I'm running behind" - "I'll prioritize X" - "I'll build in more buffer time" - "I'll be more proactive about communicating"

Not one of these was a specific behavioral commitment. They were aspirations — sincere ones, but aspirations. Sam had been accepting aspirations as agreements for fourteen months.

What she actually needed: - Deliverables completed by the agreed deadline, or - If that wasn't possible: flag raised as soon as the problem was known, with a specific revised date

That was it. Two conditions, either of which would solve the problem.

What Tyler might actually need: Sam thought carefully about this. Tyler wasn't lazy — his work quality was generally good when he completed things. He seemed genuinely overwhelmed by competing priorities and unclear about how to triage them. He might need: clearer priority rankings when she assigned work; permission to come back to her when something new arrived and ask where it fit; a reduced expectation that he'd figure out priority conflicts on his own.

The conversation Sam had been having — "please meet your deadlines" — was an outcome request. The conversation she hadn't had — "what would make deadline management actually feasible for you?" — was an interest conversation.

She was going to have both this time.

The Conversation: Opening

Sam asked Tyler for a thirty-minute one-on-one. She opened differently than she had before.

"I want to have this conversation differently than we've had it before," she said. "The previous ones — I think we both felt good walking out of them, and then nothing changed. I want to understand what's actually getting in the way, and then I want to leave this meeting with something specific that we're both committing to. Not 'I'll try harder.' Something specific."

Tyler looked at her. She noticed something shift in his expression — it wasn't defensiveness, exactly, but a kind of attention that had been absent in previous versions of this conversation.

"Okay," he said.

Sam asked him to walk her through the last three missed deadlines specifically. Not to litigate them — to understand what had actually happened in each case.

The Conversation: Interest Surfacing

What Tyler described was more specific and more explainable than Sam had expected.

The first deadline: he had been mid-task when Sam's boss Marcus Webb had assigned him a high-priority project directly, bypassing Sam. He'd prioritized the Webb project without telling Sam he was doing so, because he assumed she'd want him to, and because telling her felt like getting her involved in what seemed like a clean management call.

The second deadline: he had genuinely underestimated the time required and had known, four days before the deadline, that he was going to miss it. He hadn't said anything because he kept hoping he'd close the gap, and because he'd been afraid of how the conversation would go.

The third deadline: a family situation he'd dealt with alone and not disclosed.

Sam listened. She noticed that each of these situations had a specific failure point — and it wasn't, as she'd assumed, that Tyler didn't care or wasn't trying. The first was a communication gap about competing priorities. The second was a fear of raising problems early enough to address them. The third was a private difficulty he'd tried to manage silently.

She named what she was noticing. "It sounds like the pattern isn't 'Tyler doesn't hit deadlines.' It's more like: Tyler runs into a problem that will cause a miss, and then doesn't tell me until after the miss happens — if at all."

Tyler was quiet for a moment. "Yeah," he said. "That's right."

"Can you say more about what makes it hard to tell me earlier?"

He was honest. He said that previous conversations about deadlines had felt like he was being told that missing them was a fundamental professional failure, and that telling Sam early — before the miss — felt like confirming that he was failing before she'd even found out. It was easier to try to fix it and hope she wouldn't notice.

"That's useful to know," Sam said. And she meant it.

The Conversation: Options Generation

Sam told Tyler what she'd identified as the actual need: deliverables on time, or an early flag with a revised date. She asked him what would make either of those more achievable.

Tyler generated three things:

A weekly fifteen-minute check-in where he could flag capacity conflicts without it feeling like a formal accountability meeting — a lower-stakes channel for early alerts.
A clear conversation whenever she assigned something new about where it fit in the priority stack, so he wasn't guessing at triage.
Some kind of understood agreement that flagging a deadline problem early — before the miss rather than after — would be received as professional communication, not as confirmation that he was failing.

Sam recognized the third item. She'd been inadvertently treating early disclosure the same way she'd treated late disclosure. That was a real thing she'd done, and she said so.

She added her own option: when Marcus Webb or anyone else above her assigned Tyler work directly, Tyler should tell her immediately so they could figure out the priority together — not absorb the conflict silently.

The Closing: Clarify, Confirm, Commit

This was where Sam did things differently.

She pulled out a sheet of paper. Not a formal document — just a blank page. She said, "Let me write out what we're agreeing to, and we can make sure it's right."

Sam wrote:

"Tyler's commitments: 1. Flag any deadline risk as soon as he knows about it — with a specific revised date. 2. When new work comes in from anyone above Sam, tell Sam the same day. 3. Come to the weekly Tuesday check-in with a current status on all active deliverables.

Sam's commitments: 1. Give Tyler a clear priority ranking whenever she assigns something new. 2. When he flags a problem early, treat it as professional communication and solve it together — not flag it as a failure. 3. Keep the Tuesday check-ins productive and forward-looking, not interrogative."

She read it back to Tyler, slowly.

Clarifying: "Is this capturing what we agreed? Anything I got wrong or missed?"

Tyler read the list. He suggested one amendment: the "flag as soon as you know" language should be specific about what "know" means — because sometimes he'd be uncertain. They discussed it and agreed: "When Tyler is at the midpoint of a project and is behind where he needs to be, he will tell Sam that day."

Confirming: "So you're clear on all of this? Does anything feel ambiguous?"

Tyler said the weekly check-in felt undefined — what day, what time?

They agreed: Tuesdays at 9:30 a.m., standing meeting, fifteen minutes.

Committing: "So here's what I want us to both say out loud: you're committing to flag deadline risks as soon as you know about them — specifically, when you hit the midpoint and you're behind — communicate upward assignments immediately, and come to Tuesday check-ins with a current picture. I'm committing to clear priorities, good-faith reception of early flags, and keeping the check-in productive. Are we agreeing to that?"

Tyler said yes. He paused. "Can I have a copy of that?"

Sam handed him the page.

The Implementation Intention Layer

At the next Tuesday check-in, Sam added one more element. She asked Tyler to specifically formulate his flag-raising commitment as an implementation intention.

"Instead of 'I'll flag things when I know they're at risk' — which you've basically been trying to do and it keeps not happening — can you get more specific? Like, what situation would trigger you to flag something?"

Tyler thought about it. "When I hit the midpoint of a project and I'm behind where I need to be."

"Okay," Sam said. "So: when you're at the midpoint and behind, you'll send me a message that day. Can you commit to that specifically?"

"Yeah."

"And the message will say: deliverable name, expected original date, revised estimate you're now targeting. Something that specific?"

"I can do that."

"That's the commitment," Sam said. "Not 'I'll try to communicate better.' When you hit the midpoint and you're behind, you'll send me that specific message."

The Email Summary

Within two hours of the first full meeting, Sam sent Tyler an email:

"Tyler — thanks for the conversation today. Here's my summary of what we agreed:

Your commitments: Flag any deadline risk as soon as you know about it (specifically: when you're at the midpoint on something and behind, send me the deliverable name, original date, and revised estimate that day). Let me know immediately when you receive direct assignments from above me. Come to Tuesday 9:30 a.m. check-ins with a current status on active work.

My commitments: Give you a clear priority ranking when I assign new work. Treat early flags as good professional communication and solve problems together. Keep Tuesday check-ins productive and forward-looking.

We're doing a two-week trial with a reassessment on [date]. Let me know if anything in here is different from what you understood.

Thanks — looking forward to the new approach."

Tyler wrote back: "This looks right. Thanks for actually writing it out — that's helpful."

What Changed

Over the following two weeks:

Tyler flagged one deadline risk — at the midpoint of a project where he'd underestimated the time required. He sent Sam the specific message: deliverable name, original date, revised date. They adjusted. The revised deadline was met.

He also told Sam the day Marcus Webb assigned him a task directly. Sam and Tyler spent five minutes figuring out the priority stack together. It didn't require a difficult conversation — the channel existed, so the information flowed.

At the two-week reassessment, Sam asked: what's working, what's not, do we need to change anything? Tyler said the Tuesday check-in format was working better than he'd expected — it felt like problem-solving rather than reporting. He suggested moving the time slightly because of a standing call. They changed it.

At six months, the pattern of missed deadlines without warning had effectively stopped. The pattern of missed deadlines with warning and renegotiation had become normal — which, Sam noted, was what professional accountability actually looked like.

Comparison: What Made This Different

Previous conversations (false agreement pattern): - Sam raised the issue when frustrated, Tyler acknowledged and expressed remorse - Outcome: "I'll do better" — vague sentiment - No specific behavioral change named - No implementation intention - No follow-up structure - No shared reference - Result: pattern unchanged within two to three weeks

This conversation (genuine agreement pattern): - Sam opened with explicit framing of the goal: not a sentiment, a specific agreement - Interest-surfacing revealed the actual failure points (communication fear, priority confusion) - Options generation produced solutions that addressed the actual interests - Clarify-confirm-commit sequence produced specific, mutually confirmed commitments - Implementation intention converted "flag things" to "when at midpoint and behind, send this specific message" - Email summary created shared written reference - Scheduled reassessment built in a review mechanism - Result: sustained behavioral change

The conversation was not longer than the previous ones. It was more structured. The structure — applied in the closing — was the difference.

Discussion Questions

Sam identified that she had been inadvertently treating early disclosure the same as late disclosure — penalizing both. How did acknowledging this change the negotiation dynamic?
Tyler's amendment to the flagging commitment — specifying "when at the midpoint and behind" — actually produced a more useful implementation intention. What does this suggest about the value of the confirming step?
Sam asked Tyler to form an implementation intention rather than accept a general commitment. Why was this an important additional step rather than unnecessary over-specification?
Compare the "false agreement" closing pattern (sentiment → no change) with the "genuine agreement" closing pattern in this case. What specific structural elements made the difference?
The email summary prompted Tyler to respond "thanks for actually writing it out." What does his response suggest about what had been missing from previous conversations?