We get upset when our expectations are not met. Making constraints understandable will avoid those upsets.
The Cambrian explosion in design-related job titles and - supposedly - skills is getting us nowhere.
Forget the T-shaped professional: you need an octopus-shaped one.
Microsoft should trademark “It’s not a flaw, it’s a feature”, because I’m having a really hard time calling this device “a tablet”.
What I mean each and every time I have to tell someone that they don't need an app
Ideas Proofing 101
You have to provide a common context in which all the people involved in the project understand that they’re building a system, not an app.
We're always sort of blinded while trying to do the next big thing that we forget the humbleness of things that "just work".
In 2010 the iPad was welcomed as the publishing industry’s saviour: the publishing industry is still looking for answers, which also means they’re still looking for real disruptors.
Like many early adopters, my needs are counter-cyclical: we get sick and tired of things that are being massively used because we used it before.