31–40 of 76 posts
Earlier quoted context omitted.
I don't understand why designers have started with those huge fonts. Seriously not everyone visits your site from some mobile device ffs!
The fact that you don't like how it looks means only that you don't like how it looks. I'm sure most of the people don't mind or like it (me included).
The color hurts my eyes. The heading font sizes look out of place. I think this site needs some design principles.
I think I will stick with the 10 principles of Dieter Rams: Good design is innovative Good design makes a product useful Good design is aesthetic Good design makes a product understandable Good design is unobtrusive Good design is honest Good design is long-lasting Good design is thorough down to the last detail Good design is environmentally-friendly Good design is as little design as possible
I agree with the last 9, but I have my quarrels with the first one. It just begs for people to make innovative designs even though the original one worked perfectly. Like a microwave oven with dozens of buttons even though the one with two dials (power, time) and the door-opener button works 99% of the time.
So I think you can see all ten rules as a complete set.
Genuine question: Is there an applicable takeaway from principles this vague? "Tolerant: Handle errors respectfully. Effortless: Don’t make demands or place restrictions on your users. Accommodating: Be approachable, uncluttered and give people room to manoeuvre. Consistent: Follow standards, guidelines, conventions and best practices."
The color hurts my eyes. The heading font sizes look out of place. I think this site needs some design principles.
It depends. I viewed this on a regular computer monitor and didn't find it unpleasant. I acknowledge that black-on-bright-yellow is a matter of taste, but it was nowhere near eye-hurting.
Earlier quoted context omitted.
This is a great point. "Principles" should be about taking a stand about the trade-offs between two desirable things. They can then be used to help guide you when these things come into conflict. Who is trying to make a product that is intolerant, burdensome, aloof, and inconsistent? A framework I usually use is a "this over that", where both "this" and "that" represent things generally considered "good". The Agile M…
I've seen #1 used many times to solve the problem of "too many regressions" with "the team just needs to communicate more" or "we should set up regular meetings to deal with this issue". It was hard to argue that those teams weren't following both the message and spirit of the agile manifesto, as individuals and interactions were plainly taking precedence over tools and processes. It doesn't, after all, say "individu…
That said, the problem you described isn't really with the manifesto, but with people refusing to use common sense - or even more likely, with incentives within the organization being so aligned that decisionmakers benefit from making bad calls. It's something that happens surprisingly often.
Earlier quoted context omitted.
I agree with the last 9, but I have my quarrels with the first one. It just begs for people to make innovative designs even though the original one worked perfectly. Like a microwave oven with dozens of buttons even though the one with two dials (power, time) and the door-opener button works 99% of the time.
But a microwave oven with dozens of buttons don't follow the other rules. So I think you can see all ten rules as a complete set.
Earlier quoted context omitted.
But a microwave oven with dozens of buttons don't follow the other rules. So I think you can see all ten rules as a complete set.
Yeah, but then I don't really see what purpose the first rule serves. I'd maybe put it last and rephrase it to something like "Good design is innovative when necessary".
I've used Asana on and off since it started. Because I'm an occasional user, it feels as if every time I come back to it, something seems to have changed and I lose all reference to where my tasks are.
Right now, whenever I go there every few months, I have to remember that my client's tasks are buried in a dropdown in the top right.
Worst part is, it doesn't look like a dropdown, it doesn't look like a menu, it doesn't look like a link. It's just black text saying "Overview" next to my picture.
Also, for some reason the default task list I land on is completely empty. I have no idea why. At one point I was using it for quite a lot of stuff and there are a load of unfinished tasks in it when I start clicking in categories in the right. But there is no indication anywhere on the screen of what lists might actually contain something.
It's a bloody awful design.
Their design principle no. 6:
Be consistent and standard, and innovate when it’s worth it.
So you can have design standards all you want, but when your designers think "consistent and standard" means something completely different than your users, it turns out they're not really meaningful.