Who Needs a Solutions Architect?
I was in a meeting with a customer who had a firm requirement but needed to agree on how best to approach it. Several teams were involved, including management, developers and business stakeholders. The requirement was presented, and everyone had their own ideas about how best to approach it. To be fair, none of the ideas were unreasonable.
However, as the discussion progressed, objections were raised, counterarguments were volleyed back, and a few small political battles were being fought. I could sense them, even if I didn't fully understand the context behind them. As a Solutions Architect, my job was to help everyone get clarity on the requirement and reach a consensus on what to do next.
An hour later, after cutting through the noise, separating what mattered from what didn't and working through the competing priorities, we'd finally agreed on a way forward.
Interestingly, nobody had necessarily been wrong. They'd simply been looking at the same problem through the lens of their own responsibilities and concerns. As a group, they'd benefited from having a Solutions Architect in the room. But what did each of them need from me?
Usefulness is in the Eye of the Beholder
Being the curious fella I am, I decided to ask my peers: What is a Solutions Architect?
I first asked a Technical Documentation Lead, who emphasised product expertise and engineering skills, describing a Solutions Architect as someone with:
“in-depth knowledge of the product and outstanding engineering and communication skills.”
Next, a Customer Success Manager focused on technical design, explaining that:
“the SA owns translating the customer's requirements into a concrete technical design.”
A fellow Solutions Architect saw things differently, explaining that:
“while we are not the technical stewards of any project or team, it's our job to make sure those people have what they need to be successful.”
And finally, a Partner Engineer described the role as:
“A ninja who acts as half project manager half technical guru.”
The Customer Success Manager sees the SA as the technical counterpart to their own role, responsible for translating customer requirements into a technical design. The fellow Solutions Architect, however, emphasises supporting the people who own the project rather than owning it themselves. These aren't necessarily contradictory, but they reveal different expectations of the role.
The Partner Engineer sees someone who combines technical expertise with visibility across the project, while the Documentation Lead emphasises product knowledge and communication skills. You'd be forgiven for thinking they were describing completely different roles.
Four responses to the same question, each offering a different perspective. The same Solutions Architect is being described through the lens of each person's responsibilities.
In Their Shoes
Any Solutions Architect worth their salt instinctively understands that they need to adjust their language depending on who they're engaging with.
People in different roles have different priorities and therefore require different things from the SA, just like our examples above. Some require immediate, in-depth technical information. Others need confidence in their strategy through discussion. Then there are those who require regular sessions, with a clear schedule and agenda, to help their teams learn.
However, it's also the SA's job to balance these competing perspectives.
Think back to the customer meeting I described earlier. In a meeting like that, management might want clear deliverables, timelines and success criteria. Business stakeholders want confidence that their requirements will be satisfied. Meanwhile, developers want to understand the technical implications and constraints.
The Solutions Architect needs to ensure that everyone is working towards the same outcome, even when their individual priorities differ. So the job isn't simply to come up with 'solutions', but also to manage expectations and reconcile competing requirements.
Good Solutions Architects Stay Close to Engineering
In his 2003 essay Who Needs an Architect?, Martin Fowler introduces two species of architect. The Architectus Reloadus, who operates from above, making important architectural decisions and directing the engineering team. And the Architectus Oryzus, who works alongside developers, collaborating, mentoring and guiding them towards better solutions.
My experience as a Solutions Architect doesn't quite fit either species. I'm expected to recommend architectural solutions and provide technical direction to customers, but I don't own their implementations. I work with internal Engineering and Product teams to communicate customer requirements, investigate limitations and influence product improvements, but I don't direct their work either. And when the product doesn't have a ready solution for a customer's requirements, I investigate, design and often write code to demonstrate that my proposed solution is technically viable.
I find myself hovering somewhere between Fowler's two species, which perhaps gives birth to a third type: Architectus Consiliarius, the advising architect. An architect who must influence decisions they cannot enforce, validate solutions they may never implement, and guide engineers they do not manage. I suspect this describes plenty of Solutions Architects across different industries.
It is my belief, you may disagree, that a good Solutions Architect sits closer to engineering than circling from above. Solutions exist at different levels and across boundaries. Some require high-level planning to understand how different services integrate. Others require a detailed understanding of the underlying platform to develop a solution within its constraints.
I believe understanding the layers beneath the one you're working at allows you to have better conversations with stakeholders and the engineering teams implementing your designs. It's likely that a Solutions Architect comes from an engineering background, and I believe it's important to keep those skills sharp. It's not enough to conceptualise a solution. Whenever possible, you should be able to demonstrate that it works.
Negotiating Solutions
A Solutions Architect can also act as a mediator between different people involved in a solution. Each member of the team has their own responsibilities and priorities. When they start collaborating, they come equipped with their own agenda and ideas about how the solution should be implemented.
A stakeholder may request a feature that developers estimate will take a significant amount of time. Working alongside the engineers, the Solutions Architect might identify an alternative that delivers most of the required value in considerably less time. This is similar to the 80/20 principle. Sometimes the final portion of a requirement introduces a disproportionate amount of complexity. By understanding which requirements genuinely matter, the architect can help stakeholders make informed compromises rather than pursuing technical completeness at any cost.
But while I can recommend and validate a solution, ultimately it's the customer's engineers who must implement and maintain it. That means my responsibility doesn't end with presenting a technically sound design. I also need to explain the reasoning, trade-offs and constraints behind it, so the engineers can make informed decisions themselves.
The Solutions Architect's Mindset
I believe a good Solutions Architect needs to be curious, critical, slightly pessimistic and, above all, a problem solver who can work with incomplete information and constraints beyond their control. Curiosity drives us to ask questions, challenge requirements and understand why something is needed rather than simply accepting what's presented. A critical eye allows us to question assumptions and identify weaknesses in a proposed design, while a healthy dose of pessimism encourages us to consider what could go wrong before it actually does. It's not about being negative, but recognising risks, limitations and potential failures that others may have overlooked. Ultimately, a Solutions Architect must take these observations and find practical ways forward. I think a good Solutions Architect should be optimistic about finding a solution, but pessimistic about the assumptions on which that solution depends.
Solutions Architects are Information Processors
Whilst negotiating solutions and balancing the expectations of different stakeholders, a Solutions Architect must process a huge amount of information. There's the existing implementation, requirements, wishes, technology restrictions, compliance, risk, market factors, cost and staff capabilities. There are so many different factors to consider that bringing them all together into a coherent solution can be challenging. But it's someone's job to do this, and without someone to bring it all together, the process can become political and unnecessarily drawn out.
It's the job of a Solutions Architect to extract the relevant details, identify what matters, what doesn't and what can be safely discarded based on their assessment. They take the relevant information, make it concise and bring it together to produce a solution design. Solutions Architects can consume information from various sources and formats, using it to inform and shape their recommendations.
Rather than seeing constraints as restrictions, I see them as helpful guides that allow you to align a solution with the customer's circumstances. The goal isn't necessarily to produce the most technically elegant or efficient solution, but one that fits the business, given its requirements, capabilities and constraints at that moment in time.
Rather than defending one particular perspective, a Solutions Architect should recognise that every stakeholder brings their own priorities and biases, often shaped by their responsibilities. The developers may favour technical simplicity, the business may prioritise speed to market, while Product may want consistency across the platform. A Solutions Architect needs to recognise these biases when considering compromises in the solution design.
That's not to say a Solutions Architect has no agenda. Their responsibility is to remain as neutral as possible, weighing up competing perspectives to find a solution that works for the business as a whole. Not necessarily the most technically elegant or the cheapest, but the one that delivers the greatest value given the circumstances.
Perhaps you need a Solutions Architect to bring different perspectives together and find the most appropriate solution. The measure of a successful Solutions Architect isn't how often they're needed, but how often they ensure they won't be needed for the same problem again.