Designers Trilemma. Why designers are siloed and how to break out of it |

IT-блоги Designers Trilemma. Why designers are siloed and how to break out of it

UX Planet 13 января 2021 г. Andra Oprișan

Why designers are siloed and how to break out of it

A case for more collaboration between the different species of designers.
Part of
Designers Trilemma, a series of articles on helping designers grow transversally.

It recently struck me that the reason why Design is still hard to grasp by outsiders is because we are not a cohesive discipline. We understand insufficiently what other design disciplines do and how they add value in relation to what we do. As a result, we collaborate very little intra-disciplinary. That leads to inefficient use of design skills, overlaps at best, misalignment at most, mistrust between teams, slowed down processes, and a general bad vibe when it comes to selling our own discipline to non-designers. Better intra-disciplinary comprehension and collaboration will lead to more impactful work, a stronger more cohesive industry, and more buy-in from non-designers.

Let me unpack it.

Strategies like aggregation and vertical, horizontal and diagonal integration have become the main sources of value creation for many new businesses. That means that most new products or services that disrupt markets are not entirely new ones, but rather mashups of existing services or technologies. A case of 1 + 1 = 3.

For example, a car sharing service is a service that allows people to move around a city by integrating a mobile app, map services, localisation services, payment services, car insurance, maintenance, customer help lines, bank accounts, legal services, and so on. This is what we’ll call a transversal output — a product or service that intersects various other services or technologies.

This fairly new approach to value creation has resulted in a tight interdependence between a multitude of disciplines. Collaboration between departments or teams is the vital factor for creating better, faster and cheaper transversal solutions. Neither an interface designer nor a lawyer nor an engineer can make a car sharing service work on their own. Instead the very fact that the designer and the lawyer and the engineer collaborate for a common output is what generates the new value. You might know this concept by the name of multidisciplinarity. It refers to the input — what goes into creating something.

So, in order to create a transversal output, you need a multidisciplinary input. Obvious enough.

Except it’s not how most organisations work.

How Designers went separate ways

Big Corp is often optimised — and incentivised — to work in silos. Meaning each team, department, vertical, division or unit are excellent at delivering a specific piece of the puzzle, but not aware of the other pieces made by other teams. It’s how they’ve managed to be efficient and profitable over time. They all work under the assumption that someone up there will put everything together. As a result the organisation is incapable of creating transversal solutions, even if they posses (all the) outstanding pieces of puzzle.

Ever wondered why weren’t the large automakers the ones who came up with car sharing service? Or why weren’t big banks the ones who came up with fintech solutions?

Now how’s that relevant to designers?

Despite the fact that designers have been advocating for organisational de-siloing ever since they were allowed into boardrooms, the reality is that designers have inadvertently siloed ourselves too.

Much like in any other markets, the offer has been shaped by the demand. The simple fact that each type of designer or design agency is usually called in by a different, often siloed team inside an organisation, means that each type of designer has grown alongside the challenges they were asked to solve. Those pieces of the puzzle that originate from legacy, siloed, organisational structures.

Each type of designer has grown alongside the challenges they were asked to solve.

The result is that Brand designers, working for Brand teams, don’t understand what UX designers do, who work for Digital Product teams. And vice-versa.

Editorial designers, who work for communication teams, don’t know what Service designers do, who work for customer experience teams. And vice-versa.

Industrial product designers, who work in R&D departments, don’t know what Digital product designers do, who work in technology departments. And vice-versa.

(Ok, I’m slightly generalising to make the point)

Unless they get to collaborate on a transversal solution — say a new car sharing service — Brand, UX, service, editorial, industrial or digital product designers don’t get to work with each other. And don’t get to understand how each adds value to the output.

Competition > Collaboration

Now, design collaboration is by no means a new topic (hello co-creation, my old friend), and I’m not pretending to reinvent any wheels here. But I’ve noticed that the emphasis tends to fall on the collaboration between designers and other disciplines or between designers of the same craft. Hardly ever on collaboration between different types of designers.

Design collaboration is mostly between designers and other disciplines or between designers of the same craft. Hardly ever on collaboration between different types of designers.

Best case scenario, the relationship between various design disciplines gravitates towards competition. But more often, it’s a downright fight for supremacy. I’ll spare you the ugly details of the feuds between digital product designers and physical product designers, between service designers and UX designers, between type designers and brand designers, between content designers and copywriters.

Open Twitter on any given launch day of a large corporate rebrand, or a new phone release, or an upgrade of a popular app, and you’ll see the design stoning in full swing. Hierarchy is the obvious power play in this discourse: my design discipline is better than yours and we would have done it so much better than you, had we been given the opportunity.

Fitting in is the new standing out

The more transversal solutions the world will require (another topic for another article), the more we’ll have to figure out how to build value collaboratively — not only between designers and engineers or businesses, but particularly between designers and other designers.

In the long run, those who will prove they are able to integrate into ecosystems and work alongside others are going to stick around, while those who will remain islands, under the pretext of maintaining the integrity of their craft, or for the sake of autonomy, will slowly fade away.

In the long run, those who will integrate into ecosystems and work alongside others are going to stick around, while those who will remain islands will slowly fade away.

Fitting in with fellow designers requires understanding how each and very type of designer adds value. If you’ve also noticed the boundless ways in which one can add designer to their Linkedin headline, you probably agree that’s no easy feat. Every new technology generates its new design niche. So over the recent years we’ve witnessed a proliferation of design disciplines — together with their own jargon, rules, processes and tools.

Designer Mapping

Let’s zoom out.

To understand where the opportunity for collaboration lies, I propose we map all the different design disciplines — the input — against an output. It could be a digital product, a service, a business, a city, whatever you want. The only rule is that it should be something transversal, wide enough in its scope to requiere a multidisciplinary input.

I chose to do this exercise with the lifecycle of a new service, and I’ve included as many design disciplines that could potentially be involved in creating, growing and evolving a new services that creates transversal value for the people who use it.

Mapping the design disciplines involved in building a transversal service
Mapping of design disciplines involved in building a transversal service

The cool thing about looking at design disciplines in this way is that you get to see the interdependencies and overlaps. It allows us to understand what collaboration actually means — in specific milestones of building a service.

When someone needs to take the lead.

When someone needs to seek help from other type of designers.

When there are too many cooks in the kitchen and adult supervision is needed.

Understanding who needs to contribute and where, and what they’re best at not only ensures that the output is better, but also helps designers grow into other areas — by learning from how others approach their work.

Of course, painting a chart like this is not enough for a UX designer to collaborate with a retail designer, or for an editorial designer to be buddies with an industrial designer. But it serves as a map. It helps us get our bearings. It’s shows us the territory. It’s still up to us to go places.

Notes to self

Having done this exercise, a few questions came to my mind,

  • Who should take the lead and to facilitate the collaboration? Client-side? Agency-side?
  • How should the role of a Design Manager evolve?
  • How should businesses who don’t have a Design Manager approach this?
  • What’s the best way for a designer to share their work with other types of designers?
  • How do you incentivise collaboration, while allowing each designer to find their own space (and not pigeon hole them)?

Designers Trilemma. Why designers are siloed and how to break out of it was originally published in UX Planet on Medium, where people are continuing the conversation by highlighting and responding to this story.

Источник: UX Planet

designer collaboration transversal-design design multidisciplinary

Читайте также

What Makes Up the Backbone of Website Development

Разработка DZone Web Dev 20 января 2021 г. 3:21
Developing a website isn’t much different than building a house. In order to do so, experts in engineering, design/architecture, project management, creative, and development must work together to understand and achieve specific goals. First, let’s d...... читать далее
web dev website design website development ux ui

Step-by-Step Guide: Application Using NestJs and Angular

Разработка DZone Web Dev 20 января 2021 г. 2:32
Just a few days before Christmas, I came along the NestJs framework. I always wanted to give NodeJs development a try, but the idea of a JavaScript backend seemed to keep me away. NestJs is a framework for building Node.js server side applications a...... читать далее
tutorial web dev angular nodejs nestjs

SEO biznology 20 января 2021 г. 0:05

Distribution strategy, despite being one of the fabled 4 P’s (“Place”), has traditionally been outside the direct purview of B2B marketers. It’s time for a change. The severe disruption in distribution value... The post Why Distribution Str...... читать далее

Consultants Collective Corner business advice Business and Economy distribution e-Commerce leadership skills partnerships technology processes

DevOps DZone DevOps 19 января 2021 г. 22:15

Why do people hate change management? Probably because most of the time it feels like the management portion of change management is implemented with arcane approval processes and bureaucratic red tape that have historically gotten in the way of team...... читать далее

devops continuous integration ci/cd continuous deployment change management ci/cd pipeline

Разработка DZone Web Dev 19 января 2021 г. 21:44

The Go programming language, often referred to as "Golang," has gained a lot of well-deserved traction in the DevOps community. Many of the most popular tools such as Docker, Kubernetes, and Terraform are written in Go, but it can also be a great cho...... читать далее

web application development heroku golang gin web framework

DevOps 19 января 2021 г. 19:58

Laptops are great for all forms of computing and you get the added benefit of portability and space-saving.Laptops aren’t only useful for productivity they can also be great for media consumption and, with enough computing power, some gaming. The iss...... читать далее


DevOps 19 января 2021 г. 19:56

Do you want a tablet? Or a laptop?Well, the good news is that you don’t have to choose! You can get yourself a 2-in-1 laptop-tablet, which is essentially a tablet that you can attach a keyboard to. You can either use it as a tablet when you don’t nee...... читать далее


Популярные темы

ux (343) новости (334) design (304) новость (203) javascript (191) web dev (189) ux-design (189) ubuntu (183) devops (183) headline (180) security (175) python (172) seo (134) tutorial (130) ui (121) статьи (110) user-experience (102) programming (96) testing roundup (92) software testing (89) product-design (85) дизайн (83) дайджесты вакансий от (83) working in tech (81) design-thinking (79) игровые проекты (78) java (78) api5 (76) google (74) primary (73) ui-design (69) прочее (67) laravel (65) windows 10 (65) технологии (63) php (62) бизнес (60) hardware (59) uncategorized (55) technology (53) мероприятия (52) обучение (52) движки и конструкторы игр (51) español (51) работа (49) css (48) турбо-страницы (47) case-study (46) covid-19 (46) web design and applications (46) debian (46) android (45) docker (44) навыки алисы (43) обзоры (43) angular (42) publication (42) bash programming (41) cloud (41) inspiration (40) инструкции (40) machine learning (40) ux-research (40) data (40) chrome (39) web (39) home page stories (39) job hunting (39) art (39) networking (38) wp (38) маркетинг (37) kali linux (37) vue.js (36) aspnet (36) тестирование (36) автоматизация (36) полезное (36) .net (35) powershell (35) кейсы (35) wordpress (35) google ads (35) events (35) tutorials (34) arch linux (34) productivity (33) linux mint (33) разработчики (33) навыки (33) api (32) события (32) apple (32) marketing (32) windows (32) dotnet (32) freebsd (32) интервью с экспертами (31) virtual reality (31) system administration (31)