open-design-kit / opendesignkit

Open Design Kit is a living toolkit for designing with distributed collaborators.
http://opendesignkit.org
Creative Commons Attribution 4.0 International
194 stars 79 forks source link

Who is the audience for odk? #260

Closed iamjessklein closed 6 years ago

iamjessklein commented 7 years ago

Now that Open Design Kit is shifting to be a community - owned project, it makes sense to review the audience. Is our audience for the site the same as it was when this was incubated at Bocoup? If not, who is the audience for the Kit? How will this change things for the website?

mjchamplin commented 7 years ago

@iamjessklein is there some documentation clearly defining who the original audience was intended to be? I've told a lot of people about this project, and that's always kind of a stumbling block I guess.

I know the initial focus was on distributed teams, but I think many of the methods work on non-distributed teams as well, and even for individual designers and developers.

iamjessklein commented 7 years ago

@mjchamplin yes, we have a whole wiki page dedicated to personas for the project that I think we should reconsider.

The major shift here is that the project was incubated within Bocoup, so by default the main use case for us was working directly with clients and collaborators. Now that the project is under community ownership we have the opportunity to refine that mission further.

However, all that said, I still believe that the audience are makers who are:

  1. sharing their process openly
  2. collaborating with people who may have different skillsets
  3. looking for remote - friendly methods

I'd love thoughts on that loose definition. cc/ @pamela-drouin @toolness

mjchamplin commented 6 years ago

@iamjessklein I think your list is good and inclusive. Just given my personal situation in the past year, I've found some of the methods especially useful for communicating with developers during the hand-off process.

I also do basically all the design, both UX and UI, on all our native app projects at my current agency, and I've found that checking back in with methods helps keep me thinking more holistically. Whereas I might normally fall into some routines that could show themselves as redundancy across the different projects I work on, I can choose methods that might be more appropriate to a given project. This helps me 1) maintain perspective on my work and 2) include other stakeholders in the design process to varying degrees.

I'm still working on clarifying the language here, but hopefully you can see what I mean. I can see large teams and small teams (and individuals) using the kit in different ways.

iamjessklein commented 6 years ago

Ok, so for the purpose of this issue, I:

👍 or 👎 to close issue?