Frederick Vanbrabant's
delirious rantings

Antwerp, Belgium

15 May, 2026 • 4 min read

I don't think AI will make your processes go faster

I have the feeling that every organization out there is, at least partially, focusing on process optimization, something that often happens when the market is down. These days there is also the AI angle to the entire thing, and the unrealistic expectations that follow it.

To come fully prepared for this, I’ve decided to re-read two absolute classics in this space: The Toyota way & The Goal ¹. I’ve read both of these books in college, but re-reading them made me realize that a lot of these process optimization exercises are too simplistic in nature, and often misunderstand what to focus on.

I don't think AI will make your processes go faster

17 April, 2026 • 5 min read

Good architecture shouldn't need a carrot or a stick

Last post I wrote about how you can approach buy in for your architecture. I’ve been thinking a lot more about the topic, and would like to delve a bit deeper into it.

I still stand fully behind the post I wrote two weeks ago, but the more I think (and research) about it, the ideal situation is that you don’t have to seek buy in for your architecture at all.

Good architecture shouldn't need a carrot or a stick

04 April, 2026 • 5 min read

"What’s In It For Me" Architecture

I recently read the quote, ‘The best architecture that isn’t implemented is just an expensive drawing,’ and I couldn’t agree more. I wish I came up with it.

When organisations hire for architecture roles they always look for extremely technical and knowledgeable people. While it is true that you need deep technical knowledge to set up large-scale architecture outlines, it’s all worthless if you can’t convince people to actually implement it.

22 March, 2026 • 8 min read

Governance: Documentation to support projects

Two weeks ago I wrote an article about governance and documentation on an organisational scale. This is the follow-up post that focuses on the project scale. You could just read this post, but it’s probably better that you start with the previous one first

The biggest problem with documentation is that nobody just sits down to write it all out. And I also think that’s the wrong way to go about it. You can’t just give someone the task of ‘starting to write whatever needs to be written’. You will never cover the important parts.

Governance: Documentation to support projects

07 March, 2026 • 11 min read

Governance: Documentation as a Knowledge Network

If you’ve known me for long enough, there will be a point where I’m going to pitch you the concept of Obsidian. I adore that program¹, I basically live my life in it. Everything is connected, and ideas just bubble up on their own.

That love for Obsidian is always amplified when I have to look up something on an organisational documentation platform. I can never find anything, it’s always out of date, and it has conflicting ideas all over the place. I’m pretty sure you can relate (if you even have one).

Governance: Documentation as a Knowledge Network

20 February, 2026 • 6 min read

Systems Thinking in Enterprise Architecture

I first learned of systems thinking in the domain of city planning, and that is apparently also where the idea comes from. It was described to me in the context of building new residential buildings and effects on local bird populations.

Birds don’t always perceive glass clearly, especially when it’s a tall apartment building and on their flight path. So there are birds that think they can pass under an arch, yet instead fly straight into a glass wall.

Systems Thinking in Enterprise Architecture

04 February, 2026 • 10 min read

The middle ground between canonical models and data mesh

Some years ago I worked with a scale-up that was really focused on the way they handled data in their product. They extensively argued over data language, had value objects everywhere, explicit models and, even hexagonal architecture.

It was a cool place to work, with a lot of smart people.

At some point they started to talk about standardizing their data transfer objects, the data that flows over the API connections, in these common models. The idea was that there would be a single Invoice, User, Customer concept that they can document, standardize and share over their entire application landscape.

The middle ground between canonical models and data mesh

22 January, 2026 • 10 min read

The death of the enterprise service bus was greatly exaggerated

Every six months or so I read a post on sites like Hackernews that the enterprise service bus concept is dead and that it was a horrible concept to begin with. Yet I personally have great experiences with them, even in large, messy enterprise landscapes.

I would go even further and say that I see a resurgence in their usage in big enterprises. Even companies that moved away from them seem to have a renewed appetite. Sometimes they are rebranded as integration platforms / iPaaS, but they are still very much the thing under the hood.

The death of the enterprise service bus was greatly exaggerated

09 January, 2026 • 7 min read

Bring back opinionated architecture

Before my end-of-year holiday break, I received an email ¹ from someone who read my post about “Choosing your starting line in enterprise architecture”. Mark asked me what I meant by the line:

So yes, you can map the AS-IS. You can design the TO-BE. You can even claim you’re doing both, which is the classic architect escape hatch.
Read More

13 December, 2025 • 6 min read

What is a Value Stream and how does it relate to a Value Chain

Organizations often use “value stream” and “value chain” as interchangeable labels. It’s not the biggest architectural drama in the world, but it’s still something that always annoys me a little.

We as architects might actually be to blame for this. We keep on coming up with related concepts that are very close to each other and then naming them ever so slightly differently.

Frederick Vanbrabant'sdelirious rantings

Frederick Vanbrabant's
delirious rantings