Frederick Vanbrabant's Delirious Rantings

Home /

Choosing where to spend my team’s effort

Strategy , People

It’s the start of a new fiscal year. Strategy season. That time when all the grand ideas come out and everyone is still hopefull. Over the years, I’ve settled into a structure that helps me define projects that not only link to the strategy above but also looks at my own team’s enviroment, I thought I’d share it here.

What's the role of software in an organization

Enterprise architecture , Strategy

Last week, while sitting in a bar, I had a chat with a good friend of mine about the role of software in an organization. I stated that the primary role software plays in an organization is to facilitate processes. My friend argued that this is a strict and overly theoretical view of software in the workplace. He might be right, but nevertheless, I think there is an article in this conversation.

People, Processes, Technology and Information

Enterprise architecture , Managing information

In my last post1, I briefly talked about how I include information (PPTI) in my operating model (PPT), and I even promised to write a post about it. This is that post. People, processes, and technology are very common ways to look at an organization from an architectural point of view. It is often argued that everything that happens (projects, implementations, strategy, etc.) is impacted and driven by these three pillars.

Now without vague hand waving: What is Enterprise Architecture

Enterprise architecture

One of the most confusing things about architecture is the vagueness of the naming surrounding it. This is true not only for non-architects, who often don’t really know in detail what all the different disciplines do, but also for the architects themselves. A lot of the naming seems to be based on feelings without any clear definition.

Business strategy is like a lizard

Enterprise architecture , Strategy

Well, the real title was going to be “Business strategy is like a lizard: It leaves behind its tail while it grows a new one,” but that was just too long. Strategy never exists in isolation: it’s always a response, a build-up, or a pullback. It also has to be passed down to all the layers of the organization to make these chances. It’s a very reactive business.

What's the use of Archimate anyway

Enterprise architecture , Managing information

Last week, I discovered a new podcast called The Enterprise Architecture Experience. They had two episodes featuring interviews with Dr. Svyatoslav Kotusev about his books and work. Svyatoslav is a fascinating figure in the Enterprise Architecture space 1, and I was delighted to hear his insights on the podcast. The conversation did not disappoint. Near the end of the podcast, Svyatoslav made a brief remark about ArchiMate, stating that it is a language spoken only among architects and reinforces the stereotype of the ivory tower architect. His comment resonated with me, and I have been reflecting on it ever since. Allow me to share my thoughts.

Enterprise architectural skunk works

Enterprise architecture , Strategy

Most big organizations I’ve worked with are more akin to an ecosystem of multiple smaller companies. These smaller companies all share the same umbrella of the bigger total but internally compete for resources and priorities. Think of it as a federation of specialised companies that all share the same banner and want to achieve the same bigger goal.

Enterprise architecture , Strategy

A big part of enterprise architecture is keeping your architecture model up to date. Without this model, it’s impossible to do your real job in advising projects, strategy and general company awareness. The problem is that getting a full model is a daunting and maybe even impossible job. Let’s talk about the pitfalls and how we can approach this.

Modeling data and information in an organization

Enterprise architecture , Managing information

The last weeks I’ve been focusing a lot on the data and information models in our architecture. Organizations have so much data flowing around that it’s hard to effectively map it all out. That’s a shame because there are some very valuable learnings to be had from that data. That’s why I wrote this post; it’s mainly to gather my current thoughts on this topic. Might as well share it with you. It’s a combination of techniques I’ve done at previous organizations (things I know work) and things I’ve been thinking about for a long time now (things that might work). So this isn’t a full-on manual, more a collection of current thoughts. I hope that makes sense.

Turning Complexity into Manageable Complication

Enterprise architecture , Strategy , Managing technology

Have you ever made bread before in your life? Like from start to finish? It’s not a difficult thing to do. You start off with flour, yeast, salt, and water. Combine them, let that dough sit for a while, knead it again, let it sit again, shove it in an oven, and voila: you have a bread.