Hi, my name is Marcel and I write about Enterprise Architecture, Digital Strategy and modern IT Management.
EnterpriseArchitecture
Enterprise Architecture has a persistent credibility problem. Not because the discipline is conceptually flawed, but because most organizations implement it in a way that separates the feedback connections that would make it useful. The result is an architecture function that produces artifacts — roadmaps, reference models, principle catalogues — without producing measurable
AI
How do we automate Architecture efforts with AI? Is this really the right question to ask? It sounds logical, but it rarely leads to the highest return on investment. The better question to ask is: What are architectural preconditions for AI agents to function reliably, economically, and at scale? There
EnterpriseArchitecture
Executives rarely wake up and decide to block progress. Yet across organizations, digital initiatives stall every day. * Customer experience programs drag on. * Data platforms miss their promised impact. * Transformation roadmaps quietly slip by quarters. The default explanation is familiar: organizational silos, lack of alignment, resistance to change. But after reviewing
Mindset
These aren’t rules. It is about a state of mind. Ten virtues to remind you why you design – and for whom. They’re the foundation for architecture that endures, uplifts, and delivers value. I. Clear needs before fancy solutions Virtue: Listen deeply. Clarify. Speak clearly. “The beginning is half
Mindset
The world is constantly changing. How can you be successful today? What do you need to learn to stay relevant in the future? The content is created by me personally. It is meant only for people to read and must not be used to train any machine learning models, including
Architecture
No one has told you about this. How does it feel to enter the Architecture profession? Does it match with what you had in mind? What turns out to be a fallacy? The content is created by me personally. It is meant only for people to read and must not
Strategy
Buying software from the market vs. creating your own intellectual property. Or is there more to it? Timeless decisions that every organization must make for its own IT estate. The context of this article Before we go into details, let’s define the scope. This article is for large enterprises