Questions for Designers from Engineers
Regarding: http://twitter.com/rands/status/6123537976:
- Mainly I’d suggest that they ask designers open-ended questions. Closed questions stifle creativity. neontapir
- Qs: 1. What is your communication style (tools, speed…)? 2. How best can I give input & collaborate on UX? jeffreypriebe
- “Can you tell me more about IxD and how it adds value to…?” Some devs aren’t quite sure of what we do and how we can help. katiejohnston
- “The engineer is always [ ] Right. [ ] Wrong.” danielpunkass
- Do you know how to use version control? How do you create HTML/CSS? What’s your favorite Javascript framework? How do you comp? chockenberry
- When did you last redo a design because an engineer pointed out a problem with it? dirkstoop
- ask about recently learned things, if that’s only about visual dsgn, they never worked closely|well w/ engineers dirkstoop
- To be closely followed by the question: how do you approach an engineer whose implementation needs to change? chockenberry
- Q: How do you track & share assets? Bad: email. Better: shared drive with strict naming conventions. Best: source control. dsandler
- Perhaps: “How do you make sure your design is implemented correctly” looking for doubt re: *your* and *correctly* mfloryan
- also how they communicate their design and gather feedback and where they seek input into the initial design mfloryan
- “Have you worked in [XYZ platform/technology] before?” (Important to gauge understanding of platform limitations.) preed
- they need to recognize that both roles are necessary. A good engineer should understand how the design should ‘feel’ when used. jlongtine
- “Explain/justify to me why your website is the way it is”. darkhelmetlive
- how about “do you produce actual markup or are you useless?” zacharydanger
- Creativity test - Name a simple object (e.g. a brick), ask what uses they can think of for it. Test of lateral thinking. daveconcannon
- “What were you thinking?” hakmem