I agree with your conclusions and there is another type: the artifact manager, who mostly works in an IT architecture tool. They think that the tool does everything for them and just "feed the beast" without any conceptual thinking (or modeling) ... "The report will tell us."
Oh yes, that one definitely exists. The artifact manager: faithfully feeding the tool and waiting for insight—and ROI—to materialize automatically. You do sometimes encounter them in the wild, including LinkedIn comments.
Hey Eetu, Spot on diagnosis. I would argue there is a more uncomfortable truth: Could it be that many of these "advisor-only" architects do not model model because they don't have the background? Sure you can grow into it to a certain degree, but if you lack the bottom-up engineering scars it is very hard to make actual decisions that work (and stick).
I agree with your conclusions and there is another type: the artifact manager, who mostly works in an IT architecture tool. They think that the tool does everything for them and just "feed the beast" without any conceptual thinking (or modeling) ... "The report will tell us."
Oh yes, that one definitely exists. The artifact manager: faithfully feeding the tool and waiting for insight—and ROI—to materialize automatically. You do sometimes encounter them in the wild, including LinkedIn comments.
Great article. It's definitely "both-and" in my book. I like to think of it as enrollment first and alignment second.
Thanks! Very much a “both-and” for me as well.
Hey Eetu, Spot on diagnosis. I would argue there is a more uncomfortable truth: Could it be that many of these "advisor-only" architects do not model model because they don't have the background? Sure you can grow into it to a certain degree, but if you lack the bottom-up engineering scars it is very hard to make actual decisions that work (and stick).