Comments on: design by committee vs design by community (things we learned from the Drupal.org project)

By: Navigation Designs « Blog for Designers

Navigation Designs « Blog for Designers — Thu, 15 Jul 2010 06:24:09 +0000

[...] Disambiguity Use of rounded corners and a strong color difference to separate the tabs not in use. [...]

By: Experience is Everything » Feb200919 leisa.reichelt 13 design by committee vs design by community (things we learned from the Drupal.org project)

Thu, 12 Mar 2009 00:04:47 +0000

[...] pickups — Leisa Reichelt March 11, 2009 Link var gaJsHost = ((“https:” == document.location.protocol) ? “https://ssl.” [...]

By: Katski

Katski — Tue, 10 Mar 2009 19:16:59 +0000

Bit late on from the original post, apologies, but following the Drupal.org process has been a massive help in my developing career. If there’s any way to learn how to begin to approach a community project without the overhead of that process yourself, this is surely one of the best examples out there – transparent and communicative throughout and it’s moved my (and the agency that I work for!) forward in our thinking. Really appreciate it Leisa and Mark B.

By: Quicklinks (March 2nd - March 3rd) | Arketype

Quicklinks (March 2nd - March 3rd) | Arketype — Wed, 04 Mar 2009 01:23:43 +0000

[...] Design by committee vs design by community (things we learned from the Drupal.org project) – Great insights from Leisa Reichelt from her experience managing a collaborative design project (the drupal.org redesign) [...]

By: Juliette Culver » February Links

Juliette Culver » February Links — Sun, 01 Mar 2009 23:40:57 +0000

[...] design by committee vs design by community (things we learned from the Drupal.org project) [...]

By: penny

penny — Wed, 25 Feb 2009 10:57:18 +0000

thanks very much for sharing this leisa, having watched the process from the out I was wondering how it was feeling on the inside. interestingly the process you describe sounded similar to me to analysing user research generally i.e looking for themes, gems that stick out, and at first feeling a little naughty for not taking it all on or responding to all bits :) – the similarity makes sense too given Larry’s comment above
thanks again
penny

By: Larry Garfield

Larry Garfield — Tue, 24 Feb 2009 05:44:51 +0000

I think part of what made/makes “design by community/crowdsource” so compelling is that it doesn’t separate stakeholders from users. In traditional design you have the designer, a small number of expert stakeholders, maybe a focus group or two to represent users, and then a big amorphous blob of users you don’t talk to directly.

With a community/crowdsourced approach, the stakeholders, focus group, and users all collapse into one group. That removes layers of indirection and gives the designer direct access to the full user base, or at least the vocal parts of it. :-)

By: RodeWorks » Blog Archive » Crowdsource your next application design

RodeWorks » Blog Archive » Crowdsource your next application design — Mon, 23 Feb 2009 21:52:40 +0000

[...] this is to invite feedback from a lot of people, and use technology to aggregate the results. In this post Leisa Reichelt explains that in that design by community (NOT committee!) helps identify 1) emergent trends, 2) [...]

By: Vaguely Related « Salt Talker

Vaguely Related « Salt Talker — Fri, 20 Feb 2009 21:07:26 +0000

[...] Vaguely Related Since we are talking about community and design here’s a related post from the Disambiguaty Blog. [...]

By: » OLDaily per Stephen Downes, 19 de febrer de 2009 TIC, E/A, REF / PER…:

Fri, 20 Feb 2009 02:02:04 +0000

[...] de membres individuals del comitè als quals no pots ignorar. Leisa Reichelt, Disambiguity.[L'enllaç] [etiquetes: sistemes de gestió de Continguts, [...]