I was mulling over today’s Human Centered Design breakout meeting and it occurred to me that one possible lens for looking at all the issues we discussed is to think about design data; by that I mean, the data which is required to formulate and execute on a given design. Whether we’re talking about user feedback, feature requirements, budget numbers, or even our own mockups, I realize it can be helpful (at least, for me) to think of it all as different forms of data, which can inform the decision making process. And so like any kind of data, we can ask certain questions about it:
- How do we capture that data and guarantee its completeness?
- How do we organize and structure that data?
- How do we clean, filter and process that data?
- How do we make that data accessible and actionable to the user (ie, ourselves)?
- Or, to get totally meta, how do we design a system for handling this design data in its own right?
I’m not sure if this is helpful to anyone else, and I guess it’s just a re-phrasing of the same idea(s) we’ve already tread upon, but perhaps we could work towards answering some of those questions within the specific context of OpenTEAM, with special attention to how all that can be achieved in coordination with the hub farms (keeping in mind the idea of “survey fatigue” that Kita or Greg mentioned).
Anyways, that’s my 2 cents. Looking forward to picking up the conversation tomorrow!