If you’ve ever been called the framework person, you’re not alone. For many Enterprise Architects, this moment will feel familiar:
You’ve done the work. Mapped the dependencies. Clarified the risks. Framed the decision. And then someone introduces you with a line like:
“This is our architecture lead. They’ll talk through the TOGAF stuff.”
It lands with a thud.
Suddenly, your strategic insight is reduced to a framework label. You’re seen not as a partner, but as the framework person.
If you’ve felt this, you’re not alone. And if you’re tired of it, you’re not stuck. But the change won’t come from speaking louder; it’ll come from repositioning what you do.
The Real Reason You’re Being Framed That Way
Being labelled the “framework person” isn’t just a branding issue. It’s a positioning problem, and it often begins with how architecture is introduced into the business.
In many organisations, architecture is framed in one of three ways:
• As a compliance requirement (“We need to tick the governance box.”)
• As a methodology(“We use ArchiMate, TOGAF, or insert framework here.”)
• As a technical alignment function (“They help IT match strategy.”)
None of these make the real value obvious.
They describe the tools, not the impact. And when your value isn’t understood, people focus on what’s visible: your diagrams, your models, your terminology.
That’s how you become the framework person, even when you’re aiming for much more.
The Language Gap: Speaking Architecture vs Driving Impact
Often, the problem isn’t what you know, it’s how you express it.
When you lead with “Let me show you the capability map,” you might think you’re setting context.
But what the business hears is:
This will take time. This will be theoretical. This isn’t helping me make a decision right now.
Contrast that with:
“Here are three places where business decisions get stuck, and how that shows up in delivery risk.”
Now, you’re no longer delivering a model. You’re framing a decision.
Architecture is a lens, not an output. The goal isn’t to show your knowledge; it’s to expose what needs to be decided, challenged, or corrected.
Frameworks Aren’t the Problem, They’re Just Not the Headline
Frameworks are useful. They provide structure, consistency, and discipline. Internally, they’re critical.
But externally, in rooms where strategy is being shaped, they’re rarely what earns attention.
The most effective architects understand this. They don’t lead with jargon. They lead with clarity.
They talk in:
• Trade-offs
• Constraints
• Investment priorities
• Business behaviour
• Timing and risk
They’re not dismissing architecture. They’re translating it.
How to Know You’re Being Seen as “the Framework Person”
There are patterns. If any of these feel familiar, you’re likely stuck in that perception:
• You’re brought in after a project is scoped
• Stakeholders request artefacts, not insight
• Your input is valued during delivery, but ignored during planning
• Strategy discussions happen without you in the room
It’s not that you’re not capable, it’s that you’re not being positioned for influence.
Shifting Perception: From Framework to Strategic Translator
Changing this dynamic takes intent. Here’s where to start:
1. Lead with outcomes, not artefacts.
“This model highlights where we’re overinvested, and what that means for delivery risk.”
2. Anchor your insights in decision-making.
“This isn’t just a system diagram, it’s a map of where work breaks down and why.”
3. Align to business rhythms.
“This matters most during budgeting, not just at go-live.”
4. Ask sharper questions earlier.
“What problem are we solving, and how will we know when it’s actually solved?”
The goal isn’t to stop doing architecture. It’s to make the impact of your architecture immediately relevant.
Final Thought: Your Value Isn’t in the Model, It’s in the Clarity You Create
The best architects aren’t just technical. They’re translators of ambiguity. They make the invisible visible. They connect delivery to purpose.
If you’re constantly being seen as “the framework person,” the answer isn’t to abandon the frameworks; it’s to stop leading with them.
Speak like the person who sees the real problem. Ask the question no one else is asking. And make sure your work doesn’t just align; it matters.