Not Strategic Enough? Here’s What Your Manager Is Probably Actually Complaining About

“Be more strategic” is maddening feedback because it sounds both vague and expensive.

It lands like your manager just informed you that everyone else came with some deluxe workplace operating system, and you’re still running the free version. If you’re early in your career, it can trigger a very particular spiral: you replay old project updates in the shower, Sunday night starts humming louder than usual, and your next 1:1 begins to feel less like a conversation and more like a performance review pop quiz.

Underneath all that noise is the thought people often don’t admit even to themselves:

Are they saying I can do the work, but I’m not the kind of person they picture growing here?

Usually, no.

Usually, “not strategic enough” is lazy umbrella feedback for a much smaller problem: your judgment is either underdeveloped in one specific area, or it’s happening privately in your head instead of visibly in your work.

That is better news than it sounds. It means you do not need a personality transplant. You need a clearer signal.

The short version

• “Not strategic enough” usually means one of five things: weak prioritization, no recommendation, narrow ownership, poor stakeholder awareness, or updates that describe motion without meaning.
• Early-career strategy is not about sounding like a mini-CEO. It is about showing that you understand outcomes, timing, tradeoffs, and people.
• A lot of smart employees are thinking reasonably well and communicating terribly. Managers then assume the thinking never happened.
• The fix is not to inflate your language. The fix is to make your reasoning easier to see.
• In your next 1:1, do not defend your effort. Get one example, one missed behavior, and one chance to practice it differently.

First: stop treating this as a verdict on your potential

The fastest way to make this feedback useless is to turn it into an identity.

You hear one fuzzy sentence and instantly translate it into something much harsher: - too junior - too tactical - not leadership material - dependable, but not impressive - good at doing, not good at thinking

That spiral makes emotional sense. Ambiguous criticism is like catnip for insecurity. Your brain hates an empty space, so it fills it with whatever fear was already pacing around the apartment.

But most managers are not making a grand statement about your ceiling. They are reacting to a visible gap in behavior.

And what’s visible is usually pretty ordinary: - the update where you reported progress but not implications - the meeting where you raised a problem but offered no point of view - the project you executed cleanly without questioning whether it deserved that much effort - the stakeholder you forgot until they became a blocker - the risk you noticed but never said out loud

That is not a fate. That is a fix.

So separate who you are from what they saw. “I’m not strategic” is a dead-end sentence. “My manager did not see prioritization and tradeoff thinking in how I handled that launch” is painful, but at least it points somewhere.

Here is the grounding question to bring into your next conversation: What observable behavior would have made them describe me differently? Write your answer before the meeting, even if it’s rough. That one question pulls the problem out of the swamp of vibes and back onto solid ground.

What managers usually mean when they say “strategic”

Managers love using the word strategic the way people use the phrase communication issues: broadly, lazily, and with just enough confidence to make you feel underqualified.

So let’s translate.

What they said	What they may actually mean
“I want you to be more strategic”	You start doing the work before clarifying what matters most
“This feels too tactical”	You completed the assignment but ignored the larger problem around it
“I’d like stronger strategic thinking”	You keep bringing updates instead of recommendations
“Think more strategically about stakeholders”	You’re not factoring in who needs buy-in, who gets disrupted, or who can stop this cold
“Take a more strategic lens”	I need to hear goals, risks, tradeoffs, and implications—not just activity
“Show more ownership”	Stop acting like your responsibility ends at your checklist

Look at that table for a minute and notice what is not required: genius, charisma, or executive mysticism.

What is required is judgment with range. Professional maturity. The ability to see one layer past your own task.

Before your next 1:1, take the exact phrase your manager used and write down three possible translations. Do not walk into that meeting carrying only the original vague sentence. Fog is where bad feedback goes to survive.

What “strategic” actually looks like when you’re not the boss

This is where a lot of early-career people get misled. They hear “strategic” and imagine they’re supposed to march into a meeting and casually redesign the company’s future while everyone else updates a spreadsheet.

No.

If you are not setting company direction, strategic behavior is much less glamorous and much more useful. It looks like: - knowing which task matters most when everything arrives marked urgent - noticing that solving today’s problem creates next month’s mess - understanding who needs a heads-up before the work can actually move - making a recommendation instead of dropping three options on your manager’s desk like a waiter who forgot the specials - asking whether the requested work supports the team goal, not just whether it is technically possible

The people who get described as strategic are often not the most polished people in the room. They are the people who reliably show they understand consequence.

Here’s the difference in practice.

Tactical update:
“The deck is done. Waiting on feedback.”

Strategic update:
“The deck is ready. The bigger decision is whether we optimize for speed or for smoother alignment across Sales and Product. I recommend one more review round, because a fast rollout is likely to create preventable churn for the teams using it.”

Same project. Same employee. Completely different signal.

One says, “I finished the assignment.”
The other says, “I understand the decision underneath the assignment.”

Pick one recurring update you send every week and rewrite it in that second format today: goal, risk, tradeoff, recommendation. You do not need a promotion to start sounding like someone who sees the whole field.

The embarrassing detour: performing strategy instead of showing judgment

Once people get this feedback, many of them enter a deeply uncomfortable phase where they try to sound strategic.

Suddenly every sentence contains “leverage,” “cross-functional alignment,” “north star,” or some other phrase that sounds like it was assembled by a management consultant in an airport lounge. The wording gets shinier. The thinking gets blurrier.

This is not strategy. This is camouflage.

Managers rarely trust people because they sound important. They trust people because they are clear, useful, and reality-based.

Useful sounds like this: - “If we do A now, B slips by two weeks.” - “Legal needs to see this before we announce anything.” - “This request conflicts with the Q3 priority we already agreed to.” - “Option one is faster; option two reduces rework later.” - “Here’s my recommendation and what I’m optimizing for.”

That’s it. That’s the whole magic trick. No TED Talk voice. No jargon fog. No verbal peacocking.

If you suspect you’ve been compensating with polished vagueness, be ruthless on your next call. Cut one fluffy phrase and replace it with one concrete tradeoff. You will sound calmer, smarter, and much more senior than the person still trying to “elevate the stakeholder journey.”

The fastest way to improve: pin the feedback to one example

Do not respond to “you need to be more strategic” by defending how hard you worked.

Do not recite your accomplishments like a lawyer building a case.
Do not insist that you were thinking about the bigger picture.
Do not give a heartfelt speech about effort.

Effort is not the dispute. Visibility is.

What matters is the gap between what you thought and what your manager perceived. You need a diagnosis, not a self-defense memo.

Ask these instead: - “Can you point to one specific project or moment where this showed up?” - “What would a stronger version of my approach have looked like there?” - “Was the gap in my prioritization, my communication, or the scope of how I looked at the problem?” - “What would you want to hear from me next time that would signal better judgment?” - “Where will I have another chance to practice this in the next few weeks?”

These questions do two things at once. They calm you down, because specifics are less terrifying than abstraction. And they gently force your manager to stop hiding behind executive-sounding mush.

Sometimes the uncomfortable truth is that your manager has been lazy. They know they’re dissatisfied; they just haven’t bothered to articulate why. You are allowed to politely demand a better explanation than “be more strategic.”

Try This: after the conversation, send a recap note:

“My takeaway is that you want to see clearer prioritization, more explicit tradeoffs, and a recommendation in project updates—not just status. I’m going to start framing updates that way and would appreciate feedback over the next few weeks on whether that’s the right adjustment.”

That is not administrative tidiness. That is career self-defense.

Most cases fall into one of three buckets

Once you force the feedback into specifics, the issue usually lands in one of three buckets. This matters, because each bucket needs a different fix. If you confuse them, you can work very hard and still look unchanged.

1. It’s a thinking problem

This is the hardest version to hear and the most valuable one to know.

Sometimes you really are not prioritizing well yet. You’re treating every request like it deserves equal urgency. You’re solving what was asked without testing whether it matters. You’re missing second-order effects because your experience is still under construction.

That is not a moral failure. That is called being earlier in the learning curve.

If this is your bucket, stop asking for reassurance and start asking for context. In meetings, use your curiosity more aggressively: - “What are we optimizing for here?” - “If this slips, what takes the hit?” - “Which stakeholder matters most in this decision?” - “What would make this a successful outcome?”

Those questions are not signs of weakness. They are reps. And reps are how judgment gets built.

2. It’s a communication problem

This one is wildly common.

You saw the risk. You had a view. You made a decent decision. But you kept all the reasoning in your own head, and everyone else received the stripped-down version with none of the logic attached.

This is the competent-but-invisible trap. Strong work. Thin narration. Low trust.

If this is your bucket, narrate your reasoning without turning every update into a hostage situation. Use this structure:

What we’re trying to do → what could complicate it → the tradeoff → my recommendation

For example:

“We’re trying to ship before the client review next Friday. The risk is that Design hasn’t approved the latest changes. We can move now and risk revision churn, or wait 48 hours and reduce rework. I recommend waiting.”

Brief. Clear. Human. Trust-building.

Take a recent message you sent and see what’s missing. Did you include the recommendation, or just the weather report?

3. It’s a scope problem

In this bucket, you are doing your assigned work well—but acting as if your responsibility ends at the edge of the ticket.

You finish your part and mentally clock out. You don’t think much about adoption, dependencies, downstream pain, stakeholder reactions, or what happens after launch. Managers often label this “too tactical,” but what they mean is simpler: you are working inside the task, not around it.

The fix is not to suddenly own the whole company. The fix is to widen your frame by one layer.

Ask: - Who else does this affect? - What could block this from working in practice? - What needs to happen before or after my part? - If this goes badly, where will the pain show up first?

Pick one project you’re touching this week and answer those four questions before your next update. That alone will make you sound different.

If this feedback stings more than it should, here’s why

Sometimes this lands so hard because you are already trying like hell.

You care. You catch details. You stay late. You fix the thing nobody else noticed was broken. And then somebody says you’re “not strategic,” which can feel like being told your effort is invisible and your competence is somehow lower-grade than you thought.

That sting is real. So is the resentment.

Organizations have a cruel little rule: people evaluate what they can see and interpret, not the effort you privately poured into making things work. Hidden care gets discounted. Silent tradeoff thinking gets mistaken for obedience. Quiet competence gets labeled “solid, but junior.”

Unfair? Frequently.
Common? Absolutely.

A lot of career frustration comes from confusing doing good work with being perceived as someone with good judgment. They overlap, but they are not the same thing. If people cannot see the reasoning, they often assume there wasn’t much reasoning there.

So sit with this question for a minute: Where am I making decent decisions that nobody else can currently see? Your answer is probably the start of your development plan.

Build your reputation in the boring moments

People love to imagine careers are shaped by big presentations, dramatic launches, and heroic meetings where someone finally notices your brilliance.

Mostly, no.

Your reputation is built in the repetitive, semi-dull moments that barely feel important while you’re in them: - the Monday status update nobody wanted to read - the Slack message where you frame a risk clearly - the cross-functional meeting where you name the dependency everyone else was politely circling - the 1:1 where you bring a recommendation instead of a bag of unresolved facts - the project note where you connect your work to a team priority instead of expecting effort to earn automatic credit

That’s why this kind of improvement does not require a cinematic reinvention. It requires consistency in small, almost forgettable places.

Your Move: choose one channel for the next month—status emails, Slack updates, team meetings, or 1:1s—and practice being more legible there. Not everywhere. One place. Get sharper in public in a repeatable way. That’s how people start describing you differently before your title changes at all.

If you want a structure, steal this one: - Goal: What are we trying to achieve? - Current state: Where does it stand? - Risk: What could derail it? - Tradeoff: What are we balancing? - Recommendation: What do I think we should do?

Use it for four weeks and watch how the temperature changes around your work.

What to bring into your next 1:1

Do not walk in hoping the conversation magically becomes useful because you have good intentions and a notebook.

Bring structure.

Write down: 1. The exact phrase your manager used 2. One or two examples where you think it came from 3. The questions you need answered 4. One adjustment you plan to test

You could say:

“I’ve been thinking about your feedback that I need to be more strategic, and I want to make sure I’m interpreting it correctly. Could we look at one recent example? I’d like to understand whether the gap was in my prioritization, my recommendation, or how I communicated the broader impact.”

That opening does something powerful. It shows you are not pouting, posturing, or guessing. You are treating feedback like a problem to solve.

And when a 1:1 goes well after that, the relief is almost physical. Your chest unclenches. The meeting stops feeling like a trap. You leave with something solid instead of carrying one vague sentence around like a brick in your backpack for another week.

Specificity creates that relief. Go earn some.

Turn vague feedback into visible progress

What makes this kind of feedback so corrosive is not just the comment itself. It’s what happens after, when you try to improve in private.

You overthink at night. You promise yourself you’ll “show more leadership” somehow. You work harder in three random directions at once. You hope your manager notices an aura change. It’s exhausting, and it usually doesn’t work.

The better move is boring and much more effective: turn the feedback into behaviors you can repeat and track. Get the example. Name the missing signal. Practice one visible adjustment. Watch what changes. If people start responding differently to your updates, trusting your calls more quickly, or asking for your view earlier, that’s evidence—not just a better mood.

That’s also where a tool like Career Compass can actually help, because career growth is hard to do on vibes alone. When feedback is fuzzy, it’s useful to have a place to turn it into a concrete plan, notice patterns in your week, and track whether you’re becoming clearer, calmer, and more trusted over time—not just more anxious and compliant. Progress is easier to sustain when you can see it.

And that’s the real mindset shift here: “not strategic enough” is usually not a verdict handed down from the mountain. It is incomplete feedback about visible judgment. Treat it that way. You do not need to become a different species of professional by next Tuesday. You need to make your thinking easier to see, in the ordinary moments, often enough that other people can finally trust what may already be there.