Over the years I have worked in enterprise architecture (EA) and consulting, I have designed and redesigned several EA practices. Of all the things you need to work out when setting up a practice, architect roles are probably the least interesting to me. They still get a surprising amount of attention in frameworks and online articles. I even discuss them in my own book, Enterprise Architecture: Your Guide to Organizational Transformation, so I am hardly in a position to complain.
In practice, the distinctions are rarely as clear as they look on paper. In one consulting assignment, I was the client’s only enterprise architect. I had to cover the organization-wide architecture as well as the work you might give to separate business, data, application, and solution architects. At another client, I spent several years as part of an architecture team. I worked on the overall architecture, modeled processes for specific business areas, and designed solutions for individual projects. One assignment had one enterprise architect and the other had a team. In both, my work covered several of the usual roles.
Some of that comes with being a consultant. But an internal architect can look after the same business area for years and still design a solution for one of its projects. Their ongoing responsibility is clear enough. What they do on any given Tuesday is another matter.
Architect titles are useful shorthand. The trouble starts when we treat them as a ready-made division of labor. I want to look at where those distinctions get awkward in practice, then at how I would divide the work based on what the organization wants EA to achieve.
Why the Roles Are Less Clear-Cut Than They Look
A list of architect roles can look quite tidy until you try to use it to divide the work. Even when everyone agrees on what the titles mean, you still need to know what people actually do, how much time the work takes, and who else needs to be involved. And once you have divided the work, you still have to deal with the dependencies that made it architecture work in the first place.
Role Definitions Vary
There is no generally agreed set of definitions for architect roles. Still, some roles have much the same core across organizations, even if the scope varies. A solution architect is generally responsible for working out how the main parts of a solution fit together. Some definitions stop at high-level design, while others include detailed component design. With application architect, the difference can be more fundamental: the title can refer to responsibility for the overall application landscape or to the design of individual applications.
The labels also describe different things. Solution suggests a scope, data a specialization, and lead a responsibility. Even domain can mean a business area such as finance or a perspective such as data. A finance architect can be responsible for processes, applications, and data within finance, while a data architect can be responsible for data across business areas. Both roles can be clearly defined and still share responsibility for finance data.
The Same Role Can Look Different in Practice
A general role description tells you what the job can include. An enterprise architect, for example, might be expected to maintain the overall architecture, advise projects, and help management plan strategic changes. That sounds like a varied job. In practice, one of those responsibilities can take up most of the week.
In one organization, keeping the current-state descriptions up to date may leave little time for anything else. In another, advising projects is the main job. Somewhere else, management regularly asks the architect to work through what a proposed change would mean across the organization.
All three jobs fit the same general description. What you actually spend your time on depends on what the organization needs most and what it makes time for. Department boundaries and the way people are used to working also matter. You may be expected to look across the organization, but how much you can influence depends in part on which teams involve you in their plans and when they bring you in.
Role Descriptions Mix Skills, Tasks, and Responsibilities
Architecture role descriptions often put skills, tasks, and ongoing responsibilities on the same list. That is fine as long as you can tell them apart. The trouble starts when a task gets assigned and everyone assumes the responsibility went with it. A competency profile tells you what someone needs to know. A job description tells you what they are expected to spend their time doing. A role description should make clear what they are responsible for over time and what they can decide.
Take customer data. Knowing how to model it is a skill. Reviewing the customer data model for a new sales application is a task. Keeping the organization’s shared definition of a customer up to date is an ongoing responsibility. If sales and billing use the term differently, agree on who works with both teams to draft a shared definition, who has the authority to approve it if the teams disagree, and who keeps it up to date. Those responsibilities can sit with different people, and the decision can sit with someone outside architecture.
Role Descriptions Leave the Actual Work Vague
Architect role descriptions often name tasks without explaining what they involve in practice. Take provides architectural guidance. This is one of the clearer tasks on the list, and it still leaves the project team guessing when to involve the architect and what help to expect.
Does the architect help the team understand what is already in place and compare options while it still has a choice? Or do they review a design the team has already put together? Both count as guidance. In the first case, the architect can help shape the solution. In the second, they may get to explain why the team should have called earlier.
I would spell out what the architect does and when. Before the team commits to an approach, the architect helps it check whether an existing solution could meet the need, compare the alternatives, and identify dependencies that could affect other projects. That gives the team a reason to call and tells them when to do it. Another paragraph defining solution architect would do rather less.
Role Boundaries Can Hide Dependencies
At one organization, I saw one person draw the business process for a solution architecture description and another draw the connections between the applications supporting it. Move a process step to another application and you may change where data is entered, which systems need it, and how the process works. Sure, you can split the drawing. But the design still has to be worked out together.
The same problem comes up when several architects maintain the current state and plan the target state. You can divide the work by perspective or by business area, but how do you manage dependencies across perspectives once the work is divided? Data, for example, is tied to the processes that create it and the applications that use it. If the target state calls for retiring an application, someone needs to trace those dependencies and work out what has to change first. A data architect can look after a shared model and lead the work on a common standard. The people whose processes and applications will change still need to work through the implications together.
The Workload Varies More Than the Role Lists Suggest
In a small organization, one person may maintain the overall architecture, support projects, and coordinate the practice. If the architecture stays at a high level and only a few initiatives need support, there may not be enough work for even one full-time architect. You can give those responsibilities separate names if that helps. You still have one person who may be doing architecture alongside another job.
A large, complex organization may have enough work for dedicated business, data, application, and technology architects, many solution architects supporting projects, and several leads coordinating work across different areas. The volume of descriptions is only part of it. You also have more plans to reconcile, more people to involve, and more dependencies across areas that may have their own priorities. Dividing the work can make it manageable. It also creates coordination work that someone needs time to do.
Role Lists Leave Out People the Practice Depends On
A list of architect roles tells you who does the architecture work. It often leaves out the people who contribute to it, use it, or make decisions based on it. Business and IT specialists, process modelers, product owners, and project teams all know things architects need to know. They can also use the architecture to set priorities or change the scope and design of a project. In my experience, architects usually prepare and influence decisions; a CIO, business leader, or steering group may make them. An architecture director may have the mandate to approve certain principles or standards.
Two responsibilities can also go unassigned within the practice itself. The practice lead sets priorities, coordinates work across areas, and checks whether the results are being used. The practice owner or sponsor gives the work a mandate, secures resources, and makes room for architecture in planning and decision-making. One person can do both if they have the time and authority. The distinction matters when the lead needs to change a planning process they do not own.
Start With What You Want Enterprise Architecture to Achieve
When designing an EA practice, I would start by asking what the organization wants EA to help it achieve. Better investment decisions, better solution designs, and a more coherent plan for a transformation are all reasonable aims. Each calls for different work. Once you know where EA is meant to help, you can work out what needs doing and how it fits into the way the organization already works.
Take investment planning. If the aim is to avoid buying applications that duplicate what the organization already has, someone needs to keep enough portfolio information up to date to spot the overlap. The architect should get involved while the team is still defining the need, before buying a new application becomes the assumed solution. That gives them time to check with the team whether an existing application could meet the need and get the findings to whoever decides on funding before the money is committed. This tells you what information to maintain, who needs to be involved, and when the work has to happen.
Then I would group activities that make sense to do together and agree who looks after the ongoing work. How you assign those responsibilities depends on the volume of work, the expertise it requires, and the time people have. A role describes a set of responsibilities. One person can cover several roles, and several people can hold the same role for different parts of the organization. If the work becomes part of someone’s existing job, agree on what they will spend less time doing. If it is shared across teams, agree on who will coordinate it.
By then, the role names are usually the easy part. You know what the work is for, what people need to do, and what they can expect from one another. That whole arrangement is what I call the EA operating model.
What Role Descriptions Should Make Clear
Once you have worked out how the EA practice should operate, use the role descriptions to record the agreements people need to work together. Project teams should know when to involve an architect and what help to expect. Architects maintaining different parts of the current and target states should know who keeps track of dependencies across them. When a proposed standard affects several areas, make clear whose input is needed and who can approve it.
I would also make sure the responsibilities people take on are reflected in their formal job descriptions. One job can cover several roles. If someone is expected to coordinate the EA practice alongside their regular work, that responsibility needs to show up both in their job description and in the time their manager sets aside for it. Otherwise, the practice and the manager can end up counting on the same hours for different work.
At the organization where one person drew the process and another connected the applications, either person could have drawn the whole thing. The important agreement was how they would work out the design together and involve the people who had to make it work. Who drew which line was the easy part.
🔗 You May Also Like
Are you looking to dive deeper? Here are some related articles you might find useful:
👨💻 About the Author
Eetu Niemi is an enterprise architect, consultant, and author.
Follow him elsewhere: Homepage | LinkedIn | Substack (expert work) | 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 strategy, change, and delivery.





