Re: comments on use-cases

> I'm trying to figure out what our low bar is. That's why it starts  
> with (and you removed in quoting) "At a minimum". If you think  
> that's not our minimum, let us all know what is. But I think it's  
> important to get it stated. What's the least we'll settle for, such  
> that if we don't get it, we'll have to declare failure? I'm setting  
> that bar at _some_ usability testing, with those resources.

Point taken and I agree -- I'm not sure why I originally had a  
problem with estimating a lower bound for the number of participants.


> Turning it around, how about we also state a goal - what we're  
> hoping for and realistically believe we could achieve. Could you  
> (or anyone else) propose a sentence or two on that?

I'm assuming you mean the goal of doing at least lo-fi testing (I'll  
rewrite this if you meant something else).


Tyler: I also re-worded bullets 1 and 2, I'm not sure what was  
intended by the original version of bullet 1 - "Substantially  
different lo-fi testing for each iteration"



Suggested re-write of 10.3:


At a minimum, we will find the resources to do "lo-fi" prototyping  
with a modest number of volunteers (10-20) for each recommendation  
where user feedback appears necessary [Tiny Fingers]. Volunteer  
participants will be found through WG member organizations.  
Prototyping at this level will provide feedback in early design  
phases at a point where needed changes can be made easily. It will  
also create a more user-centered design process and will help in the  
realization of our goals that address usability.

In addition, we will pursue resources that allow us to do more  
extensive usability testing, including:

     * Incremental testing incorporating feedback from previous  
iterations
     * Recruiting participants from broader groups which better  
representative target user groups, either in size or relevant  
characteristics
     * Lab testing of sample code, for example [Johnny 2]
     * Contextual or "in the wild" testing of sample code [Social  
Phishing]
     * More iterative combinations of the above, throughout the  
specification lifecycle