662 karma · joined January 5, 2016
Also, they are ( or at least were) a prime example of a company that can bet on high risk, longish term investments that don't have an immediate application : e.g. their investment in chips, touch technology etc. It may not be as long term as some of the Google X stuff but I don't think it is fair to call them averse to making high risk long term investments.
There is a service for that. It's called Uber Black.
To make it better. And then to make it even better :) Isn't that what a significant amount of engineering and design endeavor is about?
The blunder (and yes, it is a blunder and not only in hindsight) in the shifter is that it provides poor feedback to the human. While changing technology may render some types of control not necessary, and thus correctly invite new design thinking, the fundamental human need for feedback does not change. In fact, when something that is so habitual to you changes, that is precisely when the design should provide even more feedback because otherwise you are likely to miss it. This is amplified if the consequences of not comprehending ones actions are high - which clearly was the case here.
The designers here dropped the ball. There is no way early feedback through rigorous testing on prototypes would have not identified this issue way before it went into production.
More thoughts on that here: https://medium.com/@ux/will-linkedin-and-microsofts-new-play...
Haven't read the entire paper but...learning from something doesn't mean you need to design something 'based' on that.
The advantage of studying how people unfamiliar with a specific way to solve problems will solve that problem is actually a great technique to try to understand common patterns and approaches humans think about problem solving.
Some pattern solving strategies will be more successful than others and it is worth understanding what is common to those (especially when compared to the unsuccessful ones)
Identifying patterns in the way people solve these problems can prove to be great design insights that go into the design of problem-solving solutions for those problems.
My neatest trick at that point was to make a 'fake' pre-loader where the progress bar showed a fake percentage with a cool graphic. My next 'impress project' was build a menu in QBasic where you could use the arrow keys on the keyboard to graphically move the highlighter on a menu. Almost everyone else at that time was doing menu selection pressing the number of the menu item. At that point I thought of it myself since there wasn't any internet in our lab so I still feel really good about it :) It also got me a spot on our school programming team primarily because no one else did the menu as quickly as I could then.
I'd like to think that I'm an interaction designer today partly because of the feedback and enjoyment I got out of doing projects like that.
One important aspect to consider here is people don't necessarily think of it as illegal or a drug. There isn't really 'police' enforcing anything for the local. The local police station has like 1-2 people who pretty much just hang out and are friends with the locals.
Everyone in the village knows each other (sort of) and it is only the adult (males) that will have access to and make it. Teens and children don't really do it because someone or the other will find out and then they are in trouble, so the system corrects itself pretty quickly. I've never heard of a single case ever of overdose or anything like, though it has ruined the productivity and general health of a very large number of people.
Compare that with a nugget of wisdom from Charles Eames - someone who actually built things that designers can look upto. Humble, to the point and not obvious but insightful.
Is there a design ethic? There are always design constraints and these usually include an ethic.