How to take a problem oriented approach

I’ve sometimes (often?) been in the situation where I’ve been put on a project where the only input is a business case that says something like “we are going to run a project to develop and implement a system that does these things ….”. In other words – a solution. Unfortunately, there is no description or analysis of the business Continue reading How to take a problem oriented approach

Architects should solve problems, designers should design solutions

This is my view of the difference between architects on the one hand and designers, developers, coders etc, on the other. Architects solve problems and define optimal solutions.They make decisions about the problem – its type, its definition, its scope and the solution definition. Solution definition means the major characteristics of the solution (what information is in scope, the processes Continue reading Architects should solve problems, designers should design solutions

Why Steve Jobs was a system architect and Bill Gates wasn’t

Steve Jobs understood how to communicate with both the problem domain and the solution domain. He also had style and drive, but essentially he operated as a problem oriented architect. He didn’t have the skills to do the technical design or run the business. But what he did have was the ability to cross the divide. Jobs had a problem Continue reading Why Steve Jobs was a system architect and Bill Gates wasn’t