Blog
Solution Architect vs Enterprise Architect: The Difference
Solution architect vs enterprise architect: how scope, time horizon, deliverables, and day-to-day work differ, and how the two roles work together.
TL;DR
- Enterprise architects shape the whole organisation's technology over years; solution architects design one initiative at a time.
- Enterprise architecture sets the direction and standards; solution architecture turns a specific need into something a team can build.
- In startups and smaller companies, the solution architect often makes some of the wider decisions too.
- Titles vary, so ask what scope someone owns and what question they're answering.
An enterprise architect looks at the whole organisation: which business capabilities, systems, and data it should have over the next few years, and how they fit together. A solution architect works on one problem or initiative at a time: what to build or change to solve it, and how that connects to the systems that already exist. Enterprise architecture sets the direction; solution architecture turns a specific need into a design a team can deliver.
At a glance
| Enterprise architect | Solution architect | |
|---|---|---|
| Scope | The whole organisation | One problem, project, or initiative |
| Time horizon | Years | Weeks to months, through delivery |
| Main question | What should our technology landscape look like? | What should we build for this problem, and how does it connect? |
| Typical outputs | Target architecture, capability maps, roadmaps, standards | Solution designs, options and trade-offs, integration and data designs, decision records |
| Works most with | Leadership, strategy, portfolio management | Product, engineering, business stakeholders, delivery teams |
| Detail level | Broad, abstract | Specific enough to build from |
What an enterprise architect does
Enterprise architects keep the organisation’s technology coherent as it grows. Their work usually includes:
- Mapping the business capabilities the organisation needs and the systems that support them.
- Defining a target architecture and a roadmap for getting there.
- Setting standards and principles: preferred platforms, integration patterns, data ownership.
- Spotting duplication, like three teams buying three tools for the same job.
- Advising on which initiatives to fund, based on how they fit the bigger picture.
Frameworks such as TOGAF are most associated with this role.
What a solution architect does
A solution architect takes a specific problem and designs how to solve it. The work usually includes understanding the problem and constraints, mapping the systems and data involved, comparing options, recommending one, and staying close during delivery. I cover this in more depth in what solution architecture is and what a solution architect does.
How the two roles work together
In a larger organisation the relationship looks like this: enterprise architecture says “we’re moving customer data into one platform and integrating through APIs”. A solution architect then designs how a particular project, like a new onboarding flow, fits inside that direction. When a project needs to break a standard, the solution architect brings the trade-off back to enterprise architecture instead of quietly working around it.
In smaller companies and startups there often is no enterprise architect. The solution architect (or a senior engineer acting as one) ends up making some of those wider decisions too, which is one reason it helps to write them down.
Where other architecture roles fit
- Software or application architects focus on the internal structure of one system: its components, code organisation, and interfaces.
- Technical or infrastructure architects focus on platforms, hosting, networks, scaling, and security.
- Data architects focus on data models, data flows, storage, and governance across systems.
Titles vary a lot between companies. The easiest way to tell the roles apart is to ask what scope a person is responsible for, and what question they’re answering.
Which one do you need?
If you’re shaping technology strategy across a large organisation, that’s enterprise architecture. If you have a specific problem, like a migration, a set of integrations, a build vs buy decision, or a project that has stalled, you need solution architecture. That’s the work I do; here’s how it works.