Antwerp, Belgium
Before my end-of-year holiday break, I received an email 1 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
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.
Read MoreI’ve been part of the creation of five enterprise architecture offices in my life. Some I’ve led, others I’ve simply been part of.
If you start up an enterprise architecture office, you have two types of strategies people use. Some people start by mapping everything that exists, in whatever state it happens to be. They then assess what they have and start building a gap analysis towards a better, more uniform state.
Read MoreEvery company that I’ve helped start their enterprise architecture practice so far, always tell me that they might not have architecture setup yet, but they do have a ton of information in the CMDB that we can use to kickstart the exercise.
The CMDB is our source of truth of all the applications, servers, and it’s all linked to service lines and capabilities. Furthermore, it’s maintained by a team and it’s fully ITIL aligned. It’s a treasure trove!
Read MoreWhen I was a developer, half of our frustrations were about technical debt (the other were about estimates that are seen as deadlines).
We always made a distinction between code debt and architecture debt: code debt being the temporary hacks you put in place to reach a deadline and never remove, and architectural debt being the structural decisions that come back to bite you six months later.
Read More
A few weeks ago I walked into a meeting room to discuss my solution to a fork in the road problem. We’ve been roadblocked for two weeks with two clear paths forward. One of them I preferred; a bit more work, but it would bring dividends in the future and not burden us with a less than ideal solution. The other way forward was what a different group wanted: to push the project through so they could reach the deadline.
Read MoreArchitects always get a bad rap when it comes to design documents.
We get blamed for delivering these massive solution design documents that take weeks to produce, eat into the time for development and in the end result into an encyclopedia that nobody reads.
The architectural drive to document and cover as much as possible naturally evolves into templates that are in the 40–50 pages (template alone).
Read MoreEvery time I go to teams and start talking about process mapping and standard operating procedures (SOP) I notice an undeniable amount of unease like it just got a few degrees colder.
What people hear isn’t “we’re here to understand your work and make it smoother.”
What they really hear is: “We’re here to judge, strip the creativity, maybe even replace you with a machine.”
In my startup days, we often had these dead marches where we had to implement a massive new feature in time before some kind of trade show happened. We worked long hours and even weekends to make it happen so the boss and a project manager could go to Vegas for the trade show.
When they came back on Monday, they told us what the competition was doing, and laid out a brand-new strategy they’d dreamed up between hotel bars and expo booths.
Read MoreI’ve been working a lot with service line architecture recently. If you’re not familiar with that; it’s how business units such as IT, HR, or Sales bring services to clients, both internal and external. These structures often mirror team organization.
Think of it as a hierarchy: IT at level one, Software Development and Ops at level two, and then individual teams, like: Software Team X or Ops Team Y, at level three.1
Read More