Monday, 22 August 2011

What Happpened to the Designers ?

A couple of years ago a lot of job names in The Netherlands changed. One day it seems, it was no longer acceptable to call the lady who cleans your house 'cleaner' but 'interior caretaker'. A farmhand became an 'agrarian assistant'. I really don't know why. At the time it looked like it was aimed to change the perception of less-liked jobs. Maybe to increase interest?

These days, everybody is an architect. Process Architect, Software Architect, Information Architect, Infrastructure Architect .....

I experience a devaluation here. I see lots of 'architects' designing applications (making process models, logical data models and use case models, etc), abusing the PSA (for those without IT background: Project Start Architecture) for the job. Even worse: a lot of people and organizations think that's what architecture is all about.

Depending of the level of architecture, an architect should set out the framework, the guidelines for the solution, not the lowest details of the solution itself. He (She included) should focus on the consistency of the total solution for the enterprise, making sure that no effort goes to waste, but delivers to the long term goals of the organisation.

That also means you don't need a whole army of architects. Just a few (depending on the size of your organisation), assisted by a minor army of designers, would do the job!

1 comment:

  1. sipayi@gmail.com25 August 2011 at 22:55

    Unfortunately, may be due to the inevitable reasons such as massive outsourcing, the respect towards, and salaries of designer/developer have dwindled. Also, the title 'architect' has historically had some nice effect to it (pick any Vandalay episode from Seinfeld.)

    People like me, with 15+ years of programming experience, do not mind working as designers/developers, but do mind the 'factory' mentality corporates and management has developed towards old fashioned 'engineers' and 'designer/developers'. The only option is to tout a fake 'architect' to show that a person has considerable experience in a certain field. After a while, this becomes a mandatory requirement; employers 'weed-out' any developer resumes, as they think developers are under-qualified for a position. Sad state of affairs, actually.