We noted that 3 people on the call were voting members and that the group did not meet quorum on this call.
Example of patterns in our work: Personal RFP:
A) making this info available for response, no further use, reference to FAQ.
B) May also use this info to analyze effectiveness of your marketing and sales campaigns--as it's related to purpose (in this case the personal RFP). (Not same as product improvement.) Example: google being a better google: storing the data for another occasion.
The difference is that one allows a particular activity, AND it's impact/permission to use in future transactions.
Joe would like to see 6-12 patterns.
Some concerns that need to be included in discussion: Negative patterns, like Capture for hidden use. Inappropriate use that causes harm. Alcove as a pattern: balances need for public and private spaces, social dynamics: enter the room and don't interact with others in the room, it's a snub. Alcove allows private yet connected space. Christopher Alexander and conflicts: negative situations have more dynamics than positive lists. Observed patterns, abstractions that you can use to generate solutions.
1) Capture for hidden use
2) Over-capture for proposed use
3) Capture for unknown future use
4) Capture driven by regulation
5) Capture because it is easier than not capturing
6) Holding longer than needs be
7) Holding in formats that could be bettered
8) Making accessible too broadly
9) Making accessible without masking
10) Gathering without governance
11) Gathering without maintenance plan
Iain noted that when the lawyers refer to FAQs, they're expecting a small level of detail of the actual contract. They're referring to a binding agreement.
From our conversation with Scott: two different perspectives in law (and regulation) correspond to data on the move and data at rest. Different question about how they (who?) are allowed to reach you. Iain's 11 stages are a lens through which we can find those patterns. Some patterns might appear in multiple stages, may be generalized into one pattern that's re-used. This is an aspiration. We're not there yet. (Analytical CRM (plans, strategies, a 3-5 yr plan) and Operational CRM (marketing, selling, service, maybe billing, a 3-5 minute plan))
FAQ: Purpose, duration, responsibilities and liabilities (from our working draft of Car Buying Engagement Model). From Work Group Report: data scope (aligned with current appendix in Iain's doc), data use (real-time service provision, like a keyword for search results), communications (can put it on web page for me--once). The latter pattern is same as ISharedWhat.com. It's understood that the web page may pre-fill form data that has different rights associated with it.
Compare Sally scenario with Google Alerts: search terms & source, send me an email (instant, daily, weekly) or add to my feed. Scope: keywords, typed in to box (as I type), to return search results on a web page.
We don't include data access, should be in scope: what data (file, photos, etc), how (facebook connect, via email or upload), and when (now, later/subscription). Look for Joe's email to group on the triumvirate.
Sunday 1 May 2011
9:00am - 5pm PDT
in San Francisco, CA
(email Judi or Joe if you need details)
TUESDAY 10 May 2011 - 90 minutes
9am Hawaii, noon Pacific Daylight, 3pm EDT, 8pm UK Daylight
US Dial-In: +1-201-793-9022
UK Dial-In: +44 (0) 8454018081
Room Code: 2954214
NOTE: Do not follow the code with a "#" symbol as it may cause the code not to be recognized.