Including the community in design processes

This page attempts to outline tips and advice for people or companies doing design work on major parts of Drupal who wish to know the best way to include the community in that process, with some lessons learned from D7UX.

Communication

  • Often and timely communication: The community values when they are "in-the-loop" and know what is coming and what has been done, and that they have a certain frame of time to give feedback. It's bad when people don't know when and on what you're working.
  • Clear feedback loops: The community and especially top contributors deeply value clear loops on how their feedback was considered. This requires a though balance, not responding on each individual comment but also not "just" responding to all of the comments in aggregate ("spotting the trend").
  • The community is not full time: Concise and considered proposals, findings and responses are truly valued. Avoid very lengthy and bulks of communication - people like more spread out, summarized communication. The UX-Team often spends a lot of time in writing clear and concise proposals, focused on giving full insight in considerations, and asking for specific feedback.
Subscribe with RSS Subscribe to RSS - design process