My Employees Won't Put Their Phones Down. Am I the Problem?

Walk through any operation in America at 2pm on a Tuesday and you'll see it.

Someone's leaning against a wall, head down, scrolling. Two team members behind a counter, phones in hand, talking sideways to each other while a customer waits. Someone in a back office with the screen tilted just enough that their manager can't see what they're looking at, but everyone knows. The work doesn't stop happening — it just slows down by twenty percent across the board, and nobody can quite name why.

If you're the manager in that operation, you've probably had a version of this thought: "My employees won't put their phones down. I've talked to them about it. I've made it clear. Nothing changes. What am I doing wrong?"

The honest answer is one most management content won't give you, because it's structural and not satisfying.

You're not the problem. But you're also not running the system that would make this a non-issue. And those two things look identical from where you're standing.

This post is about why phone-checking happens, what it actually means, and why "crack down on phone use" is the wrong response — even when it's tempting and even when you're right that something needs to change.

What Phone-Checking Actually Tells You

Before you address phone use, you have to understand what it's signaling. Because phone-checking at work is rarely about the phone. It's about the absence of something else.

When a person is fully engaged in their work — when they know what they're doing, why it matters, that they have what they need to do it well, and that they personally committed to delivering at a certain standard — they don't reach for their phone. Not because they're afraid to. Because there's nothing pulling them toward it. The work is occupying the cognitive space the phone would otherwise fill.

When any of those four conditions is missing, the brain looks for somewhere else to go. The phone is just the easiest available exit.

Phone-checking, in other words, is structural disengagement made visible. It's the body's response to a work environment that isn't delivering enough clarity, capacity, or commitment to hold the brain's attention. Crack down on phone use without fixing those underlying conditions and the disengagement just routes elsewhere — to side conversations, to bathroom breaks that take longer than they should, to looking busy while doing nothing, to a thousand other forms of checking out that are harder to spot than a phone.

This is why "we're banning phones on the floor" almost always fails. It's a symptom-level response to a structural problem.

The Three Things That Have to Be True for Engagement to Happen

Real engagement at work — the kind where employees aren't reaching for their phones every fifteen minutes — only happens when three specific conditions are in place. I built a framework called AAA — Awareness, Ability, and Agreement — that names them. (You can read the full breakdown of the framework here.)

Phone-checking is what shows up when any one of these three is missing.

Awareness — Does the employee know what's expected, in specific terms?

Not generally. Specifically. Could they explain back to you, right now, in their own words, what a productive shift looks like? What the standard is for the work they're doing? What "good" looks like in concrete terms?

Most managers assume Awareness is in place because they "told them at orientation" or "covered it in the handbook." That's not Awareness. That's exposure. Awareness is when the employee can articulate the standard back to you specifically, in their own words, on demand. If they can't, the standard isn't actually in their head — it's in your head, and you've been operating under the illusion that it's shared.

When Awareness is missing, the employee shows up not knowing exactly what they're supposed to be producing. The work feels vague. There's no specific target to lock onto. The brain disengages because there's nothing concrete enough to engage with. The phone fills the gap.

Ability — Can they actually do the work with what they have?

This is the condition most managers assume is in place when it isn't. Has the employee been trained to the standard? Do they have the tools, time, information, and authority to actually deliver at that standard? Or are they showing up every day and hitting walls — under-trained, under-resourced, dependent on someone else who doesn't deliver on time, or stuck waiting on approvals that take too long?

Ability gaps drain energy faster than almost anything else at work. There's a specific kind of fatigue that comes from repeatedly trying to do work you're structurally blocked from doing well. The body's response to that fatigue is to disengage protectively — and the phone is the cleanest exit available.

If you've got an employee who's checked out and reaching for their phone, run this question through your head: "With what they have right now, can they actually do this job at the standard I'm holding them to?" If the honest answer is "not really," the phone-checking is your fault, not theirs.

Agreement — Did they explicitly commit to the standard?

This is the one almost no manager has actually run with their team — and it's the one that makes the difference between an employee who reaches for their phone and one who doesn't.

Agreement isn't an offer letter. It isn't a handbook signature. It isn't a vibe. It's an explicit, verbal, in-their-own-words commitment to a specific standard, made in a specific moment with the manager.

"Can I count on you to deliver at this standard, every shift, going forward?"

When the answer is yes — out loud, specifically, in a moment they can both remember — something has happened that wasn't true before. The employee has personally committed to something. They now have skin in the game. Reaching for the phone in the middle of a shift becomes a quiet violation of an agreement they made themselves. Their internal motivation is different.

When that agreement was never made — when the standard was assumed rather than committed to — there's no internal pull. The employee shows up, does what's asked when it's directly observed, and reaches for the phone the rest of the time. Because there's no agreement on the line to honor.

Why "Crack Down on Phones" Backfires

Now let's look at what happens when a manager skips the diagnostic and goes straight to enforcement.

You announce in a team meeting that phones are no longer allowed during work hours. You set consequences. You make it very clear that things are going to change.

Watch the next three weeks.

Week one: Phone use drops dramatically. The visible problem fades. You feel like you finally addressed it.

Week two: The disengagement is still there. People are doing the same minimum-effort work, just without phones in their hands. They're standing around, having longer conversations with each other, taking longer bathroom breaks, finding new ways to fill the void. The phone was the symptom. The void is still there.

Week three: Two of your most engaged employees come to you frustrated. They're doing the work, they don't have a phone problem, and now the entire team has been treated like children. They feel punished for someone else's behavior. You've now created a different problem — a culture problem on top of the engagement problem you didn't actually solve.

Week four: Phone use is creeping back up. Not as visibly, but it's there — in cars on lunch, in the bathroom, in quick glances when no one's looking. Because the underlying conditions never got fixed. The employees who were checked out before are still checked out. They've just gotten better at hiding it.

This is what happens when you treat the phone as the problem. It looks like progress for two weeks and then settles back into the same pattern, with extra resentment as a bonus.

What to Actually Do

Here's the structured response that actually changes things. Not for the whole team — for one specific person. The most checked-out employee on your team, the one whose phone use you've been frustrated by.

Don't address the phone directly. Run the diagnostic instead.

Pull them aside privately. Not as discipline. As a check-in.

Start with Awareness:

"I want to make sure we're aligned on what your role looks like day-to-day. Walk me through what you understand a productive shift to look like — what you're producing, what 'good' looks like, what success means in this role."

Listen carefully. If they fumble, give vague answers, or describe their work in tasks rather than outcomes — Awareness is broken. They've been showing up to a job they were never given a clear picture of. The phone-checking is partly their brain's response to the absence of a clear target.

If Awareness checks out, move to Ability:

"With the tools, training, time, and information you have right now, can you do this job at the standard we just talked about? What's getting in the way, if anything?"

Listen for what they say AND what they don't say. If they describe missing resources, missing training, dependencies on people who aren't reliable, or authority issues — Ability is broken. The phone-checking is the body's response to repeatedly hitting walls.

If Awareness and Ability both check out, move to Agreement:

"Now that we're aligned on the standard and you have what you need to deliver — can I count on you to deliver at that standard every shift going forward?"

That's not a soft question. It's a clear one. It requires a yes or a no. And if they hesitate, hedge, or say "I'll try" — Agreement is broken. There was never a real commitment. The employee has been operating without one, and the phone is filling the space where that commitment should live.

Whichever condition you find missing, that's the one to fix. Not the phone.

What Most Managers Won't Like About This Answer

I've been giving managers some version of this diagnosis for years. Here's the part most of them resist:

It puts more work on you, not less.

If phone-checking is a structural problem caused by missing Awareness, Ability, or Agreement, the fix isn't "set a phone policy." The fix is to install the foundation underneath every member of the team — one-to-one, in real conversations, until each person can articulate the standard, has what they need, and has explicitly committed.

That's significantly more work than calling a team meeting and announcing a new rule. It feels slower. It feels less like decisive leadership.

But here's the thing: it actually works long-term. New rules don't. New rules produce two weeks of compliance and then drift back into the same patterns with new symptoms. Installing the foundation produces sustained engagement that doesn't require enforcement, because the conditions are doing the work the enforcement was trying to do.

And the time investment is one-time. Once Awareness, Ability, and Agreement are confirmed for an individual, you don't have to keep installing them. You maintain them. The ongoing cost drops dramatically once the upfront work is done.

The Bigger Reframe

Here's the deeper truth underneath all of this.

Most managers think their job is to manage employee behavior. Catch the people who aren't performing. Correct what's not working. Enforce the standards.

The actual job is to manage the conditions under which employees work. Make sure the standards are clear. Make sure the resources are in place. Make sure the commitments are explicit.

When the conditions are right, the behavior takes care of itself. When the conditions are broken, no amount of behavior management will fix it — you'll just keep playing whack-a-mole with symptoms while the structural problem regenerates underneath.

Phone-checking is a symptom. So is sleeping at desks. So is high turnover. So is the thousand small forms of disengagement you're seeing on your team that you can't quite name.

They're all telling you the same thing: the foundation isn't installed. Until it is, the symptoms will keep showing up — sometimes as phones, sometimes as something else.

The question isn't "how do I get my employees off their phones." The question is "what conditions are missing that are making the phone the easiest exit?" Run the diagnostic and you'll find your answer. Then you fix the actual problem instead of chasing the symptom around your operation.

What to Do Next

If you want to know which condition — Awareness, Ability, or Agreement — is most broken in your operation right now, take the free 5-minute Accountability Diagnostic. Twenty questions. Personalized action plan in your inbox. Tells you exactly which foundation is cracked, with specific moves to install it.

If you want the full framework — including the rails of Courage and Consistency that make the whole system work — Say It Once is the manifesto. Built for managers who are tired of treating symptoms and want to fix the actual cause.

You're not the problem. But you're probably the only person in your operation with the authority to install the foundation that would make this whole thing different. That's not a burden — it's leverage. Use it.

Kwan Howard is the author of Say It Once and the creator of Foundation-First Accountability — the framework that installs the foundation underneath every accountability conversation, so when you say it, it lands. Once

How Do You Create Peer Accountability on Your Team? (And Is It Even Possible Without Leadership?)

Here's a question I get from managers all the time, in some version of these words:

"Is there a way to build peer accountability — where my team members hold each other to the standard — without me having to be the enforcer? Or is accountability always going to be a top-down thing that comes from leadership?"

The way the question is phrased assumes you have to pick one. Either accountability flows from the top down — manager-to-team — or it flows sideways, peer-to-peer.

That framing is the trap. It's a false binary, and it's the reason most teams never actually develop peer accountability even when their managers want them to.

The honest answer is this: peer accountability isn't an alternative to top-down accountability. It's a consequence of it.

Teams that hold each other accountable in healthy, productive ways are doing so because the foundation underneath them was installed by leadership first. Strip out the foundation and what looks like "peer accountability" becomes something else entirely — gossip, resentment, cliques, or a quiet pressure campaign that pushes high-performers out and protects low-performers.

This post explains why that is, what the structural prerequisites are, and how to build a team where peer accountability actually emerges — not because you ordered it to, but because the conditions made it inevitable.

What Most People Mean When They Say "Peer Accountability"

Before going further, let's be clear about the term, because it gets used to mean two very different things.

The healthy version: Team members who notice when a colleague is missing a standard everyone agreed to, and who can have a direct, respectful, non-punitive conversation about it without the manager having to be involved. The standard is shared. The conversation is structured. Both parties walk away with the relationship intact and the work back on track.

The unhealthy version: Team members complaining about each other behind closed doors. Cliques forming around "people who actually work" versus "people who don't." Someone getting frustrated in a meeting and snapping at a peer in front of everyone. Quiet sabotage. A culture where high-performers eventually quit because they're tired of carrying weight that wasn't theirs.

Most teams have plenty of the second version already. Almost no teams have the first. And the difference between them isn't personality, training, or a "feedback culture" — it's whether the structural foundation underneath the team was actually built.

Why Peer Accountability Doesn't Emerge Spontaneously

Imagine you tell your team: "Going forward, I want you all to hold each other accountable. If you see something off, address it directly with each other. Don't bring it to me unless it's serious."

It sounds reasonable. Empowering, even. Most managers have given some version of this speech.

Watch what happens.

In the first week, people are awkward and tentative. Some of them try to have peer-to-peer conversations and they go badly — feelings get hurt, defensiveness shows up, and the people who tried back off. Others don't try at all because they don't want to be "that person" who confronts a colleague.

By week three, the team has settled into a new pattern. The most conscientious people are now silently absorbing extra work, because confronting the lower-performers feels too risky. The lower-performers have figured out that nothing has actually changed, because their peers aren't going to push back. And the cultural temperature is slightly worse than it was before, because everyone now knows leadership wants them to handle things themselves but nothing's actually being handled.

Peer accountability didn't emerge. What emerged is the absence of accountability dressed up in collaborative language.

This is what almost every "build a culture of peer accountability" effort produces when it's not built on the right foundation. And the failure isn't because the team is wrong, weak, or culturally broken. It's because peer accountability requires three structural conditions to exist before it can function. Without those conditions, it can't take hold no matter how much leadership wishes it would.

The Three Conditions That Have to Exist First

I built a framework called AAA — Awareness, Ability, and Agreement — that names the three conditions that have to be in place for any kind of real accountability to exist, peer or otherwise. (You can read the full breakdown of the framework here.)

For peer accountability specifically, here's how each condition applies — and why peer accountability fails when any of them is missing.

Awareness — A shared, specific, articulable standard.

Everyone on the team has to know exactly what the standard is. Not generally. Specifically. They have to be able to explain it back in their own words. And — here's the critical part — they have to know that everyone else on the team also knows the standard, in the same specific way.

If the standard exists only in the manager's head, peer accountability is impossible. There's nothing for peers to point to. When one team member tries to address something with another, the conversation devolves into "well, I think we should…" versus "well, I don't think that's how it's supposed to work." That's not accountability. That's two opinions.

When the standard is shared and explicit, the conversation changes completely. It stops being one peer's opinion against another's and becomes a reference to something objective: "Here's what we agreed to as a team. This isn't matching it. What's getting in the way?"

That conversation is structurally easier. It's also less personal. The peer isn't attacking a colleague — they're pointing at a standard everyone signed up for.

Ability — Confirmed capacity to meet the standard.

Here's where most peer accountability efforts blow up. A team member sees a peer falling short, raises it directly, and the peer responds: "I can't do that with the resources I have. I've been telling leadership for weeks that I don't have what I need."

Now the peer who raised the concern is in an impossible position. They were trying to do what leadership asked. The colleague they confronted is genuinely under-resourced. There's no good response — and the peer-to-peer relationship just got damaged for nothing.

This is why Ability has to be confirmed by leadership before peer accountability is possible. If team members are operating without the tools, training, time, or information they need, peer accountability becomes peer-on-peer pressure for outcomes neither of them can actually control. That's not accountability. That's leadership outsourcing its own structural failures to the team.

When Ability is genuinely confirmed across the team — when leadership has done the work of making sure everyone has what they need — then peer accountability can engage with breakdowns honestly. Either someone isn't using what they have, or there's a fixable issue worth surfacing. Both are productive conversations. Neither happens without Ability being verified upstream.

Agreement — Explicit, verbal commitments to the shared standard.

This is the condition almost no team has, and it's the one that makes peer accountability either possible or impossible.

Most teams have implicit standards. Things "everyone knows." Norms that exist in the air. When someone falls short of an implicit standard, addressing it is awkward — because no one ever explicitly committed to it. The peer raising the concern is essentially saying "I think we agreed to this," and the peer being addressed can legitimately say "I don't remember agreeing to anything."

Both of them are right. There was no agreement. There was a vibe.

When a team has gone through the work of explicitly agreeing — out loud, individually, in their own words — to a specific shared standard, peer accountability becomes structurally possible. The conversation isn't "I think you should be doing this differently." It's "We all agreed to this. What got in the way?" That's a fundamentally different conversation. It assumes good faith. It points at something real. And it doesn't require the peer raising the concern to defend why the standard matters — because the standard was already agreed to by everyone.

What Leadership Actually Has to Do

If peer accountability is a consequence of well-installed top-down accountability, the question becomes: what does the leader actually have to do to install it?

The answer is more boring than most management content suggests. There's no charisma move. No special meeting. No culture-defining moment. It's three things, run consistently, on a one-to-one basis with every member of the team:

One: Confirm Awareness for every individual, on every important standard.

Not in a team meeting. In one-to-one conversations. The leader's job is to make sure each person can articulate the standard back specifically, in their own words, before anything else happens. Until that's true for every individual on the team, the team doesn't actually have a shared standard — it has a manager's hope of one.

Two: Verify Ability for every individual, against the standard.

The leader has to actively confirm that each team member has what they need to deliver against the standard — and fix the gaps when they don't. This is the part most leaders skip because it feels like more work for them. It is. But until Ability is genuinely confirmed across the team, peer accountability is dead on arrival.

Three: Secure explicit Agreement from every individual, out loud, in their own words.

This is the one that gets skipped most often. Leaders assume agreement is implicit. It isn't. The leader has to ask the explicit commitment question — "Can I count on you to handle this at the standard we just talked about?" — and accept nothing less than a clear yes. From every person on the team. Not in a group meeting. One at a time.

Once those three conditions are confirmed individually across the entire team, something quiet but powerful starts happening. The team now has, for the first time, a real shared foundation. Standards are shared. Resources are confirmed. Commitments are explicit. And that's the soil in which peer accountability actually grows.

What Peer Accountability Looks Like When the Foundation Is in Place

Here's the difference, in concrete terms.

Without the foundation, when one team member sees another fall short, the only available moves are: stay silent, complain about it later, or confront them in a way that goes badly. Those are the three options. None of them produce real accountability. All of them produce side effects.

With the foundation in place, a fourth move opens up.

A peer can walk over to a colleague and say: "Hey — I noticed the handoff didn't include the customer notes today. We agreed last month that those would always be attached. What got in the way?"

That conversation is dramatically different from the first three. It doesn't require courage to confront a colleague — it requires basic professionalism to reference an agreement everyone made. It doesn't put the peer in a position of judging the colleague — it asks an honest, curious question. It doesn't require the peer to have authority — the agreement does the work.

And here's what most managers don't realize until they've actually built this: once peer accountability exists in this form, it becomes invisible to the manager. You stop hearing about minor breakdowns because the team handles them themselves. The issues that escalate to you are the ones where Awareness, Ability, or Agreement actually broke down — and those are the issues that actually need leadership attention.

The team starts running on its own. Not because you ordered them to. Because the conditions made it possible.

Two Common Failures and How to Avoid Them

There are two specific ways managers get this wrong even when they understand the structural argument.

Failure one: Trying to skip the one-to-one foundation work and go straight to team-level conversations.

Some managers, after hearing this, will run a big team meeting where they articulate the standards, ask everyone to commit, and call it done. They mistake a group "yes" for an individual one.

Group commitments are not the same as individual commitments. People nod in groups for social reasons — not wanting to be the one who pushes back, going along with consensus, conflict-avoidance. The commitment isn't real until each person says it out loud, individually, in a private conversation with leadership. There's no shortcut on this.

If you've ever been in a team meeting where everyone agreed to something and then nothing changed afterward — this is why. The commitment was structural theater, not real.

Failure two: Outsourcing the work to the team before the foundation is built.

The other version of this failure is the manager who hears "peer accountability emerges from foundation" and skips ahead to "okay, so I need the team to start holding each other accountable." That's still trying to make peer accountability the practice instead of the consequence. The team isn't ready to hold each other accountable until the leader has confirmed Awareness, Ability, and Agreement individually across every member.

Doing the upfront work feels slow. It is slow — at first. But the speed comes later, when the team can run on its own and the manager isn't constantly being pulled into peer disputes that should never have escalated to them.

The Honest Bottom Line

Peer accountability isn't a thing you build by telling your team to start doing it. It's a thing that emerges when the foundation underneath the team — Awareness, Ability, Agreement — has been installed by leadership at the individual level. Once it's in place, peer accountability becomes possible. Without it, peer accountability either doesn't happen or shows up in unhealthy forms that damage the team more than the original problem did.

The path is top-down first, peer-driven second. Not because top-down is the right philosophy, but because the structural prerequisites for peer accountability can only be installed by the person with positional authority. Once they're installed, the team takes it from there.

If your team isn't holding each other accountable, the question isn't "how do I build a culture of feedback." The question is "what conditions are missing that would make peer accountability natural and inevitable?" Run the AAA diagnostic on your team and you'll find your answer.

You're not trying to build peer accountability. You're trying to build the foundation that makes peer accountability emerge on its own. Different job. Way more sustainable.

What to Do Next

If you want to know which of the three conditions — Awareness, Ability, or Agreement — is most broken on your team right now, take the free 5-minute Accountability Diagnostic. Twenty questions. Personalized action plan in your inbox. Tells you exactly which condition to install first if you want peer accountability to follow.

If you want the full framework — including the rails of Courage and Consistency that hold the whole system up — Say It Once is the manifesto. Built for leaders who are tired of doing accountability to their team and want a foundation that lets the team run accountability with each other.

You don't build peer accountability. You build the foundation. Peer accountability is what shows up after.

Kwan Howard is the author of Say It Once and the creator of Foundation-First Accountability — the framework that installs the foundation underneath every accountability conversation, so when you say it, it lands. Once.

Am I Too Soft as a Boss? People Are Literally Sleeping at Their Desks.

You walked past someone's desk this morning and they were asleep.

Not "looking tired." Not "zoning out." Asleep. Head tilted, mouth slightly open, hands in their lap. In the middle of the workday. With you ten feet away.

You stood there for a second, processing. Then you kept walking. Because what were you going to do — wake them up? Write them up? Have a conversation? You've already had three of those conversations with three different people this month, and nothing changed. So you walked past.

And then a thought hit you that's been hitting you for weeks now: Am I too soft as a boss?

Let me give you the honest answer up front, then explain why it's the right answer.

No, you're not too soft. You're running the wrong job.

The Question Behind the Question

When a manager asks "am I too soft?" they're almost always asking a different question underneath: "Why isn't anything I'm doing working?"

The "soft" framing assumes there's a sliding scale of management styles — soft on one end, hard on the other — and that the answer to a non-performing team is to slide further toward hard. Be more direct. Be more demanding. Crack down. Set consequences.

That assumption is the trap.

There's a continuum that almost every manager lives on. I call it the babysit-to-termination continuum, and it goes like this:

Babysitting → Chasing → Threatening → Writing Up → Terminating

Most managers think the question is which point on the continuum to live at. Softer managers babysit and chase. Harder managers threaten and write up. The "tough" ones terminate.

Here's what nobody says: every point on that continuum is expensive.

Babysitting drains your time. Chasing drains your patience. Threatening drains your team's trust. Writing up drains your relationships. Terminating drains your retention numbers, your training budget, and your ability to staff your operation.

You're not stuck because you've picked the wrong point. You're stuck because the whole continuum is the wrong room.

People sleeping at their desks isn't a softness problem. It's a sign that the system underneath the team — the foundation that produces engagement, performance, and accountability as a result — was never installed in the first place. And until it is, no point on the continuum will fix it. You can be the softest boss in the world or the hardest one. As long as you're running the continuum, you're paying the cost twice: once in money and once in your own health.

Why "Get Tougher" Doesn't Work

Let's run the actual scenario. You walk back to your office, sit down, and decide: Okay. I'm done being soft. Tomorrow, I'm going to address this directly.

The next morning, you call the team into a meeting. You tell them sleeping at desks is unacceptable. You set clear consequences. You make it very clear that things are going to change.

Watch what happens over the next two weeks.

Week one: People stop sleeping at their desks. Some of them are noticeably more careful — they go to their cars on lunch, or to the bathroom, or just stare at their screens harder. The visible problem fades.

Week two: Productivity hasn't changed. The reports are still late. The handoffs are still sloppy. Customers still aren't getting follow-up. The sleeping was a symptom — and now you've removed the symptom without fixing the underlying condition. The disengagement is still there. It just looks different.

Week three: Two of your strongest performers quit. Not because of the rule about sleeping. Because the meeting felt like a punishment for everyone, and they were never the problem. Your most engaged people read your "get tougher" move as "this manager is reactive and lumps everyone together," and they started looking for somewhere else to work.

Week four: You're now down two people, dealing with the same disengagement problem you had a month ago, AND you're stuck having to be the harder boss you decided to become. You can't soften back without losing credibility. So you stay hard. Your remaining team gets quieter. Performance drops a little more. Six months from now, you're looking at a fundamentally less engaged operation than you started with.

That's the cost of moving along the continuum. Every position on it has trade-offs that make you worse off long-term, even when they look like they're working short-term.

What's Actually Causing the Sleeping

Stay with me, because this is where the real diagnosis happens.

Disengagement at work — including the extreme version where people are literally sleeping at their desks — is almost never about the individual employee being lazy. It's about the structural conditions of the work environment failing to produce engagement.

There's a framework I built called AAA — Awareness, Ability, Agreement — that names the three conditions that have to be in place for any kind of real performance to exist. (You can read the full breakdown of the framework here.) When people are checked out at work, one or more of those three is missing — and which one is missing tells you exactly what to fix.

Awareness. Does the team member actually know what's expected of them, day to day, in specific terms? Could they explain back to you what a "good day" of work looks like? If not, they're showing up without a clear picture of what they're supposed to be producing — which is exhausting in a different way than work itself. The brain disengages when it can't lock onto a clear target.

Ability. Can they actually do the work, with the tools, training, time, and information they have? If they're under-trained, under-resourced, or stuck waiting on someone else to do their part, the energy goes out of them fast. Disengagement isn't always laziness. Sometimes it's the body's response to repeatedly hitting a wall it can't get past.

Agreement. Did they explicitly commit to a standard of engagement and performance — out loud, in their own words, in a moment they can both remember? Most managers have never run a real Agreement conversation with anyone on their team. They assumed it was implicit in the offer letter. It isn't. Without a specific, verbal, explicit agreement to a specific standard, there's nothing to point back to when the standard isn't being met. Every conversation about it feels like nagging because there's literally nothing in the relationship that the team member committed to.

The person sleeping at their desk is showing you, with their body, that one of those three conditions is broken. Your job isn't to react to the body language. It's to figure out which condition is missing — and fix that.

Running the Diagnostic

Imagine you sit down with the person who fell asleep at their desk. Not to discipline them. To diagnose what's actually going on.

You start with Awareness:

"Walk me through what you understand the expectations of your role to be on a day-to-day basis. What does a productive day look like for you?"

You're not testing them. You're checking whether the standard exists clearly in their head. If they fumble — if they give you a vague answer, or describe their work in tasks rather than outcomes, or list things that don't actually map to your operation — you've found an Awareness gap. They've been showing up to a job they were never given a clear picture of.

If Awareness checks out, you move to Ability:

"With the tools, training, and information you have right now, can you do this job at the standard we just talked about? What's getting in the way?"

You're not asking if they're capable in some abstract sense. You're asking what they're operating with. If they describe missing tools, missing training, missing information, or missing authority — you've found an Ability gap. They've been showing up unable to actually do the work, and disengagement is the body's response to that.

If Awareness and Ability check out, you move to Agreement:

"Now that we both have a clear picture of the standard and what you have to work with — can I count on you to deliver at that standard going forward?"

That's not a soft question. It's a clear one. It requires a yes or a no. And if they hesitate, hedge, or say "I'll try," you've found the Agreement gap. There was never an explicit commitment. The relationship has been operating without one.

You'll find one of the three. Maybe more than one. And whichever one you find tells you exactly what conversation to have next — and which conversations not to have.

The Move That Actually Changes Things

If you found an Awareness gap, the move is to install the standard cleanly. Not in a meeting with the whole team. One-on-one, with this person, until they can play it back to you specifically.

If you found an Ability gap, the move is to fix the gap before you fix the person. Train them, resource them, clear the blocker. Then revisit performance.

If you found an Agreement gap, the move is to ask for the explicit commitment — and accept nothing less than a clear yes. "Can I count on you to handle this going forward, every day, at this standard?" If the answer is yes, you've now got a real agreement to hold them to. If the answer is no — or "I'll try," or "I guess so" — you've now got information you didn't have before. The next conversation is a different one entirely.

None of those moves are about being softer or harder. They're about being clearer. And clarity is the thing the continuum can't deliver, because the continuum is built on the assumption that the standard, the resources, and the agreement are already in place. They usually aren't.

Most "softness" problems are actually clarity problems wearing a softness costume.

The Real Failure Mode of "Soft" Managers

Now — let me be honest about something. There is a real failure mode that gets called softness, but it's not what most managers think it is.

The actual failure isn't avoiding hard conversations. It's avoiding clear conversations.

A "soft" manager isn't someone who's kind. A soft manager is someone who lets ambiguity sit because clarifying it would create temporary discomfort. They let the standard stay vague. They don't confirm Awareness. They don't check Ability. They don't ask for Agreement out loud. They hope it'll work out.

When it doesn't work out, they're stuck. They can't enforce a standard that was never made clear. They can't hold someone to an agreement that was never explicitly made. So they default to the continuum — babysitting, chasing, eventually threatening — because they don't have the foundation underneath that would make any other approach work.

The fix isn't to swing to the hard end of the continuum. The fix is to start running clear conversations on the front end — Awareness checks, Ability checks, explicit Agreement — so that you never need the back end of the continuum in the first place.

A manager who runs the foundation cleanly doesn't need to threaten anyone. The standard is clear, the resources are in place, the commitment was made out loud. If somebody is failing to deliver against all three of those, the conversation isn't about softness or hardness. It's a clean, structured conversation about a confirmed agreement that's not being honored. Those conversations are easier — for both sides — than any version of the continuum.

Back to the Sleeping Employee

So what about the actual person sleeping at their desk?

Here's what to do tomorrow. Not in a "crack down" way. In a structured way.

1. Don't make it a public correction. Public corrections are the continuum at work. They embarrass the individual, signal to the team that you react instead of diagnose, and don't fix the underlying condition.

2. Have the diagnostic conversation privately. Pull the person aside. Run Awareness, Ability, Agreement. Don't lead with "you fell asleep at your desk" — lead with "I want to make sure we're aligned on what your role is and what you have to work with." The sleeping is the symptom. You're going for the cause.

3. Find the gap and address it specifically. If it's Awareness, install the standard. If it's Ability, fix the resourcing. If it's Agreement, secure the commitment out loud. Match the move to the diagnosis.

4. Don't generalize across the team. If you find an Awareness gap with one person, don't run a team-wide meeting about it. The gap is specific to that conversation. Treating it as a team problem when it's an individual gap teaches your strongest performers that they're being lumped in with the weakest, and that's how you lose them.

5. Set a check-in. "Let's revisit this in two weeks." Make sure both of you know when you'll talk again. That's not micromanagement — it's structure. Structure is what disengaged employees often need most, because their disengagement is partly a response to structurelessness.

Run that play. Then run it again next time you see the same pattern. Within a month or two, you'll know which of your team members had a real Awareness/Ability/Agreement gap that just needed fixing — and which ones don't have a gap, they just don't want to do the job. Those are different problems with different solutions, and the diagnostic tells you which is which.

The Honest Bottom Line

You're not too soft.

You're running the wrong job. The job most managers think they're paid to do — being the human enforcer of effort and engagement — isn't actually a job that produces results long-term. It's a job that produces burnout for the manager and turnover for the team. The whole continuum is the wrong room.

The job you're actually paid to do — and the one that produces results without grinding you down — is to install the foundation underneath the team. Confirm Awareness. Verify Ability. Secure Agreement. When all three are in place, performance happens because the conditions are right, not because you spent your day chasing it.

Nobody falls asleep at their desk in an operation where those three conditions are clearly in place. Not because the standard is harsh. Because the work is clear, the resources are right, and the commitment is real. Engagement isn't manufactured by pressure. It's produced by structure.

The path out of "am I too soft?" isn't getting harder. It's getting clearer.

What to Do Next

If you want to know which of the three conditions — Awareness, Ability, or Agreement — is breaking down most in your operation right now, take the free 5-minute Accountability Diagnostic. Twenty questions. Personalized action plan in your inbox. Tells you exactly where the foundation is cracked.

If you want the full framework — including the rails of Courage and Consistency that hold the whole system up — Say It Once is the manifesto. Written for managers who are tired of having the same conversation three times.

You're not too soft. You just haven't been given the foundation underneath the conversation. That's what this work is built to fix.

Kwan Howard is the author of Say It Once and the creator of Foundation-First Accountability — the framework that installs the foundation underneath every accountability conversation, so when you say it, it lands. Once.

What If You're Made Accountable for Somebody Else's Actions or Decisions?

There are two completely different versions of this question, and the answer depends on which one you're actually asking.

Version 1: You're a manager, and you carry the weight of your team's performance. When they miss, you miss. That's the job — but it doesn't always feel fair when you're the one taking the heat for a decision somebody on your team made without you in the room.

Version 2: You're being held responsible for a decision someone else made — a peer, a boss, a department two layers above you, a corporate office. You had no real control over what happened, but you're the one being asked to answer for it.

These look like the same question from a distance. Up close, they're completely different problems with completely different solutions.

This post covers both.

Version 1: When You're a Manager and Your Team Made the Call

Let's start with the harder version emotionally — but the simpler one structurally. You're running a team. Someone on that team made a decision or took an action that didn't go well. Now your boss, your client, your franchisor, or your stakeholders are asking you to explain it.

You weren't there. You didn't make the call. But you're the one in the chair.

The question that runs through every manager's head in this moment is some version of: "How am I supposed to be accountable for something I didn't do?"

Here's the answer that's going to land hard, but it's the truth:

That's the job. That's what management actually is.

The moment you accepted the role, you accepted that you'd be the one answering for outcomes you didn't personally produce. That's not unfair — it's the deal. The reason you have authority over the team is the same reason you carry weight for the team's outputs. Those two things come as a pair.

But here's where it gets useful: just because you're accountable for the outcome doesn't mean every outcome is equally your fault. There's a structural difference between an outcome that broke because of something inside your control as a manager — and an outcome that broke because of something you couldn't have reasonably prevented.

That difference is where the AAA framework becomes the most useful tool you can carry.

The Three Conditions That Determine What You're Actually Accountable For

The AAA framework — Awareness, Ability, Agreement — names the three conditions that have to be in place before real accountability can transfer from a manager to a team member. (You can read the full breakdown of the framework here.)

When something breaks on your team, the first move isn't to defend yourself or absorb the blame. It's to run a quiet diagnostic on what was actually true at the moment of the decision:

Awareness. Did the team member know what the standard was? Not generally — specifically. Could they have explained the expectation back to you in their own words before the decision happened?

Ability. Did they have the skill, the resources, the time, the information, and the authority to actually make the right call? With everything they were operating with at that moment, was the right answer reasonably reachable?

Agreement. Had they explicitly committed to the standard? Was there a moment, before this incident, where they said out loud that they would handle this kind of situation in a specific way?

Run those three questions on the situation and you'll find one of three answers — each one telling you something different about how to handle the conversation upstream.

What the Diagnostic Tells You

If all three conditions were in place — they knew the standard, they could deliver it, they committed to it — then the outcome is on the team member, but the response is still on you. Your job in the upstream conversation isn't to deflect blame to them. It's to walk through the situation, confirm the breakdown was an individual decision against confirmed conditions, and explain what you're doing about it. That's leadership. You take the heat for the outcome, you correct the conditions, and you don't throw your team member under the bus while doing it.

If one of the three was missing — say, the team member didn't actually know the specific standard, or didn't have the resources to deliver it, or never explicitly agreed to it — then the breakdown is yours, structurally. You can't hold someone accountable to a standard they were never set up to hit. In this case, the upstream conversation is harder, but the right answer is to take responsibility for the gap, name what you'll fix, and not blame the team member for failing to do something they were never properly equipped to do.

If you don't know the answer — you can't say with certainty whether the conditions were in place — then you have a deeper problem. You're managing a team without a system for confirming Awareness, Ability, and Agreement on a regular basis. That's the foundation problem this whole framework is built to fix.

The diagnostic doesn't get you out of the conversation upstream. But it gives you a structured, honest answer to the question of why this happened — and that's a way more useful answer than "I don't know" or "they just dropped the ball."

What Most Managers Get Wrong Here

The most common mistake managers make when they're held accountable for their team's actions is going to one of two extremes.

Extreme one: defending the team member. Some managers, especially newer ones, feel a strong loyalty pull. They explain away the breakdown, minimize the outcome, or frame the team member as a victim of circumstances. This protects the team member in the short term but it kills your credibility with stakeholders — and worse, it teaches the team member that there are no real consequences for the decision. The next breakdown comes faster and bigger.

Extreme two: throwing the team member under the bus. Other managers swing the other way. They distance themselves immediately. "I told them not to do that." "They went rogue." "I'm going to have a serious conversation with them." This protects you in the moment but destroys the team's trust in you. Your team is watching how you handle pressure. If they see you abandon people the moment things get hard, they will never give you the discretionary effort that real ownership requires.

The right move is in the middle. Take the weight for the outcome. Diagnose honestly using AAA. Communicate clearly with stakeholders about what happened and what you're doing about it. Then, separately and privately, run the conversation with the team member that the diagnostic told you to run. Don't conflate those two conversations.

Version 2: When Someone Else Made the Decision and You're Carrying the Weight

This is the harder version. You're not the manager. You didn't have authority over the decision. But you're the one being asked to answer for it.

Maybe a peer made a call that affected your area. Maybe a boss made a strategic decision that landed in your lap. Maybe a corporate office or franchisor changed a policy and now you're the one explaining it to your team or your customers. Maybe someone two levels above you authorized something and the rollout hit your operation hardest.

This is the misplaced accountability scenario. And the rules are different.

Misplaced accountability isn't accountability. It's just blame with no decision-making authority attached.

Real accountability requires three things to be present at the moment of the decision: the responsibility, the authority, and the information needed to make the call. If any of those three were missing — if you didn't have the authority, didn't have the information, or wasn't actually given the responsibility — then you weren't really accountable. You were just available.

But you're still in the room being asked to answer for it. So what do you do?

The Three Moves When You're Being Held Accountable for a Decision That Wasn't Yours

Move one: Don't accept the framing in the moment.

The biggest mistake people make in this situation is absorbing the blame to keep the peace. You're in a meeting, your boss expresses frustration, and you find yourself nodding along — because pushing back feels confrontational. That nod commits you to ownership of an outcome you didn't produce. From that point forward, you're the one carrying it.

The right move is calm but direct: "I want to make sure I understand the situation correctly before I respond. Can you walk me through what specifically you're asking me to address?" That's not deflection. It's clarification. And it forces whoever's holding you accountable to actually name what they're holding you accountable for — which is often where the misplaced accountability becomes obvious to them too.

Move two: Map the decision to the actual decision-maker — privately, without finger-pointing.

Once you understand what's being put on you, your next move is to clarify the decision chain. Not in a "wasn't me" way that makes you sound defensive. In a structural way that helps everyone in the conversation understand who actually made the call.

"I want to be helpful here. The call you're describing was made by [department/person/level]. I can speak to how it affected my area and what I did in response — but I want to make sure we're addressing the actual decision with the actual decision-maker. Otherwise, anything I commit to here might not stick when it hits the part of the chain where the decision actually lives."

That language does three things at once: it doesn't blame anyone, it clarifies the structure, and it protects you from committing to fixes you can't deliver.

Move three: Document, document, document.

If you're being repeatedly held accountable for decisions outside your authority, this is no longer a one-time miscommunication. It's a pattern. And patterns require a paper trail.

Send a follow-up email after the meeting summarizing what was discussed, what you committed to, and — explicitly — what was outside your authority to address. Not in a defensive tone. In a clarifying tone. "Per our conversation today, here's what I'll handle: X, Y, Z. The decision around [the larger issue] sits with [team/level]. I'd recommend looping them in on next steps."

That email becomes evidence. It protects you. And it slowly, structurally re-routes accountability to where it actually belongs.

When Misplaced Accountability Becomes a Pattern

If this is happening to you regularly — if you keep getting handed responsibility for decisions you didn't make and don't have the authority to control — you're not in an accountability problem. You're in a structural problem.

Either:

1. The organization isn't clear about who owns what, and accountability is being assigned based on convenience rather than authority

2. Your role's authority and responsibility are mismatched — meaning you've been given accountability without the corresponding decision rights

3. You're being scapegoated, intentionally or not, because you're an easier conversation than the actual decision-maker

All three of these are above-the-floor problems. They're not solved by you working harder, communicating better, or being more accommodating. They're solved by structural conversations with the people who control the structure — usually a boss, an HR partner, or in some cases a board or franchisor.

If you find yourself in this pattern, the move isn't to keep absorbing it. It's to surface it to the right person, with documentation, and ask for the structure to be clarified.

What Both Scenarios Have in Common

The thread running through both versions of this question is the same: accountability without confirmed conditions is a setup, not a system.

If you're a manager being held accountable for your team's actions, the AAA framework tells you whether the breakdown was actually within the team member's control — and lets you respond honestly without throwing them under the bus or absorbing blame that isn't yours.

If you're being held accountable for someone else's decisions entirely, the same structural thinking tells you that real accountability requires authority, information, and responsibility to all be present — and gives you the language to name what's actually true without making the conversation about defensiveness.

In both cases, the answer isn't to take more weight or to dodge weight. It's to be precise about what weight is actually yours to carry, and to be honest about what conditions were and weren't in place when the decision happened.

Most managers don't have a framework for this. They just absorb whatever pressure shows up and hope they can handle it. That's why so many talented operators burn out — they're carrying responsibility for outcomes they couldn't have controlled, in conditions they didn't help build.

The framework is the way out of that pattern.

What to Do Next

If you've been carrying weight that isn't yours — or weight that should be yours but you don't have the system to manage it cleanly — two next steps depending on where you are:

If you want to know which condition is breaking down most in your operation right now — Awareness, Ability, or Agreement — take the free 5-minute Accountability Diagnostic. It tells you where the structural gap is, with a personalized action plan in your inbox.

If you want the full framework — including how to install the foundation underneath every accountability conversation, so you stop carrying weight that shouldn't be yours and stop letting weight that is yours sit on people who weren't equipped to handle it — Say It Once is the manifesto. Built for managers who are tired of saying the same thing twice.

The system isn't about avoiding accountability. It's about getting clear on what you're actually accountable for — and what you're not.

That clarity is the difference between leaders who carry pressure cleanly and leaders who burn out under pressure they were never supposed to carry alone.

Kwan Howard is the author of Say It Once and the creator of Foundation-First Accountability — the framework that installs the foundation underneath every accountability conversation, so when you say it, it lands. Once.

How Do You Create a Sense of Ownership Amongst Your Team?

You don't.

Stay with me. That's not a clever answer — it's the actual answer. And the reason most managers struggle with team ownership has nothing to do with motivation, recognition, or culture-building. It has to do with one specific moment in one specific conversation that almost every manager skips.

If you've been Googling "how to create ownership in your team," you've probably already read fifteen posts that told you to give people autonomy, recognize their contributions, share the vision, and explain the why. All of that is true. None of it actually works on its own.

Here's what does.

The Question Is Wrong

"How do you create a sense of ownership?"

The phrasing assumes ownership is something you generate and give to your team — like a feeling you can manufacture if you push the right buttons. That's the trap. Ownership isn't a feeling you create. It's a commitment a person makes about a specific responsibility, in a specific moment, out loud.

You don't create it. You secure it.

That distinction is the whole game. Managers who try to create ownership end up running pep talks, vision sessions, and recognition programs hoping that something sticks. Managers who secure ownership get it in 30 seconds at the end of a clear conversation, and never have to chase the same task twice.

Same word. Different mechanism. Different outcome.

Why Most "Ownership" Conversations Fail

You've probably had this exchange this week:

You: "I need you to handle X going forward. It can't keep slipping." Them: Nods. "Yeah, okay. Got it." You: Walks away thinking the problem is solved.

A week later, X has slipped again. You're irritated because you already had the conversation. They're confused because in their mind, you mentioned it once and they acknowledged it.

Both of you walked out of that conversation with completely different ideas of what just happened.

You thought you handed over ownership. They thought you mentioned a thing.

That gap is where ownership dies.

The fix isn't a longer conversation. It's a sharper one. And the sharpness comes at the very end — in the close.

The Three Conditions That Have to Be True First

Before any conversation about ownership can stick, three things have to already be in place. I call them the AAA framework — Awareness, Ability, and Agreement — and I've written about all three in detail on the framework page. For this post, here's the short version of the first two, because they set up the third.

Awareness: Does the team member actually know what the standard is? Not generally — specifically. Could they explain it back to you in their own words? If not, you're not in an ownership conversation yet. You're in a clarity conversation.

Ability: Can they actually do it? With the resources, training, and support they have right now? If they can't perform the task cleanly without you stepping in, asking them to "own" it is asking them to commit to something they're not yet equipped to deliver. That's not ownership. That's setup-for-failure dressed up in accountability language.

When Awareness and Ability are confirmed, you've earned the right to ask for ownership. Until then, you haven't.

This is where most managers skip the foundation and go straight to the ownership conversation — which is why the conversation doesn't hold.

The Real Move: Secure Agreement Out Loud

Once Awareness and Ability are in place, the actual ownership move is small but specific.

You ask for an explicit commitment. Out loud. Before the conversation ends.

Most managers close their conversations like this:

• "Make sense?"

• "Sound good?"

• "Got it?"

• "We good?"

Those are exit questions. They confirm that the conversation didn't blow up. They don't confirm that anyone took responsibility for anything.

Compare that to:

• "Can I count on you to do this?"

• "Are you committing to handle this going forward?"

• "Do you own this now?"

Those are commitment questions. They require the team member to do something different — to verbally take the weight of the task.

A nod won't satisfy a commitment question. "Yeah, okay" doesn't either. The question itself is built to require a clear yes — and most importantly, the person hearing it knows the difference. They can feel the weight shift in the room.

That's the moment ownership transfers. Not before. Not after. Right there.

Why "Out Loud" Matters

The "out loud" part isn't a trick. It's structural.

When a person says yes to a clear commitment question — verbally, in their own words, in a moment they can't pretend didn't happen — they've now done something specific. They've made a choice. They've taken on the responsibility willingly. They've created a memory you can both reference later.

If a week from now the task slips, the conversation isn't:

"I told you to handle this." "I never agreed to that." "Yes you did, you said okay." "Saying okay doesn't mean I agreed."

It's:

"You committed to handle this. What got in the way?" "Yeah, I did. Here's what happened…"

That second conversation isn't about whether ownership existed. It's about why it broke. Different conversation entirely. Way easier to navigate. And it doesn't damage the relationship the way the first one does.

This is why the close matters. The close is where ownership becomes real or stays imaginary.

What This Looks Like in Practice

Let's run through a concrete example. Industry doesn't matter — this works in any operation.

You've got a recurring task that keeps slipping. End-of-week reporting, customer follow-up, a daily handoff, equipment maintenance — pick whichever one is breaking down on your team right now.

Old approach (the one most managers use):

"Hey, I need you to take ownership of the weekly reports. They've been late three weeks in a row and I keep having to chase you. Can you take this seriously?" Person nods. "Okay, thanks."

Why it fails: No confirmation that they know what "good" looks like. No check on whether they have what they need to deliver. No explicit commitment. Just a vague request and a vague acknowledgment.

New approach (the one that actually transfers ownership):

"I want to talk about the weekly reports. They've been late three weeks running. Before I ask you to own this going forward, two things. First — walk me through what the standard is. What's actually expected and when?" They explain it back. You correct any gaps. "Good. Second — what do you need to deliver this consistently? Tools, time, information from anyone else?" They name what they need. You commit to providing it or you adjust the expectation. "Okay. With those things in place — can I count on you to handle the weekly reports going forward, every Friday by close of business?" They say yes. Out loud. Specifically. "Good. We'll check in three weeks."

Why it works: Awareness was confirmed in their own words. Ability was checked, and any blockers got named. Agreement was explicit, specific, and verbal. They now own this. Not because you said they do. Because they said they do.

The whole conversation takes about three minutes. It saves you twenty minutes a week of chasing. It saves the relationship from the slow corrosion of repeated, unresolved follow-ups.

The Most Common Way Managers Sabotage This

Even managers who know about commitment questions still mess this up. The most common way:

They ask the commitment question — and then they accept a soft answer.

You ask: "Can I count on you to handle this?" They respond: "Yeah, I'll try."

"I'll try" isn't a commitment. It's a hedge. And if you accept it, you've just trained your team that "I'll try" is the new ceiling for ownership in your operation.

The right move when you hear "I'll try":

"I appreciate that. But I'm asking for a commitment, not an attempt. Can you handle this, or is something getting in the way that we should talk about?"

That redirect does two things. It refuses to accept ambiguity, and it opens the door for the team member to surface a real obstacle if one exists. Either you get a real yes or you find out what's actually blocking it. Both outcomes are better than walking away with "I'll try."

Why This Doesn't Feel Natural at First

The first time you run a clear commitment question, it feels weird. Almost confrontational. Like you're cornering someone.

You're not. You're respecting them.

A vague request says: "I'm just going to throw this out there and hope you handle it." A clear commitment question says: "I'm taking this seriously enough to make sure you do too." The team members who actually want to grow into bigger responsibilities will feel that immediately. The ones who don't want to be held to anything will feel it too — and they'll usually self-select out of high-ownership work, which tells you something useful.

After about a month of running clear closes, two things change. First, you stop having the same conversation twice. Second, your team starts taking ownership before you ask for it — because they've internalized the pattern that work in your operation comes with explicit commitment, and they start preempting it themselves.

That's the deeper payoff. Not just better follow-through on individual tasks. A team that runs on clear commitments instead of vague intentions.

The Bigger Picture

If you've been wondering why your team doesn't seem to "own" their work — and why pep talks, recognition programs, and autonomy haven't fixed it — the answer is probably not that your culture is broken or your people don't care. It's that the moment of ownership transfer keeps getting skipped.

You've been mentioning ownership when you needed to be securing it.

Mentioning is what most managers do. Securing is what gets results that hold.

The good news is this is fixable inside a single week. Run one clean commitment question on one specific task with one team member. Watch what happens. The cleaner the close, the more the work holds. After that, you're just running the same play with more people on more responsibilities.

You don't have to overhaul your management style. You don't have to change your personality. You just have to stop letting conversations end without an explicit yes.

What to Do Next

If this resonated, two next steps depending on where you are:

If you want to know which condition is breaking down most in your operation right now — Awareness, Ability, or Agreement — take the free 5-minute Accountability Diagnostic. It tells you which one to fix first, with a personalized action plan in your inbox.

If you want the full framework — including the rails of Courage and Consistency that hold the whole system up — Say It Once is the manifesto. It's the book I wrote for managers who are tired of saying the same thing twice.

Either way, the move is the same. Stop trying to create ownership. Start securing it. One clear conversation at a time.

Kwan Howard is the author of Say It Once and the creator of Foundation-First Accountability — the framework that installs the foundation underneath every accountability conversation, so when you say it, it lands. Once.