Preface

Most fights are over before they start. In war, success depends primarily on planning, training, and preparing before the significant battles. IT systems are similar. Projects are complex beasts that succeed or fail, mainly based on meticulous preparation before the project. Your role as an aspiring IT architect is crucial in this phase. There is only so much a project manager or a development team can do when they are already waistline-deep in the sticky substance.

No IT system implementation has ever failed because of a purely technical issue. The genuine root cause is, without exceptions, something more complex. People, processes, and assumptions have impacted significant decisions throughout. What seems like an IT issue is usually the symptom, not the cause. The root cause is the string of decisions that led the project to the crisis point.

Most established companies have IT architects who either make or recommend these decisions. The architects are diverse, coming from various backgrounds and not necessarily holding universally recognized professional certifications or degrees. They often see the ‘bigger picture’ and are always at the forefront of addressing the most pressing issues. Their role is crucial as they are responsible for designing and overseeing the implementation of complex IT systems, ensuring they align with the company’s goals and needs.

Architects actively shape their working environments’ why, what, and why. They are opinion leaders who work daily with all the necessary stakeholder groups, building systems, shaping futures, and leading companies’ digital transformations. As an aspiring IT architect, you will be responsible for advising on how to salvage failed projects and advising senior business leaders about the root causes of failure and success.

I have compiled a collection of short articles based on my experiences as an architect, covering various aspects of IT architecture. These articles aim to guide aspiring architects on their journey to becoming great architects. In the first part, I delve into identifying the correct development initiatives and choosing the right implementation type. The second part focuses on selecting the proper technology, and the third part discusses how architects steer major development initiatives.

The reoccurring themes are dialogue, learning from failure, technical competence, development teams, and communication skills. While you may be an architect without these, you cannot effectively steer anything but the most minuscule details. Real-world business requirements and environments in which we build IT systems have nuances on top of nuances. As an aspiring IT architect, you must understand that while you may not master them all, you must strive to master them most.

While I cannot cover every IT architecture-related phenomenon, I hope I have covered the most crucial parts. I hope to offer a few valuable pointers and things to consider for aspiring new IT architects. Let’s embark on this essential journey together. The real work begins in the next chapter, where strategic decision-making takes center stage.