11–20 of 54 posts
The article left a bitter taste. It's probably intentionally all black and white, but it does sound almost passive-aggressive to me. I can safely consider myself senior designer (doing UX design for more than 20 years). I always ask about deadlines. I believe not doing so is highly unprofessional. I have other tasks in parallel, clients have other tasks in parallel. Deadlines = priorities. Discussing priorities is cr…
The article left a bitter taste. It's probably intentionally all black and white, but it does sound almost passive-aggressive to me. I can safely consider myself senior designer (doing UX design for more than 20 years). I always ask about deadlines. I believe not doing so is highly unprofessional. I have other tasks in parallel, clients have other tasks in parallel. Deadlines = priorities. Discussing priorities is cr…
Some of these even contradict one another:
> The other knows the answer is "ASAP,” so they propose their own timeline.
> The other does as many drafts and explorations as possible within the time allotted, then shares their favorite options.
Sounds for me like some senior punishing juniors with "do it ASAP! you only did one draft? do more! ASAP!"
Maybe I am imagining things or maybe I met colleagues/clients like that.
The article left a bitter taste. It's probably intentionally all black and white, but it does sound almost passive-aggressive to me. I can safely consider myself senior designer (doing UX design for more than 20 years). I always ask about deadlines. I believe not doing so is highly unprofessional. I have other tasks in parallel, clients have other tasks in parallel. Deadlines = priorities. Discussing priorities is cr…
On deadlines: sometimes there is none. Of course it still needs to be done, but it needs to be done correctly, so you set your own timeline based on sustainability. Things can be high priority and still not have an actual deadline. But sometimes it really needs to be done in a week or a month because it's tied to a big promotional campaign or it needs to be presented to important stakeholders or whatever, and you need to drop everything to whip something up that does the job and tech debt be damned. But if the actual deadline is "yesterday", then it's already too late and doesn't have to be done anymore; that's not a deadline, that's fake urgency.
(I realise the article is about design, not programming, so maybe tech debt is not a concern there, but I'd expect there are other quality aspects that matter.)
These are completely different situations and need to be treated completely differently. Only an idiot would assume there's only one answer to the deadline question.
The article left a bitter taste. It's probably intentionally all black and white, but it does sound almost passive-aggressive to me. I can safely consider myself senior designer (doing UX design for more than 20 years). I always ask about deadlines. I believe not doing so is highly unprofessional. I have other tasks in parallel, clients have other tasks in parallel. Deadlines = priorities. Discussing priorities is cr…
One designs exactly what they’re told.
The other knows what they’re told is just one idea, and explores beyond it.
The article left a bitter taste. It's probably intentionally all black and white, but it does sound almost passive-aggressive to me. I can safely consider myself senior designer (doing UX design for more than 20 years). I always ask about deadlines. I believe not doing so is highly unprofessional. I have other tasks in parallel, clients have other tasks in parallel. Deadlines = priorities. Discussing priorities is cr…
Yeah, many of these are bullshit or only valid in very specific circumstances. On deadlines: sometimes there is none. Of course it still needs to be done, but it needs to be done correctly, so you set your own timeline based on sustainability. Things can be high priority and still not have an actual deadline. But sometimes it really needs to be done in a week or a month because it's tied to a big promotional campaign…
Some customers may be inclined to manage more and set specific deadlines rather than get into the external factors discussion. This spares you from some higher-level planning but doesn’t fundamentally change the ultimate responsibility of managing expectations (aiming to under-promise) regarding work scope and timeframe: fixed scope means variable timeframe, fixed timeframe only means you adjust the scope part of the equation. If expectations are unrealistic and there’s no flexibility in either direction, run.
I don't like how the article uses "young designers" to mean "junior designers", as if time served magically gives you a senior level knowledge.