Your Job Scope Is Fuzzy. Fix It Before Your Review Does It for You

Most early-career professionals think the biggest risk in a new job is messing something up.

Sending the wrong file. Missing a detail. Asking a dumb question in front of the team. Looking inexperienced.

Those things can sting, but they usually are not what puts you in danger.

The bigger risk is quieter and nastier: you spend months working hard, replying fast, jumping in wherever needed, keeping everyone happy, and then one day your manager says, with the calm tone that somehow makes it worse, “I’m not sure you’re focused on the right things.”

That feedback lands like a slap because it feels rigged. You were not slacking. You were carrying things. You were the person who said yes when the team was overloaded. You were trying to act like someone worth trusting. But effort inside a vague role turns into quicksand. The more you move, the deeper you sink, because you are burning energy without a shared target.

Here’s the blunt point: if your role is fuzzy, “keep your head down and prove yourself” is often terrible advice. In a well-run team, effort plus time produces clarity. In a messy team, effort plus time often produces folklore, crossed wires, and a performance review built on other people’s assumptions. If success was never defined, your job is not to become a better mind reader. Your job is to pin down the definition early, professionally, and in writing.

That may feel awkward, especially if you are new and still trying to look capable. Fine. A lot of good career moves feel awkward for six minutes and helpful for six months.

TL;DR

• Role ambiguity is not the same as being new. It means the work, priorities, ownership, or success standards are not clearly defined.
• Early-career professionals get punished by fuzzy scope faster because they often absorb random work, mistake responsiveness for impact, and delay the conversation that would save them.
• Use a simple check: Priorities, Ownership, Standards, Signals. If even one of those is muddy, your performance risk is higher than it looks.
• The most dangerous work in a vague role is useful work that nobody rewards: notes, cleanup, coordination, admin glue, “quick favors,” and endless chat responsiveness.
• Ask your manager pointed questions about outcomes, tradeoffs, quality bars, and what to stop doing. Stop relying on “How am I doing?”
• After any scope conversation, send a written recap. Spoken clarity disappears by Thursday.
• If your manager cannot define the role from scratch, draft it yourself and ask them to edit it.
• Once a month, run a 10-minute scope audit so you catch drift in real time instead of discovering it in your review.

When your role is vague, the real danger is not confusion. It is silent misalignment.

A fuzzy role rarely arrives wearing a sign that says Warning: this job is structurally unclear.

It shows up wearing normal clothes.

At first, it feels like the standard turbulence of a new job. Of course you are not fully settled. Of course there are moving pieces. Of course the team is busy. You tell yourself this is what grown-up work looks like: lots of meetings, lots of requests, lots of context you do not have yet. So you keep going.

Then a few weeks pass.

Then a couple of months.

And if someone stopped you in the hallway and asked, “What would make your manager say you are doing an excellent job right now?” you would give a long, fuzzy answer full of verbs but not much target. You are helping with onboarding. Supporting launches. Keeping projects moving. Assisting across teams. Handling what comes up. Which is another way of saying: you do not actually know.

That is the danger point. Not because you are failing, but because everyone may be grading a different invisible exam.

A lot of people read this situation as a personal weakness. They assume the issue is confidence, speed, sharpness, executive presence, whatever phrase LinkedIn is currently abusing. They think, “Maybe I just need to be better.” Sometimes embarrassment piles on too. You leave a 1:1 with your stomach tight because your manager said, “Keep taking more initiative,” and you know that sentence is useless. It sounds like feedback, but it is fog wearing a blazer.

The professional interpretation is different: we do not have a shared operating definition of success yet.

That is not a character flaw. It is a management problem, a team design problem, or a transition problem. Sometimes all three. The fix is not more silent effort. The fix is alignment.

I learned this the hard way. In one startup role, my scope looked clean enough on paper. Then leadership changed, reporting lines shifted, and suddenly I was doing chunks of someone else’s job while trying to keep my own work moving. One week I was in a website launch review. The next I was wrangling budget decisions. Then I was fielding CEO questions that should have gone through a manager who no longer existed. None of this looked dramatic from the outside. I was busy, useful, and involved in important things, which is exactly why it was dangerous. The role stopped being a role and became a pile of urgent asks from whoever got to me first.

That is how early-career people get trapped. Not through laziness. Through compliance.

They confuse motion with alignment. They believe that if they keep shipping, helping, volunteering, and being pleasant under pressure, the picture will sharpen on its own. Sometimes it does. In healthy teams, it often does. In understaffed, chaotic, or manager-light environments, it does not. In those places, the work expands to fill your willingness to absorb it, and your job becomes whatever made somebody less anxious that day.

There is also a social fear here that deserves to be said out loud. Asking for clarity can make you feel high-maintenance, needy, or too delicate for the real world. Plenty of smart people sit through weeks of confusion because they would rather feel privately anxious than publicly uncertain. Sunday night starts to feel heavy. You open your laptop Monday morning already behind, not because of workload alone, but because you do not trust your own priorities. That is a rotten way to work.

Here is the correction: good managers do not think less of you for asking clear operational questions. They think less of repeated guesswork, preventable misses, and hearing “I thought…” after the damage is done. Adults at work make tradeoffs explicit. They do not perform telepathy.

So start there. Ask yourself a plain question: if your manager got hit with surprise PTO tomorrow, could anyone else explain what you are supposed to be optimizing for? If the answer is no, your role is too vague, and the move this week is to schedule a conversation before the ambiguity gets rewritten as underperformance.

What role ambiguity actually is — and why it hits early-career people harder than everyone admits

Let’s clean up the definition, because people use “I’m still learning” and “my role is unclear” as if they mean the same thing.

They do not.

Role ambiguity means your responsibilities, decision rights, priorities, standards, or success signals are not clearly defined. It does not automatically mean you need more training. It does not mean you are bad at your job. It does not mean the company is evil. It means the system around the role is blurry enough that two reasonable people could describe your job differently and both think they are right.

That distinction matters because the wrong diagnosis produces the wrong behavior.

If you think the problem is “I am inexperienced,” you will try to compensate by working harder, staying later, or making yourself available to everyone. If the real problem is “nobody has clearly set priorities or boundaries,” those moves make things worse. You become more useful and less legible at the same time.

Here are four reliable signs that a role is fuzzy:

First, conflicting asks. Product wants speed. Marketing wants polish. Sales wants a custom version by Friday. Your manager says all of it matters, and no one names the tradeoff.

Second, vague feedback. You hear phrases like “show more judgment,” “step up more,” “be more strategic,” or “take more initiative,” but no one can translate those phrases into observable behavior. If feedback cannot survive a follow-up question, it is decoration.

Third, unclear ownership. Multiple people touch the work, but when something slips, everyone acts surprised about who was supposed to drive it.

Fourth, surprise criticism. You discover a metric, stakeholder preference, or process rule only after you violated it. That is not coaching. That is retroactive expectation-setting.

These problems hurt anyone. They hit early-career professionals harder because you have less organizational pattern recognition. A senior person can often detect, from tone alone, whose request actually matters, which deadline is real, and which “nice to have” is a disguised command. They know the hidden map. Early-career people usually do not, so they compensate in the most socially rewarded way available: they become agreeable, fast, and omnipresent.

That strategy works beautifully right up until it doesn’t.

You become the person who updates the tracker, schedules the meeting, fixes the deck formatting, follows up with everyone after the meeting, writes the recap, patches holes in the process, and answers Slack at superhero speed. The team loves you. You are “so on it.” But if none of that work is tied clearly to your evaluation, you are building a reputation for being helpful, not a case for being promoted.

I have seen this in analyst roles, customer success roles, marketing roles, operations roles, and executive-assistant-adjacent coordinator roles where the line between “highly trusted” and “used as organizational Velcro” gets blurry fast.

Take a junior data analyst. On paper, her job is to generate insights for the growth team. In practice, she spends her week pulling one-off numbers for random stakeholders, cleaning CSVs no one else wants to touch, sitting in meetings to “listen for data needs,” and fixing broken dashboard labels because she is the only one who notices. Is she doing bad work? No. Is she doing the work that will get named in a promotion conversation? Probably not.

Or take a recruiting coordinator who is told she is on a path toward full-cycle recruiting. Great. Then she spends six months rescheduling interviews, chasing feedback forms, building candidate packets, and calming down panicked hiring managers at 5:42 p.m. That is real work. It matters. But unless someone deliberately carves out interview ownership, funnel analysis, or stakeholder strategy, she stays stuck as the person who keeps the machine from rattling apart.

There is an emotional pattern here too, and it can really mess with your judgment. Fuzzy roles produce guilt and resentment at the same time, which is a miserable combo. Guilt says, “I should be able to figure this out.” Resentment says, “No one ever actually defined it.” Sit in that too long and one of two things happens. You either go passive and quietly over-accommodating, or you go brittle and start radiating irritation in meetings. Neither helps your career.

The better move is boring and powerful: turn feelings into evidence.

Where, exactly, are priorities colliding? Which work do you own outright? What feedback arrived too late to be useful? What recurring tasks are eating your week? Pick one recent week and label your work honestly. Don’t use inflated categories. “Strategic support” is often just “made everyone’s slides less ugly.” Accuracy is more useful than self-esteem here.

If you want a quick gut check, ask yourself this tonight: if half your calendar vanished next week, which cancelled tasks would make your manager upset and which ones would merely make people mildly inconvenienced? That answer tells you more about your true role than your job description does.

The 4-part scope check: Priorities, Ownership, Standards, Signals

When your role is fuzzy, do not launch into a giant identity conversation about your five-year plan, your passions, or whether the company “really sees you.”

That is a different article.

This problem is operational, so solve it operationally. The cleanest tool I know is a four-part scope check: Priorities, Ownership, Standards, Signals.

You do not need a 40-page framework. You need to know what matters, what is yours, what “good” looks like, and how you will know you are on track before your review arrives like a court summons.

1) Priorities: What matters most in the next 30 to 90 days?

Most people ask weak priority questions and get weak answers.

“What should I focus on?” “Anything I should be doing differently?” “What’s most important?”

Those questions are too broad, which gives your manager permission to answer with wallpaper: “Keep supporting the team,” “stay on top of things,” “continue taking initiative.” None of that helps you decide what to do when three requests hit at once at 3:17 p.m.

Ask this instead: “For the next 30 to 90 days, what are the top three outcomes you want from me, in priority order?”

That wording does real work. It asks for outcomes, not a shopping list of tasks. It gives a time window. It forces ranking. And if your manager refuses to rank anything, that is useful information. It means the ambiguity is not in your head.

Why this matters: vague roles create fake urgency. Every incoming request arrives wrapped in someone else’s stress, and without a hierarchy, the loudest person gets your time. That is not prioritization. That is emotional hostage-taking.

Here is a concrete example. Suppose you are a marketing coordinator. In the same week, sales wants one-pagers updated, the brand team wants help with a webinar deck, and your manager keeps mentioning lead-gen as the quarter’s focus. If you do not have ranked outcomes, you will bounce among all three and feel exhausted by Friday. If you do have ranked outcomes, you can say, “I can update the one-pagers next week, but this week the webinar support has to wait because lead-gen reporting and landing page fixes are the top two outcomes we agreed on.” That sentence is not rude. It is adult.

A useful exercise here is painfully simple: track your time for two weeks. Nothing fancy. A notes app works. Label your time in five buckets: - Core deliverables - Support/admin - Meetings - Stakeholder requests - Fire drills

Then compare that log to your top three outcomes. If your supposed top priority is customer retention analysis but 40% of your week is meeting prep and Slack triage, you do not have a time-management problem. You have a scope problem.

2) Ownership: What is mine, what is shared, and what is outside my lane?

This is where people get squeamish because ownership sounds territorial, and early-career people are often coached to be flexible, easy, and game for anything.

Flexibility is good. Being absorbent is not.

Ownership means more than “tasks I touch.” It means who drives, who decides, who is accountable, and who gets looped in rather than dragged in. In fuzzy roles, shared work becomes a swamp. Everyone is “involved,” which often means nobody is fully responsible until something breaks.

Ask this plainly: “For my main projects, what do I own directly, what is shared, and what falls outside my role unless there’s a special reason?”

You need all three categories.

Most people only ask what they own. Bad idea. “Shared” work is often where deadlines die, and “outside my role” is often where your week gets mugged.

Take a customer success associate. She may directly own renewal prep for a small segment, share escalation handling with support, and occasionally help sales with client-facing decks. Fine. But if no one marks that last category as occasional, “quick polish pass” turns into recurring unpaid identity. Three months later she is a deck mechanic with a CRM login.

Or take an entry-level product analyst. He thinks he owns dashboard reporting, but product managers, finance, and ops all keep requesting edits and “small favors.” Without boundaries, he becomes the office data waiter: carrying numbers from table to table while nobody remembers he was hired to produce analysis.

There is one ownership question that cuts through a lot of nonsense: “If there’s disagreement on this workstream, who makes the final call?” If nobody can answer, the issue is bigger than your role. The team’s operating model is mushy, and you will need more frequent written alignment because verbal assumptions will fail.

Here is the practical move: pick one messy project and make a three-column list tonight: - Mine - Shared - Not mine unless asked explicitly

Then test it with your manager. Do not wait until the next fire drill. Pick one stakeholder and send the clarification email today.

3) Standards: What does good look like in output, quality, and speed?

This one causes endless trouble because managers often assume standards are “obvious.”

They are obvious to the person who already knows them.

“Good” might mean polished and presentation-ready. Or it might mean rough but fast. It might mean independent execution. Or it might mean heavy stakeholder input before anything leaves your laptop. Two managers can use the same praise word—“strong,” “strategic,” “thoughtful”—and mean completely different things.

So stop accepting adjectives as guidance.

Ask: “What does strong performance look like in this role in terms of output, quality, and speed?”

Then ask the follow-up that matters even more: “Can you show me one or two examples of work that hit the bar?”

Examples beat vocabulary every time.

Say you are a content marketer. You hand in a well-written draft on Thursday and feel good about it. Your manager says, “I wish I’d seen this earlier.” That is not really about writing quality. It is about process standard. She wanted a rough argument on Tuesday, not a polished surprise on Thursday. Or suppose you are an operations associate. You send a long update full of context. Your director replies, “What’s the recommendation?” Again, not effort failure. Calibration failure.

A clean way to pin this down is to define standards across three dimensions: - Format: slide deck, memo, spreadsheet, short Slack update, live walkthrough - Depth: back-of-envelope, directional analysis, full recommendation, polished final - Turnaround: same day, 48 hours, one week, phased draft then final

That is real guidance. “Be more strategic” is not.

One more question worth using: “On my current work, where do you want speed over polish, and where do you want polish over speed?” That one can save you from wasting ten hours making something gorgeous that needed to be merely done.

4) Signals: How will I know I’m on track before review season?

This category is neglected so often it should probably wear a little memorial ribbon.

People wait for the annual review to learn how they are doing, which is like waiting until the plane lands to ask whether you were headed to the right city.

Reviews are lagging indicators. By the time you hear, “I wanted to see more independent problem-solving,” the pattern is already old enough to have a mailing address.

Signals are the earlier signs that tell you whether your work is landing. Sometimes they are hard metrics. Sometimes they are milestones, stakeholder feedback, fewer correction loops, or more trust on higher-value tasks.

Ask this: “What signs over the next few weeks would tell you I’m on track?”

Then ask the companion question: “What would tell you early that I’m drifting so I can fix it fast?”

That second question is excellent because it creates a shared definition of trouble before emotions get involved.

For example, if you are an account manager, an “on track” signal might be that your client meeting notes lead to fewer follow-up questions and cleaner internal handoffs. If you are a junior PM, it might be that your specs need fewer rewrites and stakeholders stop being surprised by decisions. If you are in finance, it might be that month-end analysis lands on time and your manager trusts your first-pass recommendations without rebuilding them.

Signals also calm your nervous system. That matters. A vague role creates constant low-grade dread because you never know whether silence means approval, indifference, or future disappointment. Clear signals replace mind-reading with data.

So here is your checkpoint: take one active project and answer these four categories on a single page. If you cannot write down the Priorities, Ownership, Standards, and Signals without sounding slippery, the role needs a reset. Don’t overthink it. Draft the page and bring it into your next 1:1.

The hidden trap: doing useful work that earns gratitude, not advancement

One of the most painful early-career patterns goes like this:

You become indispensable in all the wrong ways.

Everyone relies on you. Everyone appreciates you. You are the one who catches things, smooths things, fixes things, reminds people of things, and quietly prevents small disasters. You get thank-yous. You get praise in chat. People call you “amazing” and “so helpful.”

Then performance review season shows up and suddenly the conversation is about ownership, initiative, business impact, strategic thinking, or leadership potential.

If you have lived this, you know how maddening it feels. You want to say, “Leadership potential? I have been holding half this circus together with a clipboard and caffeine.”

The problem is not that your work lacked value. The problem is that organizations reward some forms of value more visibly than others.

There is visible ownership, and there is support gravity.

Visible ownership means people can point to a result and say, “She drove that.” Support gravity means work keeps sliding toward you because you are competent, available, and easy to trust with the annoying stuff. Support gravity feels good at first because it gives you a constant drip of appreciation. It can also quietly colonize your job.

Let’s make this real.

Maya is a customer success associate at a mid-size SaaS company. She starts out helping her manager prep quarterly business review decks, taking notes in renewal meetings, cleaning up customer issue trackers, and doing quick polish passes on slides for sales. None of this is absurd. All of it is useful. She says yes because she wants to be seen as dependable and sharp. Also, if we are being honest, these tasks are emotionally safer than owning a gnarly retention problem with an unhappy client.

Six months later, she asks about growth. Her manager says, “I’d love to see you take on more strategic retention work.”

If you are Maya, your blood pressure goes up immediately. Strategic retention work? What did he think all these late nights were for?

But her manager is not fully wrong. She has been doing work that makes everyone’s day easier without owning a result that can be named. She is respected. She is not yet promotable.

What fixes it is not a dramatic speech. It is a scope correction.

In her next 1:1, Maya says: “I want to line up my time with the outcomes that matter most in this role. Right now a big share of my week goes to deck prep, meeting notes, and tracker maintenance. I can keep some of that, but I want to clarify which of those are core expectations versus support tasks, because I also want direct ownership of renewal risk analysis and churn reporting.”

That is a good sentence. Calm. Specific. No martyrdom.

Her manager realizes the drift. They hand off recurring notes to a rotating system, keep one tracker on her plate because it genuinely matters, and give her ownership of a churn-risk report reviewed in the Monday leadership meeting. Four weeks later, people can point to a business outcome she drives. Her stress drops. Her work becomes easier to explain. Her next review is a different conversation.

This happens constantly in less obvious ways too.

A junior marketer becomes the unofficial slide designer for every exec review.

An analyst becomes the person who can “quickly pull numbers” for anyone, which sounds flattering until you realize no one is protecting analysis time.

A recruiting coordinator becomes emotional support for hiring managers and candidates, which is admirable and completely invisible in most promotion rubrics.

An operations associate becomes the keeper of the master tracker, a role that somehow requires endless labor and receives almost no glory.

Some support work is part of the job. I am not telling you to act above admin. I am telling you to watch the ratio. If too much of your week disappears into low-ownership support tasks, and no one has explicitly said those tasks carry serious evaluation weight, your role is drifting into invisible labor.

There is also a psychological hook here that is worth naming because it catches smart people. Support work often gives you immediate positive social feedback. People thank you. The Slack message gets heart-reacted. You feel needed. Ownership work is different. It is slower, riskier, more public, and much easier to get wrong. So if you are anxious or still building confidence, your brain may prefer the work that earns instant appreciation over the work that builds long-term leverage.

That is human. It is also how careers stall.

Here is a rough test. Open your calendar and your brag doc—or start one if you do not have it. How many of your recent wins are outcomes with your name attached, and how many are support actions that made other people’s outcomes possible? If your list is all “helped,” “supported,” “coordinated,” “followed up,” and “assisted,” you do not need more hustle. You need a clearer scope.

Try this question in your next 1:1: “Looking at my current responsibilities, which ones matter most to how my performance will be evaluated, and which ones are useful support work but lower weight?” It is hard for a manager to answer that lazily. Good. Make them choose.

What to ask your manager — and how to reset scope without sounding lost

Most people are not actually afraid of the conversation.

They are afraid of the identity threat attached to the conversation.

They worry the manager will hear, “I’m confused,” and translate it to “I’m not capable.” They worry they will sound needy, junior, fragile, or like one of those employees who wants constant reassurance and a laminated life plan.

Usually that fear is exaggerated.

What makes you look junior is not asking direct clarifying questions. What makes you look junior is finding out three months later that you were solving the wrong problem while everyone politely watched.

Broad check-in questions produce broad, forgettable answers. “How am I doing?” invites politeness. “Anything I should do differently?” invites drift. If you want calibration, ask questions that force a useful response.

Here are five that earn their keep:

1. “What are the top three outcomes you most want from me this quarter, in priority order?”

2. “When tradeoffs happen, what should win?”

3. “What does strong performance look like here in concrete terms?”

4. “What should I spend less time on or stop doing?”

5. “How do you want me to raise scope conflicts when priorities collide?”

Those questions tell your manager something flattering and important: this person thinks in terms of outcomes, tradeoffs, standards, pruning, and escalation. In other words, like someone they can trust.

Now let’s get practical.

Script for a new role

Use this in a 1:1 or ask for a separate conversation:

“I want to make sure I’m putting effort against the right outcomes, not just staying busy. I’ve learned a lot in the first few weeks, and I can also see a few places where sharper scope would help me prioritize better. My current understanding is that my main responsibilities are [X], [Y], and [Z]. I’d like to confirm the top outcomes you want from me in the next 30 to 90 days, what I own directly versus what’s shared, and what strong performance looks like in terms of quality and speed. I also want to clarify what I should deprioritize when tradeoffs come up. After we talk, I’m happy to send a quick written recap so we have a shared reference point.”

What makes this good? You are not asking to be rescued. You are proposing calibration.

Script for a role that has drifted

This is for when the job started one way and now feels like a junk drawer:

“I want to reset on scope so I’m spending my time where it helps most. Over the last [month/quarter], my work has expanded across [A], [B], and [C], and I’m noticing tradeoffs that aren’t always explicit. I want to align on what matters most rather than spreading effort thinly across everything. From your perspective, what are the top outcomes I should drive right now? Which responsibilities are core to my role, which are shared, and what should move lower? I’d also like to define the early signs that show I’m on track.”

Again: no blame. No wounded energy. No “you have failed me.” Just specificity.

Script for conflicting stakeholder demands

If two people are pulling you in opposite directions, do not become the unpaid conflict-resolution department.

Say this:

“I’m seeing two valid requests that pull in different directions, and I want to make the tradeoff explicit instead of guessing. [Stakeholder 1] needs [X], and [Stakeholder 2] needs [Y]. Given my current priorities, which should take precedence? If both need to move, what would you like me to deprioritize?”

That sentence is clean enough to use verbatim. It prevents panic, protects your time, and teaches people not to smuggle all requests in as emergencies.

Script for “I’m doing a lot, but I’m not sure it counts”

This one is especially useful if you suspect your role has filled with support work:

“I want to check that the way I’m spending time matches how success in this role is judged. Right now a meaningful share of my week goes to [support tasks]. I’m happy to keep doing the right amount of that, but I want to understand which responsibilities carry the most weight in evaluation and where you want me to build clearer ownership.”

That is a mature sentence. It says, I respect the work and I respect my future.

There is also a timing issue. Don’t spring this on a manager at minute 28 of a packed 30-minute 1:1. Ask for a proper block. “I’d love to use our next 1:1 to align on role priorities and scope so I can plan the quarter well.” That sounds organized, not emotional.

And yes, your pulse may jump before the meeting. That is normal. Scope conversations often trigger a weird blend of fear and relief. Fear because you are naming uncertainty. Relief because at least now the uncertainty has a shape. Ask anyway. The electric relief of walking out of a good 1:1 with actual priorities is worth the 10 awkward minutes it took to get there.

After the conversation, send the alignment note

Do not trust memory.

Do not trust verbal summaries.

Do not trust the warm feeling of “I think we’re aligned.”

People leave the same meeting carrying different versions of reality all the time. Your manager is busy. You are busy. Everyone’s brain edits conversations in self-serving ways. If the scope conversation matters, write it down while the details are still warm.

This is not bureaucratic. It is self-defense.

A good alignment note does three things: 1. It confirms what was actually agreed. 2. It makes it easy for your manager to correct mistakes quickly. 3. It gives you a future reference point when priorities shift and everyone develops selective amnesia.

Here is a template that works:

Subject: Recap: role priorities and scope alignment

Message:

Thanks for talking this through today. I wanted to capture my understanding so I can prioritize correctly.

For the next 30–90 days, my top priorities are: 1. [Priority 1 outcome] 2. [Priority 2 outcome] 3. [Priority 3 outcome]

Current ownership: - Directly owned by me: [items] - Shared ownership: [items + with whom] - Lower priority / not core right now: [items]

What strong performance looks like: - Output / deliverables: [what needs to be produced] - Quality bar: [what “good” looks like] - Speed / cadence: [turnaround expectations]

Signals that I’m on track: - [Metric, milestone, or feedback indicator] - [Metric, milestone, or feedback indicator]

Open questions to revisit: - [question 1] - [question 2]

I’ll use this as my working guide unless you’d like to adjust anything.

That final line matters. It converts silence into implied agreement, which is often the highest form of approval you will get from a busy manager on a Wednesday afternoon.

If email feels too formal for your team, use Slack:

“Thanks again for talking this through. My takeaway is that my top priorities this quarter are [A], [B], and [C], with [A] winning when tradeoffs happen. I directly own [X], share [Y] with [person/team], and should spend less time on [Z] unless you tell me otherwise. Strong performance looks like [brief definition], and we’ll use [signal 1] and [signal 2] as checkpoints. If I’ve got any of that wrong, let me know and I’ll adjust.”

What this note really buys you is leverage later.

Imagine priorities change in three weeks, as they often do. Without a written recap, you are stuck saying, “I thought we were focused on…” which sounds defensive and slightly bruised. With a recap, you can say, “Based on our last alignment, I was prioritizing A and B. Has the focus now shifted to C and D?” Same issue. Much better posture.

Save these notes somewhere boring and searchable. Review them before performance conversations. When people panic before reviews, a lot of that panic comes from trying to reconstruct six months of expectations from memory and vibes. Your notes are evidence. Evidence is calming.

Your move: after your next scope conversation, send the recap within an hour. Not tomorrow morning. Not “when things calm down.” Immediately, before everyone’s brain rewrites the meeting.

What to do if your manager stays vague — and how to tell temporary mess from structural mess

Sometimes you do everything right and still get nothing useful back.

You ask for top priorities and hear, “Just keep taking initiative.”

You ask what strong performance looks like and hear, “You’ll know.”

You ask what to deprioritize and hear, “Everything is important right now.”

At that point, the issue is no longer your willingness to be clear. The issue is that your manager is either overloaded, conflict-avoidant, under-skilled, or operating inside a genuinely chaotic system.

Still, you have moves.

The best one is to stop asking your manager to invent structure from a blank page and start handing them a draft to edit. Many weak managers are terrible at generating clarity and perfectly adequate at reacting to it.

Try this:

“To make sure I’m not operating on assumptions, I drafted my current view of the role. My understanding is that my top priorities are [A], [B], and [C], that I directly own [X], share [Y], and should treat [Z] as lower priority unless there’s a specific need. I’m planning to work from that unless you’d like me to adjust anything.”

That is a different posture entirely.

You are not asking, helplessly, “Can you define my job?” You are saying, “Here is the model I’m using. Correct it if needed.” Editing is much easier than authoring. That matters.

Then make the ambiguity concrete using live tradeoffs, not abstract complaints. In your 1:1, bring current decisions:

“This week I have three competing pieces of work: finishing the customer analysis, helping with Friday’s deck, and cleaning up the CRM backlog. Based on our current priorities, I plan to focus on the customer analysis first and move the CRM cleanup to next week. Does that match your view?”

This is extremely effective because it forces decision-making where it matters: on actual work.

If the confusion continues, document the pattern cleanly. Not in an angry diary. In a factual running note: - March 3: priority stated as launch support - March 12: priority shifted to analytics cleanup - March 19: feedback focused on stakeholder responsiveness - March 26: asked to deprioritize reporting for deck support

You are not gathering evidence for a courtroom. You are trying to answer a practical question: is this a temporary wobble or a structurally messy environment?

Temporary ambiguity

Temporary ambiguity is annoying but survivable. It usually comes from transition: - A reorg just happened - A leader left - Your team is growing fast - Your manager is buried for a month - Your role is genuinely new

In these cases, clarity may be incomplete for a while, but the organization still believes in ownership, tradeoffs, and feedback. When you ask good questions and propose a draft, things improve. The mess is real, but it is not the whole operating philosophy.

Structural ambiguity

Structural ambiguity is different. This is when the system itself does not reliably define ownership, settle tradeoffs, or evaluate people against stable criteria.

Common signs: - Priorities reverse constantly with no acknowledgment - Multiple stakeholders direct your work and nobody arbitrates - Workload grows forever but nothing gets deprioritized - Criticism arrives late and surprises you - People talk nonstop about urgency and almost never about choice - Nobody can explain what a strong review would actually be based on - The same confusion keeps happening after repeated attempts to clarify

That last one matters. Any team can have a messy month. Structural ambiguity is what you have when the mess has tenure.

If you suspect that is what is happening, you may need a skip-level conversation. Not as a first move, and not as a complaint session. Frame it around alignment to team goals.

For example:

“I’m working to make sure I’m focused on the highest-value outcomes for the team this quarter, and I’d love your perspective on where this role creates the most impact. I want to make sure my priorities line up with the broader goals.”

That is strategic. It is not tattling.

Also, be honest with yourself if the environment remains impossible. Not every role can be fixed from below. Sometimes the conclusion is not “I need to communicate better.” Sometimes the conclusion is “This team runs on chaos, and I need to stop treating that as a referendum on my talent.”

That realization can feel depressing for about a day and liberating after that.

Sit with this question: if you disappeared for two weeks, would the team struggle because your work matters, or because nobody knows who owns anything? If it is mostly the second, you are not just in a hard role. You are in a structurally messy system.

Use this 10-minute scope audit once a month

You do not need one heroic conversation to protect yourself from role drift.

You need a recurring practice.

Once a month, block 10 minutes on your calendar and run a scope audit. Put it somewhere boring, like the first Friday of the month or the last Monday before your 1:1. Treat it like brushing your teeth. Not glamorous. Very useful.

Ask yourself these five questions:

1. If my manager had to name my top three priorities right now, would I know what they are?
2. Does my calendar reflect those priorities, or is my week disappearing into support work and random requests?
3. Can I clearly name what I own, what is shared, and what is outside my role?
4. Do I know what “good” looks like for my key deliverables in both quality and speed?
5. Do I have recent proof I’m on track, or am I waiting for review season to tell me?

If you answer “no” to two or more, that is not a moral failure. It is a maintenance alert. Schedule a reset conversation in the next week.

Then compare three things side by side: - Your manager’s stated priorities - Your actual task list - Your calendar

This sounds almost insultingly simple. Good. Simple systems get used.

And they reveal uncomfortable truths fast.

I have watched people insist their job is about analysis, customer growth, or strategic operations, then look at their calendar and realize they are spending half the week in internal coordination meetings, note-taking, and emergency clean-up for other people’s deadlines. Your calendar does not care about your narrative. It tells the truth.

Then update your brag doc. If you do not keep one, start now. Add wins tied to agreed priorities. Not “worked hard on launch support.” Write: - “Built weekly churn-risk report now used in Monday leadership review” - “Cut campaign QA turnaround from two days to same day” - “Closed ownership gap between support and product on escalation flow” - “Defined handoff template that reduced customer onboarding confusion”

The goal is to make your work visible in the same language your performance will be judged in.

This is also where tools and systems can help. Career Compass exists for exactly this practical layer of career management: building a personalized growth plan, tracking wins and career metrics, and getting regular coaching nudges so you do not wait until everything is on fire to reflect. Scope drift is much easier to fix in week four than month ten, when you are tired, resentful, and rehearsing defensive answers for your review.

So make it concrete. Put a recurring 10-minute “scope audit” block on your calendar right now. If this article did nothing else but get you to do that, it would still save some of you from a very stupid review conversation.

You do not need a perfect job description. Almost nobody has one in practice. But you do need a shared understanding of what matters, what is yours, what good looks like, and how progress will be judged. Without that, you are not being evaluated on performance alone. You are being evaluated on interpretation, politics, and whoever told the most convincing story about your work when you were not in the room.

That is too much risk to leave unattended.

Early in my career, I thought effort and skill would sort everything out. Sometimes they did. Often they did not. The older I get, the less romantic I am about this. Careers are shaped by craft, yes, but also by calibration. Work matters. Alignment decides whether the work gets counted.

So if your role feels fuzzy right now, do not shame yourself for failing to decode it telepathically. Run the scope check: Priorities, Ownership, Standards, Signals. Ask the pointed questions. Send the recap. Save the note. Repeat the audit next month.

Clarity is not a luxury.

It is part of the job.

And if nobody has handed it to you yet, go get it.