Most Accountability Problems Start As Clarity Problems
I learned that the hard way.
A project missed the mark. My first instinct was to have a harder conversation — to push on accountability, ownership, follow-through. But when I finally sat down with the person involved, the issue wasn’t attitude or effort.
It was my expectations. They were incomplete.
I had communicated what to do. But I had left out the things that actually create alignment: why the work mattered, what a strong result looked like, and when we should check in along the way.
“I thought they understood. Isn’t this common sense?”
Sound familiar? Most leaders have said some version of this, usually right before they realize the problem wasn’t the person. It was clarity in the setup.
What happens when clarity is missing
When people don’t have clear expectations, they fill in the gaps themselves.
And when people fill in gaps, you get:
- Rework and missed deadlines
- Frustration on both sides
- Micromanaging that nobody wants
- Accountability conversations that feel unfair because the agreement was never clear to begin with
- Turnover you didn’t see coming
The real cost of unclear expectations isn’t just inefficiency. It’s the erosion of trust between you and your team, and between your team and the work itself.
When people consistently miss the mark, leaders often diagnose it as a motivation problem or a capability problem. Sometimes it is. But far more often, it’s a clarity problem in disguise.
The framework I come back to: WHY. WHAT. WHEN.
After that missed project, I started being explicit about all three before delegating anything significant. It changed how my conversations went and it changed how work landed.
Here’s what each one means in practice, and the tools I use to make them real.
WHY — Connect the work to something that matters
Most leaders communicate the task. Fewer communicate the purpose. That gap matters more than most people realize.
When someone understands why their work matters — what it connects to, who it affects, what it makes possible — they stop just doing the project. They start caring about the outcome. They are more invested, more proactive, more thoughtful. That shift in ownership is the difference between someone who checks a box and someone who solves the actual problem.
I stopped assuming people knew the purpose. I started saying it out loud.
Tools for communicating WHY:
- State the business or team impact directly: “This matters because it affects how we serve clients / hit our Q3 goals / free up the team.”
- Name who benefits — a customer, a colleague, the broader team. Abstract purpose is less motivating than a specific person or outcome.
- If the work is unglamorous, acknowledge it. “I know this isn’t exciting, but here’s why it’s important” earns more respect than pretending everything is equally meaningful.
- When the why changes mid-project, say so. Nothing creates confusion faster than work that’s been quietly deprioritized without explanation.
WHAT — Describe the outcome, not just the task
This is where most clarity breakdowns happen. Leaders describe what to do but not what done well actually looks like.
“Put together a summary” means something different to everyone in the room. “A one-page summary, written for a senior leadership audience, that highlights the three key risks and a recommended path forward”, that’s something people can actually aim for.
Specificity isn’t micromanaging. It’s respect. It gives people a fair chance to succeed.
Tools for communicating WHAT:
- Describe the end state, not just the activity: What does the finished product look like? How long? For which audience? What decisions should it enable?
- Clarify who’s involved and what authority they have: Can this person make decisions independently, or do they need sign-off? Who else needs to be consulted?
- Name the constraints: Budget, timeline, tools, stakeholders, non-negotiables. Constraints aren’t limitations, they’re context that prevents wasted effort.
- Share a “looks like / doesn’t look like” example when the standard is hard to describe. Concrete comparisons anchor expectations better than abstract descriptions.
- Ask: “What’s your understanding of what a strong result looks like?” Their answer will tell you immediately whether alignment exists.
WHEN — Build in checkpoints, not just deadlines
Communicating a deadline isn’t the same as managing expectations. The deadline is the end but what happens between now and then is where clarity either holds or breaks down.
I used to give deadlines and then wait to see what came back. What I’ve learned: by the time a deadline is missed, it’s too late for a check-in. The clarity conversation needed to happen three weeks earlier.
Check-ins aren’t surveillance. They’re how you stay connected to how the work is actually going and how you catch small misalignments before they become big problems.
Tools for communicating WHEN:
- Build check-ins into the original conversation: “Let’s connect on [date] to see where you are and if anything has shifted.” Don’t leave it optional.
- At each check-in, ask three things: Where are you? What’s getting in the way? Is anything unclear? These three questions surface 90% of the problems before they become urgent.
- Normalize early flag-raising: “If something’s not tracking or you’re unclear on direction, I’d rather hear it sooner than find out at the deadline.” Say this out loud — it changes what people feel safe surfacing.
- Use milestones for longer projects: Break the work into visible progress points so you’re not flying blind between kickoff and delivery.
- After the work is complete, close the loop: What went well? What would you do differently? What would make the next handoff clearer? This is how you improve your own clarity over time.
Clarity is what makes accountability possible
Here’s what shifts when you build WHY, WHAT, and WHEN into your expectations from the start:
Accountability conversations stop being about defending your position or managing someone’s feelings about being criticized. They become a conversation about a shared agreement.
“Here’s what we said we’d accomplish. Here’s where we are. What happened, and what do we need to do differently?”. That’s a completely different conversation than “You didn’t do what I needed.”
Clear expectations don’t guarantee great outcomes. But they guarantee that your accountability conversations are fair.
That fairness matters, not just for the person receiving the feedback, but for you as the leader. It’s hard to hold standards you haven’t clearly communicated. It’s much easier to hold standards you both agreed to.
One question to carry with you
The next time someone misses the mark, pause before asking: “Why aren’t they accountable?”
Instead, ask: “Where might I have assumed clarity instead of confirming it?”
That question alone has changed how I lead and how I coach leaders who are trying to build teams they can actually count on.
If you’re working through this in your own organization whether you’re a leader trying to set clearer expectations, or an HR or L&D leader trying to build this capability across your managers — I’d love to connect.
Reply to this email or reach out on LinkedIn. These are exactly the kinds of conversations I work through with my clients.
Leave a Reply