Designer vs Architect vs Engineer

Recently a question was posed on LinkedIn asking the difference between a designer, an engineer, and an architect. A succinct response was as follows:

Designer - maps the end result the user will experience
Architect - decides which frameworks and methods to use to achieve the desired result
Engineer - develops the solution using best practices within the framework given by the Architect

Simple, but a bit too simple.

Why the confusion with designers, architect, and engineers

The terms -- designer, engineer, and architect -- originally applied to fields such as mechanics, art, and building. So the problem is that we are using "old" industry terms to possibly apply to "new" ones. A designer has veru different meanings in fashion and software.

The WWW is a rather recent profession, and as such the terminology is not exact yet. For example, a "web designer" may be proficient in programming code ("engineer"), or site architecture ("architect"). Or maybe they start as one and become the other.

So, I've stated the problem -- we are using old professional terms for a relatively new field. The solution? This is how I see it after nearly 15 active years in the web field.

Web Designer

Let's reserve this for, at minimum, the aesthetic level. A designer is trained to figure out the online experience -- how the needs and wants of a website visitor can best be served. A such, they would be involved with how a web application "looks".

But the web medium is more than just looks, it is also what happens when you hover, click, and move your mouse -- it is interactive. The field is now evolving where we have "Interaction Designers", as the designer's role is expanding to the "feel" of a web site as well as the "look."

In the end, a designer is obsessed with how a solution looks/feels, but may have little concern for how it works. These concerns are for Architects and Engineers to address.

Note: While their can be a "software designer", that is more about architecture or process, very much akin to a "interaction designer". One could possibly use these terms interchangeably, with a interaction designer having more of an aesthetic education and software designer having a technical one.

Web Architect

An architect, very similiar to a building architect, ensures that the final structure will support ("house") the end solution. With "Information Architect", they will ensure the site navigation flows in a logical manner, perhaps also responding to demands such as search engine marketing. With a "Software Architect", they will ensure the solution, whether by design or by structure, answers all the project challenges.

An architect is a very senior position on a project, if not the most. They usually require abilities in both systems design, usability, and programming. As such, an architect should be considered a rare, expert position. In my opinion, too often people use the title without the experience to match such as applying it to non-technical persons who do user experience, marketing and other functions. The end result is a junior-level solution that could look great, but perhaps lacks in its technical execution.

Web Engineer or Developer

Let's reserve this for someone with expert technical capabilities, someone who has a deep understanding of software development, coding practices, and the life cycle of software. The engineer could be involved in production of the software, or perhaps oversee the project as a whole as a Lead or Senior Engineer. Regardless, they will need a strong technical background to execute.

A web engineer and developer should focus their efforts solely on utilizing or developing the best technologies. How a system flows or works should be relegated to a designer or perhaps architect.

Final Thoughts on designers, architect, and engineers

I have placed these in order in terms of the process of a web project. A designer's notes should be given to an architect, which should then be given to an engineer. While projects could benefit from this process, all too often the budget doesn't allow for such levels of expertise. As the Web field further developers, I hope recognition of the required unique talents of these individual roles improves.