Solution

Once in a while I get asked a question that what do I do or what does a solution architect do. My definition is not necessarily the text book interpretation of solution architecture but it is the interpretation what drives the way I want to approach a solution and what resonates on my own interests towards work. The short answer is that "I design IT solutions"... But maybe that needs to be opened up a little bit.

3 key elements. People, Processes and Technology.

To me a solution is build around 3 key elements. People, Processes and Technology. In the cross-roads of these 3 elements are ways of working, integration & data and usability & access.

All of these elements combined are needed to create the complete 360 view for a solution, what again answers 3 basic questions of Who, What and How.

Who

People are the real key in achieving needed business targets and executing defined processes. People require access and the right tools in order that they can execute given tasks in the most efficient way possible. Business processes or or the supporting technology are nothing without the people responsible of using them.

What

Business processes tell the story of what needs to be done. They define the high level business requirements, targets, who is responsible, what data is needed and how are different business areas connected together.

How

Technology provides the tools to meet any given business requirements and to people the ways to execute the defined business processes. It also provides the tools to enable end to end integration and to manage the needed and used data.

When all of these 3 sides of a triangle are considered there should be enough information in order to define the best possible Solution. A good solution is easy to access, easy to use, answers the given business requirements, is integrated and contains the needed and correct data.

There needs to be room to make some errors.

And as a last taught, although slightly of topic. When working with an end to end solution it is not always possible to do things with a wanted way. There are always gaps in information, unclear questions, missing answers and wrong decisions.

I always try to remember and also endorse that there is nothing wrong in not knowing all, making a bad decision or making a mistake. Instead challenges should be expected, mistakes should be embraced and there needs to be room to make some errors.