Audit design processes and synthesize

[pamela-drouin]

No description provided.

[pamela-drouin]

Here is the link to the list of methods, along with their associated descriptions, process type, point of occurrence, type of activity, type of output, and the purpose.

I am most fuzzy on when each thing occurs, and how we'll I'm describing each activity/output types. Could really use @iamjessklein's input, and I'd appreciate @deathbearbrown and @susanjrobertson taking a look as well. Here's the link: https://docs.google.com/a/bocoup.com/spreadsheets/d/1UNvPqXvFmg1TgKHdVVAPS8gOFaT-iZbL3hVeYzPdXwk/edit?usp=sharing

In the meantime, I am futzing around with what a design process diagram might look like.

[pamela-drouin]

P.S. If you want to see the prettier version in Airtable, here's the view-only link to that! https://airtable.com/shrk06hKx0p8CxxHX

[iamjessklein]

This is a great first stab @pamela-drouin You've made a ton of progress on method identification, description and process labeling. For this database to be useful, it seems like we could build a stronger relationship between the method types. I added the column "method dependencies" for this reason (although I'm not sure that this is the right name). It seems that we should have both dependencies and associated methods (but maybe the association is already happening in the process column).

It might be worthwhile asking someone who works with data collection and analysis to provide feedback - cc/ @iros @tafsiri @vlandham @pbeshai

[iamjessklein]

@pamela-drouin - based on our new milestone thread for Susan Kare, I think that you can close out this issue, but perhaps before you do that - can you recommend a working data model for us when we "tag" activities (methods)? Or will this come directly from the #56 process diagram work?

[pamela-drouin]

@iamjessklein I agree that this issue can be closed, because it was completed during the week of May 16th.

As far as the process diagram work, I planned on revising the initial diagram I made that week, so it's very high level - not so granular that it would address a data model for tagging methods, however the process diagram should inform how we tag methods by phase. I do think it's worth talking about how we want the methods to be accessed and organized ( informing how we're architecting the information).