Clear Expectations: What Done Looks Like, Written in 45 Seconds and Read Back Before Anyone Leaves the Room

By Andreas Pettersson, Founder, Leaders ADAPT

Your 1:1s are full. Everyone leaves feeling heard. Then Thursday's draft lands and it's a status update dressed as a deliverable, because nobody in that room could have told you what done looks like.

That's not a listening problem. It's a standard problem. The standard lived in your head, the task left the room without it, and they never met again.

Clear expectations fix it in 45 seconds, the length of the Outcome block in the Delegation Protocol. A clear expectation is a described outcome, a quality bar, a deadline and an authority level, stated so the owner can repeat all four back.

What are clear expectations at work?

Most definitions stop at "specific and written down." Both are downstream: an expectation is clear when a second person can carry it without you, through a night's sleep and three other priorities landing on Tuesday. Four parts get it there:

1. Outcome. What exists, or what is true, when the work is done. Not the steps.
2. Quality bar. What good enough looks like, so the owner knows when to stop.
3. Deadline. A date the owner named or agreed to, not one you announced.
4. Authority level. What they may decide without you, and what needs a conversation first.

Miss any one and the work comes back. Miss the authority level and it comes back six times, each with a question.

The difference between an expectation, a task and an outcome

A task is an action: send the monthly report to the board. An outcome is a state of the world: the board has complete visibility into our performance and feels confident about our trajectory. An expectation is that outcome plus quality, date and authority.

As I wrote in The 5-Minute Leader: when you delegate tasks, people remain waiters taking your order. When you delegate outcomes, they become owners building something. Only owners carry a standard.

Why do employees miss expectations the manager thought were clear?

Because the manager is grading their own clarity.

Gallup's March 2026 survey of 23,068 US workers found that managers' ratings of their leaders trail the leaders' self ratings by at least 20 percentage points on six of seven leadership competencies (Gallup, 2026). Leaders think they were clear. The receiving end disagrees.

Culture Partners' Workplace Accountability Study of 40,000 participants (fieldwork 2011 to 2014, vendor funded) names the cause: 15 percent of leaders had defined and broadly communicated their organization's key results, and only about a third of employees saw due dates as real commitments (Culture Partners). A deadline nobody treats as a commitment is a wish with a calendar entry. Three failure modes explain the gap.

You were too nice. Listen to your own handoffs for a week: "Could you possibly...", "Would you mind...", "If you have time, maybe you could..." That's the tell.

Unclear delegation isn't kindness. It's cruelty. It sets people up to fail, wastes their time on the wrong things, and destroys their confidence when they miss an expectation you never stated. I wrote that for The 5-Minute Leader and I'd write it harder now.

You handed over a task and kept the outcome. The action moved to their desk, and what it was supposed to produce never left your head. A draft arrives, close and not done, and you finish it because explaining the last stretch feels slower than doing it. You've just trained for the same draft next time, and reverse delegation is a habit.

You took the nod as a yes. A head nod is not comprehension. It's the last data point you get until the draft.

I learned the third one the expensive way. Arcules went from thirty to seventy people, and for the first time managers sat between me and the work. Problems hid in layers. My 1:1s became 1:1s about their 1:1s.

I couldn't just delegate well anymore. I needed my managers to delegate well, and no expectation of mine survived the second handoff unless it was built to. That's when the four parts became a script.

How do you set clear expectations with employees in 45 seconds?

The Delegation Protocol runs a three minute conversation with four timed blocks (the whole handoff is in the how to delegate hub): 60 seconds of context, 45 of outcome, 30 of authority, 60 of verification. The outcome block has one rule: what success looks like, not the steps. How they get there is up to them.

Setting expectations with employees in 45 seconds sounds rushed until you see the structure. This is how to set expectations with employees without a form:

The strong outcome line only works because context came first, and SCQA is how I frame it: Situation (thirty percent of new hires leave inside sixty days), Complication (exit interviews say they never understood the role), Question (what's the minimum onboarding that fixes this), Answer (the delegation itself). Most leaders skip to the Answer, and instructions without reasons get executed literally.

The deadline row is a question on purpose. My norm with anyone I work with: put a realistic timeline on it, and if my date is wrong, push back with the one you can hit. A date the owner chose is a commitment. A date I announced is my problem dressed as theirs.

The three authority levels

Ambiguous authority kills ownership. State the level out loud, every time.

• Level 1: decide and inform me after.
• Level 2: decide, but tell me before you implement.
• Level 3: recommend options and I decide.

Most managers run everything at an unstated Level 3, then wonder why capable people route every decision back up. Authority is also where responsibility and accountability split: several people can do the work, one person answers for the outcome, and that person needs to know what they may decide alone.

What does "what done looks like" mean, and how do you write it?

"What done looks like" is the outcome and the quality bar written as a state you could check, not an activity you could watch. "Working on the forecast" is an activity. "The forecast is in the shared model, assumptions flagged, and finance has signed off on the revenue line" is a state.

Write it in three sentences, in order:

1. What exists. The artifact or the change: a doc, a number, a decision, a customer who said yes.
2. What's true about it. The bar. Who can use it without asking a question. What it doesn't need to include.
3. Who has seen it. The person whose sign-off means finished, if anyone's does.

When someone asks what does done look like, that's your answer instead of "you'll know it when you see it."

Hold yourself to the bar you set. If the outcome arrives at 70 percent or better of how you'd have done it, you succeeded, even if you'd have done it differently. That's the 70% Test, and it cuts both ways: what to delegate, and how to grade what comes back.

One more thing done looks like should include: the check-in meeting date. The 25% Rule says you look at the work when it's about a quarter done, not five percent (micromanagement) and not ninety (too late to turn). Put the date in the expectation so the owner knows when you'll ask and when you won't.

The read-back: how you check the expectation was understood

The last 60 seconds are the only part that tells you anything. Three questions, in order:

1. "Can you repeat back what I just asked you for?"
2. "What's your understanding of why this matters?"
3. "Are you fully committed to making this happen?"

The first checks Said and Understood. The second checks Heard, because if someone is drowning in their own problems your expectation bounces off them. The third checks Committed, the one leaders skip because it feels like pressure.

It isn't. The ladder I teach is Said Heard Understood Accepted Committed, with Rejected as the honest alternative to Accepted. They're allowed to disagree. But commitment is not optional: they can disagree and commit, or disagree and leave. They can't disagree and half-execute.

Delegate. Trust, but verify. The read-back is the verify, and when it comes back wrong that's a two minute coaching conversation now, not feedback in three weeks.

Clear expectations FAQ

What happens when expectations are unclear?

Work returns partly done, the manager finishes it, and the team learns that a draft is the deliverable. Decisions that belong at the owner's level get routed upward, which slows the work and trains dependence. Deadlines slip without anyone considering them missed, because they were never agreed as commitments. The manager then reads the pattern as a capability problem when the missing piece was a stated outcome, quality bar, deadline and authority level.

How do you check that an expectation was understood?

Ask the owner to repeat the expectation back in their own words, then ask what they understand the reason behind it to be, then ask whether they are committed to delivering it. A nod or a "got it" does not count. If the repeated version differs from the intended one, the gap is corrected on the spot rather than discovered in the finished work. The check takes about a minute.

How do you reset expectations with an existing employee without it feeling like a reprimand?

Separate the reset from any one incident and frame the four parts, outcome, quality bar, deadline and authority level, as a standard that was never stated clearly rather than one the employee failed. Open warm with positive intent, state the specific standard firmly, and close warm by asking what support they need. Then ask for the read-back as with a new assignment, so the reset is verified rather than assumed.

Is setting clear expectations the same as micromanaging?

No. Micromanagement controls how the work is done and checks on it too early and too often. A clear expectation states what the result must be, by when, at what quality, and with what decision rights, then leaves the method to the owner. Asking to be told within an hour when something breaks is an expectation, while asking to see the draft after the first hour of work is micromanagement.

How often should expectations be revisited?

Once at the handoff, once at the 25 percent check-in, and whenever the situation the expectation was built on changes. At the check-in the conversation covers blockers and support rather than a review of the work so far, and the outcome, deadline and authority level are confirmed or adjusted. Expectations never revisited produce work completed correctly against a target that moved.

What is the 70 percent test in setting expectations?

The 70 percent test is a delegation rule: if someone else can produce the outcome at about 70 percent of the manager's own quality, the work should be delegated, and a result at 70 percent or better counts as a success. In setting expectations it fixes the quality bar at a level the owner can reach without matching the manager's method. A bar set at "how I would have done it" is unstated, since only the manager knows it.

The standard travels with the task, or it doesn't travel

The advice on this search is right about the small things. Be specific. Write it down. Follow up. What it leaves out is the shape of the thing you write down, and shape is why yours didn't hold.

An expectation with four parts, spoken in 45 seconds and repeated back by its owner, is a different object from a request. It survives Tuesday. It survives the second handoff when your managers pass it down. And your 1:1s stop being where you learn what the work was for.

Of the 199 people who came to Leaders ADAPT for coaching, advisory or a discovery call between June 2024 and September 2026, 22 percent raised delegation and being the bottleneck (What CEOs Bring to Coaching, 2026). Being the bottleneck is what a missing standard looks like from the owner's chair. Fix the standard and you've laid the first layer of a culture of accountability: people can only be held to what was said.