That being said, startups like Uber, Waze, AirBnB, and Nest have all reached staggering levels of success by re-designing the entire stack of user experience in their respective markets. While the interfaces of these products are generally clean, they're not really the crux of the design innovation. Instead, the critical design innovation is elsewhere, in design of the systems, processes, technologies, and even business models that enable a magical end user experience.
And I would guess that those skills are all very valuable, but aren't enough on their own. Lots of the hardest and most important problems and needs to solve in our world are in fields that require deep domain knowledge.
It feels like because so many startup founders don't have the patience to go into a field and acquire that domain knowledge everyone is focused on problems that yuppies have that can be solved by looking at a screen.
What I was taught as the "design process" is actually much closer to what people study in anthropology and ethnography than business school.
Some of the core requirements involved going to unfamiliar places and just observing, asking questions, embedding yourself in an effort to understand domains and cultures that you aren't familiar with. That was a big part of the point, forcing people into doing that kind of stuff.
Another issue that leads to all this is that "design" is an overloaded word, with many valid uses that are only tangentially related. Product design, interaction design, graphic design, etc., some of these put form over function, by definition, others put function over form, as is their purpose.
I'd say that the main point of the article is that function/purpose/problem/need first design is the revolutionary thing, and there was an opening for the word "design" to resources behind it. Into that opening poured a stream of by great designers from form focused design domain, and the result was disappointing.
s/come from/utilize/
Generally, the tech side is one-level-removed. A lot of tech-work involves providing for people... who interact with other people who are experiencing the "real" problems.
Don't get me wrong, it's valuable work (and boundaries can blur) but it's like the difference between... a lawyer and a social worker. Or a bridge-builder versus a traffic planner.
I agree, but the key point in there is that applying new tech often requires significant domain-knowledge in whatever that other industry is.
Generally, this means chains of people, rather than just one person who happens to be both a professional programmer and professional <other thing>.
At any rate, less "You came to me for help in achieving legal goals X, Y, Z" and more "the civil-rights organization has hired me on your behalf".
* In the American sense. In the European sense, this term is often used to denote the design of interactive experiences, which is quite different.
The training we received is still the core of how I think about everything. It was all about needfinding, methods for exploring the problem and solution space, iterating with low cost mediums and moving to higher cost only as needed for more information or production, things like that. Things that relate to human needs, understanding them, and seeing how the things you make relate to them.
Visual design was a minor part of the curriculum, we had a few art requirements. But it wasn't the core.
It is sad that design means visual perfection and smooth animations. Design is really about uncovering novel ways to improve people's lives, and doing so in the simplest way possible. It doesn't necessarily even relate to interfaces.