What is solution architecture, and what does a solution architect do?
Solution architecture is the work of understanding a business or technical problem and designing how systems, data, integrations, and processes should fit together to solve it. A solution architect (also called a solutions architect) owns that design, turning a vague need into a clear plan that a team can build, along with the trade-offs behind it.
By Dino Correia · Updated
What is solution architecture?
Solution architecture sits between a problem and its implementation. Its question is narrower than enterprise architecture (how should the whole organisation's technology fit together?) and broader than software architecture (how should this one application be structured?). For one specific problem, it asks what to build, what to reuse, and how the pieces connect.
The output is usually a short set of decisions and diagrams: which systems are involved, where data lives and how it moves, what gets integrated rather than built, which constraints apply, and which options were considered and rejected. In IT, solutions architecture most often means exactly this kind of design across several existing systems, rather than the inside of a single application.
What does a solution architect do?
A solution architect spends less time writing code than most people expect and a lot more time asking questions. The work usually covers:
- Understanding the problem: who has it, what it costs them, and what solved looks like.
- Gathering requirements and constraints, such as budget, deadlines, regulation, existing systems, and the skills of the team that will build and run it.
- Mapping the current state: the systems, data flows, and integrations already in place, and where they break.
- Designing a few realistic options and comparing them on cost, risk, complexity, and time to deliver.
- Recommending one and writing down the decisions behind it, including what was ruled out and why.
- Staying close during delivery, because the hardest questions tend to appear once real data and real users arrive.
A technical solution architect goes deeper into APIs, data models, infrastructure, and security. Other solution architect roles sit closer to the business, product, or pre-sales side. Titles vary a lot between companies, but the shape of the job is the same.
The solution architecture process
Every team names the steps differently. This is the version I use, and the order matters more than the labels:
- 1
Understand
Learn the problem in the words of the people who have it, before choosing any technology.
- 2
Question
Challenge the assumptions in the request. What someone first asks for is often a symptom of the real problem.
- 3
Explore
Sketch several options, including buying, integrating, changing a process, or not building anything.
- 4
Compare
Weigh the options against the constraints: cost, risk, complexity, time, and what the team can maintain afterwards.
- 5
Decide
Pick one, record why, and agree on what would make you revisit the decision.
- 6
Build
Deliver in small steps and keep checking the design against what you learn along the way.
Solution architecture vs enterprise, software, and technical architecture
The four overlap, and organisations draw the lines in different places. In short: enterprise architecture covers the whole organisation over years; solution architecture covers one problem or initiative across several systems; software architecture covers the structure of a single application; technical architecture covers the platforms and infrastructure it runs on.
The comparison people search for most is solution architect vs enterprise architect: how their scope, time horizon, deliverables and day-to-day work differ, and how the two roles work together.
Solution architect vs enterprise architect: the full comparison →
When to bring in a solution architect
Not every project needs one. It tends to be worth it when:
- The problem touches several systems, teams, or data sources, and nobody owns the whole picture.
- Requirements are vague, or different stakeholders are describing different problems.
- You are about to make a decision that is expensive to reverse, like a platform choice, a data migration, a major vendor, or a core data model.
- A project has stalled and nobody can say whether the cause is technical, organisational, or both.
Solution architecture consulting is usually short and front-loaded: a few weeks of discovery and design that end in a clear recommendation, rather than a long build engagement. That early part is where I spend most of my time.
I did this work as a tech lead at a London fintech, and do it now for my own products. See what I've built, how I build on AWS, the decisions in my case studies, or how we could work together. If you have a problem like this, let's talk.
Frequently asked questions
What is a solutions architect?
A solutions architect is the person responsible for designing how technology solves a specific business problem. They work out the requirements and constraints, compare options, and decide how systems, data, and integrations should fit together before and during implementation.
Is it solution architect or solutions architect?
Both names describe the same role. "Solutions architect" is more common in job titles at cloud providers and software vendors, while "solution architect" is common inside organisations and in architecture frameworks such as TOGAF. The work is the same.
What is another name for a solutions architect?
Systems architect, technical architect, solutions consultant, or technical solutions consultant - the exact title depends on the company and the role.
What is meant by solution architecture?
It is the process of understanding a business or technical problem and designing how the different systems, data, technologies, integrations, and processes should work together to solve it.
What is software architecture?
The high-level structure of a software system: its components, responsibilities, relationships, data flows, interfaces, and the decisions that shape how it works and evolves.
What are the four types of architecture?
Common categories include enterprise architecture, solution architecture, software/application architecture, and technical/infrastructure architecture. Definitions vary between organisations.
Will AI replace solution architects?
Probably not. AI will automate more implementation and analysis work, but understanding ambiguous problems, challenging assumptions, making trade-offs, and aligning technical solutions with real-world needs still requires human judgment.
Do solution architects need to code?
Not necessarily, but a strong technical understanding and the ability to read, prototype, and reason about code go a long way.
Is solution architect an IT role?
Usually, yes, although good solution architecture sits between technology, business, product, data, and operations.
Is a solutions architect role stressful?
It can be. You often deal with ambiguity, competing requirements, technical constraints, and high-impact decisions. The right environment can make it intellectually challenging rather than constantly stressful.
Is solutions architect a good role?
For someone who enjoys discovery, problem solving, systems thinking, and technical decision-making more than constant implementation, it can be an excellent role.
What personality traits do solution architects have?
Curiosity, analytical thinking, systems thinking, communication, pragmatism, patience, healthy skepticism, and a willingness to challenge assumptions.
Why do I enjoy working as a solution architect?
Because I enjoy the part before the code: understanding complicated problems, discovering what actually needs to be solved, exploring alternatives, weighing trade-offs, and figuring out how the pieces should fit together. Turning ambiguity into clarity is the part I find most interesting, and because I'm an engineer too, I like staying on to help build what we designed.
Have a question about working with me instead? See the general FAQ, or read more about me.
