2 Comments
User's avatar
Ilya Hardzeenka's avatar

First of all, great article.

I can understand the confusion of your customers who expect Software Architect just fix software. I experience it myself while working full time for a company. Some people would say concerns you described are in the Enterprise Architecture domain, but Enterprise Architects discriminated the name, so probably we need new one 😀.

Moisés Macero's avatar

Thanks Ilya!

Indeed, Enterprise Architecture can connect business and technology and help align the system with other aspects of the organization. But typically, either the role doesn't exist, which is the case in startups and scaleups, or it exists, but the person is buried with a lot of processes, as it happens in more corporate environments.

Perhaps the problem is, as you say, the name "Enterprise". It implies the role is only needed in large organizations.

Just as we're witnessing the rise of the "Business Engineer" and "Product Engineer/Developer" roles, we'll soon see the emergence of the "Business Architect" role 😉 I'm happy with any name as long as someone in the organization owns those functions.