You have to think with your users, with your customers, what is your actual relationship? Are they your gods? Are they your guests? Are they a nuisance to you? Because you know where the power is.
Archive (Page 2 of 3)
I think that privacy is something that we can think of in terms of a civil right, as individuals. […] That’s a civil rights issue. But I think there’s also a way to think about it in terms of a social issue that’s larger than simply the individual.
How do we take this right that you have to your data and put it back in your hands, and give you control over it? And how do we do this not just from a technological perspective but how do we do it from a human perspective?
We have to know what we want. We have to imagine how it looks. We have to understand how it feels, how it smells, how it functions, before we can design it. Before we can code it. Before we can implement it, and before we can sell it.
There is a certain way people work, or a certain way a large portion of people work. And when you build a thing that demands them to suffer, you should make some attempt to alleviate that suffering so they can get to the goal.
Hello. Let’s talk about ego. I believe that many projects and organizations today have too much of it, and that it hinders them from doing better design work on products and services. That’s a bit of an accusation, so let me talk you through what makes me say that.
Design for emergence operates on a different set of criteria steeped in the politics and urgency of its time. I believe that in this scenario, having these so-called safe choices is not a bad thing. During this time of emergence it’s good that we have defined a graphic language of nationhood, expedient variations of heraldic traditions of crests, cartouches, and coats of arms. A lingua franca of legitimacy.