From Enterprise Architecture Transformation: A Practical Guide
Most of my enterprise architecture (EA) career has been as a consultant.
The assignments have varied quite a lot. Some have been clearly project-based: improving an EA practice, supporting a transformation, describing parts of the overall architecture, or preparing architecture content for a new initiative. In other cases, I have worked more like an external architecture resource inside the client organization. My longest assignment lasted around two years, which is already enough time to stop feeling like a brief external visitor. You may still have a consultant badge, but by then you also know where the coffee machine is and which steering group materials are mostly ceremonial.
At the same time, I have worked with many internal enterprise architects. That has made one thing quite clear: the title may be similar, but the structural position is different.
Internal enterprise architects and consultants often use the same concepts, methods, tools, and diagrams. They may participate in the same discussions and support the same decisions. But their mandate, access, incentives, and value logic are not the same.
Neither role is inherently better. They simply create different conditions for doing architecture work.
Continuity and Comparison
The internal enterprise architect usually has one major advantage: continuity.
Internal architects can stay with the same organization long enough to understand its history, constraints, politics, systems, operating model, and recurring patterns. They know which initiatives have been tried before. They know why some decisions were made. They also know which applications are officially strategic and which ones are, in practice, impossible to remove before retirement age. Sometimes the application’s retirement age, sometimes the architect’s.
This continuity creates organizational memory. Internal architects can see how decisions accumulate over time. They can recognize when a small local choice starts to become a wider pattern. They can connect current initiatives to earlier decisions and long-term direction.
But continuity also has a downside. Internal architects may become so familiar with the existing structure that some assumptions become invisible. They know why things are difficult, but they may also become used to the difficulty, or even be part of it. The internal role often creates depth, but not always distance.
The consultant usually brings a different advantage: comparison.
Consultants see multiple organizations, industries, operating models, and architecture practices. This makes it easier to recognize patterns that may be difficult to see from inside one organization. A consultant may quickly notice that a problem presented as unique is, in fact, a very familiar species. It may have slightly different coloring, but it belongs to the same family.
This external perspective can be useful. Consultants can challenge assumptions, bring reference models, introduce practices seen elsewhere, and accelerate work that the internal organization has not had time or capacity to structure. They can also sometimes say things more easily than internal people. Not always, but often.
The limitation is obvious enough. Consultants may not fully understand the organizational context. They may see the structural problem, but not the history behind it. They may recommend a perfectly sensible target state without understanding why the last three attempts to move in that direction failed.
Mandate and Access
Internal architects and consultants often have different access patterns.
An internal architect may have long-term access to people, forums, and informal knowledge. They can build trust gradually. They may know who really decides, who understands the dependencies, and where the real constraints sit. That kind of knowledge is rarely visible in an operating model diagram.
But internal access does not automatically mean influence. Internal architects may be present in many discussions and still have a weak mandate to shape decisions. They can become advisors whose input is appreciated, noted, and then quietly stepped over when delivery pressure arrives.
Consultants often enter through a more specific mandate. They may be hired to support a transformation, assess a situation, create EA deliverables, work as an architecture resource, or help solve a visible architecture-related problem. This can give them a clearer temporary role and stronger attention from leadership.
But the mandate may also be narrow. A consultant may be asked to produce a view, support a project, or assess a limited area without access to the wider decision-making context. This becomes difficult when the work is supposed to influence decisions that are actually made in leadership, portfolio, or transformation forums. Consultants can have a sharper entry point, but they do not automatically get access to the right tables.
Remote work can make this even more visible. If the consultant only meets the people included in formal calendar invitations, a large part of the organization remains outside reach.
Focus and Context
There is also a practical difference in daily work.
Internal architects often carry a broader mix of responsibilities around the architecture work itself: internal planning, governance routines, reporting, stakeholder coordination, tool maintenance, practice development, and many small requests that accumulate over time. Some of this work is necessary. Some of it is useful. Some of it is simply what happens when you are part of the organization.
Consultants are more often brought in for a defined assignment, which can allow them to focus more directly on actual architecture work. They may also be spared from some internal organizational work: recurring status meetings, internal alignment rounds, performance discussions, and political negotiations. This can make consulting work feel more efficient, at least within the boundaries of the assignment.
The trade-off is that some of those internal discussions are exactly where context, trust, and informal influence are built.
Internal architects often understand the surrounding organizational reality more deeply because they live inside it. Consultants may have more focus. But internal architects usually have more context.
Value Looks Different From Each Side
The value of internal architecture work is often indirect.
The internal architect may improve decision quality, reduce duplication, clarify dependencies, maintain organizational memory, and support coherence across initiatives. These effects accumulate over time. The organization may benefit significantly, but the contribution can be difficult to isolate. If things go better because someone helped prevent a bad decision, no one may notice.
There is no incident report for the architecture mistake that did not happen, which is unfortunate for those who enjoy measurable value.
The consultant’s value is usually more explicitly framed. There is a contract, assignment, deliverables, or business problem to solve. The work has a clearer commercial boundary. The consultant’s contribution is easier to connect to a defined engagement, even when the real value still depends on what happens after the consultant leaves.
This can make consulting value more visible in the short term. It also creates pressure. Consultants often need to demonstrate usefulness quickly. They may not have the luxury of building influence slowly over years. Their value needs to become visible within the rhythm of the assignment, sometimes after only a short time to understand the organization, its people, and its constraints.
Living With the Consequences
One important difference is that internal architects live with the consequences of decisions for longer.
If a principle is too abstract, they will see it ignored. If a platform decision creates friction, they will hear about it later. If a target state is unrealistic, they may need to explain it for years.
That creates practical discipline. Internal architecture cannot remain only conceptually elegant. It has to survive contact with budget cycles, delivery constraints, organizational habits, vendor contracts, legacy systems, and normal human behavior.
The internal architect also has to maintain relationships after difficult discussions. They cannot simply challenge everyone and leave. This makes the role relationally demanding. Influence depends heavily on trust, timing, and persistence.
Consultants face a different discipline. They need to create value before full context exists. They must learn quickly, ask good questions, identify patterns, and avoid confident recommendations based on incomplete understanding. Good consulting is not just bringing best practices from elsewhere. It is helping the organization understand its own situation more clearly.
A Career Perspective
There is also a career angle here. Working as an internal enterprise architect can build deep organizational understanding, long-term influence, and the ability to live with architectural consequences. These are valuable skills, especially for roles where architecture is closely connected to strategy, governance, portfolio work, or organizational transformation.
Consulting builds different muscles. It forces the architect to learn quickly, structure unclear situations, communicate value, and work across different organizational contexts. It can broaden perspective and make patterns easier to recognize, simply because you see more than one version of the same problem. Sometimes many versions. Organizations are creative, but not always in completely original ways.
Neither path is automatically better for career development. They develop different kinds of strength. Moving between the two can be especially useful: consulting can give breadth and comparison, while internal architecture can give depth and consequence. The important question is what kind of architect you want to become, and what kind of work will actually develop that direction.
Architecture Ownership Cannot Be Fully Outsourced
I do not think EA work can be owned only by consultants.
Consultants can support architecture work, provide capacity, bring external perspective, lead specific assignments, or work as architecture resources inside the client organization for a longer period. That can be useful, and I have personally done plenty of that kind of work.
But someone on the client side still needs to own the architecture direction, priorities, decisions, and long-term continuity.
That is different from using consultants as architecture support. The problem starts when the organization effectively outsources ownership of EA itself. Some consulting firms may offer this kind of service, and in some cases it may sound efficient. But EA is too closely connected to organizational memory, decision-making, internal priorities, and long-term accountability to be fully externalized.
Working Together
In many situations, the best results come when internal architects and consultants work well together.
Internal architects bring memory, relationships, and context knowledge. Consultants bring comparison, structure, focus, and external perspective. Together, they can create better outcomes than either could alone.
This requires mutual respect. Consultants should avoid treating internal architects as people who simply failed to solve the problem earlier. Often they have been carrying the complexity for years with limited mandate, time, or sponsorship. Internal architects should avoid treating consultants as outsiders who cannot possibly understand anything useful. Sometimes distance is exactly what helps reveal the pattern.
The useful question is not which role is better. The useful question is what kind of contribution the situation needs.
Internal enterprise architects and consultants often work with similar concepts, but under different structural conditions. The internal architect has continuity, memory, and long-term relationships. The consultant has distance, comparison, and a clearer assignment boundary.
Both can create significant value. Both can also create very little value if positioned poorly.
EA is shaped by methods, tools, and models. But it is also shaped by the position from which the architect works.
🗓️ On Work, Writing, and Making Room for What Matters
I published a short guest post in Finnish on a topic I keep coming back to: what happens when demanding expert work, writing, family life, and recovery no longer fit neatly into the same week.
In my case, the solution has been the four-day workweek. Not because it magically creates more time, but because it forces a different way of structuring work.
If you read Finnish, the post is here:
Kun kaikki tärkeä ei mahdu samaan viikkoon
🔗 You May Also Like
Looking to dive deeper? Here are more enterprise architecture insights you might find useful:
👨💻 About the Author
Eetu Niemi is an enterprise architect, consultant, and author.
Follow him elsewhere: Homepage | LinkedIn | Substack (consulting) | Medium (writing) | Homepage (FI) | Facebook | Instagram
Books: Enterprise Architecture | The Senior Expert Career Playbook | The Senior Expert Pay Playbook | Technology Consultant Fast Track | Successful Technology Consulting | Kokonaisarkkitehtuuri (FI) | Pohjoisen tie (FI) | Little Cthulhu’s Breakfast Time
Web resources: Enterprise Architecture Info Package (FI)
📬 Want More Practical Enterprise Architecture Content?
Subscribe to Enterprise Architecture Transformation for real-world advice on architecture that supports change, strategy, and delivery.
