3 ms·
I actually liked the list. I see past the literal meaning of each sentence into situations I've seen managing designers in the past. On deadlines: Sometimes th
by 3pt14159 4y ago
I actually liked the list. I see past the literal meaning of each sentence into situations I've seen managing designers in the past.
On deadlines: Sometimes there is pressure from the top that is completely unrealistic. I think it is ok to ask for a deadline, but I think it's better to propose a timeline as a way of getting to the stakeholder's real deadline in a manner that gets them amenable to reduce scope. It's an exercise in educating the stakeholder about the sheer weight of the ask. Time, money, output. Pick the one you care about the least.
On multiple designs: Of course for this one it depends. A simple button or form on a secondary page does not need several rounds of polish and iteration. Star feature on an upcoming flagship product, though, does.
On explaining decisions: This is mostly about getting buy-in from multiple stakeholders. I may be CTO and love the new design, but there are three other chairs in the room looking at the work and its more efficient if you prime the meeting with the constraints you were dealing with. A strong secondary benefit is that it makes you easier to recommend to others, since a big part of a strong referral is trusting that the referred party can properly portray themselves and their work to others.
On waiting for directions: If you've never managed juniors this may come as a shock, but a large number of juniors will sit and wait until they're told what to do. It is partially explained by cultural background at times, but its present everywhere I've worked. If one thing juniors took away from the article was this, then I would count that as a major win.
I could go on, but my overall point here is that many commenters are looking at this as designers that are focussed on specific skills of the craft, instead of seeing it as a stakeholders point-of-view on junior versus senior designers.
There is one thing I would add to the list that transcends the junior-senior distinction: Nothing beats an honest, enthusiastic designer.
- duxup 4y agoI wonder about this stakeholders pov idea. One thing I've seen at big companies are situations where "junior" folks are tasked with a laundry list of bullet points and that's all that they're given. So then the senior folks are free to do much of what is in that article... because that's their job. It's not a senior person chooses to do these things and jr do not. It's straight up the roles they're given. That's not a situation where someone's skills / enthusiasm / intuition means they do these things, they're just afforded / expected to.