Better Career Positioning Helped Steve

When Being "Technical" Means You're Being Underestimated
 
Years ago I had a client named “Steve”. He was a talented engineer who told me that he was struggling to move into a management position. He was frustrated, confused, and a little angry.

"They keep saying that I need to be more strategic. But I am strategic. I just also happen to know how things actually work."
​
I had heard this complaint numerous times. People who are top performers at execution, who understand the technical aspects of their role and could easily spot operational inefficiencies — getting labeled as being too “tactical or "technical. And in a lot of organizations, that label can become restrictive.

Steve wasn't wrong. He was strategic, but he was being misunderstood and misidentified by the hiring decision-makers in his organization. And once that label sticks, it's difficult to change it. 

---

The "Technical" Label Problem

This often happens – especially when people are good at their job. You understand the details, you can troubleshoot problems, you speak fluently about processes and systems. You're reliable and you deliver. And then one day, you realize this expertise has become a trap.

You're seen as the person who does things, not the person who decides things. You're in the implementation meetings, not the planning ones. When leadership talks about "strategic thinkers," they're somehow not talking about you—even though you've been quietly shaping strategy through your decisions for years.

This is what happened to Steve. He'd spent 5 years helping to build his company's operational infrastructure. He'd designed their supply chain strategy, helped rebuild their vendor management system, and created the framework they used for all major operational decisions.

But in his performance reviews the feedback was: "Steve needs to think more strategically and then delegate the technical details."

It seemed ironic that the "technical details" they wanted him to delegate were actually strategic decisions about operations. He wasn't being too tactical—he was being strategic in a way the leadership didn't recognize.
 
What Our Assessment Revealed

As we always do, we had Steve complete the CAES Assessment Battery — not the “nice to know” type that tells you whether you're an "ENTJ", but the kind that helps us to understand how you actually think, manage complexity, decide, and create value.

Quickly it became clear: Steve wasn't a technical thinker who needed to become more strategic. He was a systems-level strategic thinker who'd been held back in a technical role. He should have been promoted long ago.

We found that his:

• natural thinking style was integrative. When presented with problems, Steve didn't just solve them—he redesigned the systems that created them. That's not technical thinking – it’s strategic thinking with a systems orientation

 

• communication style was full of details, so people assumed he was detail-oriented. But the assessment results enabled us to see that his attention to details served a specific purpose: building credibility and presenting a complete picture before making any recommendations. He was naturally building a foundation for his strategic proposals.

 

• value came from seeing patterns across domains. Steve’s pattern recognition enabled him to easily connect supply chain decisions to customer experience and to financial outcomes. Which is typically the kind of cross-functional thinking organizations claim they want from strategic leaders.

The problem wasn't Steve. The problem was that his strategic thinking looked different from what the decision-makers expected.
 
Strategic Styles Aren't One-Size-Fits-All

Too often people assume that strategic thinking always looks one specific way.
​
They expect strategy to sound like: “high-level vision”, “big-picture ideas”, and “future focused concepts”. The kind of thinking that seems impressive in board room presentations.

But some of the most powerful strategic thinking happens when it is grounded in understanding how systems actually work. By connecting “real world” operational reality to business outcomes, it builds strategy from the ground up rather than imposing it from the top down.

Both interpretations are strategic. But only the latter tends to get recognized that way.
​
Steve was actually playing chess while everyone thought he was just moving the pieces. His "technical" knowledge was actually systems understanding, which supported every strategic recommendation he made. When he suggested operational changes, they weren't just about efficiency—they were also about building competitive advantages.
But because he led with "here's how this works" instead of "here's my vision," people heard tactics instead of strategy.
 
How We Helped Steve Fix His Positioning Problem
 
Once we understood the root issue, the answer was clear. Steve didn't need to change who he was or how he thought. He needed to change how he communicated his strategic value.

We focused on three specific areas:

1. Reframing Steve’s expertise as strategic capability

Instead of "I designed the supply chain process," we repositioned it as "I architected a supply chain strategy that reduced costs by 22% while improving delivery times." It was the same work - just different framing. The focus shifted from what he did to why it mattered strategically.

2. Leading with business impact, following with operational detail

Detail-oriented people tend to lead with details – so Steve had to restructure how he presented ideas. Instead of explaining how something worked before getting to the value, he'd lead with the strategic outcome and then use operational details as supporting evidence. And this simple shift completely changed how people heard him.

3. Building a narrative of strategic contributions

We evaluated his past five years of work through a strategic lens. That supply chain redesign - had positioned the company to expand into new markets. The vendor management framework - had become a competitive differentiator. He'd been building strategy all along—he just hadn't been telling that story.
 
The Results

Later, Steve had a different conversation with his CEO.

Instead of defending himself as being “strategic”, he explained how his operational decisions had directly enabled their strategic growth plans. He connected patterns that evaluators missed. He reframed his role from "operations executor" to "strategic operations architect."

Not long afterward, Steve was offered a newly created management role: Strategic Operations Manager.

The work he was doing didn't change. His capabilities didn't change. What changed was how his value was understood and communicated.
 
What This Means for You

If you've been told you're "too technical" or "need to be more strategic," here's what you might consider:

Maybe you're not the problem. Maybe you're being strategic in a way that isn't being recognized.

Ask yourself:

• Do you solve problems by redesigning systems, not just fixing symptoms?
• Do you see connections between operational details and business outcomes?
• Do you build solutions that create long-term competitive advantages?
• Do you make decisions that shape how your organization operates strategically?

 
If you answered yes to these questions, you're already thinking strategically. You might just be communicating it in a way that gets misinterpreted. The good news? This is fixable. Not by changing who you are, but by repositioning how your value is perceived and communicated.
 
Why Assessment Matters

That’s why we ALWAYS start with assessment: you can't fix a positioning problem until you understand what's actually happening.

Steve thought his problem was that he wasn't strategic enough. His managers thought his problem was that he was too focused on technical details. The assessments showed us that both were wrong. The real problem was a mismatch between his strategic style and his managers recognition patterns. Without assessment, we might have spent a long time trying to help Steve to be "more strategic." This would likely have felt inauthentic to Steve - and wouldn't have worked anyway. Instead, we identified his actual strategic strengths and built a positioning strategy around them.

That's what good career development does. It doesn't try to make you into someone you're not. It helps you understand your value clearly enough that you can communicate it in ways others will recognize and reward.
 
The Bottom Line

If you're being labeled as "technical" when you know you're bringing strategic value, you're probably not imagining it. And you're definitely not alone.

The solution isn't to abandon your expertise or to start speaking in vague corporate platitudes about "vision" and "innovation." The solution is to recognize that strategic thinking comes in different forms—and to learn how to position your particular form of strategic thinking so it's recognized for what it is.

Steve was not unique. I've worked with engineers who were strategic product thinkers, finance professionals who were strategic business architects, and project managers who were strategic organizational designers. Although they had been misidentified as "technical," all of them were actually strategic thinkers whose style didn't match decision-makers expectations.

The difference between being seen as tactical versus strategic often isn't about capability—it's about positioning, communication, and narrative.
​
And that's something you can learn to change.
 
If this story resonates with you, you might be dealing with a similar positioning challenge. But it's one of the most solvable problems in career development. Sometimes the biggest breakthroughs come not from changing what you do, but from helping others see what you've been doing all along.

Article List