3 ms·
Better yet: show off your unsolicited design. Just don't be a dick about it. Don't assume the designers of the current version of the thing you're redesigning a
by dictum 13y ago
Better yet: show off your unsolicited design. Just don't be a dick about it. Don't assume the designers of the current version of the thing you're redesigning are incompetent, and don't assume your version is the One True Solution for that product/company. Especially because it probably isn't: when you're making an unsolicited redesign, you don't have many of the constraints a designer has working on a real project.
To be honest, I don't get the harsh, visceral reaction some people have to unsolicited redesigns. I hate the attitude of many people who make such redesigns too, but I'm not impassioned enough to see a redesign presented with some humility as a personal affront.
The justification for many bad designs also rubs me the wrong way. I once read that the worst pedant is the one who uses the complexity of things as an excuse not to challenge the status quo. That a company has many bureaucratic barriers, legacy systems, conflicting research and internal politics is not an excuse for bad design. It's an explanation, but not an excuse.
I agree that designers should focus on creating things that will be actually be used, solving a real problem. This requires business sense, though, even if you're essentially working for free.
Real problems don't give you as much recognition as riding on the bandwagon of some hot company. It's a sad fact, but nobody ever got famous for designing a local deli website.
- darkchasma 13y agoI agree with everything, with the exception of the need to solve a real world problem. Much of the code I write is to explore, and to play. It doesn't solve a business need, it only scratches an itch to see if I can do it. Design should be the same, because when we play, we discover new avenues and ideas that we may never have realized until we tasked our brains to solve some new problem.
- nhangen 13y agoI like your first line, and if I had a single criticism of this practice, it would be the way in which design egoists need to bring others down in order to bring their own designs up.
- oblique63 13y agoIt's not so much about the practice itself as it is just a general presentation problem. It's alright to fork a particular software project if you don't like the way the main branch is going, but good luck promoting it by throwing the original under the bus. Same story when starting new competing projects/frameworks. That slippery slope isn't unique to designers.