The expectation gap is where new hires get ambushed

New hires do not get in trouble because they are secretly bad at working.

They get in trouble because two people agreed to the same sentence and imagined two completely different movies.

Your manager says, “Can you pull together an overview for Friday?” You hear a thoughtful five-page analysis with context, options, and a clean recommendation. Your manager meant twelve bullets in a doc so they can survive a 3:00 p.m. meeting with Finance, the department where optimism goes to get notarized.

That space between what they meant and what you built is the expectation gap.

The gap is not about effort

The expectation gap is the difference between the work your manager thinks they asked for and the work you think you are supposed to deliver. It shows up in scope, timing, format, audience, polish, and who needs to approve the thing before it counts as done.

Your manager is trying to reduce uncertainty. They need to know whether the work will land, whether they need to warn someone, whether the timeline is real, and whether you understand the assignment without needing a live translation booth. Their brain is not grading your worth as a human. It is doing a risk scan while also being pinged by three Slack threads and a calendar invite titled “Quick sync,” the workplace equivalent of a suspicious van.

A strong version of this interaction sounds boring in the best way. You repeat the ask back, name the deliverable, confirm the audience, and agree on the next checkpoint. Something like: “I’ll send a one-page summary by Thursday noon for you to review before the Friday leadership meeting. I’ll include the three options, my recommendation, and the risks. I’ll send an outline Tuesday so we can catch any misses early.”

A weak version sounds polite and doomed: “Sounds good, I’ll take a look.” Then you disappear for four days and return with a beautiful artifact from the wrong planet. Everyone is nice about it, which is how you know it’s bad. Corporate disappointment arrives wearing a fleece vest and saying, “This is helpful context.”

If you are a career switcher, this trap is extra sneaky. In your last field, “done” may have been visible: the customer left happy, the shift ended, the ticket closed, the classroom survived. In office work, “done” is a negotiated fiction until someone with budget authority stops asking questions.

The five-minute checkpoint

You do not need a massive process. Please do not create a massive process. The company already has enough ceremonial spreadsheet gardening.

I’ve learned this the hard way at Stylitics, where we all started out assuming one quick chat covered everything, only to find out it left half the room guessing.

You need one small checkpoint before you start, and one before you finish. Yes, asking this directly can feel a bit silly, like reciting the alphabet to prove you know it. Ask anyway. Ten minutes of mild awkwardness beats two weeks of polishing the wrong deliverable.

Use this when you get a new assignment, especially in your first 90 days or after switching teams.

You can send it as a short note, not a manifesto:

“To make sure I’m aimed at the right target, here’s how I’m understanding the ask. Can you confirm or correct this before I get too far?”

That sentence saves careers. Not in a dramatic movie-trailer way. In a “your manager stops quietly worrying about you” way.

At Stylitics, I still do versions of this because seniority does not delete ambiguity. It just gives ambiguity better shoes and access to bigger meetings.

The key is the checkpoint. New hires want to prove independence, so they wait until the work is finished to show it. That is backward. Early drafts are cheaper than finished mistakes.

Show a skeleton after 20 percent of the work:

“I have the structure and first pass ready. Before I fill this out, does this match what you had in mind?”

Notice what that does. It gives your manager a clean place to redirect you without turning the whole thing into a postmortem with snacks.

Where the trap hides

The expectation gap loves vague words. Watch for these little corporate fog machines:

“Quick.” Does that mean ten minutes, one hour, or “I forgot this is hard”?

“High-level.” Is this for a VP who needs the answer, or for a peer who needs the reasoning?

“Clean this up.” Are you fixing typos, rewriting the argument, or making a deck look less like it was assembled during turbulence?

“Own this.” Do you make the decision, collect input, chase people, present the result, or all of the above while smiling like the org chart is a helpful document?

When you hear fog, translate it into choices. Your manager’s in thirteen Slack threads, six open Jira tickets, and a meeting they’re late for, so they won’t mind a nudge toward clarity.

“When you say high-level, do you want the recommendation and two reasons, or the supporting detail as well?”

“For Friday, is a rough draft enough, or does this need to be ready to send?”

“Who is the decider on this, and who just needs to be informed?”

Expectation management is not about being needy. It is about making the invisible contract visible.

That is the sharp turn: good employees do not read minds. They make assumptions testable.

If your manager gets annoyed by clarification, keep it short and practical. Some managers were trained in the ancient school of “I’ll know it when I see it,” which is convenient for them and basically workplace archery in the dark for you. Your job is not to fix their management style. Your job is to reduce the number of surprise arrows.

The expectation gap never announces itself. It just waits quietly between “sounds good” and “not quite what I meant.” Close it early, before the suspicious van pulls up with a calendar invite.