What a solution architect actually does

Solution architect is not an easy role to explain without context. I was asked to define it in almost every interview I sat. The clearest answer comes from watching what one actually does on a transformation.

The bridge between business and technology

Construction is going through real digital change: modern methods of construction, digital engineering, automation, data science. The ambition is to become a data-driven business on scalable foundations, and that touches people, process, technology and culture at once. The solution architect sits in the middle, turning business demand into technical supply and keeping delivery predictable.

Designing the right thing, with people

The Open Group puts it well: solution architecture describes a focused business activity and how IT supports it. In practice that means turning a high-level need into a solution vision, a set of specifications and a plan of work. When operations needed technology to coordinate project information across stakeholders, it began as a sentence and became aligned business and technical requirements, then components and integrations detailed enough for a development team to design against.

None of this happens in an ivory tower. Solution discovery is a social process. The architect helps colleagues turn a practical problem into a workable design, facilitating across everyone with a stake so the answer fits both the business need and the wider technology strategy.

Architect, not developer

IT has many architecture disciplines at different altitudes, much like building, infrastructure and civil architecture. Enterprise architects set the organisation-wide blueprint; solution architects work at project level; data architects model the information. A solution architect is not a developer in disguise. The job is judgement and translation: turning business requirements into technical implications, and speaking both languages well enough that each side trusts the result.

Strategic versus tactical

Project work sits under a target architecture, and tactical fixes create technical debt, the IT equivalent of temporary works on site. The architect lives with that tension, trading short-term wins against long-term goals and mediating the conversation so the organisation does not quietly lose its technical direction one shortcut at a time.

Working in a political environment

Solution architects stand between the business and central IT, advancing client outcomes and strategic investment at the same time. That duality is political, and the right governance, whether federated, devolved or fully aligned, depends on the operating model and decides whether it works.

Start with discovery

You cannot publish a framework and expect instant compliance. Treat it as a journey where demand and business value set the priorities. Engage early to shape solutions rather than firefighting business as usual, capture what works, drop what does not, and keep architecture governance light but real. Done well, solution discovery means better questions early, sharper estimates, fewer siloed systems, and solutions that are designed on purpose.

---

Originally published on Medium.  ← All insights