I really respect the openness in this question. A couple thoughts...
1. Design is routinely short-staffed. So they are left scrambling to “feed the factory” and/or play catch-up with teams just marching forward because they are not instantly available / can work 20hr days (1/6)
1. Design is routinely short-staffed. So they are left scrambling to “feed the factory” and/or play catch-up with teams just marching forward because they are not instantly available / can work 20hr days (1/6)
2. Some large % of design has nothing to do with “Screens” or “Flows”. There’s a research component. PdM and dev routinely forget that in many cases the most skilled researcher / problem-unraveler / simplifier is the designer on their team. Oh.. do that AND MAKE SCREENS. (2/6)
3. For various reasons (most non-personal, systemic) there are some developers who view anything not involving code as non-essential. Some designers see developers as “code typers” executing their brilliant designers. Stereotypes SUCK. Combined, these views hobble teams (3/6)
4. Ironically, part of the baggage is shared by developers and designers...in their own way, being asked to sacrifice quality for speed...often for very wishy-washy, hand wavy product manager reasons. The baggage then is never being able to do an impactful job. Which is sad (4/6)
5. Related, one of the “sells” of working in an #agile way has been learning/responding to learning. This is actually a very design-centric way of working (make something, test, adapt). It is safe to say that MOST teams don’t work this way. Done is Done. A promise broken (5/6)
6. All this said, the best thing you can do is truly invite a #designer into your team, don’t tell them they need to code (but agree to teach them what might help them), form working agreements that respect their craft
start together, work together, finish together (6/6)
start together, work together, finish together (6/6)
